On Fri, 31 Oct 2003 18:27:16 +0100, Arve Knudsen <[EMAIL PROTECTED]> wrote:
Hi
Whenever I turn on xrun detection, setting stop_threshold to buffer size instead of -1, snd_pcm_start refuses to work. The exit message to do with broken pipe. I figured it might be caused by an empty buffer, so I fill it with silence before start. snd_pcm_avail_update confirms this (zero frames available), but it makes no difference. This happens with both my cards, nForce2 onboard and RME DIGI9636. If someone could point out the cause of this, I'd truly appreciate it. If it matters I am running a development kernel, 2.6.0 test9-mm1.
Thanks
Arve Knudsen
Ok, was able to track it down to snd_pcm_prepare. I already tested the stream state, so I knew the stream was in the prepared state before I called snd_pcm_prepare myself. However I would never have thought that calling snd_pcm_prepare before snd_pcm_start could cause problems, isnt this the standard procedure (preparing before start)? At least commenting out the prepare call before starting, makes the problem go away. I see I also have to fill the buffer before snd_pcm_start (or deal with broken pipe), I thought a silence size equal to boundary and silence threshold of 0 would cause the buffer to be automatically silenced (judging from the docs)?
Awww, looks like I cheered to early. Once I compile with optimizations or try to restart because of xruns, I'm hit by the same error. Completely at a loss here, maybe I should just accept the defeat :\
Regards
Arve Knudsen
------------------------------------------------------- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ _______________________________________________ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
