I just use separate files, honestly. Hybrid could save me a small amount of disk space, which is itself quite cheap. Allows me to have a central repository for files of every bitrate for each device class. Smartphone gets the 128k, I stream the 96k, 128k, or FLAC (depending on connection and browser constraints) from my private listening webapp, and I keep the 128k Opus on my laptop.
FLAC and Opus are each more widely supported than Wavpack, Chrome can play both as of the last stable release. My loudness scanner, cmus, MPD, and others all recognize each fine, including ReplayGain and album art, but I'm not sure I'd have the same experience with Wavpack.
I have about 600GiB FLAC music from bandcamp, random publishers, and CDs. I then have, separately, the same directory structure but encoded as 96k and 128k Opus. Still all fits just fine on a mere TiB disk. In a couple years the difference between 96k and 128 in terms of space won't matter and I'll drop 96.
And yeah, it's very nice to have the FLACs when I want to timewarp, transcribe, analyze, or remix. I usually do that at home though, so I can splurge on the bandwidth.
WRT the Internet Archive, Wavpack hybrid decoding is probably too slow and too rare to bother including in any major browser. Even if they did, if lossy listening is a priority, a dedicated lossy codec will save them money in short order on bandwidth. Indeed, this is exactly how IA does things, they even have wav in addition to flac and two or three lossy versions of (almost?) every recording.
Not a user of Wavpack myself, but I think the idea would be to have a sort of "pressure-based fidelity retention" setup: where you'd put the lossy-encoded versions of files onto your portable player device, but as long as your portable device has the space, it would also retain the lossless encodings as supplemental files. As soon as your portable starts running out of space, it treats the lossless encodings as a cache folder, evicting things from it to free up space.
Then, you could actually do mixing in apps like DJay straight on your iPad, on a whim, sometimes—without having planned for it in advance—and make it straight through to mastering and uploading the result... unless you filled up your whole iPad with random videos/apps/etc. in the meantime, in which case the lossless versions would be gone, you'd have to work with the lossy copies, and then, when you get home, restore the lossless copies (or transfer the project to your PC) to master the encoding.
So, not so much when you want the lossless version as canonical (most times when you have a lot of space), but rather when you want the lossy version to be canonical, and the lossless version to be there as a sort of "optional file to enable mastering using this track" file, that's sometimes available and sometimes not.
Comments
I just use separate files, honestly. Hybrid could save me a small amount of disk space, which is itself quite cheap. Allows me to have a central repository for files of every bitrate for each device class. Smartphone gets the 128k, I stream the 96k, 128k, or FLAC (depending on connection and browser constraints) from my private listening webapp, and I keep the 128k Opus on my laptop. FLAC and Opus are each more widely supported than Wavpack, Chrome can play both as of the last stable release. My loudness scanner, cmus, MPD, and others all recognize each fine, including ReplayGain and album art, but I'm not sure I'd have the same experience with Wavpack.
I have about 600GiB FLAC music from bandcamp, random publishers, and CDs. I then have, separately, the same directory structure but encoded as 96k and 128k Opus. Still all fits just fine on a mere TiB disk. In a couple years the difference between 96k and 128 in terms of space won't matter and I'll drop 96.
And yeah, it's very nice to have the FLACs when I want to timewarp, transcribe, analyze, or remix. I usually do that at home though, so I can splurge on the bandwidth.
WRT the Internet Archive, Wavpack hybrid decoding is probably too slow and too rare to bother including in any major browser. Even if they did, if lossy listening is a priority, a dedicated lossy codec will save them money in short order on bandwidth. Indeed, this is exactly how IA does things, they even have wav in addition to flac and two or three lossy versions of (almost?) every recording.
Not a user of Wavpack myself, but I think the idea would be to have a sort of "pressure-based fidelity retention" setup: where you'd put the lossy-encoded versions of files onto your portable player device, but as long as your portable device has the space, it would also retain the lossless encodings as supplemental files. As soon as your portable starts running out of space, it treats the lossless encodings as a cache folder, evicting things from it to free up space.
Then, you could actually do mixing in apps like DJay straight on your iPad, on a whim, sometimes—without having planned for it in advance—and make it straight through to mastering and uploading the result... unless you filled up your whole iPad with random videos/apps/etc. in the meantime, in which case the lossless versions would be gone, you'd have to work with the lossy copies, and then, when you get home, restore the lossless copies (or transfer the project to your PC) to master the encoding.
So, not so much when you want the lossless version as canonical (most times when you have a lot of space), but rather when you want the lossy version to be canonical, and the lossless version to be there as a sort of "optional file to enable mastering using this track" file, that's sometimes available and sometimes not.