Device setup for Mutec-3 USB is wrong

Core Machine (Operating system/System info/Roon build number)
i5 NUC running build 511

Network Details (Including networking gear model/manufacturer and if on WiFi/Ethernet)

Audio Devices (Specify what device you’re using and its connection type - USB/HDMI/etc.)
Ethernet==>RPi 4==>(USB)==>Mutec-3 USB==(AES)==>DAC

Description Of Issue

Device Setup recognizes Mutec, but the option to pass a Native DSD signal is missing from ‘DSD Payback Strategy’.

On its own, the Mutec converts all DSD streams to PCM.

By Setup forcing the pick of ‘Convert to PCM’ excess processing cycles are being introduced.

I haven’t bothered to report it because I have more than enough clock cycles, but I see more and more posts about the missing menu choice.


A post was split to a new topic: Native DSD on Pro-ject Box S2 Ultra

Hi @xxx,

What OS are you running on the RPi? Are you running DietPi? If you have Ropieee, Harry might be able to help like he did in the following thread:

Aha, I use DietPi. That might explain it.

I guess I could eventually use a WIN10 (with the Mutec driver) endpoint to test that theory.

1 Like

Sounds like a plan @xxx, do let me know how it goes!

@noris -

Yep, looks like DietPi is the culprit.

As an endpoint I used a laptop with WIN10 and the Mutec driver.

Guess I’ll try Ropey, or an old Atom I have, as an endpoint.

Thanks for the help. I marked this solved.

@xxx - Thanks for confirming. You may want to try using Ropieee and see how you fare in that regard. Until next time, take care!

This topic was automatically closed 36 hours after the last reply. New replies are no longer allowed.