I’ve come across an odd situation: The presence of a Widget in the Local Rackspace appears to block its MIDI message to Widgets in the Global Rackspace, even when “Thru” is enabled. Is this intended?
My real-world use case is this:
I have a “Soundcheck” Song and Rackspace that includes multiple “indicator” Widgets that I use to confirm that all of my controllers are functioning. It’s part of a pre-sound-check. I have a Widget in the Global Rackspace that activates the Next Songpart. It doesn’t work for my Soundcheck Song with the indicator Widgets in its Rackspace.
I can easily work around this, but I wouldn’t have expected a Local Widget with “Thru” enabled to block the MIDI message from a Global Widget.
Here is a simple Gig file that shows the situation. (The Gig uses Rig Manager, so you can easily try it with your own controller switch.) Select the first Song and press the Soft Pedal. The Songpart does not change. Select the second Song and press the Soft Pedal. Now it works.
A widget in the local rackspace and widget in the Global rackspace, each learned to the same MIDI input, with Thru enabled— only the local rackspace will be triggered by the MIDI input.
So the question is, is that intentional or should both widgets be triggered by the MIDI input?
" Note: if you assign a MIDI message to a widget in the Global rackspace, and you assign the same MIDI message to a widget in a local rackspace, the local rackspace will override the Global rackspace, which will not respond to the particular message while the local rackspace is active. If you switch to a different rackspace that does not use that MIDI message - the Global rackspace assignment will work again."
Thanks. I was wondering if this might be intentional, like, the Soft Pedal is always for selecting the next song part (globally), except for that one time when you actually want it to act like a Soft Pedal in the Local Rackspace. Then, it overrides the Global behavior.
It was… unexpected.
It would be cool if Local Widgets had a “ Pass-thru to Global Rackspace” option, mainly to inform the user of the expected behavior. Sometimes I might want a Local override. Other times, I might want parallel behavior.
A workaround could be for me to replicate the Next Songpart function in the Local Rackspace, in the rare case when I don’t want to lose the Global behavior.
In any case, it’s good to know that it’s intentional. This can be marked as solved.