I spent some time digging into JRiver ASIO issues tonight.
From what I can see, in the current Roon software, 16bit content plays ok but 24bit content does not. This has been fixed, and the fix will be available in a future build.
I was also able to reproduce a “playback parameter negotiation” issue, but only when I’m switching back and forth between playing music in JRiver and Roon.
Basically in cases like this:
- Start Roon, pick the JRiver driver
- Start playback from Roon
- Start playback from JRiver
- Start playback in Roon again (e.g. use seekbar, press “next” button).
Looking at what’s actually happening, it seems like the JRiver driver is halfway disappearing on us, and Roon is getting confused. On one hand, it continues to consume audio samples from Roon, but on the other hand, if we attempt to start a new stream, it fails with a “device not present” error. My expectation would be that JRiver would send us a “driver reset” message at the moment when it stopped playing our content, indicating that the driver was no longer available for our use, but it doesn’t.
In any case, it’s possible to work around this situation and we have. The fix will be available in a future build.
If you guys are failing in other situations, please let me know so I can try them out and confirm if the same fix addresses them, or if there’s more to do.