Re: Developing LAME
Thomas Orgis <[email protected]>
| Newsgroups | gmane.comp.audio.mp3.lame |
|---|---|
| Message-ID | <[email protected]> |
Am Thu, 26 Jul 2012 22:20:37 -0400 schrieb David Smith <[email protected]>: > Wouldn't the API need to know where the information was though in order to pass it to mpg123? I don't quite understand. LAME passes encoded MPEG data in buffers to mpglib / HIP, as it would to mpg123. Basically, libmp3lame/mpglib_interface.c needs to be changed to rely on libmpg123 (am I right here, folks?), along with extensions to libmpg123 to add missing hooks. Simplest case: For basic decoding, replace decodeMP3() with mpg123_decode(). > I wouldn't mind taking over the project for you (as long as you don't mind some potentially incessant questioning :)), plus having access to the mpg123 source would help me out a lot. I was having trouble conceptualizing what exactly you were aiming at beforehand and it would help me see the bigger picture. Yeah, let's see how that picture evolves;-) The first step would be to see what is needed in LAME and compare with the libmpg123 API at http://mpg123.orgis.org/api/ (or just mpg123.h in an installation), to see what functionality would match and what is missing. After the latter is identified, we can open a branch in the mpg123 repo to experiment with adding that. Alrighty then, Thomas ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Lame-dev mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/lame-dev