Network Details (Including networking gear model/manufacturer and if on WiFi/Ethernet)
Wired Ethernet (Netgear hubs).
Audio Devices (Specify what device you’re using and its connection type - USB/HDMI/etc.)
Oppo HA-2 portable DAC via USB2.0.
Description Of Issue
The Oppo HA-2 has always supported DSD256 via “native” mode versus DoP which doesn’t support DSD256. This only works on Windows machines since only they usually support ASIO communications and Macs don’t. But I’ve never gotten Roon to support this.
I have an Oppo UDP-205 that Roon does properly see DSD256 (and 512) support on a Windows-based client but never the HA-2.
My theory is that the device isn’t broadcasting its ability to do this feature so Roon defaults to DoP support regardless of the OS.
I have had success doing DSD256 native mode with JRiver since you are able to force the software to do this.
HQPlayer seems to have a similar problem recognizing this feature and I’ve brought it up with the vendor.
Can this feature be supported or whitelisted on the Oppo HA-2?
Can you provide a screenshot of your Device Setup tab? You can access this by right-clicking the zone name in the bottom right (next to volume icon) -> Device Setup. This is an example of what this screen looks like, please share screenshots that show both the general and advanced area:
Can you try to disable the HA-2 zone in Roon Settings -> Audio and then re-enable it? Once you have re-enabled it please note the exact local time + date when you have done so and let me know here, I can enable diagnostics mode after getting this timestamp.
I’m enclosing the screen shots you asked for. The one where I disabled, the re-enabled the device contains a date/time control panel from MacOS for your convenience (yes the HA-2 is on a Windows 10 machine elsewhere in the house, and yes, tt’s an old Mac running Windows 10). I’m in the Central Time Zone.
One bit of extra information. When re-enabled the HA-2, Roon came back and asked if the device was a Oppo UDP-205 or something else not matched (as you can see, I do have an Oppo 205 that Roon knows about in a different room/zone. So it seems to have figured out it was an Oppo device but it may not understand which one in its list of known devices. Also, I have the choice of using this device via either ASIO or WASAPI. I have been using ASIO.
Thanks for sharing those screenshots and timestamp. I activated diagnostics mode and what this does is automatically upload a log set to our servers and once these logs are received I will request feedback from the technical team.
I spoke to the technical team and it appears that this device is not reporting Native DSD capabilities to Roon. We’re going to reach out to Oppo to see if they would be willing to send us one of these DACs, unfortunately without the gear there is not much further that we can do here.
It’s unlikely that Oppo has any to give you since they stopped selling them over a year ago. The only other ones out there are on eBay.
Is there anything I can do to help in this? I could execute whatever tools that you need. And since the HA-2 is based on a similar ESS chipset as other Oppo products (like the 205), do you think that similar settings might work, i.e., a whitelist specific for this product? We know that native mode does work up to DSD256. PCM capabilities do seem to be correctly identified (up to 384).
I’ll inquire with the development team to see if this is something that we can troubleshoot remotely, but as far as white-listing, no there is no way to do this from our end, Roon ultimately relies on the capabilities information that the device provides to it.
This might be a useful place to start. One other program that polls the DAC for capabilities is HQPlayer. If you use the NAA remote function, it will tell you a lot about what is being reported back to HQPlayer. Here is that HQPlayer’s NAA is telling it about the Oppo UDP 205:
In both cases, the output is pretty much the same except in two key places. The PCM rates available for the 205 have 705K and 768K which is part of its chipset that is not supported on the HA-2. And the “outputDSD” rates include 64, 128, 256 and 512.
The HA-2’s “outputDSD” shows only 64, 128 and 256. But since 256 isn’t featured on a DAC without native support since DoP 1. I don’t believe supports 256 (at least not on a machine that maxes at with PCM 384k.