Reaper with ALSA on linux

Sound Explorers Corner Free speech
#1

On Ubuntu 24, I had a problem many seem to have running Reaper with ALSA so I thought it may help someone.

Why ALSA? It’s linux’ low level audio server. PulseAudio and Jack both use ALSA.

Pulseaudio is the usual default sound server in many desktop environment but has a noticeable latency in Reaper. Jack does not have the same problem but it is less obvious to use with controllers than ALSA. In Jack, your midi input have generic labels (eg. midi_capture1) while they are labelled by name with ALSA (eg. hw:A37 for Keystep).

Using ALSA with Reaper:
If you try to use Reaper with ALSA, while PulseAudio is running, you’ll get a “could not start device” error. So you must tell PulseAudio to stop using your sound card (turning it to off).
You should install Pavucontrol (a PulseAudio control). In the Configuration tab, you set your audio card to off (here Scarlett 4i4):

Capture d’écran du 2025-01-02 10-05-52
Capture d’écran du 2025-01-02 10-05-521981×606 63.8 KB

CAVEAT: You’ll have to turn it on after exiting Reaper else you’ll have no sound for the other apps. And make sure the output device corresponds to your desktop environment sound applet. You should note the default profile to set it back (PRO, Surround 4.0, etc.).

Then you can set Reaper Device to ALSA in Options> Preferences> Device (Crtl P):

Capture d’écran du 2025-01-02 10-29-27
Capture d’écran du 2025-01-02 10-29-271209×823 104 KB

I tested Keystep37, DrumBrute Impact, MatrixBrute and MicroFreak as input and output without problem. The VSTs Surge XT, Avldrums, Odin, and Pianoteq all worked well.

To install Surrge XT on Ubuntu 24, the following was helpful:

I quote:
In our Ubuntu systems we initially tried to install the software with the command
$ sudo dpkg -i surge-xt-linux-x64-1.0.1.deb

This wasn’t successful as our system was missing a few packages (libxcb-cursor0 and xclip). These packages were installed with the command:
$ sudo apt --fix-broken install

Nota bene: If Surge XT gui is too big, there’s a Menu in the bottom left allowing you to resize the gui.

Avldrums: x42 AVL Drumkits

SHORT EXAMPLES OF REAPER WITH ALSA

(no Jack, no PulseAudio, no wine), a sort of Paul Hardcastle smooth jazz impression.

Drum: AvlDrumkits’ Blonde Bop controlled by a sequence on DrumBrute Impact.
Bass: Keystep 37 controlling MicroFreak.
Piano: Pianoteq (with old Yamaha CP-33 as controller)
Pad: Keystep37 controlling Surge XT mks-70 warm pad preset.
Reaper’s ReaLimit on master.

Another short example with Reaper on ALSA in Ubntu. VSTs all native.
Makeshift Soprano sax: Surge XT
Bass: Surge XT
Pad: Surge XT
Guitar: Pianoteq (linux)
Drum: Avl-drumkit Blonde Bop

Less quiet short example of Reaper on ALSA (linux)
Drum: DrumBrute Impact
Bass: Surge XT
Pad: Surge XT NewLoops Surge preset
Lead: SurgeXT

3 Likes
#3

Update on Reaper on ALSA

I upgraded to Ubuntu 25.04 aka Plucky Puffin, released on April 17

Basically, ALSA is still the low level sound server. Pipewire is more widely integrated.

For instance, in Moddart’s Pianoteq 8 Options, I get to choose between
a) Default ALSA output through Pipewire
b) Scarlett USB Audio 4.0 (the direct ALSA output) or your sound device basic name.
(ex. HDA- ntel PCH ALC887 4,0)

With (a) it works like PulseAudio. The PulseAudio volume controls Pipewire volume.
With (b) AlsaMixer controls the volume.

With Reaper, I get to choose between Jack and ALSA In Preferences> Audio> Device.
If you choose ALSA, the text remains valid: ALSA is exclusive and you have to turn off the output to your audio device to use REAPER (Pianoteq,etc.) directly with ALSA.

I don’t use Jack anymore because every layer (Jack, Pulse, Pipewire) necessarily adds some latency. The latency may be slight; It all depends on your hardware.

1 Like
#4

Thanks for this post. I’ve been using Reaper via Pipewire in Ubuntu. Wasn’t aware of the new Ubuntu so I’ll upgrade to that.

1 Like
#5

I wasn’t advocating upgrade as such; but many see 25.04 as an important upgrade in general. If Pipewire’s latency is negligible, it’s more convenient than using ALSA directly and turning on/off Pulseaudio/Pipewire’s access to your audio device. ALSA is low level but serves one application exclusively.

In 25.04, Reaper does not support Pipewire directly. It offers me as devices ALSA, PulseAudio and Jack, not Pipewire. So to use Pipewire in Reaper, you’ll have to use Jack. Latency with PulseAudio is important.
A possible solution is offered here (see Elcalen):

