Print

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

[Trumpetguy]

It works, thanks a lot to Hendrik! I have tested with MQA passthrough disabled on two computers. One with a USB DAC (Hegel Super) and one with a Realtec internal DAC just to check. Both reported 24/96 as input to JRiver wdm on the tracks played. Tested with Tidal, standard, latest release of Windows PC app.

[RD James]

I'm sure that you tested it as well, but I just wanted to confirm that it's also fixed the BSOD that I was getting with foobar2000.
Would it be possible to add 32-bit input support to the WDM driver? In theory, that should remove a conversion when using it in non-exclusive mode.

[Hendrik]

I tried to add 32-bit floating point support, but the only way I could get that to work was with exclusive mode. The shared device never offered an option to configure it to floating point, which defeats the purpose in this case.

[RD James]

I tried to add 32-bit floating point support, but the only way I could get that to work was with exclusive mode. The shared device never offered an option to configure it to floating point, which defeats the purpose in this case.

I wonder if that means devices which list 32-bit support are only using integer mode? (and even so, perhaps that would still be better than 24-bit?)
I tried to test it, but both 32-bit integer and 32-bit floating point worked with WASAPI non-exclusive mode to those devices.
I'm not sure if there's anything which will tell me what their "32-bit" option is.
 
I also noticed that since the Fall Creators Update, the JRiver WDM driver has the option to change the speaker setup via the context menu of the system volume control.
All my other system devices only give me the option to change spatial sound options there, not the speaker setup.

[winterwolf]

@JimH nonprofessional in the sense that when I purchased software in the past and I had issues, I don't have to engage with a larger user base but with focused Tier 1 support who can quickly escalate issues if needed. This is just my personal opinion and not intended to sound offensive. I just have a hard time with this thread to get to the root cause of the issue since there is so much advice in multiple directions (all well intended but I think not everyone reads what the original issue was about).

@fitbit Default Format is set to whatever JRiver decides the source format is since I run my driver in ASIO mode. for 44.1k stream it is just that. For higher rez Master files it is capped at 48kHz.

@fitbit: The non master version plays at 44.1kHz (the one with Green and black cover) the other (master) at 48kHz (all green) with my JRiver version.

@dtc: I confirmed with Tidal that I have now the latest shipped version of their product. No BSOD and still capped at 48kHz with JRiver and WDM driver

@ dtc: I tried your steps you suggest: First I get a Windwos warning: the device is used by another application. If you continue that application may stop working. do you want to continue? when I say yes (and hit apply) the default format changed to 96 but JRiver input still sees 48kHz and my Headphone amp continued to play with 48kHz independend of the default format.

Non MQA files switch properly to 44.1 kHz

@Jim: Running 23.0.81 in 64 bit mode

@fitbit: Same setup. Set to Exclusive mode, Force Volume, no passthrough. Same results as you. JRiver should see 24/96KHz with only 2x unfolded but only sees 48kHz as input coming form the WDM driver.

[dtc]

I am traveling so do not have access to my normal setup. However, I just tried Tidal and WDM on my laptop and it worked with Masters. Input sample rate was 96 KHz. This is with WIndows 8.1 and Tidal version 2.1.11.333 (W: 2.4.5--3) (NP: 2.4.2) and 64 bit MC .81. I am using Joni Mitchel Both Sides Now as my Masters album on Tidal.

Since you never had a BSOD and you always get 48 KHz with Masters, it seems like the issue is probably outside of the WDM driver, although I not sure what it might be.

On my laptop, I am using the internal sound card and speakers in Direct Sound mode. I still get 96 KHz input into MC which I resample to 48 Khz for the internal sound card. Maybe try that. It would eliminate any issue with your output device. Grasping at straws here..

[fitbrit]

Winterwolf: See my latest posts. Everything works as it should with the new version of MC. When not doing passthrough, Masters files played in Tidal are showing up as expected - 96 KHz/24

[winterwolf]

Ok, wanted to report back.

I flattened my machine and put just the minimum audio drivers on: JRiver WDM and my headphone amp/dac. I thought after all the comments that something was wrong with Windows itself, and indeed it was Windows (or another app interfering with the audio device). Now JRiver plays Tidal with the expected 96kHz for MQA (unless the stream itself is lower rez). All good now! Thanks to everyone chiming in and the comments that I am only getting the Windows shared device stream. Right on the money.

