After testing recent changes in slider monitor features I found a strange behavior. In the attached workspace I create 4 scenes this scenes controls dimmer fixtures.
Scene One with 2 dimmers first set to full, second set to zero.
Scene Two with 2 dimmers first set to zero, second set to full.
Scene One-1 with dimmer 1 set to full.
Scene Two-1 with dimmer 2 set to full.
Chaser OneTwo with scenes On and Two.
Chaser OneTwo-1 with scenes One-1 and Two-1
Virtual console
2 Sliders in monitor mode one per channel/dimmer.
Cue list OneTwo with scenes One and Two
Cue list OneTwo-1 with scenes One-1 and Two-1
Playing OneTwo cue list the sliders follow the values correctly, showing the values changing smoothly.
Playing OneTwo-1 cue list. When change to next step, the slider monitoring actual step falls to zero immediately, but the fixture monitor shows the correct values.
Is this the correct behavior?.
Slider Monitor behavior
- sbenejam
- Posts: 547
- Joined: Sun Apr 12, 2015 6:28 pm
- Real Name: Santiago Benejam Torres
- Contact:
- Attachments
-
- test-slider-monitor.qxw
- (5.52 KiB) Downloaded 43 times
-
- Posts: 64
- Joined: Mon Dec 19, 2016 7:07 pm
- Real Name: Iro Suraci
i confirm this bug in GIT .89 and I found another bug :
in second chaser (one two-1) if you press pause button during transitions it do not affect fading out scene
in second chaser (one two-1) if you press pause button during transitions it do not affect fading out scene
- sbenejam
- Posts: 547
- Joined: Sun Apr 12, 2015 6:28 pm
- Real Name: Santiago Benejam Torres
- Contact:
After some tests I found that using crossfade sliders on cuelist, the sliders monitoring channels work as expected.
OS: Xubuntu 16.04
QLC+ from GIT
OS: Xubuntu 16.04
QLC+ from GIT
-
- Posts: 703
- Joined: Mon Nov 02, 2015 11:03 am
- Location: Germany
- Real Name: Lukas
I can confirm this on Xubuntu 14.04 64 Bit (Qt5).
Massimo, could you please have a look into this? I don't know about handling fade times and the monitoring feature. All I can say this issue is already present in 4.10.5b.
Massimo, could you please have a look into this? I don't know about handling fade times and the monitoring feature. All I can say this issue is already present in 4.10.5b.