INTERACT FORUM
More => Old Versions => JRiver Media Center 21 for Windows => Topic started by: AlexS on August 24, 2015, 03:32:35 pm
-
Can this be fixed for version MC21 please?
"The JRiver ASIO driver can be enabled and disabled in Options > General > Features > ASIO Driver."
However you still see the MC output drivers in other software after doing this (and restarting JRiver).
Workaround is to rename the folder:
C:\Program Files (x86)\J River\Media Center 21\Drivers
... but you have to remember to do this everytime you update MC
Thanks!
-
I agree.
I show three JRiver ASIO drivers and one PonoMusic driver.
-
I'm confused by this one.
After disabling the feature, we register the driver DllRegisterServer(...). It internally switches to an unregister if the feature is now disabled. So it calls DllUnregisterServer.
That deletes the registry keys for the ASIO plugin.
So it sounds like something is falling down, but what?
-
You need elevation to do that, and the current command as called from MC does not have it.
Should probably redirect it through PackageInstaller to get elevated.
-
Yup, I was just coming back here to say it wasn't elevated. I'll make a Package Installer command for the next build.
Hopefully it'll all be squared away then.
-
Thanks!
-
Can this be fixed for version MC21 please?
"The JRiver ASIO driver can be enabled and disabled in Options > General > Features > ASIO Driver."
However you still see the MC output drivers in other software after doing this (and restarting JRiver).
Workaround is to rename the folder:
C:\Program Files (x86)\J River\Media Center 21\Drivers
... but you have to remember to do this everytime you update MC
Thanks!
I am seeing this in v20.0.132 as well.
I built my new Windows 10 DAW last week and am now finalizing the software installs. But today as I add in my Native Instruments VSTi's - each time I open a standalone instance of an instrument to check it - MC is now opening up as well....and displaying itself as a "audio driver" for something like Kontakt to use.
I did not install the driver - yet - there it is in my driver listing
What gives? And how do I rid my system of it?
EDIT: Interesting chain of events now.
When I installed my new DAW last week - I initially placed 20.0.131 on the machine and that's the version that was exhibiting the behavior as noted above. But - without changing any settings - expect for which "channel" to watch for builds - I switched from Stable to Latest - and got 20.0.132.
As soon as I installed that build - all references to the JRiver ASIO driver disappeared from all the usual spots. So issue solved for me :)
VP