Q Light Controller+

I had set up a chaser to act as a mini-transition... An effect that has several steps to accomplish with fade/duration times for each step. It works great when I run this chaser standalone.

I then inserted the chaser into the main chaser for the show, but when that step is run there is no fades, the steps of the inner chaser seem to just jump from one to the other.

Is there a way to preserve the inner chaser definitions when run from another chaser?

In the short term, since it was only a few steps, I just moved it out to the main cue list. While all other items are infinite hold for manual stepping, I sort of didn't think of just making those items have the timed steps to accomplish the task. This wouldn't work if I wanted them in a loop, but it does work for a one-shot pass through the items.

Does anyone have a better solution to this? Nesting chasers is really useful, but this makes it problematic for a lot of what I want to do.

Keep in mind that the main chaser cannot have fade-times. This would not make any sense. (You cannot fade in a chaser) The timing has to be put inside the sub chasers.
Justin,
Welcome to the forum by the way.
What do you want to achieve?
Please start a new thread.

Hi there, I also have this problem. I have a chase sequence with timings. I want to add that to the main show Q list (also a chaser). But the timings of the main Q list step for that step override those of the inner chaser. So how do I tell the outer chaser to just ignore its fade times for that step? The 'default' timings setting for a chaser (whereby timings are taken from individual functions) can only be applied to a whole chaser (i.e. the whole Q list) and not an individual step - unless there's something I've missed?? Currently I think the outer chaser overrides all of the inner chaser timings with its own single set of values - which doesn't support the comment above that it doesn't make sense to give fade-in/out times for an outer chaser - if that were the case shouldn't it just ignore them? Thank you!

Welcome to the forum Simon.
You can set individual timings per step. https://www.qlcplus.org/docs/html_en_EN ... ditor.html
You are a theatre guy - good to know. I assume you proceed with call and go-commands? Then all steps in your main chaser would have infinite duration time. You can set this using the Speed Dial. Then all your sub chaser will be called by the main. Just give the main enough time to end the sub-chasers. But that might not be the problem since you manually Go+
House lights would justify the case where you need fade-times inside the main chaser. Or small change-overs thru darkness f.i.

I find it easier to use RGB Matrix (or even a sequence - which can be autogenerated from a RGB matrix and modified in detail regarding fade times and colors of its steps).

A very simple and quickly made example workspace is attached here.

It contains three scenes (R,G,B) using four generic RGB fixtures.

Then I created a chaser for these scenes, with infinite hold and individual per-step fade times (5 seconds each), called this Cuelist, and set up a cuelist widget in virtual console using this chaser.

Next I made a fixture group with the four lights in a row, and a RGB matrix using tis group and the gradient effect.

Now if I add this matrix as a step to the main cuelist, it can fade in, keep running at its own time until pressing "next cue", then fade to the next scene again, all timing is correct.

Note the sequence icon on top of the RGB matrix editor right side tab, which exports the effect to a sequence that you can edit and use instead, if preferred.

The workspace also contains a chaser to demonstrate the difference, when you add this instead of the sequence or matrix, strange things happen: the fade in/out of this step doesn't work, and the colors of the "inside" chaser add up instead of alternate.