Q Light Controller+

Hi all,

I may have discovered a new bug in 4.8.5 but I'm not sure so wanted to check functionality... Sorry in advance for the long (ish) post...

Let's say I have 10 buttons in my virtual console that each link to 10 different scenes for my LED baton fixtures. Each of the scenes switches the intensity of the batons to 100% and sets the baton's in-built scroll macro to 10 different settings. These buttons are in a solo frame so I can only run 1 scene at once. This all works fine and as expected.

Next I add a button in another frame in the virtual console that links to a chaser function. The chaser essentially switches between these 10 scenes with a timing of about 5 seconds between steps. When I press this button in the virtual console, the chaser runs fine. When starting the chaser, button 1 in the other frame lights up to show that scene 1 is active. When the chaser moves to the next step the second button in the other frame flashes but the first one still remains lit. Here's where my issue arises...

In version 4.8.4 the values of the second scene of the chaser are sent to the LED batons fine and the second scroll macro is activated as expected, even though button 1 in the solo frame remains lit.

In 4.8.5 the values of the second scene are not sent to the LED batons, the original values of scene 1 (the lit button) remain active.

Is this new functionality expected or is this a possible bug? Ideally I imagine what should happen is when scene 2 is activated in the chaser, button 2 in the solo frame should light up and button 1 should go out, which would then send the correct values of scene 2 to the LED batons instead of retaining the values of scene 1?

Thanks as ever for an awesome piece of software! Hope the above description helps

Cheers,
Chris

Hi,

Thanks for all the detail, it helps.

Here's a sample workspace based on what I've gathered from your description.

But I don't think I encounter the issue you describe.

Can you share a workspace file that reproduces the issues ?

Thanks

I have discovered that it seems if you set the fade in, hold and fade out times to zero (in the Chaser) then the "stuck" button problem is evident.

I have updated your example workspace and re-attached to show you what I mean. If you run the chaser now, you will see that button 1 gets stuck on.

Is it right that scene buttons in the virtual console stay on even when the scene has finished running and doesn't contain an intensity value? For example, in my workspace I have some buttons that move the colour wheel of my moving head fixtures, but these buttons are in a normal frame (not a solo one). If I press the red, green and blue button (for example) they all stay pressed, even though the scene contains only LTP channels.

In version 4.8.4 these buttons don't stay pressed but in 4.8.5 they do. Is that right? At the moment it means I have to press the button twice to turn it on and off again. You will see in the attached workspace I have an example of what I mean The three new scenes (scene 7, 8 and 9) change the colour wheel of the moving head fixture.

Cheers,
Chris

OK, thanks.

This also appears in 4.8.4.

This a known bug that is being worked on. ( https://github.com/mcallegari/qlcplus/pull/473 )

Awesome. Thanks plugz!