Q Light Controller+

Hello,

I created a number of scenes and "animated" them through the use of chasers. Those scenes control my moving heads.

I managed to create a very functional virtual console and attached it to an iPad based MIDI trigger. Everything works fine with the exception of when I have a toggle button for a scene (solo group). I push the button, scene plays as expected. When I toggle the button off, the moving heads stop in their last position but do not dim / scene is still visible. I would like to turn a scene on when button is toggled to the "on" state, and turn a scene off (ie. lights off) when button is toggled to the off state. How do I do this?

Or... Have a set something up incorrectly in my fixture definitions with respect to dimmer channels?

Thank you

I guess no one knows?

In reading the manual (v4.7.0 RC1 - pg. 61-62):

--
Toggle function on/off: When you click the button, the attached function is started. When you click the button a second time, the function is stopped, unless it has already stopped by itself.
--

My understanding is that my request on setting the INTENSITY of a FUNCTION to 0 (black/off) when stopped is a property of a function. However, I'm unable to understand how to / find a way to set a function to automatically reduce the intensity to 0 when not running. Perhaps could be this could be a feature that can be implemented?

I understand the typical use case of QLC+ and similar software and the extensive use of sub masters. For simple, mobile-type applications, I use triggers to display pre-defined (color, gobo, rate, seq., etc.) functions. Therefore the use case for blackout of function on toggle off.

Thank you.

Hello deeepdish

Now I am on windows my self, but i think the behavior is in your scene settings. I have experienced this before. First, make sure the fixtures are not set as LTP, rather HTP. That can cause this.

Second,When the button is engaged it will run or turn on a function for its designated duration time and fade times. For scenes, be sure to assign your fade time in your function tab(not to infinity). Once set, each scene will fade accordingly.

In chases, when setting your fade in/out and duration, be sure to set your fade speeds off default (the scene's default). Select common or per step. Your fade time shouldn't be larger than your duration. There has to be enough time for the fade to run. You can also assign one or more scenes or chases to a speed dial widget.

Thanks Davey,

I tried your suggestions, and I think my issue is something with fixture definitions. I had the DMX monitor window open and noticed that no channels change value when I right click on a button and change intensity.

I'll have to investigate a bit more and comeback to the forum with a more definitive description of the problem.

What would be helpful for me to understand is what "linkages" through channel classifications (e.g. shutter / intensity) exist between intensity of functions and the actual DMX channels that control these functions.

Thanks for your help.