More > JRiver Media Center 22 for Windows

MC22 Crash with Tidal

<< < (2/6) > >>

sbelter:
Anyone have any success resolving this issue yet - specifically playing Masters files via the WDM driver? Tidal support say that they're still working on it.

Trumpetguy:
Tidal Win desktop app was updated today. Still BSoD when playing MASTERS collection to WDM driver in Exclusive mode.
But I noticed that playing exclusive to my DAC's ASIO driver is ok.

So it is the Tidal->WDM path that causes BSoD, not Tidal Exclusive MASTERS in general.

I noticed that MASTERS is played back at 88.2kHz, while other contents is at 44.1kHz. The ASIO driver swithces sample rate (seen in the driver user interface). Could this be a problem with the WDM driver not switching? I will test this by setting WDM to 88.2kHz/24 in Windows Audio Device setting and report back.

Trumpetguy:
The WDM driver does not list 88.2/24 as a possible playback option (only 88.2/16)!

Devs - could this be the problem? And could you please add this option?

Matt:
I'm not sure.  Look here on my computer:


It lists the sample rate and bitdepth just fine.

You could try unchecking the WDM driver in Options and checking it again to cause a reinstall.

Trumpetguy:
This is strange. On my office workstation I don't see 88.2/24, while on the home server I do. Reinstalling MC23 WDM on the office computer had no effect. Maybe I should do a full re-installation of MC?

As a sidenote, the installs are not entirely the same. On the server, it still says MC22 WDM even if MC23 is the 'active' install. When installing MC23, the wdm driver did not show up even if it said so in the General->Features. At work, I took the effort to first uninstall MC22 WDM and then reinstall MC23 WDM. May be relevant, maybe not. I have not tested the new Tidal version at home yet.

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version