Live data from Hacker News

The Quite OK Audio Format for Fast, Lossy Compression

qoaformat.org

21–30 of 65 posts

Re: The Quite OK Audio Format for Fast, Lossy Compression

#21
post #19

Earlier quoted context omitted.

It's probably something we ( https://overte.org/ ) can use. We have a 3D environment with spatial audio. Audio is encoded server-side, and since it's spatial everyone needs their own mix. We're using Opus, and audio encoding turns out to be the usual limiting factor on small servers. So this kind of thing is exactly up our alley: an alternate option that uses less CPU than Opus, but consumes less bandwidth than raw a…

Doesnt Opus (speex?) have some low CPU settings?

It does, and I've tried tweaking that, but the performance difference isn't very significant.

I appear to be able to get maybe 30% better performance -- pretty nice, but not nearly big enough especially on low end servers.

Re: The Quite OK Audio Format for Fast, Lossy Compression

#24

I looked around, but didn't see any mention of potential patent issues. I assume that this has been considered? The Ogg Vorbis people spent a lot of time on that back when they were developing their format. Other than that, looks great!

The website says it’s made in Hesse. No software patents to care about there. https://en.m.wikipedia.org/wiki/Software_patents_under_the_E...

Probably the most infamous audio format patent ever was owned by a German research institute.

Re: The Quite OK Audio Format for Fast, Lossy Compression

#25
post #4
post #3

Earlier quoted context omitted.

> QOA is slower than ADPCM, doesn't compress as much as MP3 and sounds worse than FLAC (duh). But I believe it fills a gap that was worth filling.

MP3 compression is very fast on modern hardware. This may have a niche for low power devices, especially if they are battery constrained.

"very fast" could mean many different things that vary by orders of magnitude

Re: The Quite OK Audio Format for Fast, Lossy Compression

#26
has anyone benchmarked qoa to see roughly how many instructions per sample it needs? all i see here is that it's more than adpcm and less than mp3, but those differ by orders of magnitude

like, can you reasonably qoa-compress real-time 16ksps audio on a 16 megahertz atmega328?

hmm, https://phoboslab.org/log/2023/04/qoa-specification has some benchmark results, let's see... seems like he encoded 9807 seconds of 44.1ksps stereo in 25.8 seconds and decoded it in 3.00 seconds on an i7-6700k running singlethreaded. what does that imply for other machines?

it seems to be integer code (because reproducibility between the predictor in encoding and decoding is important, and a significant part of it is 16-bit. https://ark.intel.com/content/www/xl/es/ark/products/88195/i... says it's a 4.2 gigahertz skylake. agner says skylake can do 4–6 ipc (well, μops/cycle) https://www.agner.org/optimize/blog/read.php?i=628, coincidentally testing on an i7-6700k himself, but let's assume it's 3 ipc, because it's usually hard to reach even that level of ilp in useful code

so that's about 380 μops per sample if i'm doing my math right; that might be on the order of 400 32-bit integer instructions per sample on an in-order processor. if (handwaving wildly now!) that's 600 8-bit instructions, the atmega328 should be able to encode somewhere in the range of 16–32 kilosamples per second

so, quite plausibly

for decoding the same math gives 43 μops per sample rather than 380

i'm very interested to hear anyone else's benchmarks or calculations

Re: The Quite OK Audio Format for Fast, Lossy Compression

#27

Earlier quoted context omitted.

The website says it’s made in Hesse. No software patents to care about there. https://en.m.wikipedia.org/wiki/Software_patents_under_the_E...

Maybe not, but that doesn't help people who aren't using it in the EU.

True, it hasn’t stopped hobbyists from using x264, ffmpeg or VLC in the past but that would probably prevent companies in some markets to use this audio format.

Re: The Quite OK Audio Format for Fast, Lossy Compression

#28

Earlier quoted context omitted.

The website says it’s made in Hesse. No software patents to care about there. https://en.m.wikipedia.org/wiki/Software_patents_under_the_E...

Probably the most infamous audio format patent ever was owned by a German research institute.

I guess you mean this one: https://patents.google.com/patent/US5812672

That was an USA patent from Fraunhofer, who made quite some cash from mp3 license fees (100 000 000€ according to Wikipedia).

Re: The Quite OK Audio Format for Fast, Lossy Compression

#29
post #5

What is the LFE channel? It should be spelled out explicitly, but I figured out the rest L-Left,R-Right,C-Center,FL-Front Left,FR-FrontRight,SL-SideLeft,SR-SideRight,BL-BackLeft,BR-BackRight --- Edit: LFE-LowFrequencyEffects... so subwoofer? https://www.dolby.com/uploadedFiles/Assets/US/Doc/Profession...

LFE is an industry standard term for the subwoofer channel. It's the ".1" in "5.1","6.1","7.1" etc
Post reply on HN