by louthy | 2025-07-23 15:23:50+00:00
> The reliable way to do this (I found) is check the kernel source tree first

Sure, in general that's good advice, but it becomes more complicated depending on the solution/situation...

I’d bought the RME card long before I was hoping to make it work with Linux. I'd been running Windows for a long time for work reasons, so I had my dev work and my music setup on the same computer (a 64 core Threadripper machine, with 128gb of RAM, and fast NVMe drives). A few months before, I'd sold my company, so for work at least I didn't need to be on Windows any more. Then I started getting random audio dropouts! Presumably because of all the crap Microsoft keep loading onto the OS with after every update.

The audio dropouts was the straw that broke the camel’s back. If a machine like that, with nothing else running on it other than my DAW, could start having audio dropouts, then you know something has gone horribly wrong with the OS.

That's why I wanted to get my existing RME card working on Linux. When I wasn’t able to use it, I then assumed I’d be able to get a network based protocol running (Dante/AES67). There was plenty of discussion about it online, it seemed viable, and it's a network, Linux can do networking! Also, I kinda like the idea of network based audio, I think it's likely to be more future proof.

So, I replaced one of my Ferrofish A32 Pro interfaces with a Ferrofish A32 Pro DANTE ($4300) [1]. It supports both Dante and AES67. I figure if I can’t get Dante running then the open protocol AES67 (with support in Linux-land) should work. That didn’t feel that risky. But no amount of finagling would make the interface appear via the virtual sound-card/router concept.

This had already taken weeks (maybe months) to not get anywhere, so I looked for a Class Compliant sound-card (or, one that definitely had Linux drivers) that could support the number of channels I needed (96 channels in and out), it also needed to support the AD/DA interfaces interfaces I already had (so connectivity via MADI or Dante/AES67), but there just wasn't anything. The only other sound-card out there was another RME interface.

So, that’s when I opted for a Class Compliant sound-card [2] for casual use on Linux ($324) and a new RME Digiface Dante sound-card ($1543) [3] that I could use with a newly purchased M4 Mac Mini ($3000). I also needed to replace another one of my Ferrofish A32 Pro interfaces with another Ferrofish A32 Pro Dante ($4300) to make the setup work.

I realise now that my earlier estimate of $6000 was wildly out, it cost $13467 to leave Windows and to get an alternative pro-audio setup working. There may well have been alternative approaches and I may well have missed a possible solution that could have either worked with the original RME card (which would cost nothing) or AES67 (that would still require me to replace 3 x Ferrofish A32 Pro interfaces, so would end up about the same cost), but I felt like I'd been pretty thorough.

I guess the reason I'm writing War & Peace here is that it's often not possible to know ahead of time whether any one setup might work. Drivers is one thing, but a pro-studio setup has more moving parts, and so if you don't know ahead of time whether any one setup will work, then it can be an expensive process to walk through the different options. And that's a problem that neither Windows nor Mac has. It's a real shame, because the stability of Linux should make it the best platform for pro-audio.

[1] https://www.ferrofish.com/a32pro-dante-converter-multimode/

[2] https://solidstatelogic.com/products/ssl-2-plus-mkii

[3] https://rme-audio.de/digiface-dante.html