same problem again as 2-3 weeks back or so:
i wanted to map -within my rackspace vs. widgets- two buttons,
one for the “one Rackspace up” command. ( this mapping was executed)
The other for the “one Rackspace down” command. ( this took not place…)
…mapping based on using the “System actions” block.
after i maped my first widget, the rackspace would jump one up,
i was not able to set the other button for the “one rackspace down” command,
AND: i was never again able to enter the Rackspace i was working on,
…from where it jumped one up automaticly.
I can somehow follow, why it jumped up.
I can´t follow why i never again could enter that rackspace ( manually)
i would say, here is a safety net due to be installed , no ?
have i overlooked something ?
i would guess i tryed any method to enter my “lost” Rackspace again, incl. global midi setup, …Rack up-down… been set there
so, i saved this now faulty Gig, not knowing how much work i would lose,
i reloaded the last saved version, and things are “in that sense” again fine .
It even seems i´ve not lost to much work.
But i would claim, thats a scenario that needs to have some sort of a savety net.
the other thing:
when this happens, how can i use system actions, and set my rack up-down commands from there ? whats going wrong here ?
i can´t see what i could change while mapping my widget.
I am not sure if it is a good idea to use those “switch rackspaces” functions from within the possibly affected local rackspaces… it’s too easy to stumble upon situations beyond real control.
I rather would use this from the global rackspace (which can’t be changed).
i run several times into confusing situations using the global midi commands.
Rack up-down is for example again not working right now.*
(*) I have set it setup again in global rackspace now
you are cracks, and maybe at home in ANY part of GP.
others are not !
please try to grasp and understand the whole post bevore you come with jokes or zynism:
I was NOT able to enter this rackspace again ! NOT possible, NO access !
the problem was in that sense not, that my rackspace just switched to another.
The problem was, that the ame rackspace was from then on nolonger accessible. And thats unexpected !
did you two grasped that ?
as sayed: doing it in global midi settings is not working as aspected.
sometimes it works, sometimes not.
right now, my settings are accordingly, but it is not working.
thats what brought me back two times, to try to map it vs. the system action block.
The issue here is that we allow these “action” parameters to be tied to a widget like any other parameter. Most of these actions should not be “recalled on rackspace activation” nor used in some other context.
Some user knowledge is required as with great power comes great responsibility
We can see on our side how to make this work better, but please let’s stay civil.
@Funky40 - everyone here is always trying to help. No need for strong language. In fact - it’s really a reason for exclusion from these forums so let’s please be as civil as possible. Try to edit your posts to say what you want without being impolite.
Can someone maybe enter this into our tracking system so we don’t forget about it and take a look at it when the time permits?
