Re: [Lame-dev] Encoder padding & delay

[Roel V. <vd...@yu...>]

Hello Mark,

Monday, September 17, 2001, 10:30:23 PM, you wrote:


MT> I added a new function to the API

:))

MT> to compute the amount of padding that LAME appends to the end
MT> of the input.  I also added the code to VbrTag.c to retreive
MT> this information, but wasn't sure how to pack it into the
MT> tag.  

I see:

        {
            int enc_delay=lame_get_encoder_delay(gfp);       // encoder delay
            int enc_padding=lame_get_encoder_padding(gfp);   // encoder padding 
        }

tomorrow I'll see if it makes sense to me. if it works, I'll post the
diff, but I won't commit the CVS myself.

thanks very much Mark

MT> Right now the padding POSTDELAY + enough to pad out a complete frame.
MT> (POSTDELAY=288, is set in encoder.h).  But we have to check some
MT> decoders (including the one in lame) and see how much data they need
MT> to encode the last frame.

naah, let that up to the decoders. Important only is now the decoder
CAN know exactly how much samples were added to start, and to end of
the file and do as it pleases. Not a concern of the encoder to account
for any decoding info imo.

-- 
Best regards,
 Roel                            mailto:vd...@yu...