@icedquinn@mewmew@shebang Ogg is an extremely rare format outside of FOSS circles, so it’s not exactly a big loss. You could always send me an ALAC file. That’s an Apple lossless format and is under the Apache license.
@thor@mewmew@shebang its really weird how prevalent xiph formats actually are but for some stupid reason apple/microsoft don't want to support it by default in their music players. i'm sure it has nothing to do with them both sitting on the patent pool for mpeg-4.
meanwhile half the internet audio traffic is running on xiph s e c r e t l y.
@thor@mewmew@shebang firefox and chrome will play vorbises iirc. chrome i believe will play opus (because webm uses it, which google uses) i forget if firefox will. it's literally microsoft and apple sitting there with their butt cheeks held high like NO YOU CANT HAVE IT
@icedquinn@mewmew@shebang Firefox because it has a horse on the FOSS side of the race. Google for the reason you mentioned, I guess. I mean, there isn’t an awful lot of reasons for supporting it. Browsers support relatively few formats in general.
@icedquinn@mewmew@shebang Not saying it’s a good thing. I mean, I always felt Vorbis degraded more gracefully than the other formats due to its use of noise to hide quantisation errors. Don’t know if they brought that over to Opus though
@thor@icedquinn@mewmew@shebang Pretty sure there are third party players for Vorbis and Opus on iOS, I know for a fact there are libraries to do it because YouTube has a lot of their content exclusively in Opus and a lot of games (especially slightly older ones) tend to use either of Vorbis or WAV to store their background music
@thor@mewmew@shebang there was a whole knife fight at the W3C about this. they wanted audio and video tags in html5 to replace flash stuff with. but when it came time to ask what codecs should be supported, they debated the free ones should be baseline because they are both battle tested and don't put the net in a position of rewarding monopolists.
at first pocket players tried to support vorbis but were threatened by fraunhaufer who was butthurt that MP3 patents would be circumvented. android did support it later, i think other pocket players do now as well.
apple and microsoft screeched purely on self interest. they both receive money from M4A patents and so naturally, that's what they wanted the baseline to be. it was absolutely unworkable in their minds that multi billion dollar monopolists couldn't possibly support a player that was already written for them
W3C, being professional spineless cuckolds, gave up and went oh well you guys will figure out what to do we guess.
AV1 has some heavyweights behind it too (Google, Netflix) who really, really want out of the MPEG patent monopolies.
Bandcamp also gives you whatever format you want, mpeg or xiph, so.
the public doesn't care as long as they can just double click or push play in a browser, but the two OS pushers have a personal interest in denying free software. conveniently, they are also the ones who decide if double click works.
i was genuinely amazed to see xiph support in akai though. i guess pro audio gear is getting sick of everyone's shit too.
@icedquinn@mewmew@shebang@amolith Just tested low bitrate Opus. Seems to degrade similarly to other modern audio codecs. Not as underwatery as MP3 but still kinda the same sound... now to see if I remembered right about Vorbis and how it degrades...
@icedquinn@mewmew@shebang@amolith Hmm, how odd, it actually degrades more like an MP3, but I swear to god it didn't do that. Did they change the encoder/format during the course of its lifetime? I remember it sounding more... "distorted", "FM radio with bad reception" as it degraded, not like this...
@cy@mewmew@icedquinn@shebang I mean, when there is a download link or torrent with audio, it's extremely rare that the files are OGG. I mean, most media production tools on Mac, which is a very popular platform for such things, don't support any of the Xiph formats.
@cy@mewmew@icedquinn@shebang I always run into obstacles of lacking support when I try to use these open formats in my editing workflow because hardly any serious media production software supports them.
@amolith@icedquinn Granted, when I last tried Ogg, it wasn't long after it had first launched, so I expect things changed over time... but by this much? I think the encoder I used was a command line tool from Xiph itself.
@thor Well "optimal" is different for every use-case. If you want quality, files will be larger. If you want smaller files, quality will be lower. I don't remember what exactly the defaults are but it would be better to explicitly define each one so it's a more accurate test @icedquinn
@thor@amolith i usually use the xiph encoder or whatever fl studio uses. ffmpeg only has good defaults for mpeg because of mpeg nerds, the non-mpeg stuff has stupid defaults most of the time (ex. if you try to make a vp8/9, you will be very sad, because it doesn't even default to a useful bit rate.)
@amolith@icedquinn I did say "optimal for the bitrate", and also, the thing should adapt. If I run it from the command line, it has time to spend a little time to do extra optimisation, whereas for streaming, then the tool that runs the library/ffmpeg should set specific flags like "ultrafast".
@thor To an extent, I do agree with "command line is ultimate" because, when you know what you want to do, there's nothing better than Ctrl+R, , replace file names, done. Whereas with GUIs, you have to wait for the application to open, click around to find the files, click a thousand buttons, adjust a million sliders, and enter a billion numbers THEN you have what you want. @icedquinn
@thor That's an exaggeration of course but you get my point. When you already know what you want, command line tools are way more efficient than any GUI but they require a lot of time to learn and are far from intuitive. I personally prefer spending hours readings docs to hours clicking buttons though. @icedquinn
@amolith@icedquinn I prefer the exact opposite. Did not always, but as I got closer to my 30s, I want to think less. I often neglect to automate stuff because it's much less mental effort to just click shit.
@amolith@icedquinn I look for shrink wrap solutions where I can, and if a piece of software forces me to think as opposed to letting me get on with what I need to do, it gets replaced with something else. I mean, my actual interest in computers as a thing to play with is rather light these days. If I didn't know how to code today, I probably wouldn't have bothered with it.
@thor I like to automate things that take a significant amount of time. If there's an edit I need to make to every single image in a directory, there's no way I'm opening each one in GIMP or Inkscape. I'll use some esoteric ImageMagick one-liner to do it for me.
In general, I do prefer graphical applications for graphical work though. I'm on the fence about audio but I don't have a ton of experience with it yet. @icedquinn
haiku has advanced a bit since then, but they still host the old api manual. this is the one my api clone is based on.
one difference is since nim supports closures but not C++-ish inheritance, and since be basically only uses inheritance because C++ doesn't have closures, i just went ahead and replaced hooks with closures. otherwise its 1:1 identical.
@thor@mewmew@icedquinn@shebang Y’know, maybe I can count the amount of times I’ve seen OGG files for download on one hand, but I can count the number of times I’ve seen ALAC on zero hands. What did they do, take the FLAC format and stick the word “Apple” in the middle of it so that your files would be broken outside their vendor lockin?
sometimes apple's weird formats are there because they were started before other good options existed or so they could get something that works without having other companies bikeshed. i recall some of the ProRes formats are exactly this; they were designed so ex. the old ibooks could still play then hi-def formats that cinema people used but weren't otherwise widely there.
HISE has its own lossless codec (called HLC or something) too which is just some simple four-sample linear coding or something.
sometimes these formats are just based around whatevers efficient with what the company has at the time.
@thor@icedquinn@amolith I think the issue is creating GUI interfaces take a heck of a lot of effort and a command line isn’t really all that hard to figure out. The labor saved using a GUI is often outweighed by the labor lost in creating it. Apple just hides that cost, and makes up for the loss with behavior modification, and slavery. But that’s just a guess. I don’t know how they come up with fancy GUIs that people fall over themselves for.
@cy@amolith@thor linux just tends to have crap UX in general. even when you use just some CLI app, you have the nightmare labrynth that is ffmpeg or things like git where it's a bunch of independently cobbled scrips with inconsistent commands.
i mean, httpie's whole marketing is "we're curl but the cli arguments don't require man pages to understand." and you can prod commercial mercurial teams and they'll tell you that onboarding non-nerds is far easier.
@icedquinn@mewmew@shebang@thor It’s been a long time since there weren’t any standards for audio files… FLAC is 5 years older than ALAC. I’m calling shenanigans, until I see some reason that iTunes couldn’t support FLAC instead. And it’s really not a huge deal. I’m mostly just surprised I never heard of ALAC before.
@cy@mewmew@shebang@thor i would have to do a lot deeper peeking. I know HISE doesn't use flac because it's an archival format and not that suitable for sampler streaming. MPC ONE can read flac too, but only when loading to RAM.
Before, there was control panel. Now, it is split into 3 or 4 different settings app and you really have to guess which option is arbitrarily only accessible via a particular one of them. Sometimes, you can use either of two out of three of such programs. It is really messy. Really fucking messy.