Most basic que-running question

  • Hi,


    I'm trying to do the most simple project ever and failing on cue control. It's all single fitting control on single channels. I have a bunch of ques that work and I want to run them from a button interface but I can't get them to play at the same time.


    Any help would be fantastic.


    Thanks

  • Hi,

    did I understand it right that you put all cues into one cuelist and want to play them all in parallel? If this is right, then this will not work as expected. Instead of having all cues in one cuelist, you need multiple cuelists. You can run those cuelists in parallel and have the result you want. To move those cues to other cuelists, you can create new cuelists and copy&paste your existing cues to the new lists.

    Regards

    JP

    im Falle eines Falles klebt Gaffa einfach alles, denn Gaffa ist dein Freund und Helfer :thumbup:

    Edited once, last by JPK ().

  • Hi JP,


    Thanks for that reply. I'm replicating LEDs on a control panel for a set. I have a few cuelists (of simple flashing sequences on single-channel fittings) that I want to trigger at various times from soft buttons. some of these ques will need to run simultaneously. I can't work out how cues affect each other. I really just need each cuelist to take over from the previous cuelist but can't understand what is running and what affects what. Any advice is really appreciated!


    Thanks


    Ewan

  • Hi JP, Thanks for your reply. I'm making a fake control panel for a theatre set full of single, addressed LEDs. I have a few cueslists which run their sequences in each section of LEDs ok but I can't work out how these cuelists affect or stop each other from working. Ideally, I need to have a few buttons on a softdesk to run a bunch of cues simultaneously but so far can't get past getting the cues to behave.


    Any help would be really appreciated.


    Thanks

    Ewan

  • Ok, In your case there are three things which will help you: HTP/LTP/LoTP+Priorities, Cuelist Groups and the Input Assignment.

    1. HTP/LTP/LoTP+Priorities: If you start two cuelists which control the same device parameters of a fixture, there are three different mixing behaviors. As a default, cuelists mix with LTP (last takes precedence). So if you start the second cuelist, it wins and control the output. The first one stays active but is hidden from the second cuelist. If you now stop the second one, then the first cuelist gets the control back. It is a little bit like an advanced stack. "Advanced" because there are the HTP (highest takes precedence) and LoTP (lowest takes precedence, unfortunately broken in DMXC 3.2.1 and will be fixed in 3.2.2). You can change the mixing characteristic for every cuelist to one of those three variants. In addition you can change the priority. With it, you are able to prioritize some cuelists like for example blinder effects. Both, the mixing mode and the priority can be edited in the properties of a cuelist (in the project explorer, in the section "cuelist" right-click on the one you want to change and click on "properties" there)
    2. Cuelist Groups: If you have a group of cuelists, in which only one cuelist shall be active at the same time, you can use cuelist groups. If you start one cuelist in this group, it automatically stops all other active ones in this group. This reduces your workload enormously. You can achieve it by simply adding a new cuelist group in the cuelist group sction in the project explorer. Then you add the according cuelists by drag&drop them (just expand the cuelist folder and drag them on the cuelist group of your choice. In addition, you have to go into the cuelist group properties and change the "cuelist start behavior" to "single list running".
    3. Input Assignment: The Input Assignment is the link between the button in the softdesk and the according cuelist. The problem is, that it is a little bit complex to describe and now it is late here in Germany :saint: I can give you a first link to one of our "Did you know?" articles: Did you know? Special #7 - Input Assignment - Infinite Possibilities In it, there are some descriptions on how to link an input (in that case a fader) to a cuelist. You can adapt that to your situation. In addition, if I have some time tomorrow, I will build up a little project, where you can see how it is done.

    Regards

    JP


    P.S.: Well, usually, I also recommend to watch our recently released tutorial videos on our YouTube channel. However, those videos are currently only in German. But maybe you can use them as well with the automatic subtitle translation. The videos can be found here: https://www.youtube.com/c/Dmxc…iew=50&sort=dd&shelf_id=2

  • Thank so much for this input.


    I'm not sure I've understood what is different in my project to what you suggested but I'll be back at it with fresh eyes/mind today. If you did have a sample project, it may help.


    Thanks


    Ewan

    Edited once, last by JPK: Removed the mail address to protect the user of spam mail crawler ().

  • Hi,


    I had less time than expected, so I had not the time to build up the demo project until today. However, now I created it. You can find a simple structure of three cuelists for the color and three for the dimmer of a group of LED devices. Take a look on the cuelist group and how it manages, that only one of the dimmer / color cuelists is running at a time. I also added a simple Softdesk with a few buttons to start and stop the cuelists. You can take a look at the connectionsets and see, how to start and stop the cuelists. The third thing I added is a blinder cuelist. This cuelist has a higher priority and overrules all other cuelists. I hope, this project will help you to understand how to control cuelists with the Softdesk.


    JP


    P.S.: If you have a StreamDeck, you can use it with DMXControl 3 too.