News for hackers. Stuff that matters.

A comment on QOI – The “Quite OK Image Format” for fast, lossless image compression. Parent comment

Re:QOI – The “Quite OK Image Format” for fast, lossless imag... by zigzag312 on Thursday December 23, 2021 @03:43PM (#29666236)
WavPack seems a bit too slow already. 3x slower decode compared to FLAC in this test https://stsaz.github.io/fmedia/audio-formats/
[ Parent | on HN ]
Re:QOI – The “Quite OK Image Format” for fast, lossless imag... by TylerE on Thursday December 23, 2021 @09:54PM (#29669517)
Wavpack on a modern CPU, from your own link, decodes at approx. 250x realtime. How fast is 'fast enough' if that isn't?
[ Parent | on HN ]
Re:QOI – The “Quite OK Image Format” for fast, lossless imag... by zigzag312 on Friday December 24, 2021 @02:40AM (#29671307)
Projects with 100+ tracks are not uncommon. Sampler/rompler of a single virtual instrument can play 10+ sounds simultaneously. Playback of an orchestral score with virtual instruments can easily go over 250 simultaneous sounds, so just a real-time playback (without any additional processing) would already be a challenge.
[ Parent | on HN ]
Re:QOI – The “Quite OK Image Format” for fast, lossless imag... by TylerE on Friday December 24, 2021 @04:23AM (#29671944)
In those contexts samples are loaded once and then kept in RAM.
[ Parent | on HN ]
Re:QOI – The “Quite OK Image Format” for fast, lossless imag... by zigzag312 on Friday December 24, 2021 @05:12AM (#29672290)
No, actually only first few dozen KB of each sample are usually preloaded into RAM. The rest is streamed from a SSD. One library of an orchestral section can have 100+ GB of samples. You wouldn't fit all sections in 128GB of RAM.
[ Parent | on HN ]
Re:QOI – The “Quite OK Image Format” for fast, lossless imag... by TylerE on Friday December 24, 2021 @05:16AM (#29672309)
I'm quite aware of the size of large libraries, I own a number of them.

Part of why I built my current machine with 64GB of ram

[ Parent | on HN ]