Cannot kill RC.exe process in TaskManager

[thebutler]

Maybe a clue to my other post...

I notice, that upon exiting RC standalone (clicking close 'X' button top-right corner) that RapidComposer.exe still shows as a loaded/active process in Windows Task Manager and stays like that. Is this correct behaviour..? Shouldn't the process be shut down/killed pretty much straight away..? Several attempts at trying to force an 'End Process/Process tree' does nothing.

thebutler

EDIT [it does eventually shut out - but only after a solid few minutes before it disappears from the list... surely that's not right...? Any advice/suggestions../ Is it just me..? ]

[musicdevelopments]

Hi thebutler!

No, this is not right. There must be something wrong with the cleanup of either the VSTi plug-ins that you used or the audio interface. This is very rare when RC terminates this way.
Does this happen at each exiting the app? Did the program always behave like that, or just recently?
Did you have VST plug-ins loaded (if so which plug-ins)? Do you use the latest beta version or v2.55? Which windows version do you use?

Thanks,
Attila

[thebutler]

Hi,

I am using the 2.56b11 build of RC
The process 'still active' business may well have been happening before; I only just decided/thought of examining the Task Manager today, for no reason particularly...

And yes, I have been experimenting a bit more this afternoon and it does happen at every exit of RC.

I did have Kontakt 5 as one of the VSTi's for RC to use, but that was a few projects ago; my latest projects use soundfonts only. Maybe something is still 'hanging around' from that earlier instance..? Makes me think, I should try to get RC to load as say a new 'default' instance, and see if the issue remains... I'll check the manual later on how to do this.

I am on Win7 32bit Service Pack 1 (see sig). My audio i/f is an M-Audio Delta 1010LT, and has been faultless for the last several years. I keep the driver up to date as and when M-Audio obliges their end.

Cheers,
thebutler

[musicdevelopments]

I wonder if a fresh install would improve the situation.
Please rename C:\Users\{user}\AppData\Roaming\RapidComposer temporarily and reinstall the program. You'll need to type the key-code again.
You can type "%appdata%" in the windows start menu to quickly open the Roaming directory.

I am sure this is an issue with RapidComposer and not with your system. If all fails, logging must be added to detect problems during cleanup. Please let me know.

Thanks,
Attila

[BlackWinny]

Also, I suggest you to install it not in C:\Program files\RapidComposer
but in C:\!32\RapidComposerr (simply do a copy/paste when the installation program asks you to confirm its directory to place the application).

Don't worry, it doesn't alter anything. Simply this method gives all the warranties that you will not be bothered by the annoying restrictions of rights applied by Windows on the folder C:\Program files\ (and it is one of the reasons why the installation programs give always the choice to place an application in another place than the one suggested by default).

So, to avoid several annoying restrictions imposed by Windows, you'd prefer to place your applications in C:\!32\ instead of C:\Program files\ (and C:\!64\ when you install a 64 bit application but i see that you have a 32 bit Windows).

And also... why a "!"? It's a trick: simply because the presence of this "!" places this folder always at the top of the list of folders in the Windows Explorer. An easy method to always find at the top all one's favorite folders.

[musicdevelopments]

Thank you, BlackWinny, that is a good idea!

It would be good if all RapidComposer files were in one place, but that was not possible because Windows does not allow file modification under \Program Files\. This is why the settings and libraries were moved to ...\AppData\Roaming\RapidComposer.

[thebutler]

Thank you for the responses, Attila and BlackWinny...

Well, I tried a fresh install as you suggested Attila - no change I'm afraid; I went back to v2.1 of RC (my original purchase). No joy; then I updated straight to v2.55 - still the RC.exe is staying alive in Task Manager for over 3.5 minutes, before I see it 'clear' itself from the list.

Sorry, for now BlackWinny, I note your advice (thanks.!) but have not followed up on it yet. I need to move on from all this...
(and also, I need to get to work..!!)

For now,
the butler

[BlackWinny]

This is why the settings and libraries were moved to ...\AppData\Roaming\RapidComposer.

Yes. About this point concerning AppData\Roaming... it is inevitable whatever the place where we install the application. Simply the trick I wrote is the best to avoid all the problems which happen with the rights allowed to the user for the folders C:\Program files and C:\Program files (x86). So the eventuality of a problem with the rights allowed to these two folders is a cause which can be immediately ruled out when an issue occurs.

[thebutler]

Also, I suggest you to install it not in C:\Program files\RapidComposer
but in C:\!32\RapidComposerr (simply do a copy/paste when the installation program asks you to confirm its directory to place the application).

I got round to trying this method last night (after uninstalling, clearing registry and re-booting). I'm afraid this has not changed anything for me.

I am doing all this with release version 2.55

It launches and I can use it standalone fine. But I still notice that the RapidComposer.exe process will not clear from Task Manager for some few minutes after shutting the app down.

It still will not even load as a VSTi (32bit) inside Cubase 7.5.10 (32bit) - Reaper, ok; Studio One (demo), ok.

NOTE:- I am just reporting findings; I am not looking for/expecting Attila to jump all over this right away, as it appears I seem to be the only one with the issue..! I'm happy with standalone for now...

Cheers for now,
thebutler