That's a controversial move IMO. The advantage of true VBR is that more
complex recordings use higher bitrates and less complex have low
bitrates and filesizes with roughly the same amount of distortion. With
Marks ABR the operator chooses the bitrate, so complex recordings have
high distortion, and less complex recordings are wasting disk space.
I presume with the availability of vbrtest that some more work will be
done on GPSYCHO to correct the problems?
What might work at this stage is a mixture of both. There would be some
opposition because it would take a lot longer and require 2 passes
through the source file so couldn't be used from pipes. I propose a
dummy VBR encode pass that simply calculates the average bitrate for the
entire song. Then encode the song with ABR at the calculated rate.
This is assuming that GPSYCHO calculates the distortion correctly most
of the time.
Ross.
Robert Hegemann wrote:
> I just made Marks new VBR routine the default one.
> If someone needs the old one,
> just replace -v with --vbr-old.
>
> lame -v x.wav -> calls lame to use Marks new VBR
> lame --vbr-old x.wav -> calls lame to use the old VBR
> --
>
> e-mail: [EMAIL PROTECTED]
>
> homepage: http://linux.unixcity.de/catwalk/index.html
> --
> MP3 ENCODER mailing list ( http://geek.rcc.se/mp3encoder/ )
--
MP3 ENCODER mailing list ( http://geek.rcc.se/mp3encoder/ )
