Hi
I realise this has been discussed before but the other topics I have found are extremely detailed and only briefly touch on this point.
Would it be possible to have a second function attached to a flash button which activates when the button is released? This would solve a lot of problems and would not break any current setups that people have as it isn't a change to LTP/HTP.
I would use this for the strobe function of my moving heads and LED PARs. At the moment when I release the flash button which is attached to a function that sets the strobe channel, even though all of the programs have the strobe channel set to off the strobe remains on. I don't really understand why, but I'm sure that if I could create a second function that brings the strobe channel back to the off state then that would work.
Could flash button start a function on release?
-
Joe
The best thing you could probably do for now is if you change the shutter channel on your heads to HTP, then it will no longer return to zero. Only problem is not sure if it would go back to open shutter after. Hmm.
-
Michael Clements
Hi Paul,
You're right, a second function that is activated when a flash button is released would solve a number of problems. I assume your strobe is LTP and at present LTP values aren't reset when the flash button is released.
Unfortunately it's part of a bigger problem with flash button behaviour which will be a lot of work to change.
If you haven't seen my post on the subject, follow this link:
https://sourceforge.net/p/qlcplus/discu ... 1539/#a39b
Another solution that might work for you is to use a start and a stop button in a solo frame instead of a flash button.
You're right, a second function that is activated when a flash button is released would solve a number of problems. I assume your strobe is LTP and at present LTP values aren't reset when the flash button is released.
Unfortunately it's part of a bigger problem with flash button behaviour which will be a lot of work to change.
If you haven't seen my post on the subject, follow this link:
https://sourceforge.net/p/qlcplus/discu ... 1539/#a39b
Another solution that might work for you is to use a start and a stop button in a solo frame instead of a flash button.
-
Manfred
Hi there
sorry Michael, excellent thoughts but I don't want to think as complicated than you at that time.
I believe that assigning a second function isn't necessary at all to complete the right override-and-switch-back behavior and cheating with fixture setups like others were saying is all the more the wrong way too.
In my opinion the flashing button has only to enforce with the highest priority on the whole VC the assigned scene with its enabled channel values.
No difference, if he resides in a solo or normal frame, this has to be in exactly the same way I'm acting on the simpledesk:
If I make there a change to a channel, its background gets red to indicate the override, and the output get an overlay with the adjusted value - until "reset universe" gives me back the output of all backgrounded activities. (BTW: can I please have a button on each channel too to reset only some of them?)
This scheme could be compared now at sceneeditor to that scene setup I intend to flash by using the "set channel enabled" checkboxes as decision.
If checked, the channel gets that red state on flashing too, and could strictly enforce its value to the output.
No matter if HTP or LTP, (sure, HTPs should be influenceable by a submaster), on release/unflash all overlays made with that scene have to get void like reset universe on the simpledesk.
LTPs will return to their suppressed momentary state, set by other sticky, running or possibly started function during flash.
Finishing this, it should be even possible to flash a chaser too and I think it would be always logical comprehensible.
For an additive flash, I have to assign another button to another scene, where only those channels are enabled, I intend to overlay.
On luxury version of QLC+ I think about a checkbox in widget properties next to the option Flash Function, to decide whether I want that new enforced behavior or the merged HTP, like we have at the momentary state on v4.7.4 but LTPs should always switch twice.
On luxury+ version I can assign a script made with an assistant to a toggle button, switching these checkboxes of all Flashbuttons I want to act as Add or Kill...
sorry Michael, excellent thoughts but I don't want to think as complicated than you at that time.
I believe that assigning a second function isn't necessary at all to complete the right override-and-switch-back behavior and cheating with fixture setups like others were saying is all the more the wrong way too.
In my opinion the flashing button has only to enforce with the highest priority on the whole VC the assigned scene with its enabled channel values.
No difference, if he resides in a solo or normal frame, this has to be in exactly the same way I'm acting on the simpledesk:
If I make there a change to a channel, its background gets red to indicate the override, and the output get an overlay with the adjusted value - until "reset universe" gives me back the output of all backgrounded activities. (BTW: can I please have a button on each channel too to reset only some of them?)
This scheme could be compared now at sceneeditor to that scene setup I intend to flash by using the "set channel enabled" checkboxes as decision.
If checked, the channel gets that red state on flashing too, and could strictly enforce its value to the output.
No matter if HTP or LTP, (sure, HTPs should be influenceable by a submaster), on release/unflash all overlays made with that scene have to get void like reset universe on the simpledesk.
LTPs will return to their suppressed momentary state, set by other sticky, running or possibly started function during flash.
Finishing this, it should be even possible to flash a chaser too and I think it would be always logical comprehensible.
For an additive flash, I have to assign another button to another scene, where only those channels are enabled, I intend to overlay.
On luxury version of QLC+ I think about a checkbox in widget properties next to the option Flash Function, to decide whether I want that new enforced behavior or the merged HTP, like we have at the momentary state on v4.7.4 but LTPs should always switch twice.
On luxury+ version I can assign a script made with an assistant to a toggle button, switching these checkboxes of all Flashbuttons I want to act as Add or Kill...