Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[lordvader]

I've noticed that the latest version of JRiver (currently 26.0.80) are not releasing the output device on exit.
I'm using a Topping D50, and have JRiver configured to lock the device when in use.

On exit though (usually to jump in on a Zoom meeting #zoomlife), audio is not available. I need to unplug/replug the device.
This was not an issue with earlier versions of Media Center 26.

[JimH]

Try setting Exclusive Mode to off.

Or press the stop button in MC, not the pause button.

[Awesome Donkey]

Is the WDM driver being used?

[Awesome Donkey]

I got a Topping D50s yesterday, and I've found both ASIO and WASAPI is pretty buggy. MC itself likely isn't the cause of the issue where the output device isn't being "released" upon exit, I think it's something with the DAC and its drivers.

Are you using ASIO or WASAPI? If using WASAPI try ASIO instead as I've found it to be a little less buggy in general, but both still have some pretty glaring issues, like this issue I noticed within 5 minutes of using it. If using ASIO give WASAPI a try and see what happens.

I'm still working around issues with the Topping DAC - I've got them all licked so far except YouTube and Twitch videos not loading (giving off Audio renderer error. Please restart your computer. errors) with both ASIO and WASAPI in all web browsers while listening to music in MC (or any media player) via ASIO/WASAPI. With WASAPI (in exclusive mode) this is expected, but with it happening with ASIO too is a bit strange to me. Schiit's ASIO driver allowed me to watch videos while listening to music at the same time with no issues (and stopping the music would allow sound to work in the videos instantly). With the Topping DAC that's not the case, thus far at least.

[pluto]

I'm a long-time user of Topping DACs (of which I have two) and cannot complain about their drivers which, for my devices at any rate, are created by Thesycon – not slouches when it comes to audio interfacing.

The only valid reason to actually use ASIO in a domestic context is to send pure DSD (i.e. not DSD over PCM) to the device. Now I have never read the ASIO protocol in depth but I am not at all sure it supports an exclusive mode in the same sense that WASAPI does, the reason being that ASIO is, by design, to meet professional needs to route this device into that device and play the whole lot at a different sampling rate through yet another device etc. etc. etc.

IME the supplied drivers do exactly what they are supposed to - the ASIO mode works as it ought but is only needed if you are not happy using DSD over PCM. But you do not get the exclusive behaviour of WASAPI. It appear to me that if you want the exclusive behaviour of WASAPI, you will have to sacrifice the use of pure DSD in lieu of DoP, which sounds no different but does not support silly-high DSD rates.

p.s. I have no issues with MC not releasing the audio playback device on exit.

p.p.s. there's obviously no accounting for machines that have drivers for other devices (or the remnants thereof) installed.

[lordvader]

Sorry for the slow reply!

Yes, I do have ASIO turned on, as I am sending pure DSD to the DAC.

Today it worked fine, so it may be an intermittent issue - though I am hitting stop instead of pause now (thanks for the tip!)

[Awesome Donkey]

Yes, hitting pause can cause this, which is actually to be expected in that situation. Hitting stop should prevent it.