LinuxMusicians

Thanks Rui!

Ok, so: no HW issue and MX linux is supposed to be based on debian stable = you can very likely skip the avlinux step. -> before jumping on debian testing for the newer mesa, it could still be worth installing another window manager, select it from the lightdm greeter and see how things go with Reno...

As merlyn said. If you don't have irq threading activated, all bets are off. Regarding that graphic issue: why don't you just boot avlinux from usb and try the renoise demo from there? This should at least tell you if it's a hardware issue or not. You have a working debian system, you shouldn't need...

Nice one, even Taktik doesn't have a clue ;-) I wouldn't bet on the session manager, I was just meaning to install a minimal window manager and test the performance (after making sure all xfce related stuff is not running - preferably after reboot). This is the easiest thing to try without screwing ...

Without compton I get an extreme load of xruns in Renoise, which is somehow related to how Renoise is drawing its GUI. That is even weirder, you shouldn't need a compositor to run Renoise, it is the leanest thing around. (I have no problem using it as a DAW with Guitarix at 2-3 ms latency on a 5y o...

Ah, yes, rtkit is a dependency of pulseaudio, probably better not touch it then.

For the IRQ threads:yes you should see them in the process list (I usually check with htop).
The behavior of RT kernels is to have it enabled by default, if not you can use the "threadirqs" boot parameter.

A few shots in the dark here, after looking at your pastebin: - rtkit is abandoned for 5 years and running at RTprio 99, right in the danger zone. I wouldn't trust that nowadays, maybe it interferes with things that are now better done by the kernel. Did you try disabling it? - Is IRQ threading even...

One idea here: Try to get back to "standard" buffersizes, so something like 512 instead of 528. I don't know about Reaper but this seems to cause problems with some applications (on my setup, Ardour didn't like it for example) By the way, if anyone want to take over the github project or j...

I don't think you need to re-implement something from scratch for switching between jack patchbay presets from a keyboard shortcut. You can do that with qjackctl by using command line switches: " -a, --active-patchbay=[path] Set active patchbay definition file" Then it should be just about...

Thanks for double checking. So it looks like another configuration setting that could be detected better (although this is really a corner case) - at least we know about it. On my side I didn't have much time for more testing (or to look at the jack API), but I created the project on github: https:/...

Looking at your results I'd guess your processor is 2.6 GHz. That seems to be the most important factor in how many circles or cycles it takes to cause an Xrun. Quite close ;-) That's an old i5 3317u (Ivy Bridge) than can hardly sustain the max turbo frequency of 2.4 GHz. ...And I think I managed t...

xruncounter is very useful, thanks once more for the great job Tramp! And thanks merlyn + Drumfix for the tips about buffersizes and circles: after the tenth read this is finally making it through my thick skull ;-) So let's join the party: Here are some preliminary results on my 5+ y old notebook (...

No idea what is going on in your case, but that's probably worth reporting:
https://ardour.org/how_to_report_a_bug

Edit: Don't forget to read this as well, or you might end up disappointed.
https://community.ardour.org/support_expectations

For Arch users, here's a quick & dirty pkgbuild:
https://aur.archlinux.org/packages/kapitonov-plugins-pack-lv2-git

Ah, ok. I see very well where's you've been with those resamplers. I'm not going down that rabbit hole again (at least in the current state of technology) - life is just too short ;-) If the need really arise, I'd rather drop Guitarix and use my analog signal chain (I hope Tramp doesn't read this :D...