Print

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

[Kronsteen]

Hi JRiver.

Media Center 33 loads on boot on my DAW PC. It always activates 3 instances of the executable and will not close them when exiting the program until I kill them in task manager. I have set it to not open and also set it not start automatically in msconfig. It hogs the driver of my ASIO interface and prevents it from switching sample rates to different DAW sessions in Reaper and Pro Tools.

This seems to be a problem with JRiver Media Center 33 and does not occur when I kill the 3 processes that start upon launch.

[Kronsteen]

I tried turning off everything in task manager, msconfig, and autorun. The only solution is to kill the processes and restart the interface. I only have this problem with recent versions of Media Center.

[JimH]

MC Options for Startup?

Exclusive Mode setting?

Configure Windows Defender and don't use any other antivirus.

[Kronsteen]

MC Options for Startup?

Exclusive Mode setting?

Configure Windows Defender and don't use any other antivirus.

I have it set to nothing.
I have exclusive mode on because this is a DAW PC. Media Center should not be launching upon boot and taking control of the interfaces.
I only use Windows Defender.

Media Center executable also does not close when I close the GUI.

When I boot or close the GUI, I always get three instances of the executable running I have to kill to regain control of my interface.

[Awesome Donkey]

WDM driver enabled?

[Kronsteen]

WDM driver enabled?

I am using ASIO. I have no interest in using WDM.

The problem is JRiver Media Center 33 loading on boot in the background when told not to and refusing to the executables when exited. It has nothing to do with the protocol.

[JimH]

If you tell MC to do nothing on startup, that's what it does.

Maybe you have two versions installed and you're looking at settings in the wrong version.

[Awesome Donkey]

I am using ASIO.

Kinda doesn't matter if you're using ASIO, WASAPI, etc. (since it works with all of them) as I was asking if the WDM driver feature was enabled. Go into MC's Options > General > Features section and see if it's checked or unchecked. Would also recommend going through those and disabling features you don't use/need. For the WDM driver to be disabled it should be unchecked. ASIO driver (which is unrelated to the ASIO driver of your DAC) might be another feature there to check and uncheck to test.

MC's Options > Startup > Run on Windows startup has to be set to Nothing and MC shouldn't load on boot. If it still is (and features like the WDM driver are disabled), something on the system is causing it to.

[markf2748]

Media Center 33 loads on boot on my DAW PC. It always activates 3 instances of the executable and will not close them when exiting the program until I kill them in task manager.

This is really odd.  Forever, at most, I only see 1 instance of the Player process and 1 instance of the Service running for any given MC major version.  I have this option unchecked:  Options > General > Advanced > [] Allow multiple instances to run at one time.

See first two screenshots below.  Have you tried setting Startup Type to Manual or Disabled in Windows Computer Management > Services?

Note it is normal in Task Manager for Media Center 33.exe (Player process) to move from the section Processes > Apps to section Processes > Background processes when MC's desktop GUI is closed.  To kill it entirely, you must do so manually with RMB "End task", as you report.  JRService.exe is always listed in the Background processes section, and also must be killed manually with "End task".

Maybe you have two versions installed and you're looking at settings in the wrong version.

Good point.  I  have had this happen to me when an old major version was installed alongside a new one.  Best checked in Windows installed apps (third screenshot below), where additional versions will be listed if installed.

[Mitchco]

@Kronsteen, I get the exact same behavior as you...

If JRiver ASIO driver is the first driver in the ASIO list then the Host software initializes it first. The thing is JRiver's ASIO driver is actually a wrapper (i.e. COM object) around the JRiver application, so that is why the application is launched.

Open Regedit and go to: HKEY_LOCAL_MACHINE -> Software -> ASIO
My guess is that JRiver is the first entry...

You can either install another (real) ASIO driver and that will go to the top of the list, like I did in the attachment.

Or, I am not sure if one can install JRiver without the ASIO driver... Or simply just delete the registry entry if you don't use it.

Hope that works for you.

[Awesome Donkey]

What happens if you disable the ASIO Driver feature in MC's Options > General > Features section? Surely that removes/disables it? There it a chance you may need to run MC as an administrator when making a change to the ASIO Driver feature (and maybe the WDM Driver feature too).

[markf2748]

@Kronsteen, I get the exact same behavior as you...

If JRiver ASIO driver is the first driver in the ASIO list then the Host software initializes it first. The thing is JRiver's ASIO driver is actually a wrapper (i.e. COM object) around the JRiver application, so that is why the application is launched.

Open Regedit and go to: HKEY_LOCAL_MACHINE -> Software -> ASIO
My guess is that JRiver is the first entry...

You can either install another (real) ASIO driver and that will go to the top of the list, like I did in the attachment.

Interesting.  For the record, attached is my registry section, in which the JRiver ASIO driver is not the first ASIO entry (first is RME's ASIO driver for their ADI-2 DAC FS), and as previously stated I do not see the OP's issue.  So my case is analogous to what @Mitchco shows.

Note I do have MC's Options > General > Features > [x ]ASIO Driver selected, though I have not selected it under Options > Audio > Audio Device (I am currently using the ASIO MADIface USB [ASIO]).

It's not clear to me what determines the driver order in the ASIO registry list.  On the face of it, the list appears to be in alphabetical order!

Is the OP's DAW software or Windows set up to use the JRiver ASIO driver?

[Mitchco]

@markf2748

Looks like the default ASIO driver order is the same order as listed in the Win registry. See attached showing my registry and Reaper plus HLHost ASIO list. Of course, some apps can change that order...

@Awesome Donkey Yes, turning the ASIO feature off removes JRiver ASIO entry from the list. Thanks.

[RootAccess]

Another place to check is using the sysinternals Autoruns tool as it can automatically check multiple startup locations for you. https://learn.microsoft.com/en-us/sysinternals/downloads/autoruns

[Kronsteen]

What happens if you disable the ASIO Driver feature in MC's Options > General > Features section? Surely that removes/disables it? There it a chance you may need to run MC as an administrator when making a change to the ASIO Driver feature (and maybe the WDM Driver feature too).

Thanks. This solved the issue when I turned it off and rebooted everything including the interface. The JRiver ASIO wrapper was no longer installed and hijacking the interface.