Hi, I have 2 questions on how buttons work:
1) Is it possible to bind a button to a certain channel value without creating a scene? (i.e. if I have a moving head and want a button to activate a certain gobo when pressed)
2) Suppose I create a scene which sets:
- shutter to 255
- dimmer to 255
and bind it to a button. When in operate mode I click on the button both channel inside DMX monitor are set to 255 and the button has a green border. When I deactivate the button only dimmer is set to 0 and shutter remains set to 255. Which is the rule that governs buttons behaviour? I know the difference between LTP and HTP but when the scene is switched off I'd expect all channel values to be set to 0.
2 questions on buttons
-
Michael Clements
Hi Lorenzo,
1) The short answer is no, but you can do this instead:
Put a (very short) slider on the Virtual Console
Set it to Level Mode and make it control the gobo channel.
Select "click and go" gobo/effect/macro at the bottom of the same window.
Returning to the VC, you now get a "click and go" button which will display all the options you have set up in the Fixture Definition Editor on the gobo channel, including a picture of each gobo if you put them in the fixture definition.
2) When a button is released, HTP values return to zero but LTP values are unchanged.
This is basically because in most circumstances you wouldn't want the LTP returned to zero. A second button is needed at present to set new LTP values.
Have a look at this topic about having a second function attached to a flash button (which would solve the problem you describe and a lot more besides), which starts with this post:
https://sourceforge.net/p/qlcplus/discu ... 6997/#be98
1) The short answer is no, but you can do this instead:
Put a (very short) slider on the Virtual Console
Set it to Level Mode and make it control the gobo channel.
Select "click and go" gobo/effect/macro at the bottom of the same window.
Returning to the VC, you now get a "click and go" button which will display all the options you have set up in the Fixture Definition Editor on the gobo channel, including a picture of each gobo if you put them in the fixture definition.
2) When a button is released, HTP values return to zero but LTP values are unchanged.
This is basically because in most circumstances you wouldn't want the LTP returned to zero. A second button is needed at present to set new LTP values.
Have a look at this topic about having a second function attached to a flash button (which would solve the problem you describe and a lot more besides), which starts with this post:
https://sourceforge.net/p/qlcplus/discu ... 6997/#be98