Page 1 of 1

Chaser within a collection - Timing changes

Posted: Sun Jan 03, 2016 5:49 pm
by kumba
Hello All,

I made a chaser using 2 Chauvet Mini Kintas that slowly rotate the lights by using fade in/fade out times. The chaser works perfectly when ran by itself. But as soon as I insert that chaser into a collection, the fades are lost and the lights rotate instantly without the cross-fades...after the fade times are met (6.00 seconds).

Here are the chaser timings:

Step - Fade In - Hold - Fade Out - Duration
1. .00 .00 6.00 .00
2. 6.00 .00 .00 6.00
3. 6.00 .00 .00 6.00
4. 6.00 .00 .00 6.00

Any ideas how or why this happens?

Thanks,
Kumba

***********************
QLC+ 4.10.1
Enttec USB Pro MK2
Windows 7 Professional
***********************

Re: Chaser within a collection - Timing changes

Posted: Sun Jan 03, 2016 10:18 pm
by kumba
Is the "collection" defaulting to a different timing?

Anyone?

Thanks.

Re: Chaser within a collection - Timing changes

Posted: Mon Jan 04, 2016 11:26 am
by plugz
Hello,

Please share a workspace file demonstrating the issue.

Also, please test with 4.10.2 instead of 4.10.1.

Re: Chaser within a collection - Timing changes

Posted: Wed Jan 06, 2016 5:10 pm
by kumba
Hi plugz...and thanks for your help on this.

I’ve recreated the problem in a simplified workspace.

I have two collections that run sequentially in a chaser (with the same fixtures). The first is a fast, rotating strobe effect…and the second is a slow, full on, rotating effect. The effects execute correctly running independently or inside a collection. The issue arises when the two collections are inserted sequentially into a chaser…somehow the first
collection changes the crossfades of the second collection.

The scenes, sequences, and collections run fine when executed independently.

Any ideas on what I’m missing?

Re: Chaser within a collection - Timing changes

Posted: Thu Jan 07, 2016 7:59 am
by plugz
Hello,

1. The definition for the fixture you use in this workspace is missing, it's not ideal for debugging

2. The first description you provided does not correspond to the actual case: it's a chaser within a collection within a chaser.

3. In the main chaser, set FadeIn and FadeOut as "default" instead of "Per step"

Re: Chaser within a collection - Timing changes

Posted: Sat Jan 09, 2016 12:53 am
by kumba
Thank you so much plugz!!!

It was the FadeIn/FadeOut settings in the main chaser that was doing it! I set them to default and that fixed it!

Please know how greatly appreciated it is of you (and others) investing your time and efforts to solving issues on this forum ... is to all of us!

Best,
Kumba