Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[MGD_King]

I noticed that my PC stopped using the WDM driver in MC30. The only way to get it back is to uncheck it in the MC options, close MC and server, reopen, recheck, and then it is listed an audio device in Windows 11 and I can select it. This happens whenever the program updates.

[HPBEME]

Same here.

Every time there is a major version update, I have to uncheck WDM driver in Options/General/Features, closeout MC completely, then re-enable WDM drivers, closeout of MC completely.  After all that, when I launch MC again the WDM drivers work again.  Obviously not the end of the world to go through this process each major version change, but it would also be nice to not have to.

[terri ball]

Had both V26 and V27 installed for ages and after uninstalling V26 the same issue occured.

[HPBEME]

Yes… it happens every time you install a new major version (even when the "new" major version is reverting to a prior one).  Apparently the WDM driver user setting is impossible to carryover between major versions, or it is too low on the totem pole for the developers to address.

[Dawgincontrol]

Have to admit, I gave up on the WDM driver because it would just disappear so often.

[JimH]

Have to admit, I gave up on the WDM driver because it would just disappear so often.

Not at all normal or common.  Check the wiki page for instructions.

[JimH]

Yes… it happens every time you install a new major version (even when the "new" major version is reverting to a prior one).  Apparently the WDM driver user setting is impossible to carryover between major versions, or it is too low on the totem pole for the developers to address.

It's a driver and Microsoft makes the rules for installing drivers.

[eve]

Not uncommon at all.

For specific AoIP stuff I have to use a custom driver for Intel NICs to enable proper IEEE-1588 support on Windows. Any time Windows decides to update guess what? There's a good chance you've gotta re-install the driver.

That's sort of how it's always been.

[HPBEME]

Thanks for the clarification Jim. I figured the issue lay with the OS rather than MC, but it is nice to know specifically why it has to be reset each time.

I gather from Dawgincontrol and Eve's posts that they need to reset the WDM option regularly. For me it only crops up for me during an install of a new MC major version, and is not affected by MC minor versions (ever) or Windows updates (occasionally maybe? If it occurs at all, it is rare).  My setup is very simple - computer straight to speakers with no fancy audio equipment in between (well I guess I do have a headphone amp, but that's it). So maybe that's the difference?

While it is not terribly arduous to reset the option and then start MC a couple times to get everything back to where was, it would be a bit of PITA if you had to do that every few months/weeks.

[eve]

Thanks for the clarification Jim. I figured the issue lay with the OS rather than MC, but it is nice to know specifically why it has to be reset each time.

I gather from Dawgincontrol and Eve's posts that they need to reset the WDM option regularly. For me it only crops up for me during an install of a new MC major version, and is not affected by MC minor versions (ever) or Windows updates.  My setup is very simple - computers straight to speakers with no fancy audio equipment in between. So maybe that's the difference?

While it is not terribly arduous to reset the option and then start MC a couple times to get everything back to where was, it would be a bit of PITA if you had to do that every few months/weeks.

I don't use the JRiver WDM Driver but the same logic applies, I would assume the trigger is when the driver is rebuilt (a new version), that would require user intervention.
This is a good thing, drivers can be extremely dangerous from a security standpoint, thus, a user should have to okay them first Obviously, I'm not talking about the security of JRiver's WDM driver because there's 0 concern there, but drivers in general.

Not sure if this overcomes the problem but could JRiver include a 'Wizard' that auto launches after an upgrade if the user's configuration has the WDM Driver enabled and prompts them to re-activate the driver?