NUC to Pi4b running Ropieee to (Roon Tested) Cambridge Audio DacMagic 200M 2.0 via USB
DAC feeds Denon x4500h via RCA
Number of Tracks in Library
178 albums
Description of Issue
Several…
If I put the CA Dac on standby, then restart it, I have to restart the pi for the Dac to show up again in devices.
If I connect the Dac straight to the NUC via usb, i.e.cut out the pi bridge, It is recognised after going in and out of standby. But, as I understand it, connecting directly to Core via usb is not recommended. Can’t find that advice now, but is it still relevant?
The Roon Tested CA dac has different defaults depending on connection to pi or ROCK… how come?
Neither pi nor ROCK settings include Exclusive Audio mode for the CA dac. How come?
Advanced settings includes ‘Enable MQA Core decoder’. Does this refer to the DAC or the Roon core? I’ve already set the DAC as
Decoder and Renderer.
My Roon Core is on a m1 Mac mini
my bridge is a iFi Zen Stream
same CA 200M that goes XLR to my preamp
Does not happen to me. If 200M goes out I just press the power button and the bridge/dac is available again
I do connect directly. I do that as the USB from core does not make me dependant on a bridge.
If you connect thru a bridge (the pi or something else) you are limited by the bridge specs.
This is not for me. Going usb from core:
going with a bridge I do not get exclusive but I think this is normal, using roon bridge means it is exclusive to roon
this is for the core. not the dac. you need this if you want to do dsp and preserve the mqa
I do not get your question so I’ll tell you how I use the CA 200M
I do DSP to upsample to 256 DSD DoP or 768 PCM. 70% of my listening is classical so I use DSD as it is I bit softer for my ears and system. DoP I have to use as on Mac there is no native DSD. Sometimes when I like an electronic I switch to PCM.
I have convolution enabled using waw files created in REW
I have speakers enabled to correct the measured speakers, I have +/- 0.8 db for left right speakers so I put -1.6 db to my right speaker (the one that measures louder).
I do not use volume because I have and analog preamp
I’m not sure 100% about the inner workings, I have read that PCM is a container and I hope that then the dac treats it as pure DSD. I was under the impression that direct DSD is better or at least goes to higher rates. Anyway I can test DoP 128 vs DoP 256 and I’m not sure that on my setup I can hear a big difference
So I get back on the normal network, with a switch between m1 core and ZS, in browser setting when I tried to select DSD direct and hit save it will not stay that way, switches back to DoP
I remember now I tried this also, I remember thinking that I could do a reset and start over and that was the only thing that got stuck in to my head.
In touch with Ropieee re restarting issue. He looked at logs and said that Ropiee is seeing the DAC start up, then losing connection. So still restarting Ropieee after pulling DAC out of standby.
Only using Pi 4b / Ropieee as bridge to DAC now and defaults seem to be consistent.
Found that USB connection to DAC means Exclusive Mode is set by default and therefore no longer an option.
Enable MQA decocoder refers to Roon Core. I think it allows MQA when using DSP.
Chose DoP (DSD over PCM). Although CA DacMagic 200M has native DSD processing, Native is not an option. If anybody knows why please let me know. I suspect it’s due to using Ropiee as a bridge.
I found others talking about this. At least one said he had to hard wire to fix the issue.
Here’s what I see in the logs.
12/30 10:02:43 Trace: [raatserver] [CA DacMagic 200M 2.0] lost client connection. Retrying
12/30 10:02:43 Info: [raatserver] [CA DacMagic 200M 2.0] connecting (attempt 1)
12/30 10:02:43 Info: [transport] destroyed zone CA DacMagic 200M 2.0 was playing? False
12/30 10:02:43 Trace: [zone CA DacMagic 200M 2.0] Suspend
12/30 10:02:43 Info: [zone CA DacMagic 200M 2.0] Canceling Pending Sleep
12/30 10:02:43 Info: [zone CA DacMagic 200M 2.0] Canceling Pending Sleep
12/30 10:02:43 Warn: [raat_ll/client] [CA DacMagic 200M 2.0] failed to connect Connection refused
After that, I see the device get removed. While those could very well just be the device going into standby, that’s what we see. Is there any wifi involved in the equation?
One thing we can try is to refresh RAAT on your core. You will want to access your WebUI and stop the server. I’m not even certain it can help but it won’t hurt. Please be aware that this will reset your Roon Settings → Audio Tab to factory settings and I would advise making a backup of any custom DSP settings you have:
Hi, thanks for that.
All ethernet wired for me, but just moved ROCK off a switch and onto the router (also upgraded ethernet canbles to 6a, just for fun!). Seemsto have improved a certain harshness I noticed from the DAC.
Also rebuilt Database as suggested, put DAC in standby, then out of standby.
DAC disappeared from Roon.
Restarted Ropieee, and there it is!
Hey ho, just have to be less lazy.
If you can see Roon logs, the restart was in the last 5-10 mins, i.e. 14:35 or so New Zealand summertime.
P.S. Can I access the logs?
Right now I was using 200M usb to m1 core for HQP and the ZS with a zen dac v2 as Roon Bridge.
