> >> "compute_ath" routine calculates ATH using these 2
> >> variables..... But they are not initialized at that moment.
>
> M> this bug was also in lame 3.50, but it only effects the first
> M> frame.
>
> No, it efects every frame because ATH is calculated only at the
> 1st step and quantize.c uses it for the end of frame. see the source and
> check out where is calling "compute_ath" is.
>
oops! but the variables were initialized to the 128kbs/44.1khz values, so
at least the most common usage wasn't effected?
> M> by the way, does anyone know how to allow public access to a
> M> cvs repository? This would proably be a good idea for LAME.
>
> I think using CVS is very neat idea.
> Maybe some pro-"OPENSOURCE" vendor will rent us it "FREE" or very cheap
> fee... I hope, but I don't know who will.
I have the server, but I dont know how to add public access.
I'm sure its in the CVS docs, but maybe someone has a sample
.cvsrc file or whatever is needed.
Mark
--
MP3 ENCODER mailing list ( http://geek.rcc.se/mp3encoder/ )
