Chaser - Fade Out time does not reset to 0ms

[LukasW]

Hello,

in a Chaser when I use the Fade Out time anything other than 0ms (e.g. 500ms) on my Scenes, then after using the Chaser when I trigger the same Scene from a button the Fade Out time is still the same (e.g. 500ms) instead of being 0ms.

I when set the last Fade Out time of my Chaser to 0ms, then it is reset to 0ms for the scene. So it remembers the last Fade Out time from the chaser.

Is this supposed to happen? And is there another way of avoiding this problem, other than to set the last Chaser Fade Out time to 0ms?

I tested it on Windows 10 on Version V4.12.6 and V4.13.0.

[kenact]

I'm confused about what you're doing. Can you share your project?

[LukasW]

I attached a small example project with my problem.

From my understand this behavior is inconvenient and could be a bug.

[kenact]

I don't believe that's the intended action. I believe it's a bug. Flash, according to the documentation, should be On/Off.

A workaround would be to clone every scene you want to be able to Flash, and attach the cloned scene to your Flash button.

Adding to the strange behavior is, if you set a Fade In/Fade Out on the Scene itself, and attach that to a Flash button, the Fade In is ignored, but the Fade Out is not.

[mcallegari]

Adding to the strange behavior is, if you set a Fade In/Fade Out on the Scene itself, and attach that to a Flash button, the Fade In is ignored, but the Fade Out is not.

This is the intended behavior. Flash ignores fade in.

[kenact]

Adding to the strange behavior is, if you set a Fade In/Fade Out on the Scene itself, and attach that to a Flash button, the Fade In is ignored, but the Fade Out is not.

This is the intended behavior. Flash ignores fade in.

I understand and agree, but shouldn't it also ignore Fade Out?

This doesn't answer the OPs question about the Flash using the last Fade Out on a scene. Why would the Fade Out from a Chase affect a Flash button?

[kenact]

I have just tested this on 4.13.1, and a Flash button still follows the last Fade Out value used for a scene. If a scene is used in both a Chase and a Flash button, the Flash will go on instantly, but if the scene has been used in a Chase, with a Fade Out time associated with it, when the Flash is executed, it will go on instantly, but it will have a fade out value equivalent to the last Fade Out value executed for that scene in a Chase.

[LukasW]

In my opinion this behavior should either be added to the documentation, or be considered a bug and therefore should be fixed. Thank you Ken, for testing it on version 4.13.1.

[MichelSliepenbeek]

Why would the Fade Out from a Chase affect a Flash button?

If you have a look at the QXW file of your project in a text editor (like Notepad) and go to the specific scene, you will find something like this:

<Function ID="13" Type="Scene" Name="Block 1 - Fader 1 - Zero" Path="Midicon">
<Speed FadeIn="0" FadeOut="0" Duration="0"/>
<FixtureVal ID="88">0,0</FixtureVal>
</Function>

It will tell you that FadeIn, FadeOut and Duration values are stored within in a scene and (because of that) you can only use one value for FadeIn, FadeOut and Duration.
If you use one and the same scene in different situations (with different FadeIn, FadeOut and Duration Times) you basically create a conflicting situation that QLC will solve by keeping the "values Last Used".

You can avoid this by not using the same scene: just make a copy of the scene and rename it to "..... Flash".

[kenact]

Why would the Fade Out from a Chase affect a Flash button?

If you have a look at the QXW file of your project in a text editor (like Notepad) and go to the specific scene, you will find something like this:

<Function ID="13" Type="Scene" Name="Block 1 - Fader 1 - Zero" Path="Midicon">
<Speed FadeIn="0" FadeOut="0" Duration="0"/>
<FixtureVal ID="88">0,0</FixtureVal>
</Function>

It will tell you that FadeIn, FadeOut and Duration values are stored within in a scene and (because of that) you can only use one value for FadeIn, FadeOut and Duration.
If you use one and the same scene in different situations (with different FadeIn, FadeOut and Duration Times) you basically create a conflicting situation that QLC will solve by keeping the "values Last Used".

You can avoid this by not using the same scene: just make a copy of the scene and rename it to "..... Flash".

Using 2 different scenes is a viable workaround, but this is still a bug. Using a Flash button with a scene that has a 0 Fade In and Fade Out, works exactly as expected. If the Fade In and Fade Out are both set to 1s, there is still a 0 Fade In, but the Fade Out takes 1s when the scene is used within a Flash button.

Even if that's the way it's designed to work, the Fade Out value of the Scene should not be affected by any Fade Out value assigned elsewhere within the project.