emp wrote:Ok, thanks for responding. The problem with the Linux community is that most users there aren’t audio professionals. And you get questions like ”why would anyone need that many channels?”.
But I will give it a try for sure.
From what I am reading on other threads, it appears that altsets that are higher channel count than the minimum one seem to be not working, and causing some distorted audio. Someone tested this on a Digiface and UFX III and could not get it working beyond the smallest altset (32 channels I believe). Here is that thread: https://forum.rme-audio.de/viewtopic.php?id=31000
One thing that may be worth trying:
1. Identify the Device and Available AltsetsList audio devices: aplay -l or arecord -l (look for something like "card X: Madiface" or "Fireface" or etc).
Note the card name (e.g., "Pro70790682" is the name of my Babyface Pro) and hardware device (e.g., "device 4" or etc).
View supported altsets and their parameters: cat /proc/asound/<cardname>/stream0 (replace <cardname> with e.g., "Pro70790682").This dumps details like: Altset 1: Up to 94 channels at 44.1/48 kHz, 24-bit.
Altset 2: Fewer channels, maybe different sample rates, etc. Find the mode which has the channel count and sample rate you would like to use.
2. Since lots seem to be using Jack through Pipewire nowadays, maybe try using qjackctl to set your sample rate and max input/output channels to the values of your target altset. Then, in your DAW, set the inputs/outputs to the same values, and try recording/playback on the higher channel numbers. Hopefully you do not experience the distorted audio issue. You can monitor what the interface is doing by the command watch cat /proc/asound/<cardname>/stream0
It may also be possible using wireplumber config files, or the wpctl command to set a default altset, although I do not know if you'd run into the same issues. Or, possibly there's something in the pipewire.conf file which can help. I'll do some more digging, but I strongly suspect that if you run into the same distortion issue at higher altsets, it's an issue specific to how RME interfaces interact with Linux.