With standalone Pianoteq or SurgeXT (both offering Pipewire support), I feel a small latency between ALSA with Pipewire output and ALSA with direct access to Scarlett 4.0 output. But my PC is not new (i7-7700k). Pianoteq offers me a choice between JACK or ALSA and if I choose ALSA, i can choose between Pipewire and different audio devices (if I have many cards).

It is complex (complicated!). An article on ALSA, Pulseaudio, Pipewire and Jack;

1 Like
#6

I haven’t been using Ubuntu much, or for very long. I’ve tried it on and off over the years but even now it’s difficult to set up unless you know the magic spells to type into the Terminal.

I’m actually waiting for a new kernel that supports my RME audio interface. I installed such a kernel but as it’s not signed, safe boot won’t work, which then means I lose Windows 11, which is my main OS. Ubuntu is expected to get the right kernel soon so then I can have more of a play with it.

#7

If all goes as planned, you should not have to be looking for a magic spell in a terminal. The Ubuntu installer should be able to do the job. I’ve been a linux user since the 90’s and I’ve done my share of errors. Preserving Windows is the absolute red line since so many music applications run on Windows (unfortunate but real).

I usually choose the manual partitioning in the Ubuntu installer which requires a thorough knowledge of the different partitions. on your system The option “install linux and windows side by side” should be the preferred option for many. I haven’t used it for quite some time.

When you install Ubuntu from USB pen drive or CD, you must choose in your bios UEFI CD or USB. If you don’t, you’re choosing “legacy” and legacy can’t boot Windows 11. Windows is still there but Grub (linux boot loader) won’t see Windows 11. Then you have to find workaround, maybe that’s what you call “magic spell in a terminal”.
Finally, it’s always safer if Windows and Ubuntu are installed on separate drives.

I’ve heard of RME interfaces for quite some tome; I’m surprised you need a special kernel supporting RME. I’m unhelpful.
I have a 4i4 3rd gen Scarlett (nor fully satisfied). Ubuntu has recognized the Scarlett for quite some time but the linux app allowing one to fully exploit the Scarlett (alsa-scarlett-gui) has been around for a year or two. If it’s the case for RME then it’s not a kernel matter.

For music, I mainly use Windows. I wrote this post for those interested in linux but don’t let curiosity interfere with your music. It may sound patronizing, but it’s an appeal to caution.

1 Like
#8

Thanks.

Boot-wise all is fine with the current Ubuntu and its kernel. I have it on a separate drive and use the boot menu in the UEFI/BIOS to select which operating system to use.

At the moment my RME interface (which connects via USB) isn’t recognised at all, but my Zoom U-44 interface is, as it’s class-compliant, so I can still use Reaper with that until kernel 6.12 is integrated into Ubuntu - expected this year, I believe.

By ‘magic spells’ I was jokingly referring to commands I needed to use to set up Ubuntu - many needed to get things working. E.g. Radeon graphics drivers (although the latest Ubuntu has caught up and supports my card now).

Will go and update Ubuntu now!

1 Like
#9

You know where you’re going and why (extreme ski championships advertisement in the 90’s )!

I’ve just checked: I’m on Linux 6.14.0-15-generic right now. It’s the current Ubuntu 25.04 kernel. Hoping it will solve your problem with your RME. Let me know if you have time. :+1:

I’ve done a lot of “magic spells”. I’ve saved my system in seemingly desperate situation.

#10

Which RME interface is it ? I have been using an RME Multiface II with HDSPe for 17 years now (way back via a good old PCI HDSP card but today via some now dated HDSPe express card chained to some adapter that can link to a thunderbolt port). Remarkably, it still works like a charm with all the kernels I threw at it over the years. What I ended up with for a few years now is to use pure JACK on the RME system and use a USB to optical gizmo as my default laptop soundcard (for internet sound, etc), plugged in the back of the multiface toslink input. I do not use pipewire or pulseaudio. This arrangement is perfect for my needs. For the occasional need to voice-chat over the internet. I am using a USB compliant headset as the default mic.

#11

That’s the bottom line, Thorgal.

I’ve used JACK for at least ten years. Pipewire was not around. It was compulsory then. I was using a2jmidid to connect my old Yamaha CP33 keyboard. I found the anonymous “channel1-2…” annoying. Hardware were not tagged transparently. It may have changed.

I wrote the post for those who don’t feel comfortable with JACK or have older PCs.
I know the RME reputation. I was using an Yamafa SW1000XG card then. That’s what I could get in Quebec City in 2000.

#12

Yeah, I can understand that out of the box, things are not looking exactly friendly. Not sure how other platforms expose the different IOs to the user OOB. I also seem to remember that qjackctl has a way to alias the jack ports with more user friendly names and remember those after reboots but yeah, not straight from plugging your gears (*). During my ardour days, I was using the midi bridge as well but with time, I started to dive into a more electronic approach to my music and am now relying on Bitwig Studio. I still use jack for convenience even though not strictly necessary but the a2jmidid thingy had to go (bitwig wants to take exclusive control of the MIDI h/w and won’t be able to do so if a2jmidid is in the way).

