Can I make a global ‘control freak’ switch for snapshot behavior?

Hey folks! So here’s what I’m trying to pull off in GP5…

I want to build a global rackspace switch that decides how widget changes behave when I switch songs:

:a_button_blood_type: Mode A – “Don’t touch my stuff unless I explicitly say so!”

Widget changes are not saved unless I take a snapshot. (This is the default, right?)

:b_button_blood_type: Mode B – “Save everything! I live dangerously!”

Any widget tweaks I make during a song should be automatically saved into the snapshot when I jump to the next song.

Is there any way to set this up with a toggle switch in the global rackspace? Maybe with some GPScript wizardry?

Are you in setlist mode? I think the snapshot (“capture variations”) saves widget settings to a song part.

yes I would use it for setlist mode

Just to clarify why I’m asking for this…

During a gig, I definitely want the default behavior — no automatic saving, nothing changes unless I manually snapshot it. Totally makes sense on stage.

But when I’m prepping my setlist before a show — doing final tweaks like balancing song volumes — I often start playing around (because, well… music :sweat_smile:), and then forget to take a snapshot before switching songs.

So poof — my careful volume adjustment is gone.

That’s why I’d love a toggle in the Global Rackspace:

Let me flip into “prep mode” where widget changes are automatically saved into snapshots when switching songs, and then flip it off again before the show starts.

Basically:

Protect me from my own pre-gig scatterbrain. :joy:

I could be wrong, but I’m not aware of that option. I think you just need to remember to click on the capture variations window to save.

Maybe a script? (But, I am pretty happy just using the “capture variations” (snapshot) option).

There are some System Actions parameters made specifically for this. They work well for me.

Even when such a mechanism would exist, you have to remember to save the gig file

sure! That’s not the issue (or at least not until now :four_leaf_clover:)

yes I know, but I want to push one button to go to the next song AND before that take a snapshot of the current song… I guess I can’t set this up without a little scripting (which I’m not familiar with and it takes time to understand it)

Snapshots are per song part, so you want to take snapshots when you switch the song part?
I do not have any clue how that could or would work.

yes so essentially I would like to use a button to

  1. take a snapshot
  2. move to the next song(part)

then I could make a switch to change the behaviour of this button to only go to the next songpart (like the default behaviour) or do the above sequence of actions

With a button in the global rackspace that woul be doable I think.
But what to do when you switch to the next song part by the keys on the computer keyboard or when you use your controller or when in scripting the time line callback is used to switch song parts or when via OSC song parts are switched.
Many situations where that all would not work.
I think that all is to complicated to be implemented.
Better you train your brain to take snapshots when necessary.

yes I realise that by using the computer keys it’s impossible to do an action like taking a snapshot BEFORE moving to the next song part.

you’re right, I guess it’s too complicated and I should definitely train my brain :exploding_head:

1 Like

I can relate to this. I used to work a lot in rackspace variations, where the change you make to widgets are saved automatically. Then switching to setlist mode, I start making changes, and forget to hit “save snapshot”. I think it would be cool if there was a setting you could toggle somewhere to make setlist song parts auto save changes the same way that rackspace variations do

1 Like

In my global rackspace I have two large button widgets, both mapped to hardware buttons on one of my controllers. One takes a snapshot, the other pushes the snapshot back to the rackspace.

But I put it to you that having snapshots remember their values may not be such a good idea.

The whole point of setlist mode, songs and parts is that whenever you select a song to play, it will always sound the same.

Imagine if you have a widget knob mapped to a detune parameter (an exaggerated example to make a point) and as you reach the end of the song you add more and more detuning.

Now, next night of your tour, you select that song, play the first chord and you get a horribly detuned result…..you won’t be happy!

I understand your point and appreciate this default setlist mode behaviour. (not saving changed widget values during a performance)

It’s just that I would love a setlist “prepping mode” so I don’t have to remember to take snaphots or move to panel view to make small adjustments.

(but as @pianopaul mentioned this just might be something I should train my brain to do - it’s so easy to get lost playing around during prepping time :sweat_smile:)

Prepping in panel view is not handy because some songs share the same rackspace and I like to skip through them in the right (setlist) order.

What adjustments do you have to make related to widgets that requires you to go back to panel mode?

Nothing that I can’t do in setlist view (for example volume slider adjustments) but I mean: panel view doesn’t require me to think about saving (like creating snapshots in setlist view) before moving to the next rackspace.

I know that from your perspective this may sound strange :sweat_smile:

We have about 40 songs in total, but play only a selection of 20 live (depending on the show duration) and also change the setlist every gig so I like to make those volume adjustments in setlist mode with snapshots.

I thought my request was easy to do using GPscript, but now I understand it’s not…

Sure but if you have a snapshot in a song part, changes you make in panel view won’t be reflected in the song parts