Highlight / Stop From Cuelist

Hi,

technically, you can do that via the Input Assignment. Add a Connection Set and doubleclick it. Then, add the "All Cuelists" Node for the second one. The first one is a little bit trickier and there are multiple ways to achieve this. But they depend on the result you want to get. So what do you planing to do with that?

JP

Sorry for my late response but I needed to prepare for the livestream yesterday, where we presented the timecode player in DMXControl 3.3.0 and released a release candidate (see https://forum.dmxcontrol-projects.org/core/index.php?article/903 and https://forum.dmxcontrol-projects.org/core/index.php?article/905)

Ok, I looked into your project and hope, I understand your post correct. If not, please correct me You need a way to stop a cuelist, if another one starts to run and you need a sort of highlight function to keep the lights on and only change the color. Is this correct? If yes, then I would do the following: First, add a cuelist, which is only responsible for the dimmer of the devices / device groups. So this cuelist contains only one cue with the respective dimmer values in it (full on). This cuelist will run the whole day until you or the external computer stops this cuelist. The second change in your project is the one, where the magic comes in . DMXControl 3 uses the concept of cuelist groups. A cuelist group links the containing cuelists and controls their start and stop behavior. You define those groups in the Cuelist Groups folder in the Project Explorer. In the setting of a cuelist group, you will find the "cuelist start behavior", which is the one you need. If you select "Single List Running", DMXControl 3 automatically stops all running cuelist in the group if you start another one in this group. So just add all cuelists, which shall inhibit each other (so in your case e.g. all "PL_..." cuelists). This can be done by drag&drop the respective cuelist onto the cuelist group in the left tree view (see the following image)

Then you just need to trigger your "Theme_..." cuelists as you already do to start the correct cuelist and DMXControl 3 do the stopping by itself. So you do not need the "stop all cuelists" command anymore

I have also some hints to improve your project:

• You can change the "Release at end mode" of all "Theme_..." cuelists from "with Go" to "when last cue ends". Then the theme cuelists only start the containing cuelists and stop again afterwards. Then you do not need to handle this with another GO or the "Stop all Cuelists" command.
• You can significantly reduce the amount of cues in your "PL_Row_Pulse_Slow_..." cuelists if you use the Cue Timing Editor. It allows you to set the delay and fade times per device / device group independent from the cue delay and fade time of the respective cue. Just make a double click on the cue to open the Timing Editor for this cue. With those setup, you only need two cues, one for the first color and one in which all devices have the second color and then you can define an individual delay for those devices. You can even set the color of the respective device groups as a whole and apply a fanning in the delay entry in the Cue Timing Editor. This is the option I chose in the attached version of your project (in the cuelist "PL_Row_Pulse_Slow_LightBlueLightYellow_Improved"). There you can see, how to set up the timing editor if you want to change your other cuelists as well. If you want to know about the fanning, then you can look into the following article in our wiki: https://wiki-de.dmxcontrol-projects.org/index.php?title=Fanning_DMXC3. Unfortunately, it is only in German available yet. But the animated table shows you, which fanning operators DMXControl 3 supports (in the article presented in the context of the dimmer device parameter, but the operators are the same for the fade and delay times).
• You can set the option "Skip 1st cue trigger on Play" of your repeating cuelists to true (in the options of those cuelists). Then they start immediately after starting with the first cue. The trigger value then only applies from the second pass on. I have enabled this option in the "PL_Row_Pulse_Slow_LightBlueLightYellow_Improved" cuelist as well so that you can see the difference to your cuelist.

I hope my descriptions combined with the updated project I attached are understandable and help you to get the results you want

JP

P.S.: Your project seems quite interesting If I may ask, what is it for?