VirtualConsole and CueList : fade type

[Sylvain Laugié]

Hi,

* EDIT : I thought i was going to write a suggestion, but finally, i'm writing a bug report. More info in the end of the post


I have a suggestion for the Cue List in the Virtual Console : i would like to be able to change the way the fades are made when fading between scenes of the chaser of the cue list.

Let me explain with an example :

I am going to use QLC+ for a theatrical show.
Let's imagine a very simple setup : 2 fixtures, actually 2 dimmers (one PAR fixture per dimmer).
I have a first scene where I have the first PAR fixture @100%.
I have a second scene where I still have the first PAR @100%, plus the second PAR @100% too.
The two scenes have 5seconds fade in/out.

I activate the first item of the cue list => the first scene, so the first PAR takes 5s to go to 100%.
I go to the next step of the cue list => the first scene fades out (in 5s) while the second scene fades in (in 5s too).

What's happening ? During the first 2.5s, the first PAR fades out to 50%. Then, during the last 2.5s, the two PAR go to 100%.

The problem is : i don't want the first PAR to fade out, i want it to stay @100% while the second one if fading in.

The suggestion (here we go !) : we should be able to change the way the fades work using the cue list, so that each channel doesn't fade out to 0 when fading out, but to the value it will have on the next step.


* EDIT : Actually, this is already the way the cue list works, when using preset fades (with times). But if i use the left sliders, when linked, to go step by step manually (with a nanokontrol2), it does fade to 0 instead of fading to the next value in the next step


I hope this is clear enough, i can add images if needed.
I added a workspace project, to reproduce :
- enter production mode
- activate sliders on the cue list
- check the "link" checkbox
- open the dmx monitor
- click the play button on the cue list to activate the first scene
- keep an eye on the fixture 1 dmx value and use one of the sliders of the cue list to go to the next step. It should stay 255, it goes 255->128->255

[Jano Svitok]

Sylvain,

I've had a look at the code. The crossfade is now made using two submaster-like faders - one for each step. That explains the current behavior.

To get correct crossfade, the code must be changed to use real fading code, a that in turn must be changed to accept manual timing (unless someone comes with a easier way).

Summary: I agree that linked crossfade should not go through black (or 50%), but it will take some time to fix.

BTW. thanks for the complete report and the description. It's just so easier when you get all the information up front

[Sylvain Laugié]

Thank you, I now see the problem.

Maybe I'll look at the code, if I can find time enough, to see if I can try something

[Alberto]

I have just created a ticket on github https://github.com/mcallegari/qlcplus/issues/439

Any guidance on how to fix this bug will be very welcome.

Thanks