On Wed, 1 Nov 2017 03:41:02 +0000, David Woodfall wrote: Ok, I don't have the required knowledge to understand what's going on, I'm still surprised about such a low frame size, even more if 128 is the enforced default, with either -n 2 or 3.

I also set it not to sync with the master.

I've done multitrack recording before using ardour, jack, zynaddsubfx, a midi (usb) keyboard, non sequencer and some other stuff. I recorded at 96k (I should have use 48k), but I didn't get anything like the xruns I am getting with mplayer. But that was a few years ago, on a different kernel, which IIRC was setup for low latency. I guess I'll have to do some kernel compiling again to see if it helps. It's been a while. Dave

I was using slackware then and now. I used to customise the kernels a lot and take out all the 'generic' drivers that I could, and remove anything that didn't match the hardware. I don't really bother with such tweaking now, and just stick to the stock 'huge' kernel. Frequency scaling is either powersave or performance on this T420 with pstates in the kernel, but switching to performance hasn't helped much. The strange thing is that I have a dual core server running the same version of slackware, kernel, jack and mplayer and it has no xruns, even in powersave mode. It's also an intel CPU with pstates. I haven't tried rtirq yet. I'll give that a shot.

On Wed, 1 Nov 2017 13:07:45 -0500, Chris Caudle wrote: -p not -n ;), funny typo ;).

I tried playing an album (single file) with mplayer using the alsa backend and never got a single xrun. That is on a non-low latency kernel. So I knew that there were no problems on the local system. I found that whenever I tried to set anything regarding latency in the netone driver they either didn't do anything, or the settings were overridden. Setting num periods on the master jackd didn't seem to make any difference. So I watched the client jackd output while I started it and saw: NetOne driver started AutoConfig Override !!! AutoConfig Override: Master JACK sample rate = 44100 AutoConfig Override: capture_channels_audio = 2 AutoConfig Override: capture_channels_midi = 0 AutoConfig Override: playback_channels_audio = 2 AutoConfig Override: playback_channels_midi = 0 Then I found that jack_netsource has its own latency setting: -n periods Network latency in JACK periods So I tried setting that and got results. I'm using -n12 which isn't a great delay in audio startup, less than a second. It seems that jack_netsource will override the netone client for some of the settings, like MTU for instance. Also the sample rate is set by the master. I still see some glitches like: JackEngine::XRun: client = MPlayer [32590] was not finished, state = Triggered JackAudioDriver::ProcessGraphAsyncMaster: Process error But there was no audible glitch. It would need tweaking more to get rid of those errors I guess, but for now I'm happy with it. Thanks all for your help and ideas.

I'm using 44100 for both. I don't know how 48000 got in there.

I didn'nt realise it was jack-aware. I'll give it a shot. Thanks.

On November 1, 2017 6:58:35 AM HST, David Woodfall <dave(a)dawoodfall.net> wrote: FWIW, Audacious doesn't recognize WEBM files. Mplayer does. -- David W. Jones gnome(a)hawaii.rr.com authenticity, honesty, community http://dancingtreefrog.com Sent from my Android device with K-9 Mail.