INTERACT FORUM

Please login or register.

Login with username, password and session length
Advanced search  
Pages: [1]   Go Down

Author Topic: WDM Driver Problem  (Read 3862 times)

sjhilton

  • Junior Woodchuck
  • **
  • Posts: 73
WDM Driver Problem
« on: October 05, 2019, 01:33:45 am »
The wdm driver appears to be broken on every version of JRiver after .098. On both of the windows 10 PCs I have a dialogue pop up saying 'there is nothing to play' when the driver engages and no sound (if there is something in the 'playing now' queue it will automatically start playing what JRiver last played eg a music file). There is a similar response if WASAPI Live loopback is engaged. There is sound going to windows mixer, because if you open the settings the wdm driver is playing audio. I'm happy to supply logs if useful. Reinstalling .098 fixes the problem immediately. I have tried activating and reactivating the WDM driver feature, but that doesn't change anything.
Logged

BigSpider

  • Galactic Citizen
  • ****
  • Posts: 350
Re: WDM Driver Problem
« Reply #1 on: October 05, 2019, 05:37:54 am »
I am currently playing Amazon HD via wdm to MC 25.0.113 which is applying the dsp settings and outputting via asio to my dac and speakers. It sounds pretty good to me and definitely not broken.
Logged
English spiders are kind of small, but when I was living in the African rain forest well ......

JimH

  • Administrator
  • Citizen of the Universe
  • *****
  • Posts: 71370
  • Where did I put my teeth?
Re: WDM Driver Problem
« Reply #2 on: October 05, 2019, 06:49:30 am »
Try using MC's DSP Studio > Output Settings to force output to 48Khz, etc.
Logged

sjhilton

  • Junior Woodchuck
  • **
  • Posts: 73
Re: WDM Driver Problem
« Reply #3 on: October 07, 2019, 12:23:20 am »
Thanks for the suggestion Jim - unfortunately that didn't solve the issue. I have a separate WDM playback zone, which I set all output frequencies to 48kHz under Output Format. I actually had this already set on one of the machines.
Logged

RoderickGI

  • MC Beta Team
  • Citizen of the Universe
  • *****
  • Posts: 8186
Re: WDM Driver Problem
« Reply #4 on: October 07, 2019, 02:45:20 am »
Turn off the WDM Feature.
Restart the PC.
Turn on the WDM Feature.
Restart MC.
Set Windows Default Audio Device to Media Center 25 (the WDM).
Play a YouTube video with sound.
Check the MC Audio Path is active, and shows the audio.

All good?
Logged
What specific version of MC you are running:MC27.0.27 @ Oct 27, 2020 and updating regularly Jim!                        MC Release Notes: https://wiki.jriver.com/index.php/Release_Notes
What OS(s) and Version you are running:     Windows 10 Pro 64bit Version 2004 (OS Build 19041.572).
The JRMark score of the PC with an issue:    JRMark (version 26.0.52 64 bit): 3419
Important relevant info about your environment:     
  Using the HTPC as a MC Server & a Workstation as a MC Client plus some DLNA clients.
  Running JRiver for Android, JRemote2, Gizmo, & MO 4Media on a Sony Xperia XZ Premium Android 9.
  Playing video out to a Sony 65" TV connected via HDMI, playing digital audio out via motherboard sound card, PCIe TV tuner

Awesome Donkey

  • Administrator
  • Citizen of the Universe
  • *****
  • Posts: 7375
  • The color of Spring...
Re: WDM Driver Problem
« Reply #5 on: October 07, 2019, 04:52:16 am »
You may have to run MC as an administrator when turning the WDM feature off and back on for it to work correctly, if I recall.
Logged
I don't work for JRiver... I help keep the forums safe from Viagra and other sources of sketchy pharmaceuticals.

Windows 11 2023 Update (23H2) 64-bit + Ubuntu 24.04 LTS Noble Numbat 64-bit | Windows 11 2023 Update (23H2) 64-bit (Intel N305 Fanless NUC 16GB RAM/256GB NVMe SSD)
JRiver Media Center 32 (Windows + Linux) | Topping D50s DAC | Edifier R2000DB Bookshelf Speakers

sjhilton

  • Junior Woodchuck
  • **
  • Posts: 73
Re: WDM Driver Problem
« Reply #6 on: October 08, 2019, 06:38:32 am »
Thanks everyone. Unfortunately those suggestions didn't solve the issue, but I have worked out what appears to be causing it.

If I connect to 'main library' everything works fine. If I connect to a library server (as I always do from both clients) it breaks and comes up with the 'There is nothing to play' error as I described.

I'd be interested to see if anyone can replicate this.

I'm connecting both clients to a docker container running on my QNAP NAS so I guess the issue could be at either the linux or windows end (it's linux version 25.0.108).

I'll revert to version .098 on my windows 10 clients for now.
Logged

Hendrik

  • Administrator
  • Citizen of the Universe
  • *****
  • Posts: 10712
Re: WDM Driver Problem
« Reply #7 on: October 08, 2019, 08:25:59 am »
I use MC as a Library Client on the same machine as I use the WDM driver, no issues there.
Logged
~ nevcairiel
~ Author of LAV Filters

RoderickGI

  • MC Beta Team
  • Citizen of the Universe
  • *****
  • Posts: 8186
Re: WDM Driver Problem
« Reply #8 on: October 08, 2019, 03:51:41 pm »
Quote from: Hendrik on October 08, 2019, 08:25:59 am
I use MC as a Library Client on the same machine as I use the WDM driver, no issues there.

Same here.

