Roon can't activate M2tech Young 384 DAC connected to Raspberry Pi 4 (ref#2AADGN)

Support
1

Hi! What’s not quite right with Roon?

· None of the above quite fits

None of the above quite fits

· None of these quite match

Tell us what's going on

· Hello! I installed RoPieee on a Raspberry Pi 4, then connected it to an M2tech Young 384 DAC via USB. I installed Roon on my computer. Roon sees my DAC but can't turn it on. What can I do?

Tell us about your home network

·…

2

Hey @ayd8888,

Thanks for writing in and welcome to the community!

Thanks for the details, that’s a clean setup, and the good news is Roon can already see the DAC, so we’re close. The spinner you’re seeing (the zone stuck on “Enabling…”) usually means RoPieee can see the DAC but it isn’t responding cleanly when Roon tries to open the audio stream. A few things to try, roughly in order:

  1. Check the power-on sequence. The Young 384 is an asynchronous USB DAC and needs to be present when the Pi boots. Please power the DAC on, set it to its USB input, and then reboot the Raspberry Pi with the DAC already connected. Booting RoPieee while the DAC is off is the most common cause of a hung “Enabling…”.
  2. Use a USB 2.0 port and try another cable. On the Pi 4, the blue USB 3.0 ports can interfere with USB audio. Please move the DAC to one of the black USB 2.0 ports, connect it directly (no hub), and swap the USB cable if you have a spare.
  3. Confirm RoPieee sees the DAC. Open the RoPieee web interface at
    http://192.168.1.71
    in a browser, go to the Audio tab, and make sure the Young 384 is listed and selected there. Then reboot RoPieee from that page and try enabling the zone in Roon again.
  4. Check your Pi’s power supply. A Raspberry Pi 4 needs a genuine 5V/3A supply, an underpowered one causes USB dropouts that look exactly like this.
  5. Make sure RoPieee is fully updated, then reboot once more.

If it’s still stuck after the reboot with the DAC powered on and on a USB 2.0 port, please send us the feedback/logs from the RoPieee interface (there’s an option to submit them), and let us know, that’ll show us whether the DAC is erroring when the stream opens, and we’ll take it from there.

Here’s an upload link:

https://workdrive.zohoexternal.com/collection/nocvrfc5b2ddab55140af8640f1d7ce13291e/external

Thank you!

3

Hey @ayd8888,

Wanted to follow up on this, since we have not seen an update yet. Were you able to try the power-on order with the Young 384 already on and connected before rebooting the Raspberry Pi, move the DAC to a black USB 2.0 port with a direct cable, and confirm it is selected in the RoPieee Audio tab after a reboot? If it is still hanging on “Enabling…,” please submit the RoPieee feedback logs from the web interface and send them over so we can take a closer look.

Please note, if we don’t hear back from you this thread may close automatically soon. If the thread auto-closes and you need further assistance, please submit a reopen support request via the technical support help form below and specify that the issue should be reopened. Thank you.