More > JRiver Media Center 33 for Windows

JRiver MC 33 loads on boot when told not to.

<< < (2/3) > >>

Kronsteen:

--- Quote from: Awesome Donkey on September 28, 2024, 06:24:24 pm ---WDM driver enabled?

--- End quote ---
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:

--- Quote from: Kronsteen on September 28, 2024, 06:41:08 pm ---I am using ASIO.
--- End quote ---

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:

--- Quote from: Kronsteen on September 26, 2024, 08:25:23 pm ---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.
--- End quote ---
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".


--- Quote from: JimH on September 29, 2024, 12:45:48 am ---Maybe you have two versions installed and you're looking at settings in the wrong version.
--- End quote ---
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.

Navigation

[0] Message Index

[#] Next page

[*] Previous page