Print

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

[bhuddell]

One of my machines is a PC DAW where I would prefer that the JRiver audio engine not be listed as an available ASIO driver. What is the best way to remove this function on a given PC? I can delete the associated registry keys, but I'd like to know if there's a better method. Thanks!

[JimH]

Try updating MC.  19.0.45 is at the top of this board.

[bhuddell]

Thanks, that is the version I'm running. I'm not having the issue where another program loads the JRiver ASIO driver unnecessarily. I just like to keep the list of available ASIO drivers on my DAW PC as short as possible, so I was asking if there's a preferred way to uninstall the driver. Deleting the registry keys has worked fine so it's not really a problem, but maybe an option to disable that feature would be useful in the future.

Thanks again!

[Matt]

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.

[bhuddell]

It's mostly OCD! My audio interface has 12 channels and the JRiver driver effectively doubles that, meaning there are six stereo pairs listed that I will never use. The closest it comes to an annoyance is that I have a program that always scans for ASIO drivers on startup and I have to scroll through the JRiver outputs to get to my interface. Again, not a big deal, and not an issue at all with the JRiver ASIO reg keys removed.

[Vocalpoint]

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.

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]

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.

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.

[RoderickGI]

I uninstalled MC23 from my HTPC the other day, and was looking for some specific MC entries in the Registry. I was pretty surprised to find that there were MC entries going all the way back to MC18, the first version I used.

I cleaned up some of the entries, but there were a lot to find, and confirm as not needed. Many that use CLSIDs which I can't confirm as required or not.

It would be nice, Hendrik, if in addition to MC cleaning up its entries better when it was uninstalled, that there was a JRiver utility that went back and cleaned up all old entries of versions no longer installed. I know that there is no return on investment in that work, but I hate having my Registry just grow and grow, and I gave up using third-party Registry Cleaners some time ago.