4.12.2-Chaser(fadein) of RGBmatrices- affects RGBholds

The issues found when using the Virtual Console
Post Reply
vector
Posts: 83
Joined: Fri Sep 23, 2016 9:25 pm
Real Name: Mark Sy

Not sure about this one.
As per attached, 5 fixtures in 3 RGB matrix configurations all with the default 500ms hold times.
The pars transition one to another every 500ms as you would expect.
Add them to a chaser with 4s fade in,fade out and 8s hold.
I think what is happening is that the 4s fade in is overwriting the 500ms because you get to a point where almost no lights lightup.
ie Its worse second time around the loop.
Change the chaser fadein to 0ms and it runs as you would expect.
Change fadein to 1sec and you can see that it is slowing down the "internal"RGB transition(hold) times.

As to why im fading between RGB matrices is a long winded story. I have simplified the file below and the explanation to its rudiments.
Attachments
RGBChaser.qxw
(4.92 KiB) Downloaded 55 times
vector
Posts: 83
Joined: Fri Sep 23, 2016 9:25 pm
Real Name: Mark Sy

I guess its the acting like ,scenes where the chaser "common" setting on the chaser overrides the 0ms fade in time of scene. But in this case Id like to fade the RGB in over 4s but let it run at its own speed...hmmm
Post Reply