DSD Bridge 2.8.8 not "certified"

No, I have not posted with Roon. I was trying here first.

I will try a full uninstall and reinstall see what happens. If that fails, I will post to Roon. If I get an answer, I will come and let you know.

I appreciate your help.

They might have some more things to try. Yes please let me know.

Dennis

I have exactly the same problem from time to time. My other endpoint (a Meridian MS600) has always been correctly identified by Roon so I have assumed it was a DS issue.

My not exhaustive debugging indicates it’s related to the sequence in which the Roon server & DS Snr are powered up. I don’t think it happens if I power up the DS Snr first and let it acquire an IP address, then boot the Roon Server.

DS Snr is running Torreys, Bootloader 1.13, Firmware 1.8.8, Bridge 0.0.0. Roon shows a version string for the DS “psaudio_ug-r v2.7.11”.

Roon Server software is running on an Intel i5 NUC, Windows 10 Pro. Roon Server is running as a service using NSSM. This is my first and only Roon server. Unlike the OP, I’ve always experienced this issue.

DS and Roon Server are connected to a dedicated switch. The only other connection is to a network bridge so that I can control Roon via an iPad.

It’s a PITA when Roon identifies the DS as CDMCM-210 because even after rebooting everything and getting the DS identified as a PS Audio Directstream DAC, I have to enable it in Roon and enter a zone name. First world problem I know, but all that futzing about is not an ideal way to start a listening session…

Thanks markus46. I definitely think we are having a similar issue. Have you ever played DSD files back directly through the system? Does it convert it to PCM, or play the DSD files directly. The easiest way to see what is played at the endpoint is to look at the DSD display, but you can also see it by clicking the little light icon (north star ?) to the right of the name of the song/piece that is playing in the Roon software.

While I did have my DSD up an running on the network before I installed Roon on the new Server, you are making me realize that I did have my previous Roon Server running when I installed Roon on the new machine. I then had to decommission (wrong term, I am sure) the old server to free up the license and allow it to be associated to the new server. I bet that was the cause of my problems. I will be able to reinstall and test this weekend. This time I will remove all aspects of Roon except for the library, although I will delete that too if I get no improvement after the first test.

Drew said Have you ever played DSD files back directly through the system? Does it convert it to PCM, or play the DSD files directly.
Hi Drew,

I have no issues playing DSD files natively without conversion - when the DS is recognized as ‘PS Audio Directstream DAC’ in Roon.

I’ve never used the DS when it’s been identified as ‘CDMCM-210’, but it wouldn’t surprise me if DSD was converted to PCM in that case because Roon is not fully aware of the DS feature set.

Since I resolved the problem, I wanted to leave the answer for others.

I tried reinstalling everything to no benefit. The DS kept coming up as CDMCM-210 and kept disallowing direct DSD playback. I started searching google for any instance of CDMCM-210 and found a thread in the DS Jr product area that seemed to reflect the exact same situation. The last thing mentioned in it was the owner should check volume leveling and crossfeed should equal zero. Since I know that I have one channel set about 2 db higher than the other due to come volume inconsistency in the rest of my system, I set both to the same volume and rebooted everything. That did it. The device came up as “PS Audio DirectStream DAC” and DSD played directly. It seemed to hold onto that setting after I changed it back to be 2 db higher in my right channel.

That’s interesting that that was the solution. Reading the thread I suspected as such. In Mac the PS Audio Driver item in Audio Midi Devices has to be a 100% volume of DSD will not play. It’s crazy how many times this volume slider has slightly moved, for no apparent reason, and sabotaged my DSD efforts! I’ve spent hours chasing that gremlin down, trust me! NOw I know. I didn’t know this could also happen in Windows. This strangely comforts me a little little that this doesn’t only happen in Mac! Glad you figured it out.

Hi, having the same problem here with Bridge II firmware v2.9.14:

Screen-Shot-2017-02-12-at-11.45.28-AM.png

Screen-Shot-2017-02-12-at-11.56.17-AM.png

Are you running Torreys? If not you will get that.

Dennis

Hi Dennis, yes, I am running Torreys latest/final. Thanks.

It should show as certified. You might want to check the roon forum for this issue.

Dennis

Hi Dennis. I agree that Roon should recognize the Bridge II as “Certified,” but I respectfully disagree that individual PS Audio owners struggling with the Bridge II “Uncertified” problem – which causes an unwanted DSD-to-PCM conversion – should be directed to the Roon forum to hunt on their own for a possible explanation and/or solution. (The proposed solution in post #14, above, did not work for me.)

I reported the “Uncertified” issue here in the hope that PS Audio might work directly with Roon to come up with a solution. I am on a one-year free trial of Roon that expires in October 2017, compliments of PS Audio, and for that I am extremely grateful. But there is no way I would pay $500 for Roon in its current state.

The DS/Bridge II tandem works very well in my system with MinimServer and various UPnP control point apps. When it comes to Roon, however, I have found the experience to be frustrating and unsatisfactory. If I had paid $500 for Roon I would be more than a little upset. But because PS Audio was so generous in allowing me to try Roon free for a year, I am simply bemused by the bugginess I am experiencing.

Also, I am so happy with the sound quality and ergonomic experience of my MinimServer-equipped Melco feeding the DS via the Bridge II that I do not see Roon in my future (at least not at anything close to the astronomical $500 price point) even if Roon were to recognize my Bridge II as “Certified.”

If PS Audio is concerned that Roon is seeing some number of Bridge II installations as “Uncertified” then I suggest respectfully that PS Audio and Roon should try to figure the issue out for the benefit of their [potential] mutual customers. If not, then thanks again to PS Audio for the Roon free trial but I will take a pass on Roon and stick with the rock-solid MinimServer and Melco. Thanks.

I was directing you to the Roon forum because everything looks ok on the bridge/DAC side of thing. They might have a better idea of other things to check from their side of things, that could point you to the reason it is not certified, like log files they could point you to.

Dennis

Ah, okay, thanks for that clarification, Dennis. I might try to peruse the Roon forum this coming weekend and will report back here with any updates. Thanks again.

The main thing I have been told to look at, is Firewalls, both on your computer and router.

Dennis

I just checked the Roon forum, where a DSJr. owner reported the Bridge II “Uncertified” problem here.

Roon’s Chief Technology Officer Brian Luczkiewicz responded just ten hours ago as follows here:

It's because the device was momentarily identifying itself to Roon as "CDMCM-210" instead of its real name.

I think this sometimes happens after firmware updates of these devices. Maybe something to take up with PS Audio.

So PS Audio suggests we check with Roon while Roon suggests we check with PS Audio…

I would be grateful if PS Audio and Roon would work together to address this issue. Thanks very much.

If the bridge is reporting CDM-210 it sounds like the bridge code has been corrupted. Email me to dennis@psaudio.com and I’ll get you a way to reload it.

Dennis

Hi Dennis, thanks, I will email you momentarily. I should mention that all my UPnP control point apps recognize the Bridge II as “BridgeII” (without the quotes and with no space between Bridge and II).

Hi Dennis and thanks for emailing the v2.9.14 firmware for the Bridge II. I re-installed v2.9.14 and Roon still saw the Bridge II as “Uncertified.” I then power-cycled the DS using the rear-panel toggle switch and all is well again:

Screen-Shot-2017-02-21-at-8.14.25-PM.png

Screen-Shot-2017-02-21-at-8.16.44-PM.png

Bootzilla said

Hi Dennis and thanks for emailing the v2.9.14 firmware for the Bridge II. I re-installed v2.9.14 and Roon still saw the Bridge II as “Uncertified.” I then power-cycled the DS using the rear-panel toggle switch and all is well again:

Screen-Shot-2017-02-21-at-8.14.25-PM.png

Screen-Shot-2017-02-21-at-8.16.44-PM.png

I now have an idea how to fix this issue for good, and will be implementing shortly. would you like to test it for me when it is finished?

Dennis