Are there any plans to support native PipeWire in Reaper?

[xeityrj]

Originally Posted by chmaha

You can definitely try. However, I just know that the default Arch/Majaro (etc) kernels are ready to go and that Ubuntu requires low-latency/liquorix for best results. Debian doesn't have a low-latency option in the repositories therefore I jump straight to liquorix.

The thing I like to repeat is that, sure, no modifications might allow you to record a handful of tracks. But what about when you want to add a sampler, some reverb(s), yabridged plugins etc? Best to get your system ready for any eventuality with the only limits being your own particular CPU, RAM and HD specifications.

Others say start with no modifications but I'd hate to lose a critical take because I didn't optimize my computer as well as I could have done. Don't forget to run some stress tests too to make sure that the x-run counter really does remain at zero.

Greetings! I noticed an update to your Debian pro audio guide, so I've tested (briefly) the stock Ubuntu kernel with "preempt=full" as a kernel parameter, and was surprised to see a match in performance in terms of xruns, comparing it to the low-latency kernel. Thanks

[chmaha]

Originally Posted by xeityrj

Greetings! I noticed an update to your Debian pro audio guide, so I've tested (briefly) the stock Ubuntu kernel with "preempt=full" as a kernel parameter, and was surprised to see a match in performance in terms of xruns, comparing it to the low-latency kernel. Thanks

Good to hear! I suppose it has been technically possible since Ubuntu 21.10 (with kernels >=5.12) but my only experience recently has been with Debian 12. I guess depends when the CONFIG_PREEMPT_DYNAMIC compile option was set by the Ubuntu team...

[sonicman]

Originally Posted by chmaha

Debian Pro Audio Guide: https://github.com/chmaha/DebianProAudio

I have popOS 22.04 which uses systemd-boot instead of grub.

I can't complete the two below items in your guide.

4. Kernel tweaks
5. Swappiness: "/etc/sysctl.d/99-sysctl.conf" E166: Can't open linked file for writing

Thanks for the guide. It's a great help.

Note: Im not experiencing any issues but it's always better to have a nicely configured system.

[chmaha]

Originally Posted by sonicman

I have popOS 22.04 which uses systemd-boot instead of grub.

I can't complete the two below items in your guide.

4. Kernel tweaks
5. Swappiness: "/etc/sysctl.d/99-sysctl.conf" E166: Can't open linked file for writing

Thanks for the guide. It's a great help.

Note: Im not experiencing any issues but it's always better to have a nicely configured system.

OK, I'll look into it soon. I've only ever used grub...

[s wave]

ALSA (asoundlib)interacts with the Kernel - but it is not ABSOLUTELY necessary? I think it was everyone just defaults to it; because it works. Many make their own method.

TinyALSA that interfaces with kernel using ioctl WITHOUT help of alsa-lib: https://github.com/tinyalsa/tinyalsa

here is a little thread... with a few good tidbits... https://handmade.network/forums/t/77...x_without_alsa

[krahosk]

Originally Posted by chmaha

OK, I'll look into it soon. I've only ever used grub...

There's another top tier distro that doesn't use grub: EndeavourOS.

[chmaha]

Originally Posted by krahosk

There's another top tier distro that doesn't use grub: EndeavourOS.

I'll test in a VM at some point but the following should work for you (from the EndeavourOS installation notes):

Copy and paste:

preempt=full threadirqs cpufreq.default_governor=performance

into the file /etc/kernel/cmdline. Then run:

sudo reinstall-kernels

which is the equivalent of the update-grub command. If it works for you, I'll add the instructions to both of my guides.

[xeityrj]

Originally Posted by chmaha

Good to hear! I suppose it has been technically possible since Ubuntu 21.10 (with kernels >=5.12) but my only experience recently has been with Debian 12. I guess depends when the CONFIG_PREEMPT_DYNAMIC compile option was set by the Ubuntu team...

Whats's up! I've also tried your Arch guide on Manjaro - it seemed to be done easier than Debian one, because it didn't left no unsitisfied "rtcqs" points! In Ubuntu, I had to refer to linux audio website from rtcqs to satisfy (if I recall it correctly) the last point, which is "Power Management", Also there was something else unsitisfied besides "Power Management", but I don't recall what it was, and if is important (probably Filesystems).
In Manjaro everything worked easily right away! I didn't do the Spectre/Meltdown because I'm a little afraid to do it after getting acquainted on the topic, although I think it could give quite significant increase in performance.

Anyway, I also tested my computer's performance in Reaper on Windows and Manjaro using low latencies by playing back and audio file and measuring how many ReaEQ instances I could drop on the track without audio dropouts/glitches and being able to tweak any of them. And damn, Manjaro outperformed Windows! Especially with ALSA, the difference was significant. Not such a noticable difference using higher latencies (with Jack) though, sometimes it seemed to perform quite equally. In general, I'm very happy about my switch. Both Linux and Reaper gave my laptop a new life. I had to learn both (didn't quite learn Linux tho, still doing everything from GUI), and Reaper is fantastic. Used to work in Ableton before. Today tried it again - shocked about how much less efficient it was.

Thank you again for your guides. Cheers!

btw, regarding "Power Management" - in both Ubuntu and Manjaro after performing "sudo make install" command it said that there is no such command as "make". In Ubuntu I manually downloaded the udev rule from github, moved it to an appropriate folder, and used commands from linuxaudio to reload udev. In Manjaro it worked out by itself, idk how. Anyways, just a little observation.

[/AND/]

Originally Posted by xeityrj

...(didn't quite learn Linux tho, still doing everything from GUI), ...

Luckily we have reached a point where you don't need the terminal for more than 99% of stuff we do in Linux.

BTW regarding 'make' command, you need to install a package for it to be available, probably try (in terminal): 'sudo apt-get install make' (or use Synaptic package manager to install it in a GUI).