#rtcirqus — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #rtcirqus, aggregated by home.social.
-
And another release of #rtcirqus. I added logging when a device gets disconnected and rtcirqus doesn't bail out anymore when a device gets disconnected on a #RaspberryPi 5/500/500+.
https://codeberg.org/autostatic/rtcirqus/releases/tag/v0.2.4
-
New rtcirqus release! Added some fixes so rtcirqus also runs correctly on a Raspberry Pi 5/500/500+ and probably older models too.
https://codeberg.org/autostatic/rtcirqus/releases/tag/v0.2.3
-
-
The main difference between #rtcirqus and rtirq is that rtcirqus allows you to set the real-time priority of a thread based on ALSA card names. rtirq works differently, it sets the real-time priority based on kernel module names. So with rtcirqus you can be sure the desired audio interface gets the desired real-time prio, with rtirq you're prioritising all the devices that make use of a specific kernel module (xhci_hcd, snd_hda_intel)
/4
-
Regarding threaded IRQs, enabling those by itself doesn't change anything. You will need to configure those threaded IRQs after you've enabled them. Tools that can do this are #rtcirqus or rtirq. You could also do this manually by using the `chrt` command on the threaded IRQ process.
Modern systems use MSI(-X) interrupts though (Message Signaled Interrupts) so shared IRQs should be something of the past. On those systems there's very little gain in prioritising threaded IRQs.
/3
-
A new version of #rtcirqus is available. The only change is that I added a -v|--version CLI option to quickly see which version of rtcirqus you're running.
https://codeberg.org/autostatic/rtcirqus/releases/tag/v0.2.2
-
@ambientspace You don't need a low-latency or realtime kernel unless you're doing audio that demands very low round-trip latencies (below 10ms).
Rtirq can help but I don't think it can deal with modern systems using Message Signaled Interrupts (MSI or MSI-X). For systems with MSI-X interrupts #rtcirqus might be an alternative.
As for Milliseconds, it relies on an underlying tool, #rtcqs that in its turn links to wiki.linuxaudio.org. It's command line only but might come in handy sometimes.
-
Now what does rtcirqus actually do?
To answer that question let’s assume the following: Basically all components of a desktop computer or a laptop have an IRQ. Let’s say IRQs are some sort of communication lines between the brains of your computer (the CPU) and those components. All these communication lines are more or less the same as in, none of […]
https://autostatic.com/2025/10/21/now-what-does-rtcirqus-actually-do/ -
New rtcirqus 0.2.1 release. Fixed an error with sorting the list of IRQs that are used for Message Signaled Interrupts (MSI).
-
New release available of #rtcirqus, my real-time prioritisation tool: https://codeberg.org/autostatic/rtcirqus/releases/tag/v0.2.0
Biggest changes:
- Maximum real-time priority that rtcirqus assigns can be set.
- Steps between real-time priorities can be set.
- It is now possible to give rtcirqus a list of devices and rtcirqus will assign real-time priorities to these devices in the order they are given.
- Updated README with a new paragraph on how to use the configuration file. -
Implemented a routine in #rtcirqus to allow for custom ordering of audio devices to be prioritised. Custom ordering can be done now by adding a comma separated list of device names as a value to the `prio_list` keyword in the rtcirqus configuration file.
-
Worked a bit more on #rtcirqus.
* Added two new options that can be set in the configuration file: the maximum real-time priority and the interval between the priorities being set.
* My internal mic of my laptop did not get prioritized, fixed that too. -
While listening to "604" from #Ladytron I basically completely refactored my #rtcirqus project. Also squashed two small bugs. I think it's getting ready for prime time.
-
Just tagged v0.0.5 for rtcirqus and uploaded it to PyPi.
This means rtcirqus is ready for more testing. So if you feel audacious and are curious about a tool that automatically increases or decreases rtprios for audio interfaces upon plugging in or out those devices then you might want to check out the project. Any help or feedback is much appreciated!
Project page: https://codeberg.org/autostatic/rtcirqus
-
Did some work on https://codeberg.org/autostatic/rtcirqus/issues/3
If anyone would like to help out with testing rtcirqus then that would be awesome!
rtcirqus (Real-Time Configuration IRQ Udev Service) is a small Python script with an accompanying udev rules file that automatically assigns a higher real-time priority to IRQs being used by audio interfaces. It might be an alternative to rtirq¹ or udev-rtirq².
¹ https://github.com/rncbc/rtirq
² https://github.com/jhernberg/udev-rtirq -
Looking at my #rtcirqus project. I think I just found how I could fix finding the right IRQ for USB interfaces. I've set myself a small but doable goal for this project: publish an initial release before #LAC2025.