Sorry if the topic was already discussed, but I couldn’t find the same situation.
I would like to group widget from global rack space to trigger the widget from rackspaces (by need). For example one switch in the global rack space triggers, by need, widget in rackspace for each song maped to a different layer (in one song it will be volume of the first layer, in another volume of the second).
In my mind: I press the switch in global rack (grouped to A) and it triggers different things in rackspaces (grouped also to A). That way the same switch will control different things in each song if I wish. So far it seems it is not possible to group widgets between global rack space and non-global ones. I’m on version 4 still so if it is changed in V.5 that would be a reason for me to upgrade.
I saw that post, but I got into a problem at the very start. On drop-down menu in plugin mapping there is only Audio in, Audio out, From Rackspaces, To Rackspaces choice. No other which I can address. So either the tutorial missed some step, or I’m not doing something right.
I know about that. The question is if the grouping widgets is going to work as described, and my problem is related to using version 4? If yes, good reason for me to upgrade.
In a normal rackspace if you select from/to global rackspace you get a list of parameters. In the global rackspace you can assign a parameter (a special field for widgets, only available in the global rackspace).
For some reason I can’t upload the pictures. The tutorial that Nemanja sent has mixer in drop-down menu in plugin mapping section of global rack (so is this mixer in local or global rackspaces?). That’s the “other” I’m referring to.
Now I see that I made life too complicated in trying the opposite. Anyway I think it would be a good thing to allow global widgets to group with local ones.
The idea was not to have different widgets in rack spaces.
For example one rack space as a template with all controls from master keyboard mapped to widgets in GP. Let’s say 4 layers and pads on the master keyboard turn on and of the layers. USB switch pedal mapped to a switch widget in global rackspaces. Now all I have to do is, to be able to turn different layers for different songs, to connect switch from global rackspace to a widget in different songs. I don’t have to map CC for different layer for each song.
So song 1 I need to switch layer one - I group that songs widget for layer one to switch in global rackspace, for song 2 I need to turn layer 3 and 4 I group that songs widget for layer 3 and four to the same switch in global rackspace.
Basically one switch in global rackspace to rule them all.
I can’t find it more general than having a USB switch pedal and use it in every rackspace. Isn’t that the main purpose of global rack, not to repeat same stuff that I want to use for every rack?
If I can’t group things in global space with other rackspaces I have to make switch widgets for every rackspace I’m using and then group it with other widgets within every rack space. Also I don’t see restrictions in being able to this, grouping already exist in local rackspaces. Expending grouping to global rackspace wouldn’t harm.
If you ask me why I just don’t use song parts, sometimes I need to turn of and on strings for example more than 4 times within the song, so then it means one song part without str, then one with on, then one with without and so on.
If you have some other advice about this I’m open for suggestions. That’s why I actually started thinking grouping USB switch pedal with other things in rackspace.
So why do you not just have a button (say) on that rackspace that turns the song on or off? What is the need for the global rackspace in this scenario?
Just convenience. Instead of mapping midi cc for each widget I need in particular song, I just group that widget to a widget in global rackspace which is always mapped to the switch on the pedal. Also that way I could have two ways of turning things on or off - one is pad on the master keyboard the other is USB switch. Without grouping it’s not possible to have one widget mapped to two different sources.
I will repeat, I’m making life complicated.
But I will ask you, why you think grouping things from global rack space to a local one is a bad thing? Just curious what could be a problem.
