Re: Developing LAME
Thomas Orgis <[email protected]>
| Newsgroups | gmane.comp.audio.mp3.lame |
|---|---|
| Message-ID | <[email protected]> |
Am Tue, 10 Jul 2012 08:30:50 +0200 schrieb Alexander Leidinger <[email protected]>: > you have to come up with improvements yourself, or you need to pull ideas "out of the nose" of us. Oh, if nobody has suggestions, I can offer a starting point: dig into what LAME does regarding MP3 decoding and analysis of frame data with the goal to give me clear data about how I have to extend the libmpg123 API so that LAME can use this instead of the internal decoder fork. This is not core encoding functionality, but it deals with the codec and LAME code structure and is an entry point. In the long run, the DSP fun is in encoding, I guess, but this shouldn't be the worst start. And yes, replacing the mpg123 decoder fork in LAME is more of interest to me as mpg123 upstream as it is for LAME core folks;-) 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