Strange behaviour in chaser

Ask a generic question about the usage of QLC+, not related to a particular operating system
Post Reply
Eddie
Posts: 23
Joined: Fri Jul 24, 2020 1:02 am
Real Name: Nahuel

hello to all. I have a doubt about the usage of chasers. Here I have a chaser loaded with a simple function. Everything is set to "per step". The fade in time is set to 500ms and the fade out time also to 500ms. The hold is set to 0ms. But why the duration of the step is showing 500ms if the fade in and out times sums to 1 second ? In concrete, what I want to achieve is that the light starts on, inmediately does a fade out of 500ms and the a fade in of 500ms. Thanks for the help !
Attachments
Screenshot 2023-06-11 at 18.26.47.png
User avatar
GGGss
Posts: 3052
Joined: Mon Sep 12, 2016 7:15 pm
Location: Belgium
Real Name: Fredje Gallon

Let's make the basics clear.
Duration is the sum of the fade-in and the hold time.
The chain of command is fade-in, hold, and then fade-out.
Eddie wrote: Sun Jun 11, 2023 9:30 pm inmediately does a fade out of 500ms and the a fade in of 500ms. Thanks for the help !
What you are asking does not fit that logic: a fade-out results of something before that, and the fade-in is bound to the next step.
So a chaser would help you here.
All electric machines work on smoke... when the smoke escapes... they don't work anymore
Eddie
Posts: 23
Joined: Fri Jul 24, 2020 1:02 am
Real Name: Nahuel

GGGss wrote: Mon Jun 12, 2023 8:22 am Let's make the basics clear.
Duration is the sum of the fade-in and the hold time.
The chain of command is fade-in, hold, and then fade-out.
Eddie wrote: Sun Jun 11, 2023 9:30 pm inmediately does a fade out of 500ms and the a fade in of 500ms. Thanks for the help !
What you are asking does not fit that logic: a fade-out results of something before that, and the fade-in is bound to the next step.
So a chaser would help you here.
Thank you GGGss !! I was thinking it in the wrong way. Problem solved !!
Post Reply