Is there a way to switch Rackspace Variations independent from Song Parts? If I use the System Actions plugin, the Parameter is Select Part of Var(n)
Using the Global assignment Variation Direct Access, this also, according to the manual, and by the behavior I see “NB: this feature also works for song parts, i.e. if you’re in the Setlist view, then the same message, CC 42 7, would switch to the 8th song part of the currently selected song.”
I would like to be able to directly pick a variation without it also choosing a song part, or maybe some other way that I can keep my pedals going exactly where they are currently going (1 clean, 2 distortion, 3 lead, 4 harmony and 5 keyboard), but still able to order a song by part in any order I want without it shuffling which pedals go to which variation
For me, the reason to work with setlist view is that I can play with widget values without losing the original Rackspace (variation) configuration.
Your question is unclear, what do you want to achieve? It seems to me you’re not quite understanding how to use Setlist View and the difference between songs (song parts) and rackspaces (variations).
I want to have pedals assigned to switch variations and only variations. I don’t want them to also switch song parts. Right now the two ways I see to do it switch both and can’t be separated. .
A song part is a reference to a variation of some rackspace.
This does not make sense — when you select a song part, you ARE selecting a variation. If you want to be able to use different variations from different rackspaces, then create multiple song parts. If you want to be able to use different values for the same rackspace/variation pair, then use separate song parts and save snapshots.
Selecting variations directly can only be done when you’re in rackspace mode.
I want these pedals to stay exactly where they are, so I’ll always know who is who.
However, some songs will start with clean, some with keyboard, some with the rhythm, etc. I’m not sure how to handle this, as Variations and Parts are tied together on the same switch command. I would use the Panel mode with separate Rackspaces, but as shown in this thread: Variation load and 2 other issues with my first gig, please help - #11 by rank13 , In this mode, variations don’t load with their saved values, as that is what setlist mode is for, so I am not exactly sure what to do.
I’m really trying to find a way to set this up that is compatible with the way many (most?) guitar players would feel at home and familiar with. I’m trying to have the answers to a lot of questions I expect will be aimed my way, as I really think this year is going to be a pretty significant mass pilgrimage to a computer based guitar rig.
You’re talking about pedals, songs and variations in a way that doesn’t make any sense to me Would love to give you some advice but I guess I simply don’t understand what you are trying to accomplish.
I get that I’m definitely operating under a different paradigm than this is optimized for, I’m just not sure how to follow the best practices. For a lot of guitar players, whatever their first switch is, is what they nearly always or always always want it to be, say its their clean sound. And then their next pedal, is their distortion sound. Pedal one calls up their clean sound and all the associated settings. Pedal two calls up their distortion sound and all its associated settings. They don’t want that to change.
However, say their Song 1 should load up with the distortion sound already selected. But that’s pedal 2. But since you’ve moved it first in that Song, in order to have it the first sound on Song load, now its on pedal one. Does that make more sense what the problem is?
Are you using your pedals to switch rackspace variations (or song parts) or are they hardware effect pedals (e.g., disortion, chorus, flange, etc.) that actually process audio? (Or something else?).
They are switching rackspace variations. For instance in this case, that pedal 1 is ALWAYS my clean, pedal 2 is ALWAYS my distortion sound, 3 is leads, etc.
Same here… sort of.
From what i could grasp so far, i would tend to think about putting the “omni-present” plugins and settings into the Global Rackspace or even into a second GP-instance, but the latter might probably complicate things even more!
One of the nice things about Setlist mode is that assuming you have your song parts in the right order, you only need a single switch to move through your song. So one song could start with your clean sound, then move to distortion. And the next song is vice versa. But all you need to do is click your single “next” switch.
If you need to return to the same sound again, just add another song part that references the same variation. That way, you always move forward.
So you want each physical pedal to recall the same effect chain no matter what song you’re in.
Much like a guitarist would enable/disable certain stompboxes to create his sound. Or maybe use a patch bay to recall presets.
I would definitely put those effect plugins in Global Rackspace and create widgets to enable/disable them. (Or maybe adjust drive / feedback / mix … anything)
Then I would assign a global parameter to all widgets and create the same panel layout in Local Rackspace. You should be able to control your Global widgets from Local.
Now with widget links you can enable/disable multiple fx with one push of a button (pedal in your case)
No need for variations so far. But you could save those fx configurations in variations if you want and skip through them using another controller?
For live use you might want to look into Setlist View and create songs so you could adjust song-specific fx or use different tempo’s and the best thing is any changes you make on the fly won’t be saved unless you tell GP to do so.
This sounds promising. The main reason I would use songs at all is that even though its the same set of sounds, one song might need the harmonizer in say a minor and another song in e. Otherwise they are the exact same sounds and I know the type of tarring and feathering I’d get if I suggested to guitarists to reorder their patches, most of the ones I know ALWAYS keep them in the same order…it may be as simple as a physical stomb box being switched on or off, but nowadays its more like a whole set of parameters being switched at once with a static layout from song to song.
I’m not sure if this global way would be able to switch the harmonizer key, or the synth sound involved…Maybe it could with that local to global send thing?
The reason I suggested to put it in Global is because it gives you consistency and a streamlined workflow.
Changing songs or rackspaces doesn’t affect your Global sounds - unless you use Global Parameter Assignments.
You have the flexibility to create custom sounds for every song part in Local Rackspaces. Pedal 1 could be set up to mute that Local rackspace signal and unmute the let’s say ‘CLEAN’ channel in Global.
While this could work for me, it will certainly not be acceptable to many of the guitar players out there. Their workflow is already too established across multiple products by multiple manufacturers. It’s sort of a defacto standard.
Would love to give you some advice but I guess I simply don’t understand what you are trying to accomplish.