Wavpack lossy
Reply #15 – 2006-09-20 22:32:13
Pre-echo is specific to transform encoders; Wavpack lossy, ADPCM, DualStream are not affected by this problem. It's very hard to tell which encoder family perform the best at very/ultra-high bitrate (> 300 kbps). Both have specific (and maybe opposite) issues: smearing for transform encoders; noise for the second type of encoders. WavPack/DualStream are handling without problems all samples on which AAC, aoTuV, MPC... are failing, and the latters are sometimes more transparent at 120 kbps on samples ABXable with Wv/DS at 350 kbps. The result of any test will therefore entirely depend on the inclusion or exclusion of very rare problem cases. 10 "preecho-like" samples vs 0 "noisy" samples will show WavPack/DualStream as absolute winner; 2 "preecho" vs 8 "noisy" samples will prove that transform encoders are really better; and a "5 vs 5" fight will end on... no conclusion at all. On one side I personaly had less troubles to collect ABXable samples for WavPack/DualStream at > 300 kbps (below, there's no debate in my opinion: transform coders are much cleaner): all consists on a subtle addition of noise. On the other side, artefacts with the other kind of encoders are sometimes more weird: I remember Serge Smirnoff iTunes AAC@320 kbps issue (minor, but as audible as unexpected), some strange noise packet suddenly appearing and brutally disapearing with Vorbis (creaking or Bloch ), and also audible ringing with MPC -q10...