Patches item #1449866, was opened at 2006-03-14 21:26
Message generated for change (Comment added) made by vividos
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=300290&aid=1449866&group_id=290Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: libmp3lame
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Michael Fink (vividos)
Assigned to: Alexander Leidinger (aleidinger)
Summary: interleaved 32-bit audio sample processing
Initial Comment:
Hi,
I'm using LAME as part of winLAME. For now I use the lame_encode_buffer_interleaved() function that takes 16-bit interleaved samples, but I also want to support 32-bit interleaved sample processing, and so I came up with a patch to implement a lame_encode_buffer_interleaved_int() function to put 32-bit signed interleaved audio samples into LAME. I hope this can be put into LAME, since it's only an extra function, not a change of existing functionality. Thanks in advance!
----------------------------------------------------------------------
>Comment By: Michael Fink (vividos)
Date: 2008-02-26 23:23
Message:
Logged In: YES
user_id=124874
Originator: YES
File Added: lame.h-lame_encode_buffer_interleaved_int32_t.patch
----------------------------------------------------------------------
Comment By: Michael Fink (vividos)
Date: 2008-02-26 23:10
Message:
Logged In: YES
user_id=124874
Originator: YES
I updated the patch for the latest CVS HEAD version, lame.c revision
1.319. I also changed the type from int to int32_t as suggested. I hope the
patch can be applied to CVS. Many thanks!
File Added: lame.c-lame_encode_buffer_interleaved_int32_t.patch
----------------------------------------------------------------------
Comment By: gregTelevirtual (gregtelevirtual)
Date: 2006-10-03 17:40
Message:
Logged In: YES
user_id=1612121
Hi,
this isn't really gonna help you guys, but from reading
this i think you guys may be able to help me, as you know
about the things i'm having trouble with.
The pcm I'm creating is a mono file, I believe that to get
around this issue I need to copy my buffer so I have two
channels, left and right and feed them into
lame_encode_buffer() the main problem is however, using
Microsoft visual Studio. NET 2003 I get link error 2019:
unresolved symbol 'lame_encode_buffer()' reference in
function 'Our sound encode function'. I've tried using
all the other lame_encode functions and are having to make
do with lame_encode_buffer_interleaved() but this appears
to half the quality of the file output. In short, we need
to know a) the best way to encode a mono pcm file and b)if
this method doesn't use the interleaved function what
might cause the rest of them to generate the link error.
sorry for hijacking your thread but i'm in desperate need
of some help.
regards
Greg
----------------------------------------------------------------------
Comment By: Michael Fink (vividos)
Date: 2006-06-14 18:17
Message:
Logged In: YES
user_id=124874
The function lame_encode_buffer_int also uses int as data
type for the samples and would suffer from the same error. I
don't want need to depend that int is a 32-bit value, but I
want to put samples into LAME that come interleaved "int"
values. So I consider the patch ok in that sense.
----------------------------------------------------------------------
Comment By: Alexander Leidinger (aleidinger)
Date: 2006-06-03 13:09
Message:
Logged In: YES
user_id=90585
An int may be 64bit on 64bit systems (e.g. Athlon 64). I
suggest to use a 32bit type like int32_t instead.
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=300290&aid=1449866&group_id=290-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/_______________________________________________
Lame-dev mailing list
Lame-dev@...
https://lists.sourceforge.net/lists/listinfo/lame-dev
