Print

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

[Wasper]

Hello to everyone,

I have a new system that must use Windows 10 to work.  I have a DAC (Wadia DI122) that used to work fine on Windows 7-8 before.  The driver is available on Wadia webpage.  Unfortunately, this driver isn't working anymore on W10 in WASAPI mode, at least no more since windows updated to usb audio 2.0.  So I had to rely on the windows usbaudio2.sys.  It works, but the sound quality is awful. I can ear pop (not sure if it's the right word for static noise) randomly but often.  After research on the Internet, I was lucky enough to get an ASIO driver for my DAC made by a unknown man.  It works quite fine, no popping at all, but, my computer would freeze randomly and I have no error message in windows events.  This is acceptable as the freeze couldn't occur for hours but also unacceptable! Finally, Using the original driver from manufacturer will works fine under Kernel Streaming, but Matt said it's mad...

Wasapi mode with manufacturer driver will give me a blue screen with SYSTEM THREAD EXCEPTION NOT HANDLED.

I do think that Microsoft driver is nice but why I get pop?  Why Manufacturer driver isn't working anymore in WASAPI mode?

Any help is more than welcome.

[JimH]

Try the 32 bit version of MC.

[Awesome Donkey]

In general if you're using a recent build of Windows 10 and you're not using ASIO, you probably don't need the manufacturer's drivers anymore, since Windows 10's Creators Update added native support for USB Class 2.0, so you can play sample rates above 96 kHz without needing to install drivers. But it looks like you already know all that (so this part was for anyone else reading this topic and wondering).

Now, your issue with WASAPI sounding bad might be because you're not using exclusive mode, and everything is going through Windows' mixer (so it's essentially resampling). Otherwise we'd have to know what other settings you're using, especially if you're using any DSP Studio features like Output Format, along with the type of files you're playing, if you're using memory playback, etc. What's the settings for buffering set at under device settings in MC? You might increase the buffer and see if that helps any. Trying the 32-bit version of Media Center like Jim said is a very good idea too, to test if the manufacturer drivers you're trying to use are 32-bit only (wouldn't surprise me if they were).

Finally, it sounds like the DAC's drivers haven't been properly updated to work on Windows 10, so they cause issues like BSODs. If they cause a BSOD with both the 32-bit and 64-bit versions of Media Center, it's probably a good idea to stop using those and remove them from your system, as they're probably not compatible with Windows 10.

[Wasper]

Hello,

Thanks for the answers.  I think I might have found the problem, will try soon.  More facts:

Foobar won't play at all to my dac with windows driver in WASAPI mode.
Foobar will play well with manufacturer driver in WASAPI mode, no blue screen there.
To intstall my driver, I must use the 64bits versions.
My JRiver is 32 bits (22 old version).
So, it's time to encourage you guys and just bought the upgrade to the new version.  I think that manufacturer driver will be fine on 64bits version of JRiver.  Maybe I'm saying stupid thing also.

Hope the migration will be flawless, I have wrote my own code to make 22 behave like I want.  This is, btw, such a great feature to have user exit!

So let's give it a try now.

[Wasper]

I can confirm that installing Media Center 26 64bits fixed my bug.  Audio play well with manufacturer driver, will try Windows driver later.  No windows hang also.  Thanks, your answers popped light in my head.

Howevr, I have a playlist that contains video and image.  Media Center crash navigating between video and image.  Didn't have a look yet on how to make a proper report.  Anyway, here is the windows event logged after the crash, maybe someone knows how to fix it...

Faulting application name: Media Center 26.exe, version: 26.0.106.0, time stamp: 0x5f313e35
Faulting module name: JRImage.dll, version: 26.0.106.0, time stamp: 0x5f313d6c
Exception code: 0xc0000005
Fault offset: 0x00000000000bcd6b
Faulting process id: 0xba0
Faulting application start time: 0x01d678362a5441dd
Faulting application path: C:\Program Files\J River\Media Center 26\Media Center 26.exe
Faulting module path: C:\Program Files\J River\Media Center 26\JRImage.dll
Report Id: a155ad62-d687-470b-88cd-0c5ae8942e1a
Faulting package full name:
Faulting package-relative application ID: