Wdm driver for windows

[Note: Recent releases of Windows 10 have made this more difficult. Please see the Problems section at the bottom of this topic.]

JRiver Media Center version 20 for Windows introduced a WDM Driver (a virtual audio driver), which can be used to re-route all windows sound through Media Center. This allows full use of Media Center’s DSP stack for web content, and allows better integration with external audio sources, like streaming video services or video games. The driver is currently only available on Windows.

How to Set up the WDM Driver

1. 

   Картинка с сайта: wiki.jriver.com

   In versions of Media Center after 20.0.95 the WDM driver is disabled by default. To enable it go to Options—>General—>Features and check WDM Driver. Then restart Media Center and the driver will install.

2. Once the driver is installed, go to the windows control panel, and then to the Sound menu item. You should see all of the Audio devices on your system listed. Select the one labelled JRiver Media Center and click the Set Default button at the bottom of the menu as shown to the right.
3. Make sure that, in Media Center, your setting under Options—>Audio—>Audio Device is not «Default Audio Device.» You need to set your audio device to whatever your actual physical output device is. Because the WDM Driver is now the system default, setting Media Center to output to the system default just creates a closed loop.

Note: If JRiver doesn’t show up as a Windows Device in Control Panel > Sounds > Playback, try disabling it in MC General > Features. Restart MC and re-enable WDM.

When system audio plays (from web browsers, apps, windows sounds, or video games), it will play to the JRiver Media Center driver. This re-routes the audio through Media Center’s DSP stack to whatever output device you have selected as an audio output in Media Center.

Troubleshooting Common Issues

Clicks, Pops, and Static

Clicks, pops, and static are typically caused by buffer underruns. Because the WDM Driver is re-routing sound in real time, it is more sensitive to buffering settings than normal audio playback. There are two buffers that are important to WDM performance:

• The output buffer, found at Options—>Audio—>Device Settings, and
• The input buffer, found at Options—>Audio—>Advanced—>Live Playback Latency

If you are experiencing clicks and pops, try different combinations of settings with these two buffers. It is important to note that a larger buffer will not necessarily work better. Different hardware configurations work best with different combinations of settings, so try different combinations large and small until you find settings that resolve your issue.

Lipsync

Because the WDM driver requires some buffer to function, it necessarily adds some latency to audio. For pure audio applications, this is irrelevant, but for streaming video (or video games), too much latency can cause lipsync issues. If you’re experiencing these issues, you can adjust the two buffers listed under Clicks, Pops, and Static above. The total added latency is close to the sum of those two buffers, so you want to try and find the combination of buffer settings that creates the lowest total latency, but doesn’t cause audio drop outs as described above.

The recommendation for lipsync in film is about 22ms; the recommendations for television are about 45ms. Most delays below 45ms will not create visible lipsync issues, and higher latency may or may not be noticeable to all viewers. If your combined buffer settings are below this threshold, and you still have noticeable lipsync issues, there may be other factors contributing to your latency other than the WDM Driver, such as that native latency of your audio device or using certain DSP modules (such as Convolution).

«IPC» in Playing Now

The WDM driver’s output appears in Media Center’s playing now as a library item named IPC. It stands for «inter-process communication.» If you see it in your playing now, it’s proof that the WDM driver is working.

Problems With Streaming Video Using Media Center’s Internal Browser and/or Erasing Playing Now

Because of the way Media Center’s Playing Now is structured, the WDM driver can sometimes have unintended consequences, and this section provides some workarounds for those issues.

• For example, if playback is stopped and you’re queueing up tracks to play by adding them to playing now, and a windows sound plays (engaging the WDM driver), you may find that the playing now is now suddenly empty except for IPC. That happens because the WDM driver acts just like any other library item that you play, replacing the current playing now.
• Similarly, you may find that if you use Media Center’s internal browser to navigate to a streaming video website, when you click play, the WDM driver will engage and steal focus, effectively stopping video playback.

Neither of those situations is desirable, but there’s a fix: setup an extra zone to receive WDM input, and setup a zoneswitch rule to automatically route WDM input to that zone. Properly configured, it will protect your playing nows, and also prevent the WDM from stealing focus from web video. Here are step-by-step instructions adapted from the forum:

