INTERACT FORUM
More => Old Versions => JRiver Media Center 20 for Windows => Topic started by: AoXoMoXoA on October 30, 2014, 01:15:11 pm
-
Where is the option within Media Center where I can set it to not change my default audio device to JRiver WDM when updating to a newer build of MC?
I had disabled the MC WDM device in my Windows sound options and updating MC changed it once again to your WDM as default.
I do not wish to use this as it had too much lag causing videos to be out of sync with their audio.
I believe I should have the option to set this as I choose and should not need to reset it after each update.
-
Where is the option within Media Center where I can set it to not change my default audio device to JRiver WDM when updating to a newer build of MC?
I had disabled the MC WDM device in my Windows sound options and updating MC changed it once again to your WDM as default.
I do not wish to use this as it had too much lag causing videos to be out of sync with their audio. I believe I should have the option to set this as I choose.
Humorously I have the opposite problem; I have the WDM driver set as default and want it to remain the default, but every update seems to un-default it. A few others have reported similar issues; something in the driver install is disturbing the default driver settings in an inconsistent way.
-
Unfortunately, there isn't really a way to control this. All we tell Windows is to update the driver, and it does whatever it does.
Microsoft intentionally doesn't want applications messing with the default audio device, which means they do not even have functions to change the default device, or tell it not to change, or anything.
In practice, most people won't update audio drivers on a weekly basis, and thus never notice any problems with actual audio devices.
We're kinda in a special place here.
-
So what are the alternatives?
Surely you can't expect your software to make unapproved/unwanted system device changes to all user's machines with every install.
Can't this "Device" be an option in the install process? Or perhaps it can be offered as an optional add-on for separate install for those who desire it.
If neither of these are acceptable then at least get it to work properly . . . the audio lag when watching a video is unacceptable.
-
Is the driver actually changing after each build? I can understand what Hendrik is saying, about microsoft; but why not just have a driver install when the driver is modified, not on every build. Its when there are multiple clients and multiple users involved, where it gets sticky.
Or have a separate download for it like most drivers? Would that be doable?
@AoXo -- reading the sticky on this, you will find videos that help you. You must sync the video with the audio, then there is no problem
-
If neither of these are acceptable then at least get it to work properly . . . the audio lag when watching a video is unacceptable.
Latency is not something we can fix, its an inherent drawback of the whole system.
Careful tweaking in your system can reduce the latency, but never eliminate it.
-
@AoXo -- reading the sticky on this, you will find videos that help you. You must sync the video with the audio, then there is no problem
Thank you for the information, however:
I am sure there are a number of users who either cannot, or do not wish to go through such procedures to accommodate unwanted changes to their machines.
If the developer is inclined to make such system changes I feel they should accommodate me rather than the other way around, and if not allow me to opt out of such changes.
Latency is not something we can fix, its an inherent drawback of the whole system.
Careful tweaking in your system can reduce the latency, but never eliminate it.
All the more reason NOT to force this install on users! If it cannot be installed in a properly working fashion (no latency), or made to be automatically self-adjusting then it needs to be an option.
-
Thank you for the information, however:
I am sure there are a number of users who either cannot, or do not wish to go through such procedures to accommodate unwanted changes to their machines.
If the developer is inclined to make such system changes I feel they should accommodate me rather than the other way around, and if not allow me to opt out of such changes.
All the more reason NOT to force this install on users!
In the last version (.29) there was a change to allow folks to opt out:
2. Changed: The installer can be run with /NoDriver to skip the driver install.
-
In the last version (.29) there was a change to allow folks to opt out:
2. Changed: The installer can be run with /NoDriver to skip the driver install.
I am using .030 and did not see such option offered . . . . I will reinstall and look for it.
Nope not offered, and I did check "Custom Install"
-
I am using .030 and did not see such option offered . . . . I will reinstall and look for it.
Nope not offered, and I did check "Custom Install"
You have to run the installer from the command line with the text "/NoDriver" after the installer .exe.
I agree that's not the most convenient thing in the world, but it is an available way to opt out.
-
You have to run the installer from the command line with the text "/NoDriver" after the installer .exe. I agree that's not the most convenient thing in the world, but it is an available way to opt out.
While I am grateful about this option - what happens if I do install a version using the switch now (No driver) and then update to a newer version later - WITHOUT the switch (because I forgot to run it that way). I will assume the driver will just install itself again?
Not good at all.
VP
-
While I am grateful about this option - what happens if I do install a version using the switch now (No driver) and then update to a newer version later - WITHOUT the switch (because I forgot to run it that way). I will assume the driver will just install itself again?
Not good at all.
VP
I thought I suggested a "Stable (No Driver)" update channel in this thread but looks like my post failed or something. That would resolve the issue of subsequent updates installing the driver or not.
-
Microsoft intentionally doesn't want applications messing with the default audio device, which means they do not even have functions to change the default device, or tell it not to change, or anything.
https://code.google.com/p/audioswitch/ (https://code.google.com/p/audioswitch/)
Someone figured out a way to do it.