We all have been using the solo frame for scenes of the alike? (only intensities, only gobos, only, ...) - right?
What if one would like to add collections to the solo frame buttons?
Mayhem on stage: sticky positions, wrong gobos, rotating what-everrrr! Because of LTP - right?
I would suggest including the 'Stop All Functions' possibility INSIDE a solo frame.
All running functions inside in that frame (running thESE scenes, chasers or EFX or or) would have to be killed (stomped in MA-jargon)
this is a major release tweak - enumeration of functions: Features FIred Up To Now [FFUN]
(and filtering 'active' and filtering 'focus on') - ehhmmm - Impossible!!
What if we give the SOLO frame an external input named: 'STOP All functions' or something?
This would mimic the 'zero' value to EVERY button inside a solo frame. (solo frame - parent - enumerate members of this parent, set the value to (zero or none)
THUS releasing (stomp / temp <- future requests) the content of a solo frame...
TEMP is something else... TEMP overrides every active value running (typical LTP) and overrides it to the value set - unset temp state reveals the former state <- BAD
Your votes, please
[do we have a voting system built in?]
Q Light Controller+
Official forums of the QLC+ project