hello,
in cue list, the left fader not at full, when 'next' or 'previous' cue button is pressed the transition happens as if the left fader is at full,
as soon you move it takes again control over the levels.
qlcplus 4.10.2 / 4.10.2b, qt5, linux 64
cue list, next and previous cue problem with left fader
-
giacomo
- Posts: 568
- Joined: Tue May 26, 2015 6:17 pm
- Real Name:
you can test it on the file I posted in "Toggle Virtual Console Live Edit problem", I've the same the same issue with it.
light and sound:
set the left fader of the cue list at 0,
go to the next cue,
the output happens has the left fader is at full
(the same issue of topic "Toggle Vitual Console Live Edit problem")
light and sound:
set the left fader of the cue list at 0,
go to the next cue,
the output happens has the left fader is at full
(the same issue of topic "Toggle Vitual Console Live Edit problem")
-
plugz
- Posts: 637
- Joined: Sun Apr 12, 2015 6:30 pm
- Real Name: David
There were 2 issues in this topic : http://qlcplus.org/forum/viewtopic.php?f=5&t=9184, reproduced in the attached workspace:
- When going to VC live edit mode, intensity jumps to 100%
- When moving the submaster slider, intensity jumps to the submaster slider value
These 2 issues are NOT the same as the one you describe here. The issue you describe here as something to do with the "NEXT" button. Did you mention the "NEXT" button ANYWHERE in the other topic ?
- When going to VC live edit mode, intensity jumps to 100%
- When moving the submaster slider, intensity jumps to the submaster slider value
These 2 issues are NOT the same as the one you describe here. The issue you describe here as something to do with the "NEXT" button. Did you mention the "NEXT" button ANYWHERE in the other topic ?
-
giacomo
- Posts: 568
- Joined: Tue May 26, 2015 6:17 pm
- Real Name:
I uploaded a simple file, here the steps to reproduce the issue.
- start playing the cue list, now you're in the first cue and so open the monitor, "dimmer #01" should be at 255;
- show the crossfade sliders and move the first on the left to 50%, "dimmer #01" should be now at 128;
- go to the next step pressing the right arrow: "dimmer #02" goes at 255 despite the crossfade slider is at 50%;
- move the cross fade slider on the left and it takes again control over the output, but set it again at 50%;
- go to the next step pressing the right arrow; "dimmer #03" goes at 255 despite of the crossfade level again.
NB.
I just discovered now that if I select one cue in the list with the mouse and I play it by pressing "Enter" - I'm in gnome 3 -, the output respects the level of the crossfade slider.
But again: if now I use the "next step" button the output follows the level of the crossfade slider used when I selected the step with the mouse, no matter if I move it.
I'm using a package downloaded yesterday from opensuse, http://download.opensuse.org/repositori ... pkg.tar.xz.
- start playing the cue list, now you're in the first cue and so open the monitor, "dimmer #01" should be at 255;
- show the crossfade sliders and move the first on the left to 50%, "dimmer #01" should be now at 128;
- go to the next step pressing the right arrow: "dimmer #02" goes at 255 despite the crossfade slider is at 50%;
- move the cross fade slider on the left and it takes again control over the output, but set it again at 50%;
- go to the next step pressing the right arrow; "dimmer #03" goes at 255 despite of the crossfade level again.
NB.
I just discovered now that if I select one cue in the list with the mouse and I play it by pressing "Enter" - I'm in gnome 3 -, the output respects the level of the crossfade slider.
But again: if now I use the "next step" button the output follows the level of the crossfade slider used when I selected the step with the mouse, no matter if I move it.
I'm using a package downloaded yesterday from opensuse, http://download.opensuse.org/repositori ... pkg.tar.xz.
-
sbenejam
- Posts: 621
- Joined: Sun Apr 12, 2015 6:28 pm
- Location: Spain
- Real Name: Santiago Benejam Torres
- Contact:
Hi Giacomo,
I can confirm the behaviour that you explained, tested on Xubuntu 15.10.
I can confirm the behaviour that you explained, tested on Xubuntu 15.10.