Q Light Controller+

Posted: **Tue Jun 20, 2017 4:50 pm**

In the show I'm building, I'm using a lot of Cue Lists with Scenes, RGBMatrices, Sequences, and Chasers nested inside them.

Often, I like to re-use Scenes and have the fade-in/out times be different depending on the situation. For example, "Red Scene" might fade in over 5 seconds one place, but pop in instantly in 0ms in another place.

By setting the Cue List's Chaser to Fade In and Fade Out times "Per Step," this is easy to achieve. But there is a problem / limitation.

When I choose an RGBMatrix, Chaser, or Sequence as a step in the main Cue List, the fade times are wrong. I can't make an individual step "default" as it would need to be, to allow the nested steps to fade as they are supposed to. The outer Chaser's "Per Step" fade time takes over the fade times for all the individual steps of the nested function.

Is there any way to implement a "special" duration which would make only that one step act as "Default" - yet still allow other steps to have explicitly stated times?

Posted: **Tue Jun 20, 2017 5:28 pm**

It looks as if defaultSpeed() returns -1, similar to how infiniteSpeed() returns -2. So maybe if a chaser step has its fade time set to -1, it won't send a speed override to the nested function. Maybe all that is needed is to allow speedToString() and stringToSpeed() to work with something like "d" for default and treat that as defaultSpeed() == -1, similar to how it works with "∞" meaning infinite and treating it as infiniteSpeed() == -2.

Posted: **Tue Jun 20, 2017 5:42 pm**

Yup, that seems to do the trick. I'll continue to test in more detail. If anyone wants to try this, here's what I did. In engine/src/function.cpp, I added the final four lines here:

Code: Select all

QString Function::speedToString(uint ms)
{
    QString str;
    if (ms == infiniteSpeed())
    {
        str = QChar(0x221E); // Infinity symbol
    }
    else if (ms == defaultSpeed())
    {
        str = QChar('d'); // Default speed
    }

And the final two lines here:

Code: Select all

uint Function::stringToSpeed(QString speed)
{
    uint value = 0;

    if (speed == QChar(0x221E)) // Infinity symbol
        return infiniteSpeed();

    if (speed == QChar('d')) // Default
        return defaultSpeed();

At least in preliminary testing, that appears to allow a Chaser to be in Per Step mode, with overrides on some of the steps, but non-overriding Default timing on steps where the fade time is set to "d".

Posted: **Wed Jun 21, 2017 2:34 am**

XML seems to save properly with this modification; so far all is well when used carefully. But the total duration times seem to behave a bit unpredictably, requiring re-setting the Hold time sometimes, and it is possible to put in "d" for the Hold time, which doesn't exactly make sense.

For now this seems like a bit of a messy kludge. I think I will continue using it in testing for future shows, but not yet in current production.

Posted: **Wed Jun 21, 2017 4:37 am**

Hi Matt,

This problem seems to have been around for a long time now.

To my limited understanding, the order in which QLC+ handles fading seems to be the cause. It must be difficult to fix otherwise I suspect it would have been done by now.

https://github.com/mcallegari/qlcplus/issues/193
https://github.com/mcallegari/qlcplus/issues/445

It would great if you could find a solution especially for us 'theatre guys'.

Cheers
Mark

Posted: **Wed Jun 21, 2017 6:53 am**

Hello,

Yes, this issue is known and is being worked on.

Q Light Controller+

Set individual steps in Chaser to "default" fade time

Set individual steps in Chaser to "default" fade time

Re: Set individual steps in Chaser to "default" fade time

Re: Set individual steps in Chaser to "default" fade time

Re: Set individual steps in Chaser to "default" fade time

Re: Set individual steps in Chaser to "default" fade time

Re: Set individual steps in Chaser to "default" fade time