ERROR: JackEngine::XRun: client
Moderators: MattKingUSA, khz
ERROR: JackEngine::XRun: client
I am getting this error non-stop:
11:50:00.698 XRUN callback (1162).
Mon Dec 7 11:50:00 2020: ERROR: JackEngine::XRun: client = PulseAudio JACK Source was not finished, state = Triggered
Mon Dec 7 11:50:00 2020: ERROR: JackEngine::XRun: client = mixbus was not finished, state = Running
Mon Dec 7 11:50:00 2020: ERROR: JackAudioDriver::ProcessGraphAsyncMaster: Process error
11:50:02.120 XRUN callback (1 skipped).
Xruns everywhere when recording. Any ideas from what?
Pop OS 20.10
Linux pop-os 5.8.0-050800-lowlatency #202008022230 SMP PREEMPT Sun Aug 2 22:36:20 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
== GUI-enabled checks ==
Checking if you are root... no - good
Checking filesystem 'noatime' parameter... 5.8.0 kernel - good
(relatime is default since 2.6.30)
Checking CPU Governors... CPU 0: 'performance' CPU 1: 'performance' CPU 10: 'performance' CPU 11: 'performance' CPU 12: 'performance' CPU 13: 'performance' CPU 14: 'performance' CPU 15: 'performance' CPU 2: 'performance' CPU 3: 'performance' CPU 4: 'performance' CPU 5: 'performance' CPU 6: 'performance' CPU 7: 'performance' CPU 8: 'performance' CPU 9: 'performance' - good
Checking swappiness... 10 - good
Checking for resource-intensive background processes... none found - good
Checking checking sysctl inotify max_user_watches... < 524288 - not good
increase max_user_watches by adding 'fs.inotify.max_user_watches = 524288' to /etc/sysctl.conf and rebooting
For more information, see http://wiki.linuxaudio.org/wiki/system_ ... sysctlconf
Checking whether you're in the 'audio' group... yes - good
Checking for multiple 'audio' groups... no - good
Checking the ability to prioritize processes with chrt... yes - good
Checking kernel support for high resolution timers... found - good
Kernel with Real-Time Preemption... not found - not good
Kernel without 'threadirqs' parameter or real-time capabilities found
For more information, see https://wiki.linuxaudio.org/wiki/system ... ime_kernel
Checking if kernel system timer is high-resolution... found - good
Checking kernel support for tickless timer... found - good
11:50:00.698 XRUN callback (1162).
Mon Dec 7 11:50:00 2020: ERROR: JackEngine::XRun: client = PulseAudio JACK Source was not finished, state = Triggered
Mon Dec 7 11:50:00 2020: ERROR: JackEngine::XRun: client = mixbus was not finished, state = Running
Mon Dec 7 11:50:00 2020: ERROR: JackAudioDriver::ProcessGraphAsyncMaster: Process error
11:50:02.120 XRUN callback (1 skipped).
Xruns everywhere when recording. Any ideas from what?
Pop OS 20.10
Linux pop-os 5.8.0-050800-lowlatency #202008022230 SMP PREEMPT Sun Aug 2 22:36:20 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
== GUI-enabled checks ==
Checking if you are root... no - good
Checking filesystem 'noatime' parameter... 5.8.0 kernel - good
(relatime is default since 2.6.30)
Checking CPU Governors... CPU 0: 'performance' CPU 1: 'performance' CPU 10: 'performance' CPU 11: 'performance' CPU 12: 'performance' CPU 13: 'performance' CPU 14: 'performance' CPU 15: 'performance' CPU 2: 'performance' CPU 3: 'performance' CPU 4: 'performance' CPU 5: 'performance' CPU 6: 'performance' CPU 7: 'performance' CPU 8: 'performance' CPU 9: 'performance' - good
Checking swappiness... 10 - good
Checking for resource-intensive background processes... none found - good
Checking checking sysctl inotify max_user_watches... < 524288 - not good
increase max_user_watches by adding 'fs.inotify.max_user_watches = 524288' to /etc/sysctl.conf and rebooting
For more information, see http://wiki.linuxaudio.org/wiki/system_ ... sysctlconf
Checking whether you're in the 'audio' group... yes - good
Checking for multiple 'audio' groups... no - good
Checking the ability to prioritize processes with chrt... yes - good
Checking kernel support for high resolution timers... found - good
Kernel with Real-Time Preemption... not found - not good
Kernel without 'threadirqs' parameter or real-time capabilities found
For more information, see https://wiki.linuxaudio.org/wiki/system ... ime_kernel
Checking if kernel system timer is high-resolution... found - good
Checking kernel support for tickless timer... found - good
- lilith
- Established Member
- Posts: 1698
- Joined: Fri May 27, 2016 11:41 pm
- Location: bLACK fOREST
- Has thanked: 117 times
- Been thanked: 57 times
- Contact:
Re: ERROR: JackEngine::XRun: client
Through what are you recording? Did you try disabling pulse audio?
Re: ERROR: JackEngine::XRun: client
I am using Mixbus 6.2. Maudio 8.
When I set the frames to 1024, the xruns go away.
So that is what I will do. I will keep the buffer settings high as the extra latency is needed on my setup to record without xruns.
When I set the frames to 1024, the xruns go away.
So that is what I will do. I will keep the buffer settings high as the extra latency is needed on my setup to record without xruns.
Re: ERROR: JackEngine::XRun: client
Additionally, the errors only occur when running Mixbus.
The following messages are displayed in the Jack messages:
08:13:13.681 XRUN callback (57).
Tue Dec 8 08:13:13 2020: ERROR: JackEngine::XRun: client = PulseAudio JACK Source was not finished, state = Triggered
Tue Dec 8 08:13:13 2020: ERROR: JackEngine::XRun: client = mixbus was not finished, state = Running
Tue Dec 8 08:13:13 2020: ERROR: JackAudioDriver::ProcessGraphAsyncMaster: Process error
08:13:15.424 XRUN callback (1 skipped).
08:13:15.684 XRUN callback (59).
Tue Dec 8 08:13:15 2020: ERROR: JackEngine::XRun: client = PulseAudio JACK Source was not finished, state = Triggered
Tue Dec 8 08:13:15 2020: ERROR: JackEngine::XRun: client = mixbus was not finished, state = Running
Tue Dec 8 08:13:15 2020: ERROR: JackAudioDriver::ProcessGraphAsyncMaster: Process error
08:13:17.428 XRUN callback (1 skipped).
08:13:19.678 XRUN callback (61).
... and they keep rolling as long as Mixbus is active.
Maybe this is a post better suited for Mixbus fourms?
Running Mixbus from the cli didnt produce information when the jack messages appeared.
The following messages are displayed in the Jack messages:
08:13:13.681 XRUN callback (57).
Tue Dec 8 08:13:13 2020: ERROR: JackEngine::XRun: client = PulseAudio JACK Source was not finished, state = Triggered
Tue Dec 8 08:13:13 2020: ERROR: JackEngine::XRun: client = mixbus was not finished, state = Running
Tue Dec 8 08:13:13 2020: ERROR: JackAudioDriver::ProcessGraphAsyncMaster: Process error
08:13:15.424 XRUN callback (1 skipped).
08:13:15.684 XRUN callback (59).
Tue Dec 8 08:13:15 2020: ERROR: JackEngine::XRun: client = PulseAudio JACK Source was not finished, state = Triggered
Tue Dec 8 08:13:15 2020: ERROR: JackEngine::XRun: client = mixbus was not finished, state = Running
Tue Dec 8 08:13:15 2020: ERROR: JackAudioDriver::ProcessGraphAsyncMaster: Process error
08:13:17.428 XRUN callback (1 skipped).
08:13:19.678 XRUN callback (61).
... and they keep rolling as long as Mixbus is active.
Maybe this is a post better suited for Mixbus fourms?
Running Mixbus from the cli didnt produce information when the jack messages appeared.
- lilith
- Established Member
- Posts: 1698
- Joined: Fri May 27, 2016 11:41 pm
- Location: bLACK fOREST
- Has thanked: 117 times
- Been thanked: 57 times
- Contact:
Re: ERROR: JackEngine::XRun: client
You could ask in the ardour IRC channel. Are you just recording or are you using lots of VSTs? When just recording you easily should be able to use 256 samples as buffer sizecanezila wrote: ↑Tue Dec 08, 2020 1:17 pm Additionally, the errors only occur when running Mixbus.
The following messages are displayed in the Jack messages:
08:13:13.681 XRUN callback (57).
Tue Dec 8 08:13:13 2020: ERROR: JackEngine::XRun: client = PulseAudio JACK Source was not finished, state = Triggered
Tue Dec 8 08:13:13 2020: ERROR: JackEngine::XRun: client = mixbus was not finished, state = Running
Tue Dec 8 08:13:13 2020: ERROR: JackAudioDriver::ProcessGraphAsyncMaster: Process error
08:13:15.424 XRUN callback (1 skipped).
08:13:15.684 XRUN callback (59).
Tue Dec 8 08:13:15 2020: ERROR: JackEngine::XRun: client = PulseAudio JACK Source was not finished, state = Triggered
Tue Dec 8 08:13:15 2020: ERROR: JackEngine::XRun: client = mixbus was not finished, state = Running
Tue Dec 8 08:13:15 2020: ERROR: JackAudioDriver::ProcessGraphAsyncMaster: Process error
08:13:17.428 XRUN callback (1 skipped).
08:13:19.678 XRUN callback (61).
... and they keep rolling as long as Mixbus is active.
Maybe this is a post better suited for Mixbus fourms?
Running Mixbus from the cli didnt produce information when the jack messages appeared.
-
- Established Member
- Posts: 108
- Joined: Sun Sep 01, 2019 12:58 pm
- Has thanked: 21 times
- Been thanked: 11 times
Re: ERROR: JackEngine::XRun: client
I have essentially the same thing happening (same xruns). 256 is the absolute lowest I can go stable. 128 is hit or miss. 64 starts giving me x-runs no matter what kind of audio related thing i do and 32 as soon as jack connects its just a neverending stream of xruns.
I have the realtime check in cadence, i'm in audio group, ive run the realtimequickscan script and the only thing that fails is the threadirq thing.
Meanwhile my friend with same hardware (ryzen 3700x) but windows runs at 16 no problem.
I have the realtime check in cadence, i'm in audio group, ive run the realtimequickscan script and the only thing that fails is the threadirq thing.
Meanwhile my friend with same hardware (ryzen 3700x) but windows runs at 16 no problem.
OS: Manjaro
Amp: Echolette M40 / NG51S Tape Echo
Strings: Martin D15M, Yamaha FG-180, Alhambra 5P, Yamaha Revstar
Amp: Echolette M40 / NG51S Tape Echo
Strings: Martin D15M, Yamaha FG-180, Alhambra 5P, Yamaha Revstar
-
- Established Member
- Posts: 108
- Joined: Sun Sep 01, 2019 12:58 pm
- Has thanked: 21 times
- Been thanked: 11 times
Re: ERROR: JackEngine::XRun: client
I did try it by running avlinux (should have mentioned) which is using the RT kernel, same problem there. Slightly more stable at 64 but not by much. Stopped using it since I have nvidia and do enjoy a game now and then
OS: Manjaro
Amp: Echolette M40 / NG51S Tape Echo
Strings: Martin D15M, Yamaha FG-180, Alhambra 5P, Yamaha Revstar
Amp: Echolette M40 / NG51S Tape Echo
Strings: Martin D15M, Yamaha FG-180, Alhambra 5P, Yamaha Revstar
-
- Established Member
- Posts: 1392
- Joined: Thu Oct 11, 2018 4:13 pm
- Has thanked: 168 times
- Been thanked: 247 times
Re: ERROR: JackEngine::XRun: client
Yes, but you may have to configure rtirq to prioritise your soundcard.christobal wrote:I did try it by running avlinux ...
Is that the proprietary drivers? I had a lot of hassle with nvidia. You know what Linus thinks of them, right?... I have nvidia ...
-
- Established Member
- Posts: 108
- Joined: Sun Sep 01, 2019 12:58 pm
- Has thanked: 21 times
- Been thanked: 11 times
Re: ERROR: JackEngine::XRun: client
If the GPU market wasnt so incredibly *****ed I would have had something else
I tried the rtirq config thing. It was a bit over my head.
It's listed under the xhci_hcd in proc/interrupts but I have like 10 of them and don't know how to figure out which irq is my actual soundcard
OS: Manjaro
Amp: Echolette M40 / NG51S Tape Echo
Strings: Martin D15M, Yamaha FG-180, Alhambra 5P, Yamaha Revstar
Amp: Echolette M40 / NG51S Tape Echo
Strings: Martin D15M, Yamaha FG-180, Alhambra 5P, Yamaha Revstar
-
- Established Member
- Posts: 1392
- Joined: Thu Oct 11, 2018 4:13 pm
- Has thanked: 168 times
- Been thanked: 247 times
Re: ERROR: JackEngine::XRun: client
It's kind of disappointing to hear that a 3700x isn't giving good performance. I thought they would. I have a quad core Athlon and I can run Guitarix at a buffer of 8! 8 isn't an option in the dropdown -- I have to type it in. Mixbus may use more DSP so it may need a larger buffer. Still, I would have expected a 3700x to give better performance than my old Athlon. I'm sure it could.
-
- Established Member
- Posts: 108
- Joined: Sun Sep 01, 2019 12:58 pm
- Has thanked: 21 times
- Been thanked: 11 times
Re: ERROR: JackEngine::XRun: client
This is my usb devices in lspci:
This is the soundcard under lsusb outputs:
This is the info from dmesg when I connect it:
Under /proc/interrupts the USB controllers are not listed by the 03:00.0 etc thing, but my PCI devices are (also, there are more xhci_hcd entries):
Code: Select all
03:00.0 USB controller: Advanced Micro Devices, Inc. [AMD] 400 Series Chipset USB 3.1 XHCI Controller (rev 01)
28:00.3 USB controller: Advanced Micro Devices, Inc. [AMD] Matisse USB 3.0 Host Controller
Code: Select all
Bus 003 Device 002: ID 1235:8200 Focusrite-Novation Scarlett 2i4 USB
Code: Select all
[ +1.636366] usb 3-2: new high-speed USB device number 3 using xhci_hcd
[ +0.142786] usb 3-2: New USB device found, idVendor=1235, idProduct=8200, bcdDevice= 4.1b
[ +0.000002] usb 3-2: New USB device strings: Mfr=1, Product=3, SerialNumber=0
[ +0.000001] usb 3-2: Product: Scarlett 2i4 USB
[ +0.000001] usb 3-2: Manufacturer: Focusrite
Code: Select all
IR-PCI-MSI 25690112-edge ahci[0000:31:00.0]
IR-PCI-MSI 25165824-edge ahci[0000:30:00.0]
IR-PCI-MSI 1574912-edge ahci[0000:03:00.1]
IR-PCI-MSI 1572864-edge xhci_hcd
IR-PCI-MSI 20977664-edge xhci_hcd
IR-PCI-MSI 20977665-edge xhci_hcd
IR-PCI-MSI 20977666-edge xhci_hcd
Last edited by christobal on Fri Dec 11, 2020 3:32 pm, edited 1 time in total.
OS: Manjaro
Amp: Echolette M40 / NG51S Tape Echo
Strings: Martin D15M, Yamaha FG-180, Alhambra 5P, Yamaha Revstar
Amp: Echolette M40 / NG51S Tape Echo
Strings: Martin D15M, Yamaha FG-180, Alhambra 5P, Yamaha Revstar
-
- Established Member
- Posts: 108
- Joined: Sun Sep 01, 2019 12:58 pm
- Has thanked: 21 times
- Been thanked: 11 times
Re: ERROR: JackEngine::XRun: client
It shouldnt really, my friend running windows has the same setup and it runs at 16 no problem with tons of tracks.merlyn wrote: ↑Fri Dec 11, 2020 2:55 pm It's kind of disappointing to hear that a 3700x isn't giving good performance. I thought they would. I have a quad core Athlon and I can run Guitarix at a buffer of 8! 8 isn't an option in the dropdown -- I have to type it in. Mixbus may use more DSP so it may need a larger buffer. Still, I would have expected a 3700x to give better performance than my old Athlon. I'm sure it could.
OS: Manjaro
Amp: Echolette M40 / NG51S Tape Echo
Strings: Martin D15M, Yamaha FG-180, Alhambra 5P, Yamaha Revstar
Amp: Echolette M40 / NG51S Tape Echo
Strings: Martin D15M, Yamaha FG-180, Alhambra 5P, Yamaha Revstar
-
- Established Member
- Posts: 1392
- Joined: Thu Oct 11, 2018 4:13 pm
- Has thanked: 168 times
- Been thanked: 247 times
Re: ERROR: JackEngine::XRun: client
This is my /proc/interrupts :
The IRQs that are relevant are IO-APIC. My soundcard is interrupt 20 snd_ice1712. For a USB interface you would prioritise the whole bus by name like xhci.
This could be an nvidia issue, also there is the USB 3.0/3.1 with a USB 2.0 interface issue, but to make sure try threadirqs. First you have to load it by editing /etc/default/grub to change the parameters passed to the kernel. Change this line by adding 'threadirqs' to whatever else you've already got : Then update grub, then reboot. Then I'll tell you how to use rtirq.
Code: Select all
$ cat /proc/interrupts
CPU0 CPU1 CPU2 CPU3
0: 109 0 0 0 IO-APIC 2-edge timer
8: 0 0 1 0 IO-APIC 8-edge rtc0
9: 0 0 0 0 IO-APIC 9-fasteoi acpi
14: 0 0 0 0 IO-APIC 14-edge pata_atiixp
15: 0 0 0 0 IO-APIC 15-edge pata_atiixp
16: 0 0 0 31562 IO-APIC 16-fasteoi ohci_hcd:usb3, ohci_hcd:usb4, snd_hda_intel:card1
17: 0 3 0 0 IO-APIC 17-fasteoi ehci_hcd:usb1
18: 3 0 0 0 IO-APIC 18-fasteoi ohci_hcd:usb5, ohci_hcd:usb6, ohci_hcd:usb7
19: 0 0 0 0 IO-APIC 19-fasteoi ehci_hcd:usb2
20: 0 0 0 24548875 IO-APIC 20-fasteoi snd_ice1712
27: 0 41667 0 0 PCI-MSI 278528-edge ahci[0000:00:11.0]
28: 0 118 0 0 PCI-MSI 526336-edge snd_hda_intel:card2
29: 36144 0 0 0 PCI-MSI 1048576-edge enp2s0
30: 0 0 96074 0 PCI-MSI 524288-edge radeon
NMI: 132 72 72 161 Non-maskable interrupts
LOC: 3052702 58613465 903132 1347875 Local timer interrupts
SPU: 0 0 0 0 Spurious interrupts
PMI: 132 72 72 161 Performance monitoring interrupts
IWI: 3976 1512 4033 819 IRQ work interrupts
RTR: 0 0 0 0 APIC ICR read retries
RES: 12454170 15994275 5536061 3361226 Rescheduling interrupts
CAL: 161893 143041 109944 67823 Function call interrupts
TLB: 195858 168453 205403 183704 TLB shootdowns
TRM: 0 0 0 0 Thermal event interrupts
THR: 0 0 0 0 Threshold APIC interrupts
DFR: 0 0 0 0 Deferred Error APIC interrupts
MCE: 0 0 0 0 Machine check exceptions
MCP: 30 30 30 30 Machine check polls
ERR: 419661
MIS: 0
PIN: 0 0 0 0 Posted-interrupt notification event
NPI: 0 0 0 0 Nested posted-interrupt event
PIW: 0 0 0 0 Posted-interrupt wakeup event
This could be an nvidia issue, also there is the USB 3.0/3.1 with a USB 2.0 interface issue, but to make sure try threadirqs. First you have to load it by editing /etc/default/grub to change the parameters passed to the kernel. Change this line by adding 'threadirqs' to whatever else you've already got :
Code: Select all
GRUB_CMDLINE_LINUX_DEFAULT="threadirqs "
-
- Established Member
- Posts: 108
- Joined: Sun Sep 01, 2019 12:58 pm
- Has thanked: 21 times
- Been thanked: 11 times
Re: ERROR: JackEngine::XRun: client
Alright, threadirqs is enabled. Passed in realtimequickscan.
The rtirq package is also installed (manjaro)
This is the output of irqs and affinities from tuna btw:
The rtirq package is also installed (manjaro)
This is the output of irqs and affinities from tuna btw:
Code: Select all
# users affinity
0 timer 0xffff
7 pinctrl_amd 0xffff
8 rtc0 0xffff
9 acpi 0xffff
25 AMD-Vi 0xffff
29 aerdrv 0xffff
30 aerdrv 0xffff
31 aerdrv 0xffff
32 aerdrv 0xffff
39 ahci[0000:03:00.1] 0xffff
41 ahci[0000:30:00.0] 0xffff
43 ahci[0000:31:00.0] 0xffff
44 xhci_hcd 0xffff
46 xhci_hcd 0xffff
47 xhci_hcd 0xffff
48 xhci_hcd 0xffff
49 xhci_hcd 0xffff
50 xhci_hcd 0xffff
51 xhci_hcd 0xffff
52 xhci_hcd 0xffff
53 xhci_hcd 0xffff
58 enp34s0 0xffff r8169
59 snd_hda_intel:card0 0xffff
60 nvidia 0xffff
OS: Manjaro
Amp: Echolette M40 / NG51S Tape Echo
Strings: Martin D15M, Yamaha FG-180, Alhambra 5P, Yamaha Revstar
Amp: Echolette M40 / NG51S Tape Echo
Strings: Martin D15M, Yamaha FG-180, Alhambra 5P, Yamaha Revstar