I'm using a (modified) Resonessence Concero HD which is a 32 bit USB DAC which converts up to 352.8 and DSD128 DoP. The manual says that when the unit detects the presence of a DSD stream the Sabre chip automatically switches to DSD mode. But it seems I can't consistently get JRiver to provide the DAC with a DSD stream. I had things working last night after I reset the audio settings etc. according to the advice of another DAC manufacturer:
https://www.exasound.com/Blog/tabid/74/articleType/ArticleView/articleId/110/Configuring-JRiver-Media-Center-for-Mac-OS-X-for-use-with-exaSound-DACs--Step-by-Step-Guide.aspxThe DSP window was then showing 2.8MHz DoP as the source and bitstream as internal, and Mac's audio midi setup was showing 352. But today after opening JRiver and without making any changes to the settings, it is back to downconverting the DSD stream to 176 (or at least that's what audio midi setup is showing), even though JRiver is still showing source and internal formats as last night. I can set audio midi to 352 with JRiver open, but as soon as I start streaming DSD it resets to 176. Any idea what the problem might be now? I have verified that "Auto configure output settings on playback error" is still set to Ask.
(Before I changed the settings, when streaming DSD the source and internal formats were showing as 352.8 64 bit.)
I've also sometimes experienced problems with getting the DAC to lock to any JRiver stream (when this happens the result is a ton of noise with the ghost of the signal underneath). Is there a recommended procedure? Should the DAC be turned on (and selected in audio midi) before opening JRiver, or vice versa, or does it matter?
And I am still sometimes experiencing the JRiver Playing Now window freezing. This seems to happen when I'm streaming a file and also opening other windows, or maybe only when I've been changing settings. When this happens the music continues to play track by track but all controls are lost, so at that point I have to close JRiver if I want to pause or play something else. This is very inconvenient!
I am using 23.0.65 and El Capitan.