Hello
I made a case by creating a fuelist in dmxcontrol and setting the trigger to follow and loop, but it doesn't work when I change the fade time of a specific queue while it's working. So when I stop and start again, the changed fade time is applied only then, is this normal?
LightningBrothers Hi and welcome in our forum 
So when I stop and start again, the changed fade time is applied only then, is this normal?
Yes, this is totally normal and the way DMXControl 3 works. Fade / delay times are only updated after restarting the cuelist and e.g. fannings on device groups are recalculated for group size changes only after reapplying the fanning (or rerun the cuelist in which the fanning is stored). Otherwise, those checks would have major performance impacts and thus are not done.
JP
Hello.
This behaviour is (currently) normal, that you must stop and start the again after you change the timings.
Also when you change the assignments in the device groups, modify the order in a device group or you disable and enable devices, you have to restart a cuelist.
Stefan
Have you seen the "Fade Factor" and "Speed Factor" settings of the cuelist? Maybe these can be of help for what you are trying to achieve?
Stefan
LightningBrothers After a few experiments, I noticed that the fade value applied right after turning "Active" on and off. I don't know if this is safe
Later cues in a cuelist depend on earlier cues. So lets make an example: If the first cue sets the dimmer to 100% and the second cue sets the color to orange, then 100% and orange is output if you run the second cue because the values of the first cue also count. This is the reason why the playstate of the cue changes if you activate it (because all later cues depend on it).
JP
