Re: [Lame-dev] Minimum buffer size for beEncodeChunk?

[Ross L. <ro...@st...>]

I did receive a recording of it but I have deleted it.  A regular ticking noise from memory.  I don’t see how word misalignment could occur.  The recording buffer from the soundcard will contain whole samples.  Perhaps the issue is elsewhere but I thought I would check if the function had some issue with very small numbers of samples.

 

From: Erik Friesen [mailto:fri...@gm...] 
Sent: Saturday, 18 November 2017 12:15 a.m.
To: Ross Levis
Subject: Re: [Lame-dev] Minimum buffer size for beEncodeChunk?

 

What type of noise is it? I assume that you are not misaligning the audio word?

 

On Nov 17, 2017 4:55 AM, "Ross Levis" <ro...@st...> wrote:

Is there a minimum number of samples that should be sent to beEncodeChunk?
I wonder this as my app is recording from a sound input device and playing
to a sound output device, with the option of encoding directly to an MP3
file in the process.  This generally all works fine, but if they switch off
recording and back on again, the encoder can in some situations receive a
much smaller buffer size than the usual 9kb, and this appears to corrupt the
audio being encoded from that time onwards, with a continuous static noise
along with the correct audio.

That is my theory anyway.  Would there be an issue sending 1 sample of audio
to beEncodeChunk?

Ross.



------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Lame-dev mailing list
Lam...@li...
https://lists.sourceforge.net/lists/listinfo/lame-dev