MRCC Transport Page / Clock v1.2

[RadekPilich]

I have already asked for full MIDI control of MRCC clock and transport elsewhere. 

Here, I am suggesting / asking for:

• similarly to how clock is routed to individual outputs via the "red" LEDs page, add a secondary "blue" page that would allow setting whether a given output receives TRANSPORT messages from MRCC clock. Actually, this blue page is the "operations" page and should be the primary one, while the red page is more of a configuration page and should be secondary. 
  
• on the blue page, make it possible to press and hold one or more outputs. While holding them, the S/S/C message sent via the screen menu would be sent only to those held outputs. Upon releasing the held buttons, their on/off state wouldn't change, it would change only with short press. If no button is held, the S/S/C message goes to all blue outputs in the on state.
  
• I am not sure if this should be independent of the output filters. I think it should. Meaning the output filters are "horizontal" and are applied only to the routings coming from inputs, while the internal clock and transport are incoming to the outputs "vertically" through it's own independent input not going through output filters.
  

[Jesse Johannesen]

Fun idea. I'll put it in with the feature requests... I think it would also be cool to create a USB device that connects to the MRCC host port and has physical controls for that page's parameters like an MRCC control panel.
As for your 3rd point, I think if I understand this correctly there is a setting near the bottom of the page which asks essentially "Should settings applied here override port level filters?"

[RadekPilich]

Fun idea. I'll put it in with the feature requests... I think it would also be cool to create a USB device that connects to the MRCC host port and has physical controls for that page's parameters like an MRCC control panel.

Well, we have devices, what is missing is MIDI control implementation in MRCC If CCs are not enough, there is NRPN, that could reach pretty much anything.

As for your 3rd point, I think if I understand this correctly there is a setting near the bottom of the page which asks essentially "Should settings applied here override port level filters?"

Well, there could be a global MRCC setting on whether the internal clock/transport should go through output filters or not. But that's optional in my point of view. Without it, it should not go through the filters.