> >"You cannot set callbacks on an active client > >cannot connect alsaP:out_000 > > to alsa_pcm:playback_1" > > if these clients really do call snd_pcm_close() when ffwd'ing, then > there must be some mistake in the ALSA JACK plug, because it should > close the client down. if they do not call snd_pcm_close() then i am > not sure what the ALSA JACK plug might be doing.
I can check the code, but I suspect that they dont call pcm_close. I think the channel is paused and new data loaded. However, the point is slightly moot. Nothing at all comes out, the app appears to hang, and in the case of mplayer, it only gets these errors after the delay gets so large that overflows occur and mplayer obviously shuffles forward a bit to get back in sync. It appears that JACK is not accepting anything from the alsa client and they are just blocking. Neither mplayer, xmms, or mythtv can get anything into Jack as far as I can tell. There is nothing in the Jack log though... ------------------------------------------------------- This SF.net email is sponsored by: IBM Linux Tutorials. Become an expert in LINUX or just sharpen your skills. Sign up for IBM's Free Linux Tutorials. Learn everything from the bash shell to sys admin. Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click _______________________________________________ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
