4 ms·

WavPack seems a bit too slow already. 3x slower decode compared to FLAC in this test https://stsaz.github.io/fmedia/audio-formats/ https://stsaz.github.io/fmedi

WavPack seems a bit too slow already. 3x slower decode compared to FLAC in this test https://stsaz.github.io/fmedia/audio-formats/ https://stsaz.github.io/fmedia/audio-formats/

TylerE 5y ago
Wavpack on a modern CPU, from your own link, decodes at approx. 250x realtime. How fast is 'fast enough' if that isn't?
- zigzag312 5y ago
  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.
  - TylerE 5y ago
    In those contexts samples are loaded once and then kept in RAM.
    - zigzag312 5y ago
      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.
      - TylerE 5y ago
        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