Hello everybody!
I have the following problem:
I have a scene with a fogger - only one channel - on high value... When I press a button in the virtual console - added the scene with "flash"-functionality - and release it, the value is still on 100% - it does not go back to zero, after release the flash-button.
Is this an error or use I it wrong?
greeting from germany,
René.
Fogger holds on high DMX-Value after Flash-Button
-
janosvitok
- Posts: 1331
- Joined: Mon Apr 13, 2015 7:05 am
- Location: Bratislava, Slovakia
- Real Name: Jano Svitok
- Contact:
Most probably your fogger is using LTP strategy. Go to channel modifiers screen and mark it as HTP. http://qlcplus.org/docs/channelproperties.html
-
dj fonic
- Posts: 35
- Joined: Wed May 27, 2015 4:41 am
- Real Name: Alex Bowler
Hi rbrixel,
There's also a work round for this kind of issue.
This works for any fixture that has a issue with staying on due to LTP DMX channel settings.
If changing the channel to HTP does not work. Simply write a scene with the channel value of the troublesome DMX channel set to the value that you require it to be when you release the button. Set the scene to auto run when virtual console starts (see manual for how to do this). DON'T use this scene for any thing else.
How this works. The scene is always setting a DMX value in the back ground, so when a button is released it then changes the DMX value to the scenes value, as this is the latest takes priority value.
Without this scene, when using buttons in the virtual console with LTP ( latest takes priority ) channels. When you release a button, QLC waits for the next value as the latest takes priority value is still the value that was sent when the button was active.
In other words, buttons in the virtual console do not send a 0 value when released.
One more thing to note is the value set in the scene does not have to be 0. If you want a pan or tilt channel for example on a moving head to start from a position instead of it's home position, then by setting the value in the scene will make the moving head go to that position when the virtual console starts and also when not receiving any other DMX values for pan or tilt.
Hope this helps anyone with problem fixtures.
There's also a work round for this kind of issue.
This works for any fixture that has a issue with staying on due to LTP DMX channel settings.
If changing the channel to HTP does not work. Simply write a scene with the channel value of the troublesome DMX channel set to the value that you require it to be when you release the button. Set the scene to auto run when virtual console starts (see manual for how to do this). DON'T use this scene for any thing else.
How this works. The scene is always setting a DMX value in the back ground, so when a button is released it then changes the DMX value to the scenes value, as this is the latest takes priority value.
Without this scene, when using buttons in the virtual console with LTP ( latest takes priority ) channels. When you release a button, QLC waits for the next value as the latest takes priority value is still the value that was sent when the button was active.
In other words, buttons in the virtual console do not send a 0 value when released.
One more thing to note is the value set in the scene does not have to be 0. If you want a pan or tilt channel for example on a moving head to start from a position instead of it's home position, then by setting the value in the scene will make the moving head go to that position when the virtual console starts and also when not receiving any other DMX values for pan or tilt.
Hope this helps anyone with problem fixtures.