JRiver MC 23 and WASAPI

Every time I try to set WASAPI as the output in MC23 to the Gungnir Multibit, MC hangs and eventually both MC and the windows audio service crashes. I can run generic AISO without issue.

I've deleted and reinstalled the Schiit drivers, performed several system checks on Win10, reinstalled MC, and so on. Also, the cmedia drivers from Schiits website wont install as it cant ever detect the Gungnir Multibit, so the drivers are the autodetected install ones.

Anyone have tips? I'm tired of beating my head against the wall on this. Is it a MC setting? Are there some drivers out there I'm not finding for some reason?

Thanks

 

I had something similar happen awhile back after the Eitr arrived. There were several things necessary on my part:
1. In device manager deleted the driver used by Windows for Eitr.
2. Ran windows update which downloaded a more recent CMedia driver from mother M$
3. Opened properties for Eitr and on Enhancement tab disabled all enhancement crap
4. On Advanced tab allow applications to request exclusive mode access
5. In MC WASAPI device settings check Open device for exclusive access

 

Thanks @atomicbob!

4 and 5 appear to be on by default. Should these be on or off?

 

I have had a similar issue with my Yggdrasil after installing USB Gen V. WASAPI (exclusive access) simply did not output any sound, despite JRiver MC 23 showing normal play function. I used ASIO for a few months as I couldn't find a solution despite bothering schiit tech for quite a while. Reinstalling drivers was of no use as CMedia installer does not detect Yggdrasil, so I had to rely on auto-installed drivers.

Finally, just few weeks ago, I changed BitDepth to 24 bit integer and it worked!

(Tools > Audio > Audio Device - Yggdrasil Gen V WASAPI > Device settings)

It looks like automatic mode outputs 32bit that is not supported by Yggdrasil. Strangely enough, this issue only cropped up after Gen 5 installation. Could the auto-installed Gen V driver allow 32 bit output despite Yggdrasil not supporting it?

That said, ASIO is still my preferred output mode.

Hope it helps!

 

Works fine for me, and I have never installed any Schiit drivers. I am using Win10, and using the generic UAC2 drivers. I am also using MC23 and automatic bit depth. Works like a charm on a Gen5 Gungnir Multibit.

I know some drivers announce modes they can't do, and various other things. My mobo's soundcard/TOSlink does that, so I had manually set the mode in JRiver- unlike the drivers for the old mobo. This was annoying as piss. However, since I got the Gen5 update, I just plugged in over USB and everything has worked like a charm.

I'd be inclined to ditch whatever sound drivers you've installed to try and make it work, and just use built-in UAC2, if your Windows is new enough (fall update W10 onwards). Don't clutter it up with Schiit/CMedia drivers, and certainly don't try to bodge it with "generic ASIO drivers" (which is pretty much an oxymoron).

 

Of note,

When playing 16 bit redbook flac using Yggdrasil Gen V WASAPI and bitdepth set as 24 bit integer, the output is upsampled to 24 bit. I feel the music is degraded from the upsampling of JRiver compared to direct ASIO.

sigh... Back to ASIO until JRiver or @schiit figure this one out!

 

What? That's not upsampling. It's just adding additional 0s to the end to make it 24 bit. That can be considered bit-perfect and shouldn't affect anything.

 

Not so sure about this. I use JRiver MC22 to output WASAPI to the Yggdrasil. I have the output bit-depth left on automatic, which should select the highest bit-depth the DAC is capable of receiving (24 bit). This is not upsampling as it is just padding the data with zeroes, which I believe the Yggdrasil does internally with 16 bit input anyway before DSP ensues. With JRiver this allows for headroom for software DSP, volume control and seamless transitions between 24-bit and 16-bit source files.

So if we were outputting 16-bit Redbook: 1111111111111111
Then all JRiver is doing is: 111111111111111100000000

ASIO drivers (I assume in your case generic USB ones), also automatically output the highest bit-depth the DAC is capable of receiving (24 bit in this case). I'm not sure why you would be hearing a degradation between ASIO and WASAPI in this context. If anything, it should be the other way around.

 

Yeah, I mixed up bitdepth with bitrate. The subtle difference I heard is probably placebo. ASIO outputs 16 bit signal when fed 16 bit input on my system.

That said, I haven't yet cracked the reason why WASAPI automatic bitdepth mode outputs 32bit into the Yggdrasil. Is it Yggdrasil USB card or driver related? Here is a similar discussion about this.

 

Thanks @atomicbob. That sent me down the right road. Everything works fine now.

Performed the following:

1. Unplug Gungnir Multibit usb cable.
2. Open Device Manager. (Shortcut is Win+X keys)
3. Select View > Show hidden devices.
4. Under "Sound, video and game controllers" remove any listed Schiit drivers. Choose to delete them from disk when prompted.
5. Plug in Gungnir Multibit usb cable. Confirm that it appears in device list.
6. Right click on Gungnir Multibit device, select Update Drivers > Search automatically for updated driver software
7. New drivers should download and install.
8. Reboot
9. Open playback device menu, select Gungnir Multibit, select Properties, disable enhancements, click OK.
10. Open playback device menu, select Gungnir Multibit, select Configure, click Next, set Front Left and Right as full range speakers, click OK.
11. Open MC23.
12. Set WASAPI in MC23, used all default settings. (Default = bitdepth auto selected, exclusive mode enabled, etc.)

Plays flawlessly.

One way I know it's working - Gubmy clicks when songs switch from wav to flac or with different bitdepths. It didn't do that in generic aiso mode

Hoping that helps someone in the future.