Q Light Controller+

Every once in a while, I come upon the very frustrating issue that the fade time set in a Scene will not take effect when used in a Chaser.

Today it happened again: the fade time is set to 20s, but it's actually taking 24s to fade, as confirmed by the DMX monitor.

I tried disabling the fade times of other scenes in the chaser; I tried saving and restarting QLC; I tried updating the software... no dice.

My showfile is below. It's a pretty expansive one, but the scene in question is: "Scene/Touch the Sky/Bridge Build (20s in)".

I'm using it in the chaser: "Chaser/Runsheets/Touch the Sky".

If you run the chaser, and move from Step 6 to Step 7, then you'll see that it's taking 24 seconds to fade.

I'm most likely doing something wrong myself, but even so, I'd really appreciate some help. This only happens, like, 4% of the time.

I'm running QLC+ 4.10.2, on Lubuntu 15.04. Arch is i686, Kernel is 3.19.0-37-generic.

Hello,

Thanks for the detailed description

On ubuntu 12.04 i686 with QLC+ 4.10.2, I have no issue. It takes 20seconds to move from step 6 to step 7.

I see nothing wrong in the workspace file, the Bridge Build (20s in) function in the "Touch the Sky" chaser is only referenced in this chaser, it's not activated anywhere else. And the fade in time of the chaser is "Default"...

forresthopkinsa wrote:This only happens, like, 4% of the time.

Does this happen all the time with this workspace, like in "4% of the time I create a chaser it acts like shit", or does it happen 4% of the time when running this exact chaser ?

plugz wrote:Does this happen all the time with this workspace, like in "4% of the time I create a chaser it acts like shit", or does it happen 4% of the time when running this exact chaser ?

The former. Most of the chasers I make in this workspace work correctly. That one in specific was causing issues. The problem seemed to be happening in other scenes that night as well. Next time I'm designing on that computer, I'll see if it's still happening. I'll report back when I test it there again.

Thanks for the help; it's very appreciated!