About pipewire, I tried it for fun a couple of years ago in my rehearsal room on a linux system using an old digidesign mbox2 and 2 USB streamers carrying data from 2 old MOTU 8 pre firewire devices used as outboard preamps / ADCs (via optical links - firewire was not an option any longer). The result was a total mess with weird names all over the place. I had to quickly remove pipewire entirely and rely on my zita-a2j bridges to sync the USB streams to the mbox2 (main jack interface). But this is already history as our band just acquired a Focusrite 18i20 4th gen. So out with the old gears, will just keep one MOTU for 8 extra inputs via optical :slight_smile:

(* Irrelevant) note: I never needed any of this, I am a s/w dev for a living and have been using UNIX systems since as long as I can remember. So scripting things, tweaking things, etc, is just a reflex.

(Doubly irrelevant): I used to live in Quebec-city in the late nineties :slight_smile:

1 Like
#13

It’s not irrelevant at all. You know our access to devices and instruments are limited here.
I’m more a guitarist (and sax player) than a keyboard player. I know I should go to New-York to try and buy better guitars but I’m a bit lazy so I do with what we have here.

So you’re familiar with UNIX. It explains what you mean by “pure JACK”. I’ve only used QJackCtl with Jack. And yes a2jmidid is history. I thought high level languages like LISP and Prolog (AI 1.0) and wrote programs in C (not++) in the 90’s for language teaching with animation that would be laughable now.

I remember FireWire; I had an Ensoniq EPS sampler with a FW drive. Great fun!
I played jazz guitar with a drummer/vibe player and a tenor sax player. And with my son, a pro doublebass player when he was not running after contracts and students. Now, I’m on my own. :disappointed_relieved:

With a band, you certainly need 18i20 and more. Is it a full electronic band (like VNVNation) or a mix of electronic and “standard” instruments? I know what miking an acoustic drum is.

#14

Hi Thorgal, it’s a Digiface USB interface, with a couple of converters hanging off it (at most, usually nothing connected just the line out).

I’ve asked about it in the RME forums too, but no reply as yet. Not a big deal as everything works fine in Windows, just would be a nice-to-have.

I have my Arturia plugins working okay (using a different interface), and the machine itself seems to be faster using Ubuntu. Getting the interface working would be the last piece of the puzzle - at least for now!

#15

Hey Yearofthegoat, you are in luck: RME Digiface USB support now in kernel 6.12 (Page 1) — Linux — RME User Forum
I was considering the Digiface as well a while back when I saw that someone reverse-engineered the thing for a linux driver. It is now officially supported by linux. But after some considerations, I convinced my band to go for a Focusrite 18i20 and I have 0 regret, this thing is awesome!

#16

And the current kernel is 6.14.

The Scarlett 18i20 is also supported by alsa-scarlett-gui.since 6.14.
https://github.com/geoffreybennett/alsa-scarlett-gui/blob/master/docs/INSTALL.md

#17

That’s one of the key reasons why I chose it:

1- 100% USB class compliant, even without the GUI stuff, it works right out of the box (even though I had to update the firmware from my wife’s macbook when I unpacked it

2- I had loosely followed the development of the 4th gen scarlett gui project a few weeks before I decided that it was it. It was quite painless to set this up except for one thing: the firmware that was updated from focusrite was newer than what the scarlett gui project supports. But with the fcp-tool utility and the firmware deb package that the project provides, I could easily downgrade to the most recent version supported by this framework. And lo and behold: a magnificent GUI flashed before my eyes and everything worked. I have to admit though: when I pressed enter to downgrade the firmware from the bash terminal, I was crossing fingers that the unit would not turn into a shiny red brick … :stuck_out_tongue:

About our music, it is a mix of pure acoustic sounds + standard analog instruments, and electronic bits, I started to sample a lot of our acoustic instruments and other things that trigger my ears (e.g. - and don’t laugh - I have a hamburger shaper that sounds amazing when struck with a stick - I created a nice and simple moody pad sound in Bitwig with it). We use Bitwig for live performance (not for DAW work a la Ardour) and improvise on top of some clip launching sessions (sometimes quantized, sometimes without any sense of rhythm). it can turn a bit shamanistic at times :slight_smile:

#18

Yes, 100% compliant but I was missing the Windows’ Focusrite Center.
The linux one gives you even more control than the Windows one. But with 8 ins and 10 outs, the routing possibilities can be overwhelming, I guess.

I can understand your angst while flashing form command line. You know what you’re doing.
A hamburger shaper! I don’t laugh but I smile. Ii like Addictive drums Vintage Dead AdPack and in one setup they have as a percussion two stacked toolboxes (literally) called C24 & U67 Boxes .

Oh, shamanistic like the Shamen (Move any mountain, I bought all the remixes on cassette). I’m kidding! :wink:

#19

Unfortunately it doesn’t work properly. At least not in Ubuntu 25.04. I haven’t tried any other types of Linux, though.