[PATCH hijack] Re: problems decoding MP3 -- more

Hi John,

about troubles decoding MP3 using libmp3lame … this reminds me of the
patch I posted a year ago about making lame use libmpg123 for decoding
itself.

	https://sourceforge.net/p/lame/mailman/lame-dev/thread/20180926085129.22699274%40klammerschelle/#msg36424811

(patch attached and also on
https://mpg123.org/test/lame-svn-r6432-libmpg123.patch)

I think we got to a point where deprecating the included
decoder (which is an old fork of mpg123 code) was the plan. Can any dev
comment on this? Should I rather open a bug report with the patch?

I do realize that I'm still struggling to get the release of mpg123
with the changes needed for lame and the frame analyzer out … but it
would help to have some agreement on the API additions I made are fine
that way, before actually making them official.

Coming back to the question of correctly using the HIP decoder … John:
What about using libmpg123 for that instead of API that might get
dropped from libmp3lame in future? We are short on developer time for
either the encoder or the decoder libraries. LAME does encoding,
libmpg123 does decoding and is likely better tested against MPEG audio
files in the wild than the silbling code inside libmp3lame.

With the limited developer time, I envision each project focusing on
maintenance of encoding on the LAME side and decoding on the mpg123
side.


_______________________________________________
Lame-dev mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/lame-dev