Re: Replacing mpglib

On 2017-08-02 07:45, Thomas Orgis wrote:
> Am I right in my idea that all I need to do is this?
> 
[...]
> 4. Figure out how much lame wants to know about encoder and decoder
>    padding for MP3 input or if gapless data from libmpg123 is fine in
>    places (it cuts away those normally).

That looks ok to me.
Regarding point 4, there is a possibility that for the 
decoding/transcoding purpose, gapless handling from libmpg123 is 
sufficient (it removes both leading and trailing data, right?). A long 
time ago, gapless decoding was not available in mpglib, so we had to add 
a way to handle it.

You might also have to look at teh following options: 
--mp1input,--mp2input,--mp3input,--decode-mp3delay
I'm not sure if they are handled through lame, or if they hae an impact 
on the way we are calling the decoding lib.

Regards,

--
Gabriel Bouvigne


------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot