Re: Does lame encoding only work with 16-bit integers?

Hello Nathan,

the lame_encode_* functions expect input data to be scaled appropriately.
Read remarks in lame.h, there are variants for float, double, int, short and long.
http://lame.cvs.sourceforge.net/viewvc/lame/lame/include/lame.h?revision=1.190&view=markup

Ciao Robert


----- Original Message ----- 
From: "Nathan Rajlich" <[email protected]>
To: <[email protected]>
Sent: Monday, October 15, 2012 7:46 PM
Subject: [Lame-dev] Does lame encoding only work with 16-bit integers?


> Hello all, so I'm in the middle of writing my node.js binding to
> libmp3lame, and this are going great so far. I'm basically just
> curious about the input that the lame encoder works with. I don't see
> any "lame_set_bitdepth()" option or similar, and
> "lame_encode_buffer()" accepts "shot int[]" (i.e. 16-bit). Is this the
> only integer size that lame with work with? Perhaps I'm missing
> something about the MPEG spec and perhaps that's the only valid bit
> depth for MP3s, but I just wanted confirmation.
> 
> i.e. If I want to encode an 8-bit WAV into an MP3 do I need to rescale
> manually before passing it to lame? Thanks in advance!
> 
> ------------------------------------------------------------------------------
> Don't let slow site performance ruin your business. Deploy New Relic APM
> Deploy New Relic app performance management and know exactly
> what is happening inside your Ruby, Python, PHP, Java, and .NET app
> Try New Relic at no cost today and get our sweet Data Nerd shirt too!
> http://p.sf.net/sfu/newrelic-dev2dev
> _______________________________________________
> Lame-dev mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/lame-dev

------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_sfd2d_oct