Sorry for the vague title, I wasn't sure how to distill down what I want to happen, and I'm still very very new to QLC and learning how everything works
I have a strobe with 3 channels - Dimmer, Flash Speed, Flash Duration
I am controlling it with 2 buttons and a slider/knob.
One button is a flash function that triggers a scene with the strobe fully open, so that I can tap it for a quick flash (or multiple, to go with drumbeats for example)
The other is a regular toggle function button with just Dimmer and Flash duration channels enabled, the idea being if I want a constant, flashing strobe I just toggle that one on.
The knob is currently set to level mode because 11-250 controls strobe speed with 0-5 and 251-255 is strobe open, 6-11 is strobe closed. So I can use the knob to increase or decrease the speed of the flash for the 2nd button.
This works great, mostly. If i activate the toggle button, the strobe will flash at the rate set by the knob. However, if I use the flash function, since it sends a strobe open command to channel 2 and the toggle button has nothing set in channel 2, the toggle button is now strobe open as well until I move the knob to send it a new channel 2 command.
Basically, I'm wondering how i can set this up so that either:
1) After the flash button is pressed, it reverts to previous directions (so it sends 0 to channel 2 during the flash, and then goes back to 127 or whatever it was before once I release the button)
2) When the toggle button is pressed, it also sends the value of the knob to the channel the knob controls (in this case channel 2)
In the end I just want to be able to press the toggle button without also having to move the knob.
A slightly related but less important problem I'm having is that, if the toggle strobe is activated, hitting the flash doesn't turn it off, even if they're both in a solo frame. A little advice here would be helpful as well
Linking a slider or knob to a button in VC
-
- Posts: 3
- Joined: Sun Aug 01, 2021 1:11 am
- Real Name:
Huh. I think I may have figured out the first problem. I'm not sure exactly what I did but I think I had missed the checkmark for the knob's channel to act on. At the very least, after messing around with it I have the first problem working as desired - strobe flash no longer causes the toggle button to be on strobe open.
- GGGss
- Posts: 3052
- Joined: Mon Sep 12, 2016 7:15 pm
- Location: Belgium
- Real Name: Fredje Gallon
This is a known limitation - not only to QLC+
You have 2 priorities built-in HTP and LTP. With the manual flash, you have to send a lower value than what is active. This means HTP cannot be used (Highest Takes Precedence). So for this to work, you need LTP (Latest Takes Precedence), but then again you have to re-establish the programmed values before the flash-action... Without complex working structures (loopback channels feeding a chaser and so on) you won't be able to solve this...
On other desks, you'd find something called 'temp (orary)'.
A nice QLC+ solution would be a Temp-frame... everything happening in that frame overrules other active values - but that would become a feature request now.
You have 2 priorities built-in HTP and LTP. With the manual flash, you have to send a lower value than what is active. This means HTP cannot be used (Highest Takes Precedence). So for this to work, you need LTP (Latest Takes Precedence), but then again you have to re-establish the programmed values before the flash-action... Without complex working structures (loopback channels feeding a chaser and so on) you won't be able to solve this...
On other desks, you'd find something called 'temp (orary)'.
A nice QLC+ solution would be a Temp-frame... everything happening in that frame overrules other active values - but that would become a feature request now.
All electric machines work on smoke... when the smoke escapes... they don't work anymore