No sound on Linux with new MOTU Ultralite Mk5

Questions
1

I’m testing MOTU’s latest version of the Ultralite on my Arch Linux system running Pipewire. Everything works fine except for SuperCollider so far. Tried with system audio and Jack clients such as Bitwig and Reaper, and it’s all good. In SC there’s no sound coming out though. Booting up the server looks good (se below) and ServerMeter shows signal on ins and outs. Checking the jack patchbay in Carla looks a bit strange though. The supercollider box’s ins and outs are not listed in order (e.g. the outs right now is 10, 16, 14, 1, 22…) and seems random.
As i wrote other applications works, and also everything including sc works with my RME UCX interface, so i’m wondering what could be special with the sc/motu combo in this regard.

Booting server 'localhost' on address 127.0.0.1:57110.
Faust: supercollider.cpp: sc_api_version = 3
Faust: FaustGreyholeRaw numControls=7
Found 460 LADSPA plugins
Faust: supercollider.cpp: sc_api_version = 3
Faust: FaustJPverbRaw numControls=11
VSTPlugin 0.4.1
JackDriver: client name is 'SuperCollider'
SC_AudioDriver: sample rate = 48000.000000, driver's block size = 256
JackDriver: connected  UltraLite-mk5 Pro:capture_1 to SuperCollider:in_1
JackDriver: connected  UltraLite-mk5 Pro:capture_2 to SuperCollider:in_2
JackDriver: connected  UltraLite-mk5 Pro:capture_3 to SuperCollider:in_3
JackDriver: connected  UltraLite-mk5 Pro:capture_4 to SuperCollider:in_4
JackDriver: connected  UltraLite-mk5 Pro:capture_5 to SuperCollider:in_5
JackDriver: connected  UltraLite-mk5 Pro:capture_6 to SuperCollider:in_6
JackDriver: connected  UltraLite-mk5 Pro:capture_7 to SuperCollider:in_7
JackDriver: connected  UltraLite-mk5 Pro:capture_8 to SuperCollider:in_8
JackDriver: connected  UltraLite-mk5 Pro:capture_9 to SuperCollider:in_9
JackDriver: connected  UltraLite-mk5 Pro:capture_10 to SuperCollider:in_10
JackDriver: connected  UltraLite-mk5 Pro:capture_11 to SuperCollider:in_11
JackDriver: connected  UltraLite-mk5 Pro:capture_12 to SuperCollider:in_12
JackDriver: connected  UltraLite-mk5 Pro:capture_13 to SuperCollider:in_13
JackDriver: connected  UltraLite-mk5 Pro:capture_14 to SuperCollider:in_14
JackDriver: connected  UltraLite-mk5 Pro:capture_15 to SuperCollider:in_15
JackDriver: connected  UltraLite-mk5 Pro:capture_16 to SuperCollider:in_16
JackDriver: connected  UltraLite-mk5 Pro:capture_17 to SuperCollider:in_17
JackDriver: connected  UltraLite-mk5 Pro:capture_18 to SuperCollider:in_18
JackDriver: connected  UltraLite-mk5 Pro:capture_19 to SuperCollider:in_19
JackDriver: connected  UltraLite-mk5 Pro:capture_20 to SuperCollider:in_20
JackDriver: connected  UltraLite-mk5 Pro Monitor:monitor_1 to SuperCollider:in_21
JackDriver: connected  UltraLite-mk5 Pro Monitor:monitor_2 to SuperCollider:in_22
JackDriver: connected  UltraLite-mk5 Pro Monitor:monitor_3 to SuperCollider:in_23
JackDriver: connected  UltraLite-mk5 Pro Monitor:monitor_4 to SuperCollider:in_24
JackDriver: connected  UltraLite-mk5 Pro Monitor:monitor_5 to SuperCollider:in_25
JackDriver: connected  UltraLite-mk5 Pro Monitor:monitor_6 to SuperCollider:in_26
JackDriver: connected  UltraLite-mk5 Pro Monitor:monitor_7 to SuperCollider:in_27
JackDriver: connected  UltraLite-mk5 Pro Monitor:monitor_8 to SuperCollider:in_28
JackDriver: connected  UltraLite-mk5 Pro Monitor:monitor_9 to SuperCollider:in_29
JackDriver: connected  UltraLite-mk5 Pro Monitor:monitor_10 to SuperCollider:in_30
JackDriver: connected  UltraLite-mk5 Pro Monitor:monitor_11 to SuperCollider:in_31
JackDriver: connected  UltraLite-mk5 Pro Monitor:monitor_12 to SuperCollider:in_32
JackDriver: connected  UltraLite-mk5 Pro Monitor:monitor_13 to SuperCollider:in_33
JackDriver: connected  UltraLite-mk5 Pro Monitor:monitor_14 to SuperCollider:in_34
JackDriver: connected  UltraLite-mk5 Pro Monitor:monitor_15 to SuperCollider:in_35
JackDriver: connected  UltraLite-mk5 Pro Monitor:monitor_16 to SuperCollider:in_36
JackDriver: connected  UltraLite-mk5 Pro Monitor:monitor_17 to SuperCollider:in_37
JackDriver: connected  UltraLite-mk5 Pro Monitor:monitor_18 to SuperCollider:in_38
JackDriver: connected  UltraLite-mk5 Pro Monitor:monitor_19 to SuperCollider:in_39
JackDriver: connected  UltraLite-mk5 Pro Monitor:monitor_20 to SuperCollider:in_40
JackDriver: connected  UltraLite-mk5 Pro Monitor:monitor_21 to SuperCollider:in_41
JackDriver: connected  UltraLite-mk5 Pro Monitor:monitor_22 to SuperCollider:in_42
JackDriver: connected  SuperCollider:out_1 to UltraLite-mk5 Pro:playback_1
JackDriver: connected  SuperCollider:out_2 to UltraLite-mk5 Pro:playback_2
JackDriver: connected  SuperCollider:out_3 to UltraLite-mk5 Pro:playback_3
JackDriver: connected  SuperCollider:out_4 to UltraLite-mk5 Pro:playback_4
JackDriver: connected  SuperCollider:out_5 to UltraLite-mk5 Pro:playback_5
JackDriver: connected  SuperCollider:out_6 to UltraLite-mk5 Pro:playback_6
JackDriver: connected  SuperCollider:out_7 to UltraLite-mk5 Pro:playback_7
JackDriver: connected  SuperCollider:out_8 to UltraLite-mk5 Pro:playback_8
JackDriver: connected  SuperCollider:out_9 to UltraLite-mk5 Pro:playback_9
JackDriver: connected  SuperCollider:out_10 to UltraLite-mk5 Pro:playback_10
JackDriver: connected  SuperCollider:out_11 to UltraLite-mk5 Pro:playback_11
JackDriver: connected  SuperCollider:out_12 to UltraLite-mk5 Pro:playback_12
JackDriver: connected  SuperCollider:out_13 to UltraLite-mk5 Pro:playback_13
JackDriver: connected  SuperCollider:out_14 to UltraLite-mk5 Pro:playback_14
JackDriver: connected  SuperCollider:out_15 to UltraLite-mk5 Pro:playback_15
JackDriver: connected  SuperCollider:out_16 to UltraLite-mk5 Pro:playback_16
JackDriver: connected  SuperCollider:out_17 to UltraLite-mk5 Pro:playback_17
JackDriver: connected  SuperCollider:out_18 to UltraLite-mk5 Pro:playback_18
JackDriver: connected  SuperCollider:out_19 to UltraLite-mk5 Pro:playback_19
JackDriver: connected  SuperCollider:out_20 to UltraLite-mk5 Pro:playback_20
JackDriver: connected  SuperCollider:out_21 to UltraLite-mk5 Pro:playback_21
JackDriver: connected  SuperCollider:out_22 to UltraLite-mk5 Pro:playback_22
SuperCollider 3 server ready.
Requested notification messages from server 'localhost'
localhost: server process's maxLogins (1) matches with my options.
localhost: keeping clientID (0) as confirmed by server process.
Shared memory server interface initialized
2

EDIT: ok I just checked the specs and mk5 is class-compliant unlike mk3
hi @emp, can I ask how did you managed to make mk5 work with pipewire? what’s you kernel version? I’m trying to get mk3 work via USB and I guess it will require reverse engineering of USB driver

3

Yes, it’s class compliant but still i had quite a lot of issues with it. I actually ended up returning it and went back to my trusty old RME UCX.

4

I recommend to get a device thats truly usb class compliant and seel
the motu. Their interfaces suck (on Linux) and their customer support is
a joke.

5

thanks for the advice, but I just got it used for cheap and will stick to it, it has some neat functions apart from linux support

6

Good luck… MOTU are famous for being not only uninterested in Linux support, but actually actively hostile toward Linux.

hjh