What he described in his words I would describe as “not using the concept of songparts at all, but rather ‘tones’ instead of songparts.”
So the idea is button one (for example) is always “clean tone”, button two “gritty”, button three “lead” or whatever. Those have no direct correlation to songpart order in terms of sequence during a song. It would be up to the user to label them as such in their Songs. The reason he wants the Song to be able to start on whatever “songpart” the user wants is that if it starts with a “lead” sound and that’s button three then it needs to start on the third songpart.
I think you already covered that with the “*” at the end of the variation name. (I think that’s how you did it.)
I think his remaining issue is being able to set widgets so that some are will be “remembered” across songpart switches and others won’t. Because GP isn’t built this way I don’t think there’s a simple solution for it. What he’s asking for is further complicated by the fact that changing songparts can change rackspaces, so to the extent you tried to build a widget list whose values should be preserved across songpart changes you have the inconvenient reality that those widgets may not exist across songpart changes. Not an insurmountable problem, but it’s a whole lot more complexity to build into an extension.
Dealing with that could be simplified by requiring such widgets to be placed in the Global rackspace, and to the extent they need to exist in different local rackspaces forcing the user to make those links from Global to local rackspaces themselves. But now we’re at a level that gets quite complicated for the user.
That’s exactly it. But for the second issue, I think rank13 had an idea for it in his switcher he made.
I REALLY would rather use setlist mode, because of being able to make changes to all songs based on that rackspace instead of making a change to each rackspace when needed
The second issue in setlist mode has to do with the second entry in this pic, we are in “recall” mode, but many times I’d like it to behave in “discard” mode
If I understand item (1) correctly, then you’re not talking about resetting inidividual widgets - you are referring to the entire snapshot. Is that right?
But it sounds like you just want either the snapshot (which means all widgets) to be remembered or the snapshot (which means all widgets) to be reverted
Yeah that is right. Some modellers further allow something like ignore variations, so say you had a widget set to ignore variations, the only time that widget would be reverted to the saved value is on reloading that song.
This is for something like a last minute pitch drop, say the singer was struggling that day, but normally, you’d want the pitch set to the saved value. It would be set to ignore variation as when you change snapshots, you would still want it at the newer pitch
Murphy’s Law unlocked…We loaded a bad profile and apparently crashed it in front of the Sweetwater guys, but that’s about exactly how I always expect these to go.
@dhj Any thoughts on if these options could be implemented? When a widget is modified, how should its value be set when changing to another part?
Option “Recall”: any snapshot edits are recalled when jumping from snapshot to snapshot, and appear as you last left them.
Option “Discard”: any snapshot edits are discarded when jumping from snapshot to snapshot, and appear as the preset was last saved."
