Song part action send when EXITING song part

Or only apply the action to that specific song part.

I want to turn on chorus for a particular song part, but I want to turn it off for all other parts. Turning on is easy with actions, but the only way I can see to turn it off is either manually, or writing another action in another part to turn change the widget’s value. Problem is, I don’t always go to the next song part, sometimes I jump directly to another part. So rather than writing the action into all song parts, is there a way to send the “off” message upon EXITING the song part?

If not, this would be a great feature to turn things on and off for a particular song part.

Have it off by default in the rackspace.
Switch to the songpart you want to have it on, set the widget value on and then use the ‘Capture variation into this part’ feature (aka ‘snapshot’). The widget value will only be on when you switch to that songpart—it will default to off for other songparts.

That’s what I was doing previously. Problem with that is I want certain effects (chorus, trem etc) to NOT be affected by variations ever. I only want to manually control these effects and not be changed by the variations. Your solution would work for this specific case, but its not the behaviour I’m looking for in most other cases.

I should have explained the widget/plugin is in the global rackspace. I know you can control widgets in the GRS from the local, but I don’t want to, because I want these effects to be independent of the local rackspaces. I want to be able to turn effects on and not get turned off by switching variations or song parts. (And of course if I turn on “ignore variations” then your example won’t work anyway…) So my use case is:

A: When I turn certain effects on/off in the GRS, I want it to stay on/off and be able to change variations or song parts without affecting its state. Manual control only.

B: (But) For certain song parts, I want to automate turning on these effects and turn off when leaving the song part.

Song part actions is PERFECT for this, or at lease for the turning ON part. It’s the turning OFF that the tricky part. Either I put that command into another song part (explained why that isn’t ideal in the OP) or now I have to manually turn it off every time. Neither is ideal, but the former is better than the later. Ideally, I would love to not have to worry about what to put in other song parts and just turn off automatically that which was meant to be turn on for that particular song part.

I just discovered another pitfall of turning the effect ON via actions. Even if I put an OFF action into another song part, if I end the song on the part that has it ON and jump to another song, the effect will stay on. Of course, makes sense, but all the more reason why an “undo” action (OFF in this case) upon leaving the song or song part would be AWESOME!

Is there a way to reset the widget(s) in the global rackspace upon song change? From what I found the On Song Change is only in the gig script???

On song change should be available in the global rackspace

Excellent! On Song change everything is reset now. Any chance of implementing an “exit” action for song parts? Or an option (tick) to undo the action that was set for the song part?

To do this right, we would probably have to create the concept of Activate actions (which is basically what’s there now) and Deactivate actions.

But the good news is that GP Script, which was after all designed to allow non-built-in functionality to be added, worked for you.

Yes, it does reset the widgets on song change. However, its doing it on every song change, but I only have this here and there. Not a big deal, but if possible, is there a way to treat this in a song script for only those songs that need it? Like On Songpart…and only run the action on that song part, OR if that’s not possible, to reset the widget values in that song script? Obviously can’t define widgets in song script so I’m stuck how to tell the song script what to do.

If not, the existing workaround works for now. Thanks!

I haven’t looked at that callback in a long time but I’m pretty sure it passes in an index to the current song and the previous song indices as parameters so you can test for the one you care about