This is really nice! I also feel that the same way about how music, and especially the concept of an album, has lost its value in times of streaming due to giving up ownership, having access to everything, over-using playlists, and the absence of the visual art (i.e. packaging/booklet/liner notes) that used to accompany albums (and also compilations/EPs/single releases) when they were still physical entities.
A few years ago I made Zipped Album [1] as an attempt to solve this purely in the software domain by slightly changing the way we store and consume digitally owned (i.e. bought and downloaded vs. streamed) music. It contains a proposal for a simple single-file music album format that incorporates visual art [2], and an example cross-platform player for it that (hopefully) demonstrates how this can promote a more (inter)active/conscious listening experience [3].
Looks interesting, but I don't really understand how it works. I open the website, type a message, then I see my own message. I scan the QR code with my phone, then I also see a message window on my phone where I can type messages. Now both my laptop and phone can type messages, but the phone only sees the phone ones and the laptop only sees the laptop ones. Yet, somehow they are in the same session (since the phone scanned the QR code from the laptop). What am I doing wrong here? How do I send a message from one device to the other after connecting them in the same session?
Works in FF for me. It's rather resource hungry, maybe an OOM? Judging from RAM consumption I'm guessing it doesn't utilise GPU, but maybe it does and didn't fit in mine.
Same for me. I get the following messages in the console:
Loading failed for the <script> with source “https://streets.gl/js/index.js”. streets.gl:1:940
A resource is blocked by OpaqueResponseBlocking, please check browser console for details. script.js
Loading failed for the <script> with source “https://analytics.streets.gl/js/script.js”. streets.gl:1:815
What exactly does this do? They have examples with a divider in the middle that you can move around and one side says "input" and the other "output". However, no matter where I move the slider, both sides look identical to me. What should I be focusing on exactly to see a difference?
Yes, I was also surprised that the new features are only for phones. I guess aiming to be "better" than other chat apps (with the others nowadays being Whatsapp and co) means to be "mobile first"... sigh
I am a bit confused. This seems to be about the command line programme "ffmpeg" that comes with the library, but not the library itself. That programme seems already very well documented, with a help option, a man page and everything. It is usually the library that no one knows how to properly use, due to a lack of documentation :-)
I suspect because they don't leverage the main advantage of a GUI toolkit: provide a coherent, familiar and proven user interface. These examples all look like websites and all have completely different styles. I can see how this fits into the current just-ship-a-webapp-plus-browser trend though.
In principle, you could indeed - even with the current FLAC container - have a single FLAC file in combination with a cue sheet. But I wanted more than this:
1. Something that is based on what people do already (e.g when you download an album from Bandcamp, you get a Zip)
2. Proper booklet support
3. Support for lossy albums (Opus)
4. An easy way to get to the individual tracks (most OS can open Zip files without additional software)
So in the end, having everything zipped up seemed the most straight-forward approach.
Concerning album-level metadata, all information is currently only inside the Zip file. In theory metadata could be attached to the Zip (I think you can add comments at the beginning of a Zip file without breaking the format). Could you elaborate what would be the added benefit of additional metadata?
The problem is that those in charge disagree with that. When I brought this up after a recent policy change at my department to not allow hiring own PhDs as postdocs (because they should go to another lab, as this is what your CV is expected to look like), I was told that a Phd programme should not be seen as a path towards an academic research career. In contrast, I was told that it is very important to train as many PhD students as possible, that all don't stay in academia, so they can bring scientific thinking to all areas of society. Unfortunately, starting PhD students, of which 99% do this explicitly to do research, are not aware of this, and neither do PhD programmes offer any specific training for a non-academic career.
One solution would be to push more people towards MS degrees, which should be no more than 2-3 years in duration and focused on gaining skills and experience valuable in the private sector.
A few years ago I made Zipped Album [1] as an attempt to solve this purely in the software domain by slightly changing the way we store and consume digitally owned (i.e. bought and downloaded vs. streamed) music. It contains a proposal for a simple single-file music album format that incorporates visual art [2], and an example cross-platform player for it that (hopefully) demonstrates how this can promote a more (inter)active/conscious listening experience [3].
[1] https://zipped-album.github.io/ [2] https://github.com/zipped-album/zlbm [3] https://github.com/zipped-album/zap