INTERACT FORUM
More => Old Versions => JRiver Media Center 23 for Windows => Topic started by: lacika76 on July 29, 2017, 04:01:50 am
-
Dear JRiver!
I've a problem with WASAPI excusive access mode under WIN10 Creators Update.
After I've changed this mode and playing any file my WIN 10 crased -> BSOD.
I've created a log file. Where shound I send it? E-mail address?
Thanks!
-
Try turning exclusive mode off.
-
Above 44.1kHz I get this message:
"Something went wrong with playback.
Details:
Playback could not be started on the output 'WASAPI' using the format '192 kHz 2ch'.
The mixing format of your hardware does not support the current output format.
Please use the 'Output Format' tool in DSP Studio to convert to the mixing format listed below:
Sample Rate: 44100kHz
Channels: 2
Bit per sample: 32"
Playing with Kernel Streaming everything ok, but the recommended playing mode: WASAPI. I like to use this mode, bacause it's working good with another player (foobar2000).
In JRiver MC23 the WASAPI only working with 16bit/44.1kHz bit depth/sample rate files.
The problem exist only in MC22, 23.
-
A Blue Screen is a hardware driver problem.
What are you playing to?
If you're using foobar, make sure it's not in exclusive mode, too.
-
1) I have same issue, reported it some time ago. Different driver (m2tech)
2) Today I mistakenly set for WASAPI for my friend, he has EMM with XMOS USB... and voila --> crash
Are you sure all these cases come from a driver?
Kernel Streaming works
ASIO works
Just WASAPI does not..
-
If ASIO is an option, I highly recommend using it if WASAPI is causing BSODs.
-
And if I don't have ASIO?
? ::)
-
Well, is kernel streaming an option? There's also DirectSound, but yeah, not always the best choice. Other than those or just switching from the m2tech, not sure there's much you can do but wait for m2tech to release a new driver. It's a shame m2tech hasn't already released a new driver fixing this.
-
Are you reading what we're saying???
I have m2tech, and today also I can add that XMOS does work work.
And the originator of this thread
And it works in MC21
and it works in foobar2000
-
Honestly, I indeed thought it is my issue until yesterday, so I contacted Metronome about the upgrade of my C6 DAC (it is a 10,000 euro device) to C6+ (another 2000 euro + shipping & taxes), just because it has the Amareno USB card inside rather than M2Tech
On the **very same computer** MC21 works with WASAPI, and MC23 -- crashes
And you say M2tech should be ashamed?
-
BSODs are caused by drivers, not by software. If your system BSODs when you use a certain driver, then its likely its fault, not MCs.
If you paid several thousands of euros for a DAC, you should ask them for support, you certainly paid enough to expect it.
-
and if MC22 and 23 are sending junk to the driver causing it to crash?
It does not make any sense that all 3 drivers mentioned here suddenly stopped working with MC22
-
If the driver crashes when it receives "junk", then its still a bug in the driver. It shall never crash.
WASAPI works fine for a huge group of people around here.
-
It is not about stress-testing the driver..
I upgraded to MC22 from MC21, and last week I helped my friend to upgrade from MC21 to 23 (which is less stable than 22 regardless of this)
-
WASAPI works. Something else may be happening for you.
-
If you're running antivirus software, try uninstalling it.
-
Try uploading a minidump from one of the BSODs to a file sharing service and posting it here?
-
WASAPI works. Something else may be happening for you.
To 3 of us.. and it works with MC21 -- for 3 of us..
Nevertheless, I was in touch with Marco from m2tech, when they will be back from holiday end of the month they will look into **MY** issue.. For my friend I switched to ASIO,
and @lacika76 I don't know what will be doing
Jim, nothing changed between MC21 and later versions?