The attachments look fine for me.
No firewalls that I am aware of. Also the Jr has been powered down and up while the core is left on. I might try to restart the core machine - win10pro
i might also try to run the core on my macmini see if that changes anything.
Yes, when I click on the attachment file link (IMG_0040.jpg, a photo of the DSJ front panel), the picture shows properly. When I initially uploaded the image, the in-line display was inverted (now it is missing, only the Roon screenshot remains in-line). At any rate, it doesn’t matter very much, and only serves the purpose to show that my DSJ firmware versions all match those of wizardofoz.
wizardofoz said No firewalls that I am aware of. Also the Jr has been powered down and up while the core is left on. I might try to restart the core machine - win10proi might also try to run the core on my macmini see if that changes anything.
I think Win10 has a firewall on by default.
If turning this off as a temporary fix solves your problem, the Roon guys may be able to tell you what specific single ports (or range of ports) need to be open for the Roon-Bridge handshake.
Well one reason I hate windows, having checked all the firewall settings…seems that even having enabled all the roon settings in the firewall it still wasn’t working but turning it off seems to have fixed it after restarting the roon server.
do any of the roon public network options have to be on specifically for the DS Jr to be recognised as certified?
Windows gives me the bejeebeeze for security at the best of times…so I would like to get the firewall on again if possible
I’m not sure Windows is actually the problem. On the Roon forum, it is claimed that Roon uses only UDP 9003, TCP 9100-9200. However, when I encountered the RPi problem, it was with server running on a Synology NAS (linux), and i had all of those specified ports allowed through the firewall. I also had to turn off the firewall entirely to the RPi IP address to resolve that issue.
Look at your firewall logs to see what other ports were trying to be used.
Dennis
JimC said I'm not sure Windows is actually the problem. On the Roon forum, it is claimed that Roon uses only UDP 9003, TCP 9100-9200. However, when I encountered the RPi problem, it was with server running on a Synology NAS (linux), and i had all of those specified ports allowed through the firewall. I also had to turn off the firewall entirely to the RPi IP address to resolve that issue.So is this a Roon or Synology issue ?
It is an issue of not setting the Synology (or Windows, or other) firewall in a way that allows all of the needed Roon-related traffic through. Apparently, the UDP 9003 and TCP 9100-9200 list is not exhaustive, and RoonBridge uses a wider (but unspecified) range). See: https://community.roonlabs.com/t/device-is-not-being-recognized-as-certified-how-to-fix-this/12754/5?u=jwc
Since the Roon package on Synology is not officially supported by Synology, there does not appear to be an easily baked-in way to allow all Roon-related traffic through the firewall without explicitly setting specific port ranges (unlike e.g. Video Station, etc). The method I have found best is to set the Synology to allow all traffic on all ports to the specific IP address of the Bridge II (and any other Roon endpoints that may be on your network). Since all of these should be behind your primary router, which controls traffic to the outside world, the security risks of such Synology firewall rules should be minimal.
Dear Paul,
I just installed the Roon server on my Ubuntu machine (Also running JRiver and where my music library is located)
Roon and the DSD +Bridge II work perfectly. Detection is perfect and connection stable. Everything plays fine, but I noticed the the DSD64 albums from my library are converted by roon to 384Khz then downsampled to 192 Khz (as I set that as the maximum bitrate the bridge can handle, in the Roon setup for the PS Audio DSD DAC) before Roon’s RAAT send it to the DAC where it is displayed as 176 Khz PCM. There is (to my knowledge) no setting in Roon to enable/disable DSD playback for the PS Audio DSD DAC in Roon. By the way, via JRivefr DSD files are nicely send to the DAC in DSD (DAC displays DSD64)
Is this a little flaw in the Roon RAAT driver in the Bridge or is this a bug in the Roon application?
Fine job anyway.
Some complketely other thing. My fantasic PS Audio. BHK preamp already had one fuse (the 1.6AH) blow on power on. This is probably due to the high rush in current caused by (for a preamp) gigantic toriodal transfo and large buffer capacitors in the preamp’s supply. Maybe a zero voltage transition switch on logic or series resitor of 10 Ohm which gets shorted by a relay after a couple of seconds would prefent this from happening when the power is applied at the time when the phase is just on a high voltage. As my Preamp is connected to the P5 netregenerator it would not be a bad idea (in general) to have the P5 ( and P3, P10) also swith on outlets when the phase passes zero voltage.
Best regards
percychris said Dear Paul,I just installed the Roon server on my Ubuntu machine (Also running JRiver and where my music library is located)
Roon and the DSD +Bridge II work perfectly. Detection is perfect and connection stable. Everything plays fine, but I noticed the the DSD64 albums from my library are converted by roon to 384Khz then downsampled to 192 Khz (as I set that as the maximum bitrate the bridge can handle, in the Roon setup for the PS Audio DSD DAC) before Roon’s RAAT send it to the DAC where it is displayed as 176 Khz PCM. There is (to my knowledge) no setting in Roon to enable/disable DSD playback for the PS Audio DSD DAC in Roon. By the way, via JRivefr DSD files are nicely send to the DAC in DSD (DAC displays DSD64)
Is this a little flaw in the Roon RAAT driver in the Bridge or is this a bug in the Roon application?
Fine job anyway.
Some complketely other thing. My fantasic PS Audio. BHK preamp already had one fuse (the 1.6AH) blow on power on. This is probably due to the high rush in current caused by (for a preamp) gigantic toriodal transfo and large buffer capacitors in the preamp’s supply. Maybe a zero voltage transition switch on logic or series resitor of 10 Ohm which gets shorted by a relay after a couple of seconds would prefent this from happening when the power is applied at the time when the phase is just on a high voltage. As my Preamp is connected to the P5 netregenerator it would not be a bad idea (in general) to have the P5 ( and P3, P10) also swith on outlets when the phase passes zero voltage.
Best regards
That might be a quirk of Roon on a linux Machine. Using Roon on windows my DSD64 plays as DSD64.
Dennis
percychris said Dear Paul,I just installed the Roon server on my Ubuntu machine (Also running JRiver and where my music library is located)
Roon and the DSD +Bridge II work perfectly. Detection is perfect and connection stable. Everything plays fine, but I noticed the the DSD64 albums from my library are converted by roon to 384Khz then downsampled to 192 Khz (as I set that as the maximum bitrate the bridge can handle, in the Roon setup for the PS Audio DSD DAC) before Roon’s RAAT send it to the DAC where it is displayed as 176 Khz PCM. There is (to my knowledge) no setting in Roon to enable/disable DSD playback for the PS Audio DSD DAC in Roon. By the way, via JRivefr DSD files are nicely send to the DAC in DSD (DAC displays DSD64)
Is this a little flaw in the Roon RAAT driver in the Bridge or is this a bug in the Roon application?
There is a setting in Roon Audio Setup for the PS Audio DSD device that determines how Roon handles DSD. By default it is set to convert DSD to PCM. You need to set this to DSD via DoP.
Thanks for the info, I will try if I can find that setting when I get home. Note that I need to be able to set this using the Roon iPad software as the Roon software on the Ubuntu has no GUI.
The setting you are talking about anly appears on the USB output in Roon setup. It is not there in the Bridge setup page, because the bridge is supposed to tell Roon what it can handle.
Dennis
No I just checked the only settings are max bitrate and bitdepth
Have you ensured that you have a kernel that supports native DSD (see here–you may need to patch your kernel) and ALSA 1.0.29 or higher. This is according to the Roon documentation https://kb.roonlabs.com/LinuxInstall.
Regards,
Sourav
Yes of course I cheked that. By the way otherwhise jRiver would not be able to output DSD either.
My alsa version is 4.4.0-31 generic
Sorry I copied the kernel version in the post above. The alsa version is 1.1.0
Surprised and sorry that so many are having issues. I am sitting here listening to Jose Stone via Roon and the Bridge II and she never sounded this good. The improvement isn’t subtle either. Here comes Ann and Nancy Wilson -wow!
Thanks Paul and team!
Kirk
No problem. Its not Roon that makes the sound but the DAC Amp and mosr of all the speakers.
jRiver works perfectly with the DSD. The only thing Roon has in excess is the nice handy GUI and the Tidal integration. But my experience with Tidal is that it has a extensive nice collection of albums, but if you have a nice DSD album or a high res FLAC that I must say Tital cannot follow. The sound quality is not up to that level. But for most of the recordings on earth that does not matter as the MQ of the recording itself is not up to what the media ( in this case FLAC at maximum 44.1 KHz) can diliver.
Try Emilie-Claire Barlow’s Live in Tokyo in DSD and compair it with Tidal’s FLAC performance and you will hear what I mean. And there I am 100% sure that if Roon coud do DSD correctly via the Bridge II then there would not be any difference either.
So Roon is a very nice handy and worthfull GUI nothing more. (And it can handle Tital that’s true).