XRUNS ... but why?

Optimize your system for ultimate performance.

Moderators: khz, MattKingUSA

User avatar
lilith
Established Member
Posts: 1434
Joined: Fri May 27, 2016 11:41 pm
Location: bLACK fOREST
Contact:

Re: XRUNS ... but why?

Post by lilith »

That's not bad. :mrgreen: But will this work with alot of VST instruments?

User avatar
lilith
Established Member
Posts: 1434
Joined: Fri May 27, 2016 11:41 pm
Location: bLACK fOREST
Contact:

Re: XRUNS ... but why?

Post by lilith »

After everything was fine for months yesterday I got occasional xruns again, for which I don't have any explanation. I've gone through the whole thread again and did the optimizations proposed for my new system (set up in October). I also installed the default settings script from the KXStudio repo.

Now the only thread running with RT priority is the external soundcard:

Code: Select all

/etc/init.d/rtirq status

  PID CLS RTPRIO  NI PRI %CPU STAT COMMAND	
  158 FF      95   - 135  3.2 S    irq/28-xhci_hcd	
  191 FF      94   - 134  0.0 S    irq/29-xhci_hcd	
    9 TS       -   0  19  0.1 S    ksoftirqd/0	
   17 TS       -   0  19  0.1 S    ksoftirqd/1	
   22 TS       -   0  19  0.1 S    ksoftirqd/2	
   27 TS       -   0  19  0.1 S    ksoftirqd/3	
   42 TS       -   0  19  0.0 S    irq/9-acpi	
   68 TS       -   0  19  0.0 S    irq/8-rtc0	
  138 TS       -   0  19  0.0 S    irq/18-i801_smb	
  141 TS       -   0  19  0.0 S    irq/16-ehci_hcd	
  174 TS       -   0  19  0.0 S    irq/23-ehci_hcd	
  192 TS       -   0  19  0.0 S    irq/27-ahci[000	
  210 TS       -   0  19  0.1 S    irq/30-i915	
  379 TS       -   0  19  0.0 S    irq/31-mei_me	
  664 TS       -   0  19  0.2 S    irq/26-enp2s0	
Before it was still:

Code: Select all

/etc/init.d/rtirq status

  PID CLS RTPRIO  NI PRI %CPU STAT COMMAND	
  141 FF      85   - 125  0.0 S    irq/16-ehci_hcd	
  158 FF      85   - 125  3.0 S    irq/28-xhci_hcd	
  174 FF      84   - 124  0.0 S    irq/23-ehci_hcd	
  191 FF      84   - 124  0.0 S    irq/29-xhci_hcd	
   42 FF      50   -  90  0.0 S    irq/9-acpi	
   68 FF      50   -  90  0.0 S    irq/8-rtc0	
  138 FF      50   -  90  0.0 S    irq/18-i801_smb	
  192 FF      50   -  90  0.0 S    irq/27-ahci[000	
  210 FF      50   -  90  0.1 S    irq/30-i915	
  379 FF      50   -  90  0.0 S    irq/31-mei_me	
  664 FF      50   -  90  0.2 S    irq/26-enp2s0	
    9 TS       -   0  19  0.1 S    ksoftirqd/0	
   17 TS       -   0  19  0.1 S    ksoftirqd/1	
   22 TS       -   0  19  0.1 S    ksoftirqd/2	
   27 TS       -   0  19  0.1 S    ksoftirqd/3	
I wonder why in the "standard cconfiguartion" so many processes are running with RT priority. Obviously this is not needed.
Except of the RT kernel all checks from the realtimeconfig script are "good".

When I start the xruncounterscript without any other DSP hungry application running (like renoise or reaper with VSTs inside) I get the first xrun at
~98% (reproduced this twice), but if e.g. Renoise is running in parallel I can get the first xrun much earlier (30, 50, 70%, etc.), likely caused by VSTs that cause short peaks in the DSP load. Will have a look now if everything works as it did ~2 weeks before, otherwise I have to do trouble shooting again with your help.

This xrun issue is like a virus that comes back once in a while :lol:

User avatar
thetotalchaos
Established Member
Posts: 183
Joined: Mon Sep 29, 2014 8:29 pm
Contact:

Re: XRUNS ... but why?

Post by thetotalchaos »

lilith wrote:
Sun Mar 08, 2020 6:30 pm
That's not bad. :mrgreen: But will this work with alot of VST instruments?
Yes, it should. But you need to apply priorities to the VST as well. Guessing that you load them through Wine. If not, then in this low latency sytem state, its more likely to receive xruns from network activity (you should have a way to turn off networking while recording), than from extra audio plugin. But the secret is that this is a vanilla Archlinux installation, installed from scratch. With only the needed apps services and settings applied. Unfortunately i have tested this many times, and it doesn't work well, when i use Antergos or Manjaro. I guess there are already many undesired services, activated out of the box.
lilith wrote:
Sun Mar 08, 2020 6:30 pm
This xrun issue is like a virus that comes back once in a while :lol:
That is why you should use a stable distribution for your production machine. Like Debian stable. Although I am getting better performance on Archlinux, i am using Debian based distribution for my audio production needs.
The only unstable part of the system, should be the musician himself.!! :lol: :lol:
Check out my latest music album The girl with the stars in her eyes
https://totalchaos-music.bandcamp.com/a ... n-her-eyes

User avatar
lilith
Established Member
Posts: 1434
Joined: Fri May 27, 2016 11:41 pm
Location: bLACK fOREST
Contact:

Re: XRUNS ... but why?

Post by lilith »

I have Debian stable and I didn't install anything. But there was definitely something wrong, because the xruncounter script crashed with segfault. Only after installing the kxstudio default settings script it works again.

User avatar
thetotalchaos
Established Member
Posts: 183
Joined: Mon Sep 29, 2014 8:29 pm
Contact:

Re: XRUNS ... but why?

Post by thetotalchaos »

lilith wrote:
Sun Mar 08, 2020 9:30 pm
I have Debian stable and I didn't install anything. But there was definitely something wrong, because the xruncounter script crashed with segfault. Only after installing the kxstudio default settings script it works again.
Seems logical.In kxstudio-default-settings you have the proper system tuning, so you don't need to manually do anything more. You should use linux-image-rt-amd64 as your default kernel. You probably need to stop the pulseaudio service from loading with SystemD, and let Cadence handle it.
Check out my latest music album The girl with the stars in her eyes
https://totalchaos-music.bandcamp.com/a ... n-her-eyes

User avatar
TAERSH
Established Member
Posts: 170
Joined: Mon Feb 03, 2020 6:48 pm

Re: XRUNS ... but why?

Post by TAERSH »

Hi.

After doing some music switched to using plugin synthesizers only (no standalone synths used) some xruns happened from time to time. So, I started to read this topic almost complete. Doing /etc/init.d/rtirq status returned almost all processes/devices set to a real time priority of 50. Then I tried to execute the advice found in this topic. Resulted in a wrong version of chrt (being a symlink to busybox instead of a binary). After installing chrt binary I could apply new settings to the processes/devices.

This is how it looks now:

Code: Select all

root# /etc/init.d/rtirq status

  PID CLS RTPRIO  NI PRI %CPU STAT COMMAND	
 3584 FF      90   - 130  0.0 S    irq/64-snd_hda_	
 3587 FF      90   - 130  0.0 S    irq/66-snd_hda_	
    9 TS       -   0  19  2.0 S    ksoftirqd/0	
   20 TS       -   0  19  1.8 S    ksoftirqd/1	
   27 TS       -   0  19  1.7 S    ksoftirqd/2	
   34 TS       -   0  19  1.6 S    ksoftirqd/3	
   41 TS       -   0  19  1.3 S    ksoftirqd/4	
   48 TS       -   0  19  1.6 S    ksoftirqd/5	
   55 TS       -   0  19  1.7 S    ksoftirqd/6	
   62 TS       -   0  19  1.7 S    ksoftirqd/7	
   69 TS       -   0  19  1.8 S    ksoftirqd/8	
   76 TS       -   0  19  1.5 S    ksoftirqd/9	
   83 TS       -   0  19  1.4 R    ksoftirqd/10	
   90 TS       -   0  19  1.6 R    ksoftirqd/11	
  107 TS       -   0  19  0.0 S    irq/9-acpi	
  120 TS       -   0  19  0.0 S    irq/25-AMD-Vi	
  121 TS       -   0  19  0.0 S    irq/25-s-AMD-Vi	
  243 TS       -   0  19  0.0 S    irq/7-pinctrl_a	
  244 TS       -   0  19  0.0 S    irq/26-PCIe PME	
  245 TS       -   0  19  0.0 S    irq/26-aerdrv	
  246 TS       -   0  19  0.0 S    irq/26-s-aerdrv	
  247 TS       -   0  19  0.0 S    irq/27-PCIe PME	
  248 TS       -   0  19  0.0 S    irq/27-aerdrv	
  249 TS       -   0  19  0.0 S    irq/27-s-aerdrv	
  250 TS       -   0  19  0.0 S    irq/28-PCIe PME	
  251 TS       -   0  19  0.0 S    irq/28-aerdrv	
  252 TS       -   0  19  0.0 S    irq/28-s-aerdrv	
  253 TS       -   0  19  0.0 S    irq/30-PCIe PME	
  254 TS       -   0  19  0.0 S    irq/30-aerdrv	
  255 TS       -   0  19  0.0 S    irq/30-s-aerdrv	
  264 TS       -   0  19  0.0 S    irq/41-ahci[000	
  288 TS       -   0  19  0.0 S    irq/42-ahci[000	
  295 TS       -   0  19  0.0 S    irq/44-ahci[000	
  299 TS       -   0  19  0.0 S    irq/45-xhci_hcd	
  300 TS       -   0  19  0.0 S    irq/46-xhci_hcd	
  301 TS       -   0  19  0.0 S    irq/47-xhci_hcd	
  302 TS       -   0  19  0.0 S    irq/48-xhci_hcd	
  303 TS       -   0  19  0.0 S    irq/49-xhci_hcd	
  304 TS       -   0  19  0.0 S    irq/50-xhci_hcd	
  305 TS       -   0  19  0.0 S    irq/51-xhci_hcd	
  306 TS       -   0  19  0.0 S    irq/52-xhci_hcd	
  307 TS       -   0  19  0.0 S    irq/54-xhci_hcd	
  308 TS       -   0  19  0.0 S    irq/55-xhci_hcd	
  309 TS       -   0  19  0.0 S    irq/56-xhci_hcd	
  310 TS       -   0  19  0.0 S    irq/57-xhci_hcd	
  311 TS       -   0  19  0.0 S    irq/58-xhci_hcd	
  312 TS       -   0  19  0.0 S    irq/59-xhci_hcd	
  313 TS       -   0  19  0.0 S    irq/60-xhci_hcd	
  314 TS       -   0  19  0.0 S    irq/61-xhci_hcd	
  315 TS       -   0  19  0.0 S    irq/1-i8042	
  316 TS       -   0  19  0.0 S    irq/8-rtc0	
 3614 TS       -   0  19  0.0 S    irq/69-ccp-1	
 3841 TS       -   0  19  0.0 S    irq/71-radeon	
root#
Looks good?

This is the current config:

Code: Select all

# IRQ thread service names
# (space separated list, from higher to lower priority).
# RTIRQ_NAME_LIST="rtc snd usb i8042" # old
#RTIRQ_NAME_LIST="snd usb i8042"
RTIRQ_NAME_LIST="snd"

# Highest priority.
RTIRQ_PRIO_HIGH=90

# Priority decrease step.
RTIRQ_PRIO_DECR=5

# Lowest priority.
RTIRQ_PRIO_LOW=51

# Whether to reset all IRQ threads to SCHED_OTHER.
#RTIRQ_RESET_ALL=0
RTIRQ_RESET_ALL=1

# On kernel configurations that support it,
# which services should be NOT threaded
# (space separated list).
#RTIRQ_NON_THREADED="rtc snd"
RTIRQ_NON_THREADED="rtc snd"

# Process names which will be forced to the
# highest realtime priority range (99-91)
# (space separated list, from highest to lower priority).
# RTIRQ_HIGH_LIST="timer"
Now I need some advice on the settings of JACK. I'm using QJackCtl.
Here's current settings:

Real time: on
Priority: 5 (default)
Sample Rate: 44100
Frames/Period: 1024
Period/Buffer: 2
Latency: 46.4ms
MIDI-Driver: Seq

Soft Mode: on
Audio: Duplex
Dither: None

Max Port: 256
Timeout: 500ms

Support ALSA Sequencer: on
DBus Interface: off
JACK DBus Interface: off


Processor: AMD Ryzen 5 2600X Six-Core Processor

How to optimize these settings?

Thanks.

User avatar
lilith
Established Member
Posts: 1434
Joined: Fri May 27, 2016 11:41 pm
Location: bLACK fOREST
Contact:

Re: XRUNS ... but why?

Post by lilith »

If irq/64-snd_hda_ is your soundcard /interface, yes that's ok as it is.

Set the priority of Jack to ~80 and run the xruncounterscript to see when you get the first xruns;

https://github.com/Gimmeapill/xruncounter

There's also this neat script to check your system:

https://github.com/raboof/realtimeconfigquickscan

Concerning the other settings: https://wiki.linuxaudio.org/wiki/list_o ... _interface

User avatar
lilith
Established Member
Posts: 1434
Joined: Fri May 27, 2016 11:41 pm
Location: bLACK fOREST
Contact:

Re: XRUNS ... but why?

Post by lilith »

This command gives you all RT threads:

Code: Select all

ps -eLo rtprio,cls,pid,pri,nice,cmd | grep "FF" | sort -r

User avatar
TAERSH
Established Member
Posts: 170
Joined: Mon Feb 03, 2020 6:48 pm

Re: XRUNS ... but why?

Post by TAERSH »

Thanks for the info @lilith

So, here's the output of ./realTimeConfigQuickScan.pl
./realTimeConfigQuickScan.pl
== GUI-enabled checks ==
Checking if you are root... yes - not good
You are running this script as root. Please run it as a regular user for the most reliable results.
Checking filesystem 'noatime' parameter... 5.0.21 kernel - good
(relatime is default since 2.6.30)
cat: /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor: Datei oder Verzeichnis nicht gefunden
cat: /sys/devices/system/cpu/cpu1/cpufreq/scaling_governor: Datei oder Verzeichnis nicht gefunden
cat: /sys/devices/system/cpu/cpu10/cpufreq/scaling_governor: Datei oder Verzeichnis nicht gefunden
cat: /sys/devices/system/cpu/cpu11/cpufreq/scaling_governor: Datei oder Verzeichnis nicht gefunden
cat: /sys/devices/system/cpu/cpu2/cpufreq/scaling_governor: Datei oder Verzeichnis nicht gefunden
cat: /sys/devices/system/cpu/cpu3/cpufreq/scaling_governor: Datei oder Verzeichnis nicht gefunden
cat: /sys/devices/system/cpu/cpu4/cpufreq/scaling_governor: Datei oder Verzeichnis nicht gefunden
cat: /sys/devices/system/cpu/cpu5/cpufreq/scaling_governor: Datei oder Verzeichnis nicht gefunden
cat: /sys/devices/system/cpu/cpu6/cpufreq/scaling_governor: Datei oder Verzeichnis nicht gefunden
cat: /sys/devices/system/cpu/cpu7/cpufreq/scaling_governor: Datei oder Verzeichnis nicht gefunden
cat: /sys/devices/system/cpu/cpu8/cpufreq/scaling_governor: Datei oder Verzeichnis nicht gefunden
cat: /sys/devices/system/cpu/cpu9/cpufreq/scaling_governor: Datei oder Verzeichnis nicht gefunden
Checking CPU Governors... CPU 0: '' CPU 1: '' CPU 10: '' CPU 11: '' CPU 2: '' CPU 3: '' CPU 4: '' CPU 5: '' CPU 6: '' CPU 7: '' CPU 8: '' CPU 9: '' - not good
Set CPU Governors to 'performance' with 'cpupower frequency-set -g performance' or 'cpufreq-set -c <cpunr> -g performance' (Debian/Ubuntu)
See also: http://linuxmusicians.com/viewtopic.php?f=27&t=844
Checking swappiness... 10 - good
Checking for resource-intensive background processes... none found - good
Checking checking sysctl inotify max_user_watches... >= 524288 - good
Checking access to the high precision event timer... readable - good
Checking access to the real-time clock... readable - good
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... found - good
Checking if kernel system timer is high-resolution... found - good
Checking kernel support for tickless timer... found - good
== Other checks ==
Checking filesystem types... ok.
** Set $SOUND_CARD_IRQ to the IRQ of your soundcard to enable more checks.
Find your sound card's IRQ by looking at '/proc/interrupts' and lspci.
What to do about the scaling governor?

User avatar
lilith
Established Member
Posts: 1434
Joined: Fri May 27, 2016 11:41 pm
Location: bLACK fOREST
Contact:

Re: XRUNS ... but why?

Post by lilith »

Sorry, I was busy today.

You have to set the governor to performance, which is described in this thread

viewtopic.php?f=27&t=844

That's one of the most important points.

User avatar
TAERSH
Established Member
Posts: 170
Joined: Mon Feb 03, 2020 6:48 pm

Re: XRUNS ... but why?

Post by TAERSH »

Thanks.

When I'm following this advice after installing cpufrequtils_008-1build1_amd64.deb I'm getting these results/errors:
root# cpufreq-set -g performance
Beim Einstellen ist ein Fehler aufgetreten. Typische Fehlerquellen sind:
- nicht ausreichende Rechte (Administrator)
- der Regler ist nicht verfügbar bzw. nicht geladen
- die angegebene Taktik ist inkorrekt
- eine spezifische Frequenz wurde angegeben, aber der Regler 'userspace'
kann entweder hardwarebedingt nicht genutzt werden oder ist nicht geladen
root#
In terminal more /proc/cpuinfo | grep MHz returns:
root# more /proc/cpuinfo | grep MHz
cpu MHz : 3973.923
cpu MHz : 3940.831
cpu MHz : 3908.387
cpu MHz : 3972.074
cpu MHz : 3940.242
cpu MHz : 3983.691
cpu MHz : 3958.988
cpu MHz : 3990.269
cpu MHz : 3959.312
cpu MHz : 3980.359
cpu MHz : 3942.171
cpu MHz : 3942.971
root#
So, on AMD Ryzen 5 2600X (defined at 3600 MHz up to 4 GHz) this should be Ok. Even without having the governor setting cpu to performance. I disabled already AMD 'quiet' mode in BIOS.

Again thanks. I think it's now all setup to best performance as possible.
Maybe I'm wrong, but I didn't notice yet these xruns somehow seem effecting the export of a song?

User avatar
lilith
Established Member
Posts: 1434
Joined: Fri May 27, 2016 11:41 pm
Location: bLACK fOREST
Contact:

Re: XRUNS ... but why?

Post by lilith »

Not sure about your error messages. IIRC I set the cpu frequency for every core individually. But if it's maximum all the time in your case, maybe it will also work how you did it.

Also not sure about rendering. I think that xruns are not crucial for rendering, but Qtractor does render in real time, right? So, maybe here it plays a role and you can get xruns.

Can anyone comment on this?

User avatar
bluebell
Established Member
Posts: 1426
Joined: Sat Sep 15, 2012 11:44 am
Location: Saarland & Frankfurt, Germany

Re: XRUNS ... but why?

Post by bluebell »

TAERSH wrote:
Thu Mar 12, 2020 1:32 am
Thanks.

When I'm following this advice after installing cpufrequtils_008-1build1_amd64.deb I'm getting these results/errors:
root# cpufreq-set -g performance
Beim Einstellen ist ein Fehler aufgetreten. Typische Fehlerquellen sind:
- nicht ausreichende Rechte (Administrator)
- der Regler ist nicht verfügbar bzw. nicht geladen
- die angegebene Taktik ist inkorrekt
- eine spezifische Frequenz wurde angegeben, aber der Regler 'userspace'
kann entweder hardwarebedingt nicht genutzt werden oder ist nicht geladen
root#

Code: Select all

cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_governors
Is there an entry named "performance"? Probably not. So it can't be set.

Code: Select all

root@regen:~# cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_governors
performance powersave
root@regen:~# cpufreq-set -g performance
root@regen:~# cpufreq-set -g superdupergovernor
Beim Einstellen ist ein Fehler aufgetreten. Typische Fehlerquellen sind:
- nicht ausreichende Rechte (Administrator)
- der Regler ist nicht verfügbar bzw. nicht geladen
- die angegebene Taktik ist inkorrekt
- eine spezifische Frequenz wurde angegeben, aber der Regler 'userspace'
  kann entweder hardwarebedingt nicht genutzt werden oder ist nicht geladen
Linux – MOTU UltraLite AVB – Qtractor – https://soundcloud.com/suedwestlicht

User avatar
lilith
Established Member
Posts: 1434
Joined: Fri May 27, 2016 11:41 pm
Location: bLACK fOREST
Contact:

Re: XRUNS ... but why?

Post by lilith »

I'm still getting sporadic audible xruns from time to time. The issue started somewhere ~end of February. Even in Renoise I hear glitches sometimes which never happened before. On 14 February I installed the rtirq-init script. Possibly the problem started at that day, but I'm not sure.

I'm running the standard kernel: Linux marco 4.19.0-8-amd64 #1 SMP Debian 4.19.98-1 (2020-01-26) x86_64 GNU/Linux

Do I need a PREEMPT RT or PREEMPT kernel in order to use rtirq-init?
see also this post here from totalchaos: viewtopic.php?p=115773#p115773
edit: This answers some questions already: https://wiki.linuxaudio.org/wiki/system_configuration

The parameters from rtirq-init are located in /etc/default/rtirq and look like:

Code: Select all

# IRQ thread service names
# (space separated list, from higher to lower priority).
# RTIRQ_NAME_LIST="rtc snd usb i8042" # old
RTIRQ_NAME_LIST="xhci_hcd"

# Highest priority.
RTIRQ_PRIO_HIGH=95

# Priority decrease step.
RTIRQ_PRIO_DECR=5

# Lowest priority.
RTIRQ_PRIO_LOW=51

# Whether to reset all IRQ threads to SCHED_OTHER.
RTIRQ_RESET_ALL=1

# On kernel configurations that support it,
# which services should be NOT threaded 
# (space separated list).
RTIRQ_NON_THREADED="rtc snd"
"xhci_hcd" is my external soundcard. My internal sound is blacklisted.


Does anybody know why enp2s0 still has RT priorities and does this cause a problem?

Code: Select all

/etc/init.d/rtirq status

  PID CLS RTPRIO  NI PRI %CPU STAT COMMAND	
  137 FF      95   - 135  1.3 S    irq/27-xhci_hcd	
  186 FF      94   - 134  0.0 S    irq/29-xhci_hcd	
  658 FF      50   -  90  0.1 S    irq/26-enp2s0	
And listing all TR threads gives me:

Code: Select all

marco@marco:/etc/init.d$ ps -eLo rtprio,cls,pid,pri,nice,cmd | grep "FF" | sort -r
     -  TS  8085  19   0 grep FF
    99  FF    45 139   - [watchdogd]
    99  FF    26 139   - [migration/3]
    99  FF    21 139   - [migration/2]
    99  FF    16 139   - [migration/1]
    99  FF    12 139   - [migration/0]
    95  FF  2600 135   - /home/marco/Schreibtisch/renoise
    95  FF  2600 135   - /home/marco/Schreibtisch/renoise
    95  FF  2600 135   - /home/marco/Schreibtisch/renoise
    95  FF  2600 135   - /home/marco/Schreibtisch/renoise
    95  FF  2600 135   - /home/marco/Schreibtisch/renoise
    95  FF  2600 135   - /home/marco/Schreibtisch/renoise
    95  FF  2600 135   - /home/marco/Schreibtisch/renoise
    95  FF  2600 135   - /home/marco/Schreibtisch/renoise
    95  FF  2600 135   - /home/marco/Schreibtisch/renoise
    95  FF  2600 135   - /home/marco/Schreibtisch/renoise
    95  FF  2600 135   - /home/marco/Schreibtisch/renoise
    95  FF  2600 135   - /home/marco/Schreibtisch/renoise
    95  FF  2600 135   - /home/marco/Schreibtisch/renoise
    95  FF  2600 135   - /home/marco/Schreibtisch/renoise
    95  FF  2600 135   - /home/marco/Schreibtisch/renoise
    95  FF  2600 135   - /home/marco/Schreibtisch/renoise
    95  FF   137 135   - [irq/27-xhci_hcd]
    94  FF   186 134   - [irq/29-xhci_hcd]
    80  FF  2562 120   - /usr/bin/jackdbus auto
    75  FF  2600 115   - /home/marco/Schreibtisch/renoise
    75  FF  2564 115   - /usr/bin/a2jmidid dbus
    71  FF  2600 111   - /home/marco/Schreibtisch/renoise
    71  FF  2600 111   - /home/marco/Schreibtisch/renoise
    71  FF  2600 111   - /home/marco/Schreibtisch/renoise
    71  FF  2600 111   - /home/marco/Schreibtisch/renoise
    71  FF  2600 111   - /home/marco/Schreibtisch/renoise
    71  FF  2600 111   - /home/marco/Schreibtisch/renoise
    71  FF  2600 111   - /home/marco/Schreibtisch/renoise
    71  FF  2600 111   - /home/marco/Schreibtisch/renoise
    71  FF  2600 111   - /home/marco/Schreibtisch/renoise
    71  FF  2600 111   - /home/marco/Schreibtisch/renoise
    71  FF  2600 111   - /home/marco/Schreibtisch/renoise
    71  FF  2600 111   - /home/marco/Schreibtisch/renoise
    71  FF  2600 111   - /home/marco/Schreibtisch/renoise
    71  FF  2600 111   - /home/marco/Schreibtisch/renoise
    71  FF  2600 111   - /home/marco/Schreibtisch/renoise
    71  FF  2600 111   - /home/marco/Schreibtisch/renoise
    50  FF   658  90   - [irq/26-enp2s0]
     1  FF   192  41   - [i915/signal:6]
     1  FF   191  41   - [i915/signal:2]
     1  FF   190  41   - [i915/signal:1]
     1  FF   189  41   - [i915/signal:0]
Reported xruns come cleary from Renoise. IMO everything looks fine, is there anything I can test / look at? :?
I also checked the journal at the times when xruns occured, but there are no entries at that times.

User avatar
TAERSH
Established Member
Posts: 170
Joined: Mon Feb 03, 2020 6:48 pm

Re: XRUNS ... but why?

Post by TAERSH »

After being busy creating my own .sf2 files (120 from the Yamaha Synthesizers plus around 10 from samples of my recorded voice) and doing some songs using some of these spounds still some xruns appear. All that rtirq setup stuff doesn't seem to have any notable positive effects on my machine. Though, those xruns still seem to disappear or at least appearing very very rarely after working for some time on a song. Since Qtractor exports a song at around 1.5x speed xruns doesn't seem to have any effect on that issue. So far, so good.

The negative side effects on all that settings was trouble when doing video editing. Overlaying videos/graphics won't render without to flicker. So I almost returned to my basic settings on all that stuff, as video is also an important task of my computer work. As yet I seem to have settings I can live with.

Wasted enough time on that, so (at least on my side) closed...

Thanks for all the hints and help.

Post Reply