lossyWAV Development
... but I like the fact that quality is much more stable than that of say mp3. I didn't find any serious problems on particular "problem samples". And this noise that is introduced is much less annoying than mp3 artifacts. ... Though I'm striving for transparency your description made me curious about the behavior of -q 0. First I encoded my regular track set which I use for getting an idea of the average bitrate I have to expect when using a particular setting. The result was 263 kbps which is very low compared to what we had before with the lowest settings. The more was I surprised that I was pleased when listening to the encoded tracks. Quality is very good to me! This made me dare to use my problem samples with it. More surprise: abxing isn't very hard of course with most of the problems, but: with the exception of eig and furious the deviations from the original are not obvious at all and not at all annoying. Going -q 1 BTW (average bitrate: 281 kbps with my regular track set) made even furious not annoying to me and eig acceptable. I didn't care much about the very low quality settings before, but, Nick, with your recent changes with the encoder I think you've succeeded in giving lossyWAV an extremely broad useful quality/bitrate range! Thanks a lot. I think that the -snr parameter has a lot to do with some of these problem samples. I would propose something like quality_signal_to_noise_ratios : array[0..Quality_Presets] of Double = (18,18.87,19.81,20.8,21.86,23,24.21,25.51,26.91,28.4,30); instead of quality_signal_to_noise_ratios : array[0..Quality_Presets] of Double = (16,17,18,19,20,21,22.8,24.6,26.4,28.2,30);