[alsa-devel] Dsnoop-plugin buffer sizes

Jaroslav Kysela perex at perex.cz
Mon Mar 14 11:07:36 CET 2011

On Mon, 14 Mar 2011, Magnus Olsson wrote:

> Hi,
> I'm having issues with garbage data in my audio stream, which I believe 
> is caused by incorrect buffer sizes somewhere in the audio pipeline. The 
> garbage occurs periodically and is always constant in length. This 
> problem only triggers when I use the dsnoo-plugin. If running directly 
> towards the device, the audio stream is fine (no garbage). I've not 
> tested if this occurs with any other plugin.
> I'm using Dsnoop to capture a mono stream from a stereo device using 
> arecord, arecord -v -r 16000 -c1 -Daudiosource0 -fS16_LE /tmp/in.wav 
> (where audiosource0 is my dsnoop-device, bound to channel 0)
> The verbose info from arecord shows me that ALSA has correctly created 
> the Dsnoop device, with a "buffer_size" of 8000. It also shows that it 
> has opened my Hardware device in MMAP-mode, with a "buffer_size" of 
> 8192.

Show us this output from 'arecord -v'.


Jaroslav Kysela <perex at perex.cz>
Linux Kernel Sound Maintainer
ALSA Project, Red Hat, Inc.

More information about the Alsa-devel mailing list