Cue List faders problem

The issues found when using the Virtual Console
maximortal
Posts: 24
Joined: Mon Dec 19, 2016 7:07 pm
Real Name: Iro Suraci

Cue List faders problem

Post by maximortal » Mon Dec 19, 2016 7:20 pm

Vers. 4.10.5.246

Virtual console bug
Faders of Cue list works incorrecly if linked
If you got 2 cue named A and B both with 2 generic dimmers
A: CH 1 @ FF / CH 2 @ 0
B CH 1 @ FF / CH 2 @ FF

If you put fader each to 50% the DMX monitor show this values:
CH 1 @ 51 %
CH 2 @ 51 %

expected behaviour is
CH 1 @ FF
CH 2 @ 50 %


I'm not sure but this bug there is also in previous versions
This bug is really important to been fixed for theatrical use of QLC+
Thank for you grat job
Cheers

janosvitok
Posts: 830
Joined: Mon Apr 13, 2015 7:05 am
Location: Bratislava, Slovakia
Real Name: Jano Svitok
Contact:

Re: Cue List faders problem

Post by janosvitok » Mon Dec 19, 2016 7:49 pm

Maximortal,

I've moved your topic to a better place.

Jano

User avatar
mcallegari
Posts: 1902
Joined: Sun Apr 12, 2015 9:09 am
Location: Italy
Real Name: Massimo Callegari
Contact:

Re: Cue List faders problem

Post by mcallegari » Sat Dec 24, 2016 11:57 am

Can you please post a sample workspace to reproduce the behaviour you're seeing ? Thanks.

By the way, the description you provided seems like the correct behaviour to me.
When linked, the side faders go in opposite directions, so it is correct that @ 50% they are both @ 50%

maximortal
Posts: 24
Joined: Mon Dec 19, 2016 7:07 pm
Real Name: Iro Suraci

Re: Cue List faders problem

Post by maximortal » Thu Dec 29, 2016 1:51 pm

yes, from a particulart poin of wiev you got right, this behaviuour is correct, but no if you lock the sliders each other. I mean that the expected behaviour is something like Spark consoles: connected faders become a linear crossfader between two scenes. In other words DMX values of scene A and scene B booth @ 50% must add each others.
to recreate bug remember to lock fades each other.
Attachments
bug report.qxw
(2.8 KiB) Downloaded 63 times

User avatar
mcallegari
Posts: 1902
Joined: Sun Apr 12, 2015 9:09 am
Location: Italy
Real Name: Massimo Callegari
Contact:

Re: Cue List faders problem

Post by mcallegari » Thu Jan 05, 2017 7:17 pm

I think I've found a solution to this without impacting the code too much.

The code is in the "morphblend" branch on GitHub.
Otherwise, Windows build available here (4.10.6.54): https://dl.bintray.com/mcallegari/qlcplus/

Please test and let me know if it works and if it causes regressions somewhere else

User avatar
mcallegari
Posts: 1902
Joined: Sun Apr 12, 2015 9:09 am
Location: Italy
Real Name: Massimo Callegari
Contact:

Re: Cue List faders problem

Post by mcallegari » Sun Jan 08, 2017 11:58 am

@maximortal, can you please help with this by testing the development version ?
The issue resolution is now in progress and I'd appreciate to hear feedbacks from different users. Thanks

maximortal
Posts: 24
Joined: Mon Dec 19, 2016 7:07 pm
Real Name: Iro Suraci

Re: Cue List faders problem

Post by maximortal » Mon Jan 09, 2017 11:00 am

yes I can help if youneed it. What I have to do exactly?

plugz
Posts: 637
Joined: Sun Apr 12, 2015 6:30 pm
Real Name: David

Re: Cue List faders problem

Post by plugz » Mon Jan 09, 2017 1:18 pm

Hello,
Windows build available here (4.10.6.54): https://dl.bintray.com/mcallegari/qlcplus/
You go here, you install the test version, you test it.

maximortal
Posts: 24
Joined: Mon Dec 19, 2016 7:07 pm
Real Name: Iro Suraci

Re: Cue List faders problem

Post by maximortal » Wed Jan 11, 2017 1:46 pm

tested on 4.10.6.54 and it has finally expected behaviour.. great!
now i'm investigating about another issue on chaser inside an another chaser.
i'll keep you udpated.

edogawa
Posts: 24
Joined: Thu May 07, 2015 10:34 am
Real Name: Edgar Aichinger

Re: Cue List faders problem

Post by edogawa » Wed Jan 11, 2017 7:39 pm

I just found this thread, and as it seemed to address the most severe long standing problem we theater guys have had with the cuelist crossfade, which has been discussed in several threads over the past 2-3 years (intensity dropping when moving both faders in parallel/linked mode), I immediately had to build from git and test it :)

Well, I currently don't have my conventional dimmers at home, and the two 24 channel DMX LED Controllers I ordered from AliExpress haven't arrived yet, so I cannot test with physical lights right now. But from watching the dmx monitor it indeed seems to work, yay!!!

Can't wait to test this in a realworld environment, this will save me a lot of time and hassle with directors in future productions. Many theater lighting techs prefer to perform manual in favour of timed crossfades, because the fade time often depends on what actors do on stage, which can vary in time a lot from one to another evening.

One question though, is it on purpose that this new code only works on linked faders? Each and every lighting desk with a two fader crossfade playback that i've had the chance to work with operates with this "crossfade law" while still being able to move each fader individually to separately control fade in/out ...

Cheers, Edgar

Post Reply