More > JRiver Media Center 19 for Windows
JRiver audio engine as an ASIO driver - uninstall?
Vocalpoint:
--- Quote from: Matt on September 29, 2013, 07:23:21 pm --- If the driver isn't causing troubles, why do you care if it's in the list? I don't mean to question your motivation -- I'm just trying to understand if it's an OCD thing (which I can certainly appreciate!) or if there's some technical consideration.
ASIO driver registration is just a few simple registry keys, and nothing is loaded unless the driver is in use. There's no system overhead unless it's actively being used.
Thanks.
--- End quote ---
Matt,
I realize you are working on this to make it as non-obtrusive as can be - and while I am not speaking for others - for my DAWs - I do not want any additional listings or matter of fact - any other ASIO "driver" installs - at all.
We all have our specific reasons and our specific audio interfaces that we choose for pro level production. But I am finding this v19 ASIO function to be invasive since we cannot even use the app without it automatically installing itself as a "driver".
While this is not quite a malware scenario - it definitely is a case of lower level system software being installed without any user involvement over whether it should be allowed or not.
Ideally - with this "MC as an ASIO driver" in v19 - there should be an option during install asking the user if they want this ASIO driver function. Then the user could opt in or out as their situation dictates.
I am hoping you can work this out so v19 could just be a "play client" on a DAWs and I would also ask that you give some thought and consideration to those audio pros that do not wish to have another ASIO driver interface installed onto any machine without asking.
VP
JimH:
There is no driver installed by MC. MC, in this case, appears as if it were a driver, but it is the same MC you know.
Vocalpoint:
--- Quote from: JimH on September 30, 2013, 10:59:00 am ---There is no driver installed by MC. MC, in this case, appears as if it were a driver, but it is the same MC you know.
--- End quote ---
Understood. But it still should be an option to "not" have MC show as a driver system wide - especially when a pro audio DAW is being used.
Perhaps install MC as is - "as an ASIO driver" but have offer a checkbox in Options that lets a user remove MC as a ASIO driver. Removing this checkbox could have MC clean up the registry to ensure "MC ASIO" does not appear as a driver selection or clog up any audio interface listings in many popular DAW applications.
I did not have v19 (45) installed long enough to see what bhuddell was seeing but expect the same with many of my applications. My current RME driver offers 12 or 14 unique pairs of inputs/outputs to my hardware and my apps. I would hate to see a list with 30 (or more) inputs and outputs showing up in my software due to the "MC ASIO" item suddenly appearing.
VP
ksalno:
Doesn't look like anyone ever responded to this question, so I'd like to raise it again. Since I've been through many versions of MC, when I open a list of drivers on Windows, Media Center shows up 5 or 6 times, once per version. I don't do recording but I do a lot of streaming and having to scroll through a list of invalid drivers every time I switch outputs is a pain. I have used MC uninstall on every version but somehow it doesn't clean up these old virtual "drivers". Is there a way to do this via Regedit?
Hendrik:
The ASIO drivers are in HKEY_LOCAL_MACHINE\SOFTWARE\ASIO, you can delete old entries from there. I'll double check that future versions clean up more thoroughly.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version