More > JRiver Media Center 22 for Windows

MC 22 on Windows 10 Pro x64 has garbled/static audio output with WASAPI [SOLVED]

<< < (2/3) > >>

Awesome Donkey:
Actually, there should be NO audible improvements or disadvantages to using ASIO vs. WASAPI. They both should exactly sound the same as both bypass the Windows mixer (unless exclusive mode is disabled for WASAPI) and output bit-perfect audio. DirectSound, on the other hand, should probably be avoided completely if you want bit-perfect output even though there's no evidence any of the audio output drivers sound any "better" than the others.

http://wiki.jriver.com/index.php/Audio_Output_Modes
https://wiki.jriver.com/index.php/ASIO
http://wiki.jriver.com/index.php/WASAPI

Still, the problem at hand is intriguing. Have you checked your configuration for WASAPI output? A screenshot of your Audio settings (Options > Audio) and WASAPI settings might help.

dasmodul:
Here are some screenshots:

http://www.mpcreations.com/temp/JRiver_RealtekBug.jpg

Awesome Donkey:
Have you tried it with Bitstreaming set to S/PDIF?

dasmodul:
Solved!!

Bitstreaming suggestion did not work. However I found the source of the problem. It is the Bit Depth (under Realtek Digital Output WASAPI) settings.

The default Bit Depth is set to Auto. I went through them one by one, and found the ones that have problems and two that work. So I picked the highest bitrate of the working ones as my default and now all noise issues are gone:

- Auto (Recommended for Best Sound Quality) = Garbled/Static-ridden sound.
- 32-bit Floating point = App crashes as Audio HW does not support.
- 32-bit Integer = Garbled/Static-ridden sound.
- 24-bit Integer (In a 32-bit package) = Works Perfect!
- 24-bit Integer = Garbled/Static-ridden sound.
- 16-bit Integer = Works Perfect!

Hope this helps others that have run into this issue in the future :).

Awesome Donkey:
Excellent! Glad you uncovered it! :D

Navigation

[0] Message Index

[#] Next page

[*] Previous page