Code: Select all
GRUB_CMDLINE_LINUX="threadirqs"
Moderators: MattKingUSA, khz
Code: Select all
GRUB_CMDLINE_LINUX="threadirqs"
Code: Select all
echo -e "blacklist snd_hda_intel" | sudo tee -a /etc/modprobe.d/HDAblacklist.conf
Among other things I switch off the onboard soundcard in the Bios.lilith wrote:I just saw that my internal intel onboard soundcard was running with RT priority of 90 (but was never used) compared to my interface which was running at 80.
Code: Select all
uname -a
Could you explain how you found the RT priorities and driver names of your devices please? I just disabled my internal soundcard after reading this (since I don't use it), but I would like to see if my graphics card's HDMI audio is problematic as well.lilith wrote: ↑Sat Feb 15, 2020 6:03 pm Oh man
I just saw that my internal intel onboard soundcard was running with RT priority of 90 (but was never used) compared to my interface which was running at 80.
I blacklisted the internal card and all my xrun issues disappeared!
-->Code: Select all
echo -e "blacklist snd_hda_intel" | sudo tee -a /etc/modprobe.d/HDAblacklist.conf
I make music as Tenaba! Bandcamp
The command iscrownbird wrote: ↑Fri Feb 28, 2020 4:01 pmCould you explain how you found the RT priorities and driver names of your devices please? I just disabled my internal soundcard after reading this (since I don't use it), but I would like to see if my graphics card's HDMI audio is problematic as well.lilith wrote: ↑Sat Feb 15, 2020 6:03 pm Oh man
I just saw that my internal intel onboard soundcard was running with RT priority of 90 (but was never used) compared to my interface which was running at 80.
I blacklisted the internal card and all my xrun issues disappeared!
-->Code: Select all
echo -e "blacklist snd_hda_intel" | sudo tee -a /etc/modprobe.d/HDAblacklist.conf
Code: Select all
/etc/init.d/rtirq status
Code: Select all
PID CLS RTPRIO NI PRI %CPU STAT COMMAND
153 FF 85 - 125 0.0 S irq/16-ehci_hcd
182 FF 85 - 125 1.7 S irq/28-xhci_hcd
190 FF 84 - 124 0.0 S irq/23-ehci_hcd
197 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
146 FF 50 - 90 0.0 S irq/18-i801_smb
195 FF 50 - 90 0.0 S irq/26-ahci[000
213 FF 50 - 90 0.1 S irq/30-i915
380 FF 50 - 90 0.0 S irq/31-mei_me
679 FF 50 - 90 0.2 S irq/27-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
You could try disabling pulseaudio or set the profile of the configuration to 'off' in pavucontrol instead.lilith wrote: ↑Sat Feb 15, 2020 6:03 pm Oh man
I just saw that my internal intel onboard soundcard was running with RT priority of 90 (but was never used) compared to my interface which was running at 80.
I blacklisted the internal card and all my xrun issues disappeared!
-->Code: Select all
echo -e "blacklist snd_hda_intel" | sudo tee -a /etc/modprobe.d/HDAblacklist.conf
If pulseaudio isnt't configured to use an audio adapter but jack then there are no interrupts generated by Pulseaudio and it is not very likely that it causes xruns. Maybe Pulseaudio used the internal soundcard. Blacklisting is one option to avoid those interrupts and I think it can't hurt blacklisting an unused internal soundcard. I did it as well.
Linux – MOTU UltraLite AVB – Qtractor – http://suedwestlicht.saar.de/
Code: Select all
marco@marco:~/src$ ./xruncounter
******************** SYSTEM CHECK *********************
Segmentation fault
Thanks for that! I just saw that the default where not installed on my system and it just solved some problems for me that started yesterday ... Maybe some update changed / overwritten some settings.thetotalchaos wrote: ↑Sun Feb 16, 2020 4:06 pm You don't need to configure manually your system for audio performance. You just need to install kxstudio-default-settings. Just install it, reboot and check out if the realtimeconfigquickscan is all green. What else i can advice you? You don't need swap partition, but having a realtime linux is a huge benefit. You can test if your kernel is good withIf you have PREEMPT (or PREEMPT RT) you are fine.Code: Select all
uname -a
What else? don't use 3D effects, dont use internet or pereferals like scanner or printer, while playing audio. Check your BIOS settings. You don't need a video acceleration, and the battery saver must be turned off, while you are on Ardour for example.
Additionally i am sharing some good manuals, including a topic i made, to make Cadence and Pulseaudio like each other more
https://librazik.tuxfamily.org/doc2/manuel
https://wiki.archlinux.org/index.php/Professional_audio
https://www.linuxmusicians.com/viewtopi ... 27&t=17780
PS (edited): I saw you fixed it, by giving good values for realtime and blacklisting your internal sound card. My advice is to disable it from BIOS itself, if you are allowed.
I will try to summarize the topic of realtime preemption in a few sentiencies. If your linux kernel does not have PREEMPT value (in the output of uname -a) , this whole realtime preemption does not work for you and your system is not optimised for audio performance, the way it can and should be. The realtime preemption value is from 0 to 100 if you have a true realtime kernel ( PREEMPT RT), but from 0 to 90 if you kernel is just PREEMPT (like linux-lowlatency or the default linux on Archlinux). The fun part is with values above 50. A values between 90 to 100 are giving these processes a capability to interrupt other processes. Your sound card, gets the highest value, often 99 or 95 (check your /etc/security/limits.conf or /etc/security/limits.d/audio.conf). The value for Jack should be second in the queue, after the soundcard. 89 is a good value for PREEMPT RT, but because on PREEMPT kernels the highest value is 89, its often recommended a value of 70 for Jack. Further below you can give values for your MIDI peripheral and other apps, by giving values that are -5 below. You can also give RT values to Wine and programs that run on Wine, but you need to use wine-rt on your system. I myself am using the prepared lines, that i am taking by running Festige and copying a well prepared execute lines for the VST plugins. It makes a difference, more that you can assume.
Happy hacking,
Totalchaos, a Linux Audio veteran
I read somewhere (also here) that the latest kernels are fine for RT optimization even if they are not PREEMPT.thetotalchaos wrote: ↑Sun Feb 16, 2020 4:06 pm You don't need to configure manually your system for audio performance. You just need to install kxstudio-default-settings. Just install it, reboot and check out if the realtimeconfigquickscan is all green. What else i can advice you? You don't need swap partition, but having a realtime linux is a huge benefit. You can test if your kernel is good withIf you have PREEMPT (or PREEMPT RT) you are fine.Code: Select all
uname -a
What else? don't use 3D effects, dont use internet or pereferals like scanner or printer, while playing audio. Check your BIOS settings. You don't need a video acceleration, and the battery saver must be turned off, while you are on Ardour for example.
Additionally i am sharing some good manuals, including a topic i made, to make Cadence and Pulseaudio like each other more
https://librazik.tuxfamily.org/doc2/manuel
https://wiki.archlinux.org/index.php/Professional_audio
https://www.linuxmusicians.com/viewtopi ... 27&t=17780
PS (edited): I saw you fixed it, by giving good values for realtime and blacklisting your internal sound card. My advice is to disable it from BIOS itself, if you are allowed.
I will try to summarize the topic of realtime preemption in a few sentiencies. If your linux kernel does not have PREEMPT value (in the output of uname -a) , this whole realtime preemption does not work for you and your system is not optimised for audio performance, the way it can and should be. The realtime preemption value is from 0 to 100 if you have a true realtime kernel ( PREEMPT RT), but from 0 to 90 if you kernel is just PREEMPT (like linux-lowlatency or the default linux on Archlinux). The fun part is with values above 50. A values between 90 to 100 are giving these processes a capability to interrupt other processes. Your sound card, gets the highest value, often 99 or 95 (check your /etc/security/limits.conf or /etc/security/limits.d/audio.conf). The value for Jack should be second in the queue, after the soundcard. 89 is a good value for PREEMPT RT, but because on PREEMPT kernels the highest value is 89, its often recommended a value of 70 for Jack. Further below you can give values for your MIDI peripheral and other apps, by giving values that are -5 below. You can also give RT values to Wine and programs that run on Wine, but you need to use wine-rt on your system. I myself am using the prepared lines, that i am taking by running Festige and copying a well prepared execute lines for the VST plugins. It makes a difference, more that you can assume.
Happy hacking,
Totalchaos, a Linux Audio veteran
20ms you say. Check this screenshot from my Archlinux with gnome-shell. Think of this screenshot as a Linux Audio porn