Hello, I believe the main problem with VBR encoding was that it sometimes mis-assesses some information, and takes a too low bitrate resulting in artifacts? I was just thinking. (always at wrong times) With the help of a (very quick) test like http://users.belgacom.net/gc247244/extra/320S-V1-JS-vbr_mt.png the worse faults would be easily identifiable? Why not encode, for example, a 2 hour music piece in * 320, Stereo * V1 - JS (or alike) then decode both back to wav, and inverted mix paste both. Now only rests to evaluate the highest peaks (aberations from good encoding), and try to minimise them by tweaking the VBR engine. [the hard part that is] It wouldn't help for all (eg "C1"), but I think it could be a very handy aid in finding the worse errors? -- Best regards, Roel mailto:[EMAIL PROTECTED] -- MP3 ENCODER mailing list ( http://geek.rcc.se/mp3encoder/ )