1. Setup the WDM driver as described above
2. Go to Player—>Zone—>Add Zone. In the dialog box that pops up name the zone something like loopback, and in the second box choose to copy your current working zone (it may be named «Player» if you haven’t edited it). Click «ok»
3. Now right click on the new zone under playing now, and click on the «ZoneSwitch» context menu item. If you already have zoneswitch rules, you’ll need to add a rule that routes WDM driver output to the new zone; if you’ve never used zoneswitch before, do this:
   1. In the dialog box, press the add button. Then name the rule something like «loopback,» and enter the following rule [Name]="IPC" . Then tell it to play in the loopback zone and stop playback in your normal zone.
   2. Add a second rule, and name it something like «normal,» and enter the following rule -[Name]="IPC". Then tell that rule to play in your normal zone and stop playback in the loopback zone.
4. Some people have reported that they had to change their Jump on Play (audio) settings under Options—>General—>Behavior to «None» for best results, but it typically works fine without changes to that option.

Once configured, if you try to play a streaming video service from inside Media Center’s internal browser it should work fine. Just make sure to start playback from your normal zone, and not the loopback zone.

The primary limitation with this method is that volume control isn’t easy to manage because the zone you’re playing the video in won’t be playing the audio so the normal volume controls may not work as expected. However, you can still adjust volume in the streaming video service’s on screen volume control and it should work; it’s just Media Center’s volume control that can be hard to manage. Another good solution is to make sure to set the default volume in your loopback zone to the volume at which you you normally like to watch streaming content, so it’s close to correct by default.

Problems

If JRiver doesn’t show up as a Windows Device in Control Panel > Sounds > Playback, try disabling it in MC General > Features. Quit MC and re-enable it.

Please see Hendrik’s advice here: https://yabb.jriver.com/interact/index.php/topic,127330.msg883267.html#msg883267

Resources

• The official forum thread on the WDM Driver
• A more detailed explanation of the multi-zone workaround
• Fixing latency problems

Microsoft Windows has been a work in progress for nearly three decades and the WDM driver is one of many ideas that the Microsoft team developed during the 1990’s. The Windows driver model was developed to enable programmers and developers to create forward compatible drivers that would work with little or no modification on future editions of the Windows operation system.

WDM allows developers to write one driver for multiple platforms by using the latest version of the Windows DDK framework. This innovation reduced the amount of time a developer needed to spend on coding and testing a driver. WDM was first used in Windows 98 and is still currently in use. Criticisms toward WDM caused Microsoft to develop a successor to WDM called KMDF that is supported by Microsoft Vista and Windows 7.

WDM drivers were very useful for creating higher quality sound and videos drivers as well as faster input and output drivers. WDM was even useful in developing kernel level drivers for early USB integration and simplified the installation of network devices for all computer users. Once the initial confusion was handled, WDM drivers allowed developers to create kernel level code easier than ever before however there were some problems according to many developers.

Related:

Common WDM Drivers Problems

WDM drivers were a great improvement upon previous driver development strategies. Problems can and do occur when code updates and patches for various hardware and software are released. Some of the common problems with WDM drivers include:

1. WDM was initially hard to learn for programmers at the time Microsoft released the framework due to its different way of handling code. I/O cancellation requests were difficult to complete within the WDM framework.

2. WDM required a great deal more coding effort than previous methods of driver production. Developers generally needed more support staff to help create drivers for the WDM framework.

3. WDM drivers operate at the kernel level and when a malfunction occurs the result is usually a blue screen with little or no information the end user can interpret or diagnose unless they have experience with WDM coding. WDM is not user friendly to either the developer or the user.

4. WDM has problems interacting well with the power management features contained within windows causing many machines difficulty in going into sleep mode or waking up upon request. Plug and play issues resulting in the infamous blue screen of death are frequent on systems that have aged.

Troubleshooting WDM Drivers

If you are an end-user and you develop a WDM driver issue your probably never going to be aware of it beyond the fact that one part or another of your computer just stops working. The best advice for the average computer user is to reinstall the software for the device that quit on you. If this does not work, your next step will be to either call a service technician or reinstall your operating system from scratch.

If you are a developer and are having trouble with your WDM driver development Microsoft has plenty of developer assistance on their various websites and thousands of support forums on the web where you can find help. A good place to start is the book by Walter Oney entitled ‘Programming the Windows Driver Model’.

Related PC Drivers

WDM Driver Release
NVIDIA DRIVERS 1.331.0.1WHQL

All other trademarks, logos and brand names shown on this website other than stated are the sole property of their respective companies and are not owned by oemdrivers.com. Information on the oemdrivers.com may not be duplicated without permission. oemdrivers.com is not responsible for any damages or losses that may arise from incorrect driver installation. Only install drivers if you are qualified to do so.

About — Terms of Use — Privacy Policy & Cookies — Copyright Policy — Contact — OEM Drivers ©2018 — 2025