Chase with no pause between fades?
-
FactorFilms
So I'm trying to create smooth RGB 'rainbow' chase, but no matter what I do, the chase always pauses at each scene, adding approximately the same amount of 'hold' as there is fade in and out values, even if the hold is set to 0 or a very low number. Is this a bug, or am I doing something wrong?
-
Jon Blackwell
I think there is a possibility that this is a bug. I have run into something very similar. When in the Show Manager, I setup a sequence with specific fade out times. Rather than fading out when the sequence is set to fade out, QLC holds during the fade out time and then fades out after the fade out time. So for example, if I have a 1 second fade in, a 1 second hold and a 1 second fade out, it will fade in for 1 second, hold for 2 seconds (both the hold and fade out time) and then fade out for 1 second rather than holding for 1 second then fading out. I think this only applies to "per step" fade out times.
-
FactorFilms
Yep I've got that too - it made Show Manager practically unusable. It also means that I've had to think of different ways of achieving certain effects - like for example I wanted to have a white flash that immediately fades out like an explosion or fireworks burst. The only way to achieve that with this bug is to just trigger a scene on and off, allowing its 2 sec. fade out time to kick in like that. Fortunately the lighting for this show will be triggered by midi so that's easily achievable, but still a little annoying. BTW I'm using this on Mac OS.
-
Jano Svitok
https://github.com/janosvitok/qlcplus/c ... 500df84aa6 contains (probable, not tested) fix for this issue.
For Massimo: I believe that fade out time should not be counted to duration, since fade out is started after the function is stopped. I.e. fade in, hold, then the function is stopped, next one is started and the stopped fades out in parallel with the new function.
For Massimo: I believe that fade out time should not be counted to duration, since fade out is started after the function is stopped. I.e. fade in, hold, then the function is stopped, next one is started and the stopped fades out in parallel with the new function.
-
FactorFilms
Well it definitely is a bug. I've found that if you keep playing around with entering different values you can eventually get rid of the 'hold time' that it incorrectly adds. Flicking out of the functions editor and back again tends to refresh the value, and when you return it often shows you the true hold value (instead of showing zero when it clearly isn't). Then you can dial the hold back and get your smooth seamless fades!
-
FactorFilms
Excellent! Also there appears to be something weird with sequences, and the light values getting corrupted - so a 3 step sequence after a while starts having step 1's values replaced by step 3's. It's great being able to create chase sequences without having to actually create all the separate scenes, but it doesn't feel particularly reliable.
-
Massimo Callegari
Should be fixed too in 4.4.1.
Here's the related ticket: https://github.com/mcallegari/qlcplus/issues/160
Here's the related ticket: https://github.com/mcallegari/qlcplus/issues/160