RW Feature Annoyance!

[atalwar]

I am having a BIZZZARE thing happening with RW. It would just be with me i guess as i did not see this posted elsewere.

It's the New Feature on RW that saves the Previous Plugin state.

I am unable to get Rid of that and everytime i load RW it Opens up amplitube or whatever i had maybe 2 sessions earlier (even if i disabled it by unchecking the tick on amp) .

I Usually Record Direct from Hardware and this is driving me numb nuts as on loading RW it automatically goes into live state.

Am i misising some secret here. as i dont see any option in the menu to get rid/unload a Vst amp or anything once you loaded it.

Already had a very embarassing incident at 3 Am due to this.

[Charvelguy]

It not just you, I have had this happening alot since I bought the VST gold plugin and went scoutin for it in effects/vst section of RW. The drop down, checked or unchecked, but moreso when unchecked locks in and up. I've had to close RW, reload and it still wants to not be unchecked and loads Amplitude all the time!

In fact I was going to post something about it today as I noticed what annoyance it has been causing me when I try to load another VST.

[bjabus]

I have had this happen several times as well.

[hansanneveldt]

hi, got the same problem here!!

[randy]

I think they may be a little problem in that when you uncheck AMP or turn on Hardware monitoring, the VST plugin stays open. We'll look that. In the mean time, yere's how you can stop the Plug-in from popping up when you start RiffWorks:

1. Launch RiffWorks
2. Turn off hardware monitoring by clicking the hardware button
3. Click the input effects
4. Make sure AMP is unchecked
5. Use the "X" to close the VST plugin (I.e. Amplitube) if it's open
6. Click the hardware button to turn on hardware monitoring
7. Close RiffWorks
8. Open RiffWorks

The VST should have remained closed this time. Let me know how that works for you.

Thanks,

[atalwar]

Hi Randy,
Yes that is what i did later and it seemd to work partially but as soon as i loaded another song (after turning on HW monitoring) amplitube popped up again from nowhere.
Below are two cases that are triggering it.
Hope the below scenarios help you nail the problem.

Scenario 1 :

I Closed the vst , unchecked it, and turned HW Monitoring Off.
Exited RW. Loaded RW again all Fine.

I Turned on HW Monitoring. Amp is Still Unchecked. Good.

I Load a Song. Amp/Vst Shows Up.

Scenario 2:

I Closed the vst , unchecked it, and turned HW Monitoring Off.
Exited RW. Loaded RW again all Fine.

I Turned on HW Monitoring. Amp is Still Unchecked. Good.
I Record something and save it. (without using any vst in the entire session)

I exit RW (without turning off HW monitoring).
Launch RW again the VST shows up.

Thanks for looking into it.

I Think currently safe bet is to Keep Hardware Monitoring Off until You have loaded a song. and before closing RW turn OFF HW monitoring (or you are on for a surprse at next RW session).

[randy]

Oooh, that's very interesting. Thank you for the additional details. I'll need to run this one by Dug. I thought the VST state was saved in the registry, not the song files. I could be wrong though.

I'll get back to you when I have more info,

[atalwar]

Hi randy,
The state is not being saved in song files i am sure.

Its some event/trigger firing up on loading a song when HW monitoring is On.

Perhaps its that when you turn off HW monitoring/remove a vst, the state is not cleared in RW persistent state file, and then on next launch it loads whatever state it has and that could be from a session days before.



Perhaps a Button in Vst options (where you load a vst refresh etc) to clear state or unload a Vst would fix it.

Ok, A Confirmation, I renamed my registry entry : .app.lb.AMP.plugin (equivalent to deleting it)
and the issue was fixed ( i guess until i load some other vst , but still good enough).

[randy]

I spoke to Dug about this and we agree it's not really a big deal. Just close the plug-in manually for the time being. We agree this is an annoyance but the work around is really simple. Don't be so lazy!

We'll address this in a future update,

[atalwar]

No problems,
I can live with the registry fix for the time being.