More > JRiver Media Center 31 for Windows

Intermittent white noise from WDM Driver

(1/4) > >>

ToasterPC:
Just reinstalled Windows 11 from scratch and installed JRiver, but it seems this problem is still present and getting worse, as now I'm not able to get any proper audio input at all.

How could I go about troubleshooting this issue?

JimH:
Providing details would help.

Occasional noise may be coming from the DAC.

JimH:
Previous report:

https://yabb.jriver.com/interact/index.php/topic,130481.msg946522.html#msg946522

ToasterPC:
Ok, fair enough.

Most of the details from the previous thread are still as described, but to reiterate:


* This has been happening on the same computer for the purposes of this report, but I can reproduce the issue in at least another computer from the same manufacturer (Dell/Alienware m15 R6).
* The Windows version that has been used to reproduce the error is Windows 11 Pro for Workstations Compilation 23H2 (22631.2861).
* The problem has appeared consistently since the OS was reinstalled but has shown itself in several measures since the device was purchased.
To reproduce the issue, it is enough to follow the following steps:

* Install the latest version of JRiver Media Center 31 (31.0.87 64-bit at the time of writing)
* Following the instructions described in the Wiki, create separate zones for each of the available audio output devices and a zone used for Playback.
* Enable the WDM Driver in the Feature List of the Options menu.
* Reboot the computer
* Using ZoneSwitch, select the Playback zone and move it to the end of the list.
* Using the same procedure, select the desired device zone and list it at the top.
* Select the JRiver DSP device in the computer's Sound Control Panel.
* Select the device as an output in the active device zone.
* Open any audio-playing app (So far tested TIDAL, Plexamp, Microsoft Edge, the Netflix UWP app and Windows Media Player)
* Playback gets recognized by the system, and using software like Rainmeter to show a Spectrometer displays the corresponding track as expected.
* JRiver though shows only a sample of white noise, which fortunately I was able to capture and attach here using the Disk Writer as an output device.
* Depending on the mood of the device, the problem might come and go by itself, require a reboot, closing and opening the program, or a combination of all of the previous answers. having the computer go to sleep or change the order and availability of the output devices tends to worsen the issue.
* At the moment the problem can be seen to happen to the following devices:
* FiiO BTR7 USB DAC through ASIO
* The Realtek Onboard DAC of the computer through WASAPI (both the Onboard Speakers and the 3.5mm Jack)
* The HDMI output through the Nvidia RTX 3070 Laptop GPU using DirectSound going to a Samsung UN40EH5300F LED TV
* The Bluetooth A2DP LDAC output to a pair of Sony WH-1000XM4 using DirectSound (While using the Luculent Systems Alternative A2DP Driver)As per the logs, I'm not sure how useful it would be, but I managed to capture the following attachment.

I hope the information provided can help lead us in the right direction, but in the meantime I'd like to thank you in advance for the help and wish you happy holidays!

If there's anything else you might need, please let me know.

JimH:

--- Quote ---   Enable the WDM Driver in the Feature List of the Options menu.
   Reboot the computer
   Using ZoneSwitch, select the Playback zone and move it to the end of the list.
   Using the same procedure, select the desired device zone and list it at the top.
   Select the JRiver DSP device in the computer's Sound Control Panel.

--- End quote ---
Do you mean select WDM?  It's a driver, not a DSP device.

--- Quote ---   Select the device as an output in the active device zone.

--- End quote ---
This should be the sound device.

--- Quote ---   Open any audio-playing app ...

--- End quote ---
If you test after setting up, but without doing any zones or zone setup, what happens?  Can you make WDM work at all?
If not, the DAC isn't doing its job.
If so, maybe you've found a problem we don't know about.

Turn off anything you have set in DSP Studio.

Navigation

[0] Message Index

[#] Next page