Page 2 of 2
Re: snd-aloop daemon causing tons of xruns randomly
Posted: Wed Jul 31, 2013 7:07 pm
by wolftune
Hmm, no sound with HTML5 means that the ALSA->JACK (plugin) won't work with WebRTC
So it seems this is my sitation:
The alsa-in/out version of the loop bridge can cause kernel panics still, not sure when, even with 3.8 kernel for this new machine. It also can get totally overloaded with xruns.
The zita bridge uses more DSP and sometimes can lose connection on suspend/resume in such a way that things have to be annoyingly restarted. Otherwise, it still gets xruns slowly building but not awful.
The plugin is fine and lowest DSP, but doesn't work with HTML5.
Is there some settings or troubleshooting I should do? Should I consider just using Pulse Audio after all? Is there a way to request that the plugin be updated to work with HTML5? Or is there any other way to go forward and get a fully working situation?
Re: snd-aloop daemon causing tons of xruns randomly
Posted: Wed Jul 31, 2013 7:19 pm
by wolftune
falkTX wrote:I'm not sure what to do either...
I though the kernel panics were over in >= 3.8, but it doesn't seem the case.
I'll probably have to force-kill alsa_in/out on suspend as before.
For the xruns, are you sure that when they happen and you run:
does this makes everything ok again? (at least temporarily)
I'll try that, but for the record, I did *not* verify that this kernel panic was the same issue with suspend/resume. It might be unrelated.
Indeed, I temporarily got things better by stopping and restarting the alsa_in loop stuff in the past. I will report about that command though.
Re: snd-aloop daemon causing tons of xruns randomly
Posted: Wed Jul 31, 2013 7:58 pm
by wolftune
ok:
killall -9 alsa_in alsa_out
stopped the runaway xruns! yay! I;ll have to see if I still get any kernel panics and figure out when.
otherwise, I'd like, obviously, to avoid having to manually run this command to stop this.
I'd like very much a command to reset xrun count in Cadence without stopping JACK, btw.
If I can figure out the panics and the killall command can be automated or the source of the xruns determined and fixed, then I think it'll be all good
Re: snd-aloop daemon causing tons of xruns randomly
Posted: Wed Jul 31, 2013 8:21 pm
by wolftune
So over the last couple minutes, I still got 9 xruns, but not a string of them. Note: I'm using the unity features for the icon-only KDE task manager to track the xruns easily, but once it gets into the thousands, it doesn't show. So even though killall worked, it didn't reset xruns. So I also start/stopped JACK so that I could get a fresh count and watch for xruns again. That's why I want an xrun count reset. Please just include in cadence (ideally a context-menu option for the launcher) the very same xrun-reset that is in Claudia.
Oops, as I was typing it went crazy again! And then after a killall, it did it again after about 20 second with no problems!
Here's some log, starting with a bunch of crazy xruns (much more than this in the log) and then the results of the killall etc.:
Code: Select all
Wed Jul 31 13:19:16 2013: ERROR: JackEngine::XRun: client = alsa2jack was not finished, state = Triggered
Wed Jul 31 13:19:16 2013: ERROR: JackAudioDriver::ProcessGraphAsyncMaster: Process error
Wed Jul 31 13:19:16 2013: ERROR: JackEngine::XRun: client = alsa2jack was not finished, state = Triggered
Wed Jul 31 13:19:16 2013: ERROR: JackAudioDriver::ProcessGraphAsyncMaster: Process error
Wed Jul 31 13:19:16 2013: ERROR: JackEngine::XRun: client = alsa2jack was not finished, state = Triggered
Wed Jul 31 13:19:16 2013: ERROR: JackAudioDriver::ProcessGraphAsyncMaster: Process error
Wed Jul 31 13:19:16 2013: ERROR: JackEngine::XRun: client = alsa2jack was not finished, state = Triggered
Wed Jul 31 13:19:16 2013: ERROR: JackAudioDriver::ProcessGraphAsyncMaster: Process error
Wed Jul 31 13:19:16 2013: ERROR: JackEngine::XRun: client = alsa2jack was not finished, state = Triggered
Wed Jul 31 13:19:16 2013: ERROR: JackAudioDriver::ProcessGraphAsyncMaster: Process error
Wed Jul 31 13:19:16 2013: ERROR: JackEngine::XRun: client = alsa2jack was not finished, state = Triggered
Wed Jul 31 13:19:16 2013: ERROR: JackAudioDriver::ProcessGraphAsyncMaster: Process error
Wed Jul 31 13:19:16 2013: ERROR: JackEngine::XRun: client = alsa2jack was not finished, state = Triggered
Wed Jul 31 13:19:16 2013: ERROR: JackAudioDriver::ProcessGraphAsyncMaster: Process error
Wed Jul 31 13:19:16 2013: Disconnecting 'HDA Intel PCH:capture_1' from 'jack2alsa:playback_1'
Wed Jul 31 13:19:16 2013: Disconnecting 'HDA Intel PCH:capture_2' from 'jack2alsa:playback_2'
Wed Jul 31 13:19:16 2013: ERROR: Failed to find port 'jack2alsa:playback_1' to destroy
Wed Jul 31 13:19:16 2013: ERROR: Failed to find port 'jack2alsa:playback_2' to destroy
Wed Jul 31 13:19:16 2013: ERROR: JackEngine::XRun: client = alsa2jack was not finished, state = Triggered
Wed Jul 31 13:19:16 2013: ERROR: JackEngine::XRun: client = alsa2jack was not finished, state = Triggered
Wed Jul 31 13:19:16 2013: ERROR: JackAudioDriver::ProcessGraphAsyncMaster: Process error
Wed Jul 31 13:19:17 2013: Client 'jack2alsa' with PID 15645 is out
Wed Jul 31 13:19:17 2013: ERROR: Cannot write socket fd = 18 err = Broken pipe
Wed Jul 31 13:19:17 2013: ERROR: CheckRes error
Wed Jul 31 13:19:17 2013: ERROR: Could not write notification
Wed Jul 31 13:19:17 2013: ERROR: NotifyClient fails name = jack2alsa notification = 1 val1 = 0 val2 = 0
Wed Jul 31 13:19:17 2013: ERROR: Cannot write socket fd = 18 err = Broken pipe
Wed Jul 31 13:19:17 2013: ERROR: CheckRes error
Wed Jul 31 13:19:17 2013: ERROR: Could not write notification
Wed Jul 31 13:19:17 2013: ERROR: NotifyClient fails name = alsa2jack notification = 18 val1 = 0 val2 = 0
Wed Jul 31 13:19:17 2013: ERROR: Cannot write socket fd = 18 err = Broken pipe
Wed Jul 31 13:19:17 2013: ERROR: CheckRes error
Wed Jul 31 13:19:17 2013: ERROR: Could not write notification
Wed Jul 31 13:19:17 2013: ERROR: NotifyClient fails name = alsa2jack notification = 18 val1 = 1 val2 = 0
Wed Jul 31 13:19:17 2013: Disconnecting 'alsa2jack:capture_1' from 'HDA Intel PCH:playback_1'
Wed Jul 31 13:19:17 2013: Disconnecting 'alsa2jack:capture_2' from 'HDA Intel PCH:playback_2'
Wed Jul 31 13:19:17 2013: ERROR: Failed to find port 'alsa2jack:capture_1' to destroy
Wed Jul 31 13:19:17 2013: ERROR: Failed to find port 'alsa2jack:capture_2' to destroy
Wed Jul 31 13:19:17 2013: Client 'alsa2jack' with PID 15644 is out
Wed Jul 31 13:19:23 2013: New client 'alsa2jack' with PID 17421
Wed Jul 31 13:19:23 2013: New client 'jack2alsa' with PID 17422
Wed Jul 31 13:19:24 2013: port 'jack2alsa:playback_1' created
Wed Jul 31 13:19:24 2013: port 'jack2alsa:playback_2' created
Wed Jul 31 13:19:24 2013: port 'alsa2jack:capture_1' created
Wed Jul 31 13:19:24 2013: port 'alsa2jack:capture_2' created
Wed Jul 31 13:19:24 2013: Connecting 'alsa2jack:capture_1' to 'HDA Intel PCH:playback_1'
Wed Jul 31 13:19:24 2013: Connecting 'alsa2jack:capture_2' to 'HDA Intel PCH:playback_2'
Wed Jul 31 13:19:25 2013: Connecting 'HDA Intel PCH:capture_1' to 'jack2alsa:playback_1'
Wed Jul 31 13:19:25 2013: Connecting 'HDA Intel PCH:capture_2' to 'jack2alsa:playback_2'
Wed Jul 31 13:19:40 2013: ERROR: JackEngine::XRun: client = alsa2jack was not finished, state = Triggered
Wed Jul 31 13:19:40 2013: ERROR: JackAudioDriver::ProcessGraphAsyncMaster: Process error
Wed Jul 31 13:19:40 2013: ERROR: JackEngine::XRun: client = alsa2jack was not finished, state = Triggered
Wed Jul 31 13:19:40 2013: ERROR: JackAudioDriver::ProcessGraphAsyncMaster: Process error
Anyway, having this panic even while doing nothing really, so not such a good situation. With this randomly panic'ing like this, I'm inclined to stay away from alsa_in and go with zita or the plugin. But see the issues above. I sure wish the plugin worked with HTML5, that would solve everything for me I think.
Re: snd-aloop daemon causing tons of xruns randomly
Posted: Wed Jul 31, 2013 10:25 pm
by wolftune
Ok new update:
First, using alsa_in etc. is impossible now as it randomly panics and there's no way to be prepared and the glitch of killing it and restarting is not a good solution.
Second, I am able to use zita basically, so that's acceptable for HTML5 stuff where the plugin fails.
Third, I found some info about the plugin and HTML5 compatibility issues:
https://bugzilla.mozilla.org/show_bug.cgi?id=812900
Note: I did not try the workaround there yet, in part because someone said it no longer works but also because I don't understand it and am not sure that if I test it I will be sure everything else is the right settings to test fully.
However, further testing is made extra hard by this: I don't know how to reliably swap between the loop and the plugin for the purposes of quick testing. If I choose plugin from the pulldown in Cadence, it doesn't appear to actually change. It *says* that it is now using the plugin but behavior and DSP and looking at active processes indicates the loop is still active.
What is the proper way to quickly switch between these in order to test, ideally without changing anything else, i.e. without reloading the audio or program or restarting JACK?
Re: snd-aloop daemon causing tons of xruns randomly
Posted: Wed Aug 07, 2013 11:10 pm
by wolftune
update: I mostly have been using the alsa-jack plugin, but then there was some WebM video which I want to watch, and I had to go back to snd-aloop. Randomly it glitches and the sound goes away. Now perhaps the same glitch is affecting either alsa_in version and zita, but with zita it doesn't go crazy with xruns? I'm using zita and I don't get lots of xruns, but still have no sound until I simply stop and restart the bridge.
I'm willing to try to isolate the issue, but I have no clue what it is.
Is installing pulse worth considering?
Re: snd-aloop daemon causing tons of xruns randomly
Posted: Thu Aug 08, 2013 12:15 am
by wolftune
Ok, for the time being I decided that Chromium was less hassle and more reason to keep it around than Pulse Audio. So, I'm sticking with the plugin, and in those cases where HTML5 audio is needed, I can switch to Chromium instead of Firefox (gosh, now I'm wondering about trying all sorts of other browsers), until that bug gets fixed. And so I'll blame Firefox in this case.
EDIT: someone says it was better with a nightly build of Firefox so maybe it got fixed and will be released sometime soon, maybe v. 24
Re: snd-aloop daemon causing tons of xruns randomly
Posted: Fri Sep 20, 2013 5:58 am
by wolftune
There's a new comment on the bug report for the Firefox / JACK issue, but I don't understand it:
https://bugzilla.mozilla.org/show_bug.cgi?id=812900#c14
Re: snd-aloop daemon causing tons of xruns randomly
Posted: Wed Sep 25, 2013 5:16 pm
by akiz
Have same problem reported in here, it is very anoying. It can also freeze my computer if i dont kill alsa before restarting jack. Need to use alsa - loop - jack for serious audio work but i still can not because this bug.
http://forum.linuxmusicians.com/viewtop ... 47&t=11280