Sporadic XRUNS / Linux

Official support for: bitwig.com
User avatar
826 posts since 6 Jun, 2016 from San Marcos, Texas

Post Thu Oct 15, 2020 2:37 pm

AFAIK, I'm not experiencing this.

5.8.12-200.fc32.x86_64 #1 SMP Mon Sep 28 12:17:31 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

187 posts since 30 Jun, 2012 from Belgium

Post Fri Oct 16, 2020 2:11 am

what is the 'Zen-kernel' supose to do? i compile my kernel according to my system and is Preemptible with performance governor enabled.

790 posts since 26 May, 2013 from France, Sisteron

Post Fri Oct 16, 2020 4:48 am

I think it is in the time it takes to wake up a thread waiting on IO.

50 posts since 27 Jun, 2013

Post Sat Oct 17, 2020 5:10 am

For what it's worth I'd like to add that I'm not experiencing any of these regular spikes on Manjaro with its stock kernel and no tweaks other than using the performance CPU governor over the default powersave one. I'm using the 'By plug-in' sandboxing setting, and most of the plugins I'm using are either native U-He plugins or Windows VST2 plugins running through yabridge.

42 posts since 8 Jun, 2006 from Ann Arbor, MI

Post Sat Oct 17, 2020 7:04 am

I had been experiencing a few xruns at 48k and 256 samples using Ubuntu Studio and the stock optimizations (Low-Latency, performance mode).

Having installed the 3.3beta1, I am now able to get down to 128 samples with only a few xruns. Not sure if that has to do with the new AVx support or other optimizations, but looks like 3.3 could bring a better experience.

I had to turn off the plugin sandboxing to get the minimal amount of pops/stutters, but I haven't done any of the irq priority or Server Synchronous Mode tweaks mentioned earlier.

I'll report back once I've given those steps a try

1245 posts since 15 May, 2002 from Finland

Post Sun Oct 18, 2020 5:12 am

I think these are related to VSTs... Now I was working with a 32 sample buffer with no problem in 3.3b1 with native devices only.

42 posts since 8 Jun, 2006 from Ann Arbor, MI

Post Mon Oct 19, 2020 6:04 am

I just concluded the same experiment, but had the introduction of the native external hardware FX module introduce the xruns as well. If I turn off sandboxing (with the exception of one fussy tool), I'm working pretty well with Bitwig and a few VSTs at 128 samples, with minimal xruns. I'm hoping a few irq priority tweaks can get me completely xrun free. None of the pops and clicks appear to be making into any recorded data, so it's mostly just annoying.

Would also love to have a native IR loader, as that's my fussy tool rn.

User avatar

Topic Starter

103 posts since 7 Apr, 2018

Post Thu Mar 04, 2021 1:11 pm

I can confirm that using the sandboxing mode with VSTs causes sporadic xruns in Bitwig 3.3 (with Ubuntustudio 20.4., Jack2, buffer size 1024 samples). When choosing "Within Bitwig" everything is fine.

24 posts since 14 Jan, 2015 from Tallinn, Estonia

Post Sat Apr 03, 2021 4:37 am

It's sad to return back to this thread, but the problem is occurring again on the same machine. Recently I've switched from Mint to Kubuntu and installed liquorix kernel 5.11 to prevent these regular xruns in Bitwig. Unfortunately it doesn't help anymore.
I use Bitwig 3.3.7 and "Together" sandbox mode. The problem, like before, disappears when I switch to "Within Bitwig" mode.

109 posts since 1 Nov, 2010

Post Fri Apr 09, 2021 5:35 am

This might not be applicable here, but my experience has been that the xruns are very dependent on hardware. If I'm only using wifi, then stuff is stable, but once I start using Ethernet then I get very frequent xruns. Though I've noticed this behavior outside of BWS as well.

Maybe this doesn't say much, but perhaps you can try singling out devices and trying to see which of them might be the culprit.
((( ~ )))

457 posts since 5 Apr, 2014

Post Sat Apr 10, 2021 9:47 am

hey everyone,

i have rarely xruns on my system running the following setup:
MSI X570 Gaming EDGE WIfi
32GB of 3200Mhz RAM

5.8.0-48-lowlatency #54~20.04.1-Ubuntu SMP PREEMPT
with a Geforce GTX660TI with the proprietary driver
ontop of a default Ubuntu 20.04

I use Jack Audio Server with 512 Samples for Mixing, set to RT of course, and 128 samples for recording, but than disabling folding@home running in the Background.

I did add the following lines to the limits.conf file:

@audio - rtprio 90
@audio - memlock unlimited

you can find the limts.conf here: /etc/security/

at least on Ubuntu and Debian systems...

Inside Bitwig i have the Sandboxing set to "By Manufacturer"

I hope this might help

42 posts since 8 Jun, 2006 from Ann Arbor, MI

Post Sat Apr 10, 2021 10:29 am

Yeah, desktop parts are, more often then not, just far more stable and performant. I just set up a Ryzen 5600x in a MSI Tomahawk 550B Mobo and I'm able to get down to 2.3 Ms @ 48kHz/128 samples, no overruns or pops.

My Yoga c950 should be just as powerful, but I can only get it down to 256 samples at 48kHz, and it occasionally glitches out.

I have also found that if you don't need all the flexibility that Jack provides, setting Bitwig to ALSA is just way less hassle and finickiness.

Rn, I just use my laptop for noodling and exploring, or mixing / editing when I'm in bed and I use the desktop when I'm actually recording performances and can't do what I want without the low low latency.

Return to “Bitwig”