AVView recording sound error
A message that is not in the archive (sent off-list or not yet received): [email protected]
Quoted 14 lines · Peter Osterlund
Quoted 11 lines · Vladimir Dergachev
Quoted 7 lines · Sean Walker
If I try and record with an alsa device selected, I get the following error:
Audio reader: overrun occurred, resetting pcm device
repeated multiple times until I stop recording. The sound system is working just fine except for this.
Try reducing the sample rate, maybe your card cannot handle it.
Quoted 8 lines
I have the same problem with a 2.2GHz P4 as soon as I use the computer for anything else during recording. It turns out to be caused by the ALSA
stop_thresholddefaulting to 768, which corresponds to 16ms at a 48kHz sampling rate. 16ms is much smaller than the linux scheduler can handle, unless you use realtime priority and low-latency patches. Increasing this threshold to something bigger fixed the problem for me. 8192 was enough on my system but I don't think a big value will cause any harm, so I suggest using 32768.
Interestingly enough I don't have any problems and my card's default is 16384. I would say this is probably a bug in the alsa driver - it should set a reasonable default without requiring adjustments by a program that simply reads data.
Or, maybe, I did not read some paragraph in ALSA docs.
Could ALSA folks comment ?
Quoted 4 lines
Here is a patch I used while experimenting with this. (It obviously needs cleaning up before being applied.)
Thanks ! - merged.
best
Vladimir Dergachev
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
Quoted 27 lines · Vladimir Dergachev
Quoted 14 lines · Peter Osterlund
Quoted 11 lines · Vladimir Dergachev
Quoted 7 lines · Sean Walker
If I try and record with an alsa device selected, I get the following error:
Audio reader: overrun occurred, resetting pcm device
repeated multiple times until I stop recording. The sound system is working just fine except for this.
Try reducing the sample rate, maybe your card cannot handle it.
Quoted 8 lines
I have the same problem with a 2.2GHz P4 as soon as I use the computer for anything else during recording. It turns out to be caused by the ALSA
stop_thresholddefaulting to 768, which corresponds to 16ms at a 48kHz sampling rate. 16ms is much smaller than the linux scheduler can handle, unless you use realtime priority and low-latency patches. Increasing this threshold to something bigger fixed the problem for me. 8192 was enough on my system but I don't think a big value will cause any harm, so I suggest using 32768.
Quoted 8 lines
Interestingly enough I don't have any problems and my card's default is 16384. I would say this is probably a bug in the alsa driver - it should set a reasonable default without requiring adjustments by a program that simply reads data.
Or, maybe, I did not read some paragraph in ALSA docs.
Could ALSA folks comment ?
The default stop_threshold should be equal to buffer size. It appears to a bug. Hardware?
Jaroslav
-----
Jaroslav Kysela <[email protected]>
Linux Kernel Sound Maintainer
ALSA Project http://www.alsa-project.org
SuSE Linux http://www.suse.com
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf