Remove button toggle
Posted: 11 March 2018, 10:01
Maybe I'm missing something, but is there a way to stop Live Buttons from toggling?
I have a set of scenes on a Solo buttons page. This means there is only one button on at a time. I also have a specific black out button. However, if you accidentally hit the currently set button you then get a black out as no buttons are pressed (the existing button toggles off). This isn't great, but has been tolerable because we just try to be careful when manually setting scene transitions, but it would be nicer to be able to remove button toggling (so once pressed it stays pressed) - particularly as we have a 'Black Out' button for when we want no scene set anyway (and it resets motorised lights to their down positions).
A more serious issue is now I've moved to setting MIDI triggers so that I can trigger scenes automatically from our slide presenter. The idea was that changing the current slide would set the correct scene.
Unfortunately, if two slides are programmed to use the same scene and run consecutively then the first slide will set the scene, and the second will toggle it off. If I could prevent button toggling then the second MIDI signal would always latch on, if that makes sense?
This came up because I created a pre-service loop with the first slide setting the pre-service scene via MIDI. This worked great, on starting the slideshow, the lights are set, however each alternate loop the lights black out and then come back on on the next loop (due to the scene button toggling). I can't find any way to have a MIDI trigger force on or force off, it seems to only allow toggle. If Toggle could be disabled on a button, then the triggers could respect that behaviour.
There is no real way for me to prevent the same signal being sent consecutively (the slide software assumes that there is a different signal for OFF/ON and doesn't assume a toggle behaviour). As such, I can't find a reliable and safe way to use MIDI triggers, which is a real shame, as there is no way of the triggering software knowing the current state so it can't gaurantee that a signal will have the desired effect.
I have a set of scenes on a Solo buttons page. This means there is only one button on at a time. I also have a specific black out button. However, if you accidentally hit the currently set button you then get a black out as no buttons are pressed (the existing button toggles off). This isn't great, but has been tolerable because we just try to be careful when manually setting scene transitions, but it would be nicer to be able to remove button toggling (so once pressed it stays pressed) - particularly as we have a 'Black Out' button for when we want no scene set anyway (and it resets motorised lights to their down positions).
A more serious issue is now I've moved to setting MIDI triggers so that I can trigger scenes automatically from our slide presenter. The idea was that changing the current slide would set the correct scene.
Unfortunately, if two slides are programmed to use the same scene and run consecutively then the first slide will set the scene, and the second will toggle it off. If I could prevent button toggling then the second MIDI signal would always latch on, if that makes sense?
This came up because I created a pre-service loop with the first slide setting the pre-service scene via MIDI. This worked great, on starting the slideshow, the lights are set, however each alternate loop the lights black out and then come back on on the next loop (due to the scene button toggling). I can't find any way to have a MIDI trigger force on or force off, it seems to only allow toggle. If Toggle could be disabled on a button, then the triggers could respect that behaviour.
There is no real way for me to prevent the same signal being sent consecutively (the slide software assumes that there is a different signal for OFF/ON and doesn't assume a toggle behaviour). As such, I can't find a reliable and safe way to use MIDI triggers, which is a real shame, as there is no way of the triggering software knowing the current state so it can't gaurantee that a signal will have the desired effect.