More > JRiver Media Center 22 for Windows
WDM driver and volume control
mattkhan:
--- Quote from: BCZ on April 15, 2017, 07:50:04 am ---So does everyone have this problem? And everyone has their own way to deal with this? This seems like a very basic and big limitation.
--- End quote ---
I don't have this problem on any of my machines, it just works for me (on linux and windows). Is there anything useful in the jriver log?
mwillems:
One thing I haven't seen: how are you interfacing with the WDM Driver? I.e. how are you playing to it to test it? If I change the WDM driver's volume in the windows mixer it changes the volume coming out of JRiver on the back end. The only way I've found to reproduce what you're seeing is if some program takes exclusive control of the WDM driver (for instance by using WASAPI exclusive or ASIO4All to interface with the WDM driver). Then the volume change is being ignored, but that's by design (i.e. that's what exclusive control of the device means in part).
It's very odd that you can't get JRiver's internal volume to respond to media keys; that just works out of the box on every machine I've tried on, although it sometimes acts unpredictably when MC isn't in focus. Can you test to see if focus affects it?
In any case, a little more info about what your playback chain looks like would be helpful.
BCZ:
--- Quote from: mwillems on April 15, 2017, 12:45:52 pm ---One thing I haven't seen: how are you interfacing with the WDM Driver? I.e. how are you playing to it to test it? If I change the WDM driver's volume in the windows mixer it changes the volume coming out of JRiver on the back end. The only way I've found to reproduce what you're seeing is if some program takes exclusive control of the WDM driver (for instance by using WASAPI exclusive or ASIO4All to interface with the WDM driver). Then the volume change is being ignored, but that's by design (i.e. that's what exclusive control of the device means in part).
It's very odd that you can't get JRiver's internal volume to respond to media keys; that just works out of the box on every machine I've tried on, although it sometimes acts unpredictably when MC isn't in focus. Can you test to see if focus affects it?
In any case, a little more info about what your playback chain looks like would be helpful.
--- End quote ---
I've actually completely reinstalled (i.e. format) Windows 10 twice for JRiver, then installed the Boot Camp drivers (because this is a MacBook Pro), the latest Asus Xonar U7 driver, installed JRiver, followed the wiki to activate WDM in the features list, set JRiver's output to the U7 on WASAPI, then use foobar2000 to play music. I've done that on 3 different computers, 2 MacBooks and 1 HP desktop (which I used an integrated sound card). The volume control does not work on any of the computers.
The signal chain is just enable WDM driver, set JRiver as default output, then use foobar2000 for music. JRiver outputs to my Xonar U7, which is connected to my amps for my active speakers.
I'll check out the log later when I have some time. But it must be something procedural that is wrong.
mwillems:
Foobar 2000 supports wasapi exclusive mode; check your foobar configuration to see if it's taking full control of the sound device. If so that may be why the volume isn't working. It's also possible that Foobar (being an audio program) is intercepting the media keypresses intended for JRiver. One useful way to test would be to exit foobar entirely and try using web-audio (i.e. from youtube) to test the WDM driver. Then see if volume control works. If it does, it's probably foobar taking control of the device and/or intercepting media keys.
I'm sure you've thought of this, but for plain old local playback of audio and video files you'd probably be much better off (both practically and in terms of reducing processing steps in the signal chain) by playing the files directly in JRiver rather than using foobar to loop back through the WDM driver (so JRiver can then play them). The place where the WDM driver shines is in funneling web content or netflix which you can't play directly in JRiver.
BCZ:
--- Quote from: mwillems on April 15, 2017, 01:08:17 pm ---Foobar 2000 supports wasapi exclusive mode; check your foobar configuration to see if it's taking full control of the sound device. If so that may be why the volume isn't working. It's also possible that Foobar (being an audio program) is intercepting the media keypresses intended for JRiver. One useful way to test would be to exit foobar entirely and try using web-audio (i.e. from youtube) to test the WDM driver. Then see if volume control works. If it does, it's probably foobar taking control of the device and/or intercepting media keys.
I'm sure you've thought of this, but for plain old local playback of audio and video files you'd probably be much better off (both practically and in terms of reducing processing steps in the signal chain) by playing the files directly in JRiver rather than using foobar to loop back through the WDM driver (so JRiver can then play them). The place where the WDM driver shines is in funneling web content or netflix which you can't play directly in JRiver.
--- End quote ---
Media key volume control doesn't work anywhere. Not with a YouTube video on Chrome, or when JRiver is the program in focus. My trial ended on my Windows desktop, so I can't confirm if this happens on a non Bootcamp Windows computer.
Yes, I do plan on moving my music over to JRiver, but only if things actually work. So far I've gotten many things to work, but there are still thorns about this problem. The next one is dealing with the very noticeable lag of about 1 second with audio streamed through WDM. Video is very out of sync.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version