Re: multiple crashes in lame
| Newsgroups | gmane.comp.audio.mp3.lame |
|---|---|
| Message-ID | <[email protected]> |
On 2017-06-29 23:42, Thomas Orgis wrote: >> reading somewhere that lame, when re-encoding from mp3, does not >> simply decode into raw pcm data and feed that to the encoder but uses >> the already encoded data as a basis for calculations, possibly >> resulting in better output quality. > > Hm … do we have somebody still alive being able to give us an overview > over that or do we need to dig into the (doubtlessly abundantly clear > and well-documented;-) code ourselves to find out? Such usage of a > decoder would of course justify containing perhaps some special frame > parser code in addition to the use of libmpg123 for decoding and ID3 > parsing (for keeping the metadata). Gentlemen, When re-encoding from MP3, LAME does not make any use of algorithmical data from the previously encoded MP3 (so you can go MP3->decodetofloatingpoint->encodetoMP3). The specific points that Lame is using in the decoding library are: *gapless decoding (based on LAME/INFO tag) *gapless decoding based on stitching several encoded MP3 (encoded with the --nogap option). That could be considered as deprecated (because in reality only the LAME/INFO method is used by other decoders) *carrying ID3/ID3v2 tags *hooks for the MP3x frame analyser. Even if MP3x is a bit tricky to build, it is very valuable for people working on the encoder. -- Gabriel Bouvigne ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Lame-dev mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/lame-dev