[Fix 11.8.5] SCS 11.8.4.1 - Lighting cues not working properly in callable cue

[Edi_28]

Hi Mike,

I've setup different lighting scenes (All front lights -> Hotkey 1 / All back lights -> Hotkey A / All back lights Left -> L / etc.)
When a single lighting cue contains several fixtures, everything works fine, but when I combine a lighting scene with several parallel "callable" lighting cues, only the dimmer of the fixture in the last lighting cue gets its value, although "Fadeout others..." is set to "Do not fade out others".

I've attached a sample show file, where you can reproduce the error.

Following Hot-Keys work as expected:
1 -> Full Light (All front lights)
2 -> Full left (Leftside profiler)
3 -> Full right (Rightside profiler)
4 -> Break Light (Special Light Scene with all backtruss movingheads)
5 -> Exotic Aerobic light (Special Light Scene with all backtruss movingheads)
6 -> Fadeout All
0 -> Blackout

Following Hot-Keys DON'T work as expected:
A -> Fade In Back (Should raise dimmer of all backtruss movingheads, but only raises the dimmer of the last one in the last callable cue)
L -> Fade In BackLeft (Should raise dimmer of backtruss movinghead 1 & 2, but only raises dimmer of backtruss MH 2)
R -> Fade in BackRight (Should raise dimmer of backtruss movinghead 4 & 5, but only raises dimmer of backtruss MH 5)

Problem seems to exist only on dimmer channels. Other channels like RGB seem to work in parallel within callable cues.

Everything checked with DMX output window.

Best regards,
Dieter

[Mike Daniell]

Dieter, could you email me the log file from a run in which you tried hotkeys A, L and R? What I specifically need is the actual DMX channels assigned to all of your fixtures. This information is held in the device map file, and will be listed in the log file. A log file will have been created and saved in a folder named "SCS Logs" under "Documents", and the name of the file includes a time-stamp indicating when the log started.

[Edi_28]

Hi Mike,

Sorry for the delay. I did a new run with only activating the hotkeys in following order and attached the logfile:
- 1, 0, 2, 0, 3, 0, A, 0, L, 0, R, 0

Best regards,
Dieter

[Mike Daniell]

Thanks for the log, Dieter. I've now been able to reproduce the problem so will work on a fix.

By specifically testing hotkey L, the second call cue in LC290 seems to be suspending the action of the first call cue. So the fade-in of the first called cue (LC210) gets started, but when the second called cue (LC230) starts this suspends the fade-in of LC210. This can be clearly seen by using 'Show Display DMX Window'.

[Edi_28]

I can confirm your findings. The fader value of the first fixture starts to rise, before it is interrupted by the second fixture when the next callable cue starts. With four callable cues with one fixtures per callable cues only the fader value of the last one reaches its end value.

Thanks for your work and fast response!