Sadly, I have to report a weird side effect. The 96kHz stream is really choppy (I hear scratching and cracking noises constantly during play). Should I start a new thread or is there any quick advice you guys can give to adjust JRiver to make it go away?

Thx everyone!
-- WW

[Awesome Donkey]

You might need to increase the buffer.

[dtc]

Ok, wanted to report back.

I flattened my machine and put just the minimum audio drivers on: JRiver WDM and my headphone amp/dac. I thought after all the comments that something was wrong with Windows itself, and indeed it was Windows (or another app interfering with the audio device). Now JRiver plays Tidal with the expected 96kHz for MQA (unless the stream itself is lower rez). All good now! Thanks to everyone chiming in and the comments that I am only getting the Windows shared device stream. Right on the money.

Sadly, I have to report a weird side effect. The 96kHz stream is really choppy (I hear scratching and cracking noises constantly during play). Should I start a new thread or is there any quick advice you guys can give to adjust JRiver to make it go away?

Thx everyone!
-- WW

Thanks for your persistence. Glad you got MQA to work.

I see the same problem you do - WDM sees the 96 KHz input, but the output is uneven and scratchy. I have played with the buffers to no avail. In my case, I am traveling so the only output device I have is my laptop's build in speakers. I wanted to wait until I am home next week to do more testing, but given your report I wanted to confirm that I am getting the same result. I think there was another poster who posted the same thing. I will do more testing next week, but wanted to confirm that I am seeing the same thing. I am running Windows 8.1 and, as I said, using the internal graphics, which are awful. But, I do get the scratchy, choppy behavior.

[amdismal]

I see the same problem you do - WDM sees the 96 KHz input, but the output is uneven and scratchy. I have played with the buffers to no avail.

Yep exactly the same for me. Fiddling with buffers changes it a bit, but I can't remove it.

I'm not terribly bothered - a BSOD is a show-stopper for me, and makes me look for different software (and I know how much time it would take to configure Reaper to host my convolver system, because it took ages a few years back and I've forgotten everythinng!), but this is just an annoyance. I don't go looking for MQA masters, but at least they don't crash my PC now.

[winterwolf]

Where do you increase buffer?

[RD James]

Where do you increase buffer?

Options > Audio > Advanced > Live Playback Latency

[winterwolf]

Buffer size has no effect on the cracking and hissing. It happens with all Master files above 44.1 kHz. Really really sad, since I thought I had it figured out

-- WW

[RD James]

Buffer size has no effect on the cracking and hissing. It happens with all Master files above 44.1 kHz. Really really sad, since I thought I had it figured out

Can you play local files that are imported to the library without these issues?
If you don't have any, there are 24/96 samples available for download here: http://www.2l.no/hires/

[dtc]

With my laptop, I definitely get scratchy sound when playing Tidal Masters through WDM. However, when playing 96 KHz audio from MC22 through MC 23 WDM the sound is fine. Seems like the problem  may be specific to Tidal, although it would be good to check with other sources. I will test with good DACs once I am home this weekend.

[winterwolf]

@RD Local files play fine, up to 192kHz I used ProStudioMaster samples in flac format to test it.

Again it is just with Masters, Tidal and JRiver WDM driver.

JRiver now detects the right Tidal output format from 44.1kHz up to expected 96kHz based on the source. It is just impossible to listen to...

Non Master Tidal songs play fine.

thx!
-- WW

[amdismal]

@RD Local files play fine, up to 192kHz I used ProStudioMaster samples in flac format to test it.

Again it is just with Masters, Tidal and JRiver WDM driver.

JRiver now detects the right Tidal output format from 44.1kHz up to expected 96kHz based on the source. It is just impossible to listen to...

Non Master Tidal songs play fine.

It's exactly the same for me.

[dtc]

I previously reported hearing crackle and noise when playing Tidal Masters through WDM on my laptop (Windows 8.1). Now I have tried in on a desktop system at home (Windows 7) and hear the same thing.  There definitely seems to be a problem with Tidal Masters and WDM.  It is easy to point a finger at Tidal, but given that Tidal works with a large number of DACs but not with WDM, it seems like it may well be a issue with WDM.