More > JRiver Media Center 22 for Windows

Windows 10 crash with exclusive mode (tidal)

<< < (6/9) > >>

amdismal:
I get this too, is the consensus that it's a Tidal issue or MC? I'm on Win10.

amdismal:
You know there's a difference between a fix and a workaround? ;-)

I have been able to output bit perfect Tidal including masters to MC, as follows:

Install ASIO4ALL from www.asio4all.de
Install the HiFi cable from www.vb-audio.com

Set the tidal output to HiFi cable input. In the settings for that, choose exclusive mode and fixed volume

In ASIO4ALL, choose the HiFi cable

In MC, do File > Open live > Asio line in, and choose ASIO4ALL. Welcome to bit perfect streaming of high resolution audio with no BSOD.

The only problem is, every time you change the resolution you need to go to the Configure ASIO line in, within MC, and choose the sample rate. This is actually less onerous than it sounds. The sound breaks up, playing at the wrong speed, if you have it wrong - nothing like a BSOD or full volume noise at least.

I can't really explain why Tidal can't play to ASIO4ALL or why MC can't see the HiFi cable output as an ASIO input. Presumably because of reasons.

I would really like the MC WDM driver to be fixed, I'm sure that's where the problem is. I'm happy to upgrade to v23 and/or help with testing. If it's not, I may have to move to Reaper for my DSP system.

winterwolf:
Tidal send me a note today with a link to a version that has the BSOD fixed. Just wait for the next update and it should be fixed for everyone.

--WW

Trumpetguy:
That's good news, even if I believe it when I actually see it. A few weeks now the evidence has been against WDM, not Tidal being the problem. But hey, if it works, all's good. Could you please post the version number of the new build?

winterwolf:
2.1.11.2 (W: 2.3.7--2) (NP: 2.4.3)

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version