Special cues - odd behaviour

We proudly present: The release of DMXControl 3.3.3!


On September 29, 2026, we held our release show for DMXControl 3.3.3. During our usual “hour-long” session, we showed you all the new features in this version and what it now has to offer.
Read all about it in the corresponding news article: We proudly present: The release of DMXControl 3.3.3!

    Hi guys,

    I've noticed a cuelist behaviour that seems incorrect, but I just want to check that it's not intentional before I report it as a bug.

    I have a cuelist (we'll call this the master cuelist), and within that cuelist, I am triggering some other cuelists (we'll call these sub-cuelists) using the 'Go' and 'Stop' special cues.

    If I use the 'Go to' function to jump to a later point in the master cuelist after I have triggered a 'go' and then a 'stop' on a sub-cuelist, that sub-cuelist remains playing when I believe it should be stopped.

    Is this behaviour of DMXC3 deliberate, or is it a bug?

    So in this example above, if I "Go To" cue 17, I would expect the 'Petro Alts' and 'Petro Zips' cuelists to be stopped, but instead they are running.

    If I play the cuelist from the start, they behave as expected.

    If this behaviour is intentional, can you explain the thinking behind it so i can understand why it happens.

    Thanks,
    Phil

    I dont think this is the wanted behaviour, but dont quote me on that. Id reccomend creating a ticket on the bugtracker.

    Usually, the go to function should be used very rarely. Because each cue builds up on the previous cue (unless tracking is disabled, which is not a preferred workflow in DMXC), a cuelist should almost always be run sequentially. What is your workflow? (when are you using go to?)

    I only use Go To when I'm programming, not during shows.

    Most of the cuelists that I create are timed to music with many 'Wait' cues,

    So in the example above, if I wanted to edit cue 17, I would use 'Go To' to jump to cue 17, so that I could see how the lighting looks at that point without having to wait for ~2 minutes for the cuelist to play, and then 'Edit in programmer' to make the changes to cue 17, then update.

    I'll create a bug ticket :)