As you are getting the  'There is nothing to play' error, you should look at your Zones.
Which one is active when you play to the WDM?
Which one has content listed against it in Playing Now? (Clear all Zone Playing Now's before testing, and see where your media is directed to.)
Do you have fancy ZoneSwitch rules?
Do you have multiple Zones set up in MC?
Logged
What specific version of MC you are running:MC27.0.27 @ Oct 27, 2020 and updating regularly Jim!                        MC Release Notes: https://wiki.jriver.com/index.php/Release_Notes
What OS(s) and Version you are running:     Windows 10 Pro 64bit Version 2004 (OS Build 19041.572).
The JRMark score of the PC with an issue:    JRMark (version 26.0.52 64 bit): 3419
Important relevant info about your environment:     
  Using the HTPC as a MC Server & a Workstation as a MC Client plus some DLNA clients.
  Running JRiver for Android, JRemote2, Gizmo, & MO 4Media on a Sony Xperia XZ Premium Android 9.
  Playing video out to a Sony 65" TV connected via HDMI, playing digital audio out via motherboard sound card, PCIe TV tuner

sjhilton

  • Junior Woodchuck
  • **
  • Posts: 73
Re: WDM Driver Problem
« Reply #9 on: October 09, 2019, 04:31:55 am »
Thanks RoderickGI.

The first thing I did when I was diagnosing the problem was to disable zoneswitch. Unfortunately that isn't the issue.

I have a 'WDM' and 'not WDM' zoneswitch arrangement. WDM directs audio to my WDM zone (the criteria I use for this is [Filename]="live:////ipc" and all other playback is set to stop in the other zones) and the 'not WDM' directs audio to my default playback zone (the criteria used is -[Filename]="live:////ipc") and stops playback in the WDM zone (the only thing this really does is stop playback in the WDM zone which is set quite a bit louder than the default playback zone).

If zoneswitch is enabled JRiver is not detecting that the playback is coming from WDM so it doesn't switch to the WDM zone - it just gives the 'there is nothing to play' message in the default zone if the playing now queue is empty or if it's not empty then it will just play whatever was last played in playing now (eg the last track of an album that I was listening to).

Thanks again everyone. I'll see if I get a different response connecting the two windows 10 machines as server and client, but then I'm certainly out of ideas.
Logged

sjhilton

  • Junior Woodchuck
  • **
  • Posts: 73
Re: WDM Driver Problem
« Reply #10 on: October 09, 2019, 05:17:04 am »
Just to follow up - everything works perfectly between two windows 10 PCs running .113 so whatever the issue is it is being caused by some interaction between my linux server and the windows clients.
Logged

sjhilton

  • Junior Woodchuck
  • **
  • Posts: 73
Re: WDM Driver Problem
« Reply #11 on: October 09, 2019, 05:29:56 am »
Further (and final) followup - I tested the latest ARM version on my raspberrypi, set that up as a new server, connected one of my windows 10 client and the same issues were present.
Logged

RoderickGI

  • MC Beta Team
  • Citizen of the Universe
  • *****
  • Posts: 8186
Re: WDM Driver Problem
« Reply #12 on: October 09, 2019, 05:59:36 pm »
Ah, so it is a unique issue to a Windows MC Client connected to a Linux MC Server, and then playing to the WDM on the Windows Client.

That is one for JRiver.
Logged
What specific version of MC you are running:MC27.0.27 @ Oct 27, 2020 and updating regularly Jim!                        MC Release Notes: https://wiki.jriver.com/index.php/Release_Notes
What OS(s) and Version you are running:     Windows 10 Pro 64bit Version 2004 (OS Build 19041.572).
The JRMark score of the PC with an issue:    JRMark (version 26.0.52 64 bit): 3419
Important relevant info about your environment:     
  Using the HTPC as a MC Server & a Workstation as a MC Client plus some DLNA clients.
  Running JRiver for Android, JRemote2, Gizmo, & MO 4Media on a Sony Xperia XZ Premium Android 9.
  Playing video out to a Sony 65" TV connected via HDMI, playing digital audio out via motherboard sound card, PCIe TV tuner

pschelbert

  • Galactic Citizen
  • ****
  • Posts: 459
Re: WDM Driver Problem
« Reply #13 on: October 20, 2019, 08:03:58 am »
since I switched to ASIO I have not anymore driver problems.

Microsoft does not understand audio, many different driver models, none working bullet proof. WDM is another example.

Go with the pros, use ASIO.

Peter
Logged

JimH

  • Administrator
  • Citizen of the Universe
  • *****
  • Posts: 71370
  • Where did I put my teeth?
Re: WDM Driver Problem
« Reply #14 on: August 08, 2020, 07:37:44 am »
Quote from: sjhilton on October 09, 2019, 04:31:55 am
I have a 'WDM' and 'not WDM' zoneswitch arrangement. WDM directs audio to my WDM zone (the criteria I use for this is [Filename]="live:////ipc" and all other playback is set to stop in the other zones) and the 'not WDM' directs audio to my default playback zone (the criteria used is -[Filename]="live:////ipc") and stops playback in the WDM zone (the only thing this really does is stop playback in the WDM zone which is set quite a bit louder than the default playback zone).
Wild guess.  The rule you're using is escaping the slashes.  Something there isn't right.  It would explain why Windows works for you, but linux doesn't. 
Logged

mattkhan

  • MC Beta Team
  • Citizen of the Universe
  • *****
  • Posts: 3961
Re: WDM Driver Problem
« Reply #15 on: August 08, 2020, 08:04:52 am »
not obvious to me how this could be related to the OS of the library server but I tested it anyway and browser to MC client on windows client connected to a linux server works fine for me, both with and without the specified zoneswitch rules.

Logged

sjhilton

  • Junior Woodchuck
  • **
  • Posts: 73
Re: WDM Driver Problem
« Reply #16 on: August 08, 2020, 10:40:58 pm »
Thanks both of you for the follow up. I confirmed just now that I still have the same issue (irrespective of whether zoneswitch is enabled). From a Windows 10 client WDM works if it is connected to 'main library' (I've just tried it on three machines - one of which is a clean install). The main update to what I posted previously is that I have confirmed I experience the same issue when connecting to a windows library server as well. So I've verified it is not an OS issue at least. I have tried a test video on youtube and it presented an 'audio renderer error' when attempting playback (running Chrome). All machines are now running the most current version of 26. It is a mystery. I'm happy to try any other suggestions you have. Apologies for cross posting on this.
Logged
Pages: [1]   Go Up
« previous next »