Re: multiple crashes in lame

Am Fri, 30 Jun 2017 13:56:11 +0200
schrieb [email protected]: 

> 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).

Great. Also I just verified that current lame is happy with floating
point WAV input (remembered differently).

> The specific points that Lame is using in the decoding library are:
> *gapless decoding (based on LAME/INFO tag)

Done by libmpg123 (actually one of the main points that got me hacking
on mpg123 in the first place). WAVs created by `mpg123 -w output.wav
input.mp3` are gapless if info is present.

> *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)

I only very faintly remember --nogap, but not actually using it.

> *carrying ID3/ID3v2 tags

Libmpg123 gives you those, to some extent (parsed to UTF-8 strings).
Maybe we need some added hooks to extract the raw ID3v2 tag(s) for lame
… as libmpg123 does not deliver unsupported parts of ID3v2. A separate
tool that copies metadata from one MP3 to another one might be a more
proper way. There are better metadata parsers and writers out there
(also supporting a variety of tag formats).

> *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.

I'm very much interested in what those hooks are exactly to add them to
the libmpg123 API.


Alrighty then,

Thomas
------------------------------------------------------------------------------
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