How does anyone acctually use this software?

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!


  • ok as you can see from the subject line i am having some issues!

    1: I am trying to create a control area which houses a go and back button to run my cues, How do i create a button in the command boxes which will go back to a previous cue, i have found the edit menu for the command boxes that allows you to choose cue list>previous> go, but this just makes each of my cue execute as if the button i created were a go button (they go forward, not back)

    2: I have created an audio scene in which i have setup lighting to execute automically a certain points in a song, i placed the audio scene in my cue list and now i want it to play until the next cue is executed at which point i want the audio and lighting to fade out. When i press go for the next cue the music just stops instead of fading out. How do i make it fade?

    3: when using a regular audio cue, i have placed a volume adjustment command as the next cue, when the audio adjustment cue is executed the volume does not fade to the new volume level, it just drops to the new level. How do i make it fade to a new volume level?

  • Hi!

    1: I am trying to create a control area which houses a go and back button to run my cues, How do i create a button in the command boxes which will go back to a previous cue, i have found the edit menu for the command boxes that allows you to choose cue list>previous> go, but this just makes each of my cue execute as if the button i created were a go button (they go forward, not back)


    Sorry, but at least the actual Version of DMXControl does not support a "GO-" oder "GO back" possibilty. What you found is the function to switch through your lists if you have more than one cuelist. Thats why the function labels "previous (cue list)". Dont mess it up with "previos entry/scene/position/cue".
    So I don't know a solution for that.

    Quote

    2: I have created an audio scene in which i have setup lighting to execute automically a certain points in a song, i placed the audio scene in my cue list and now i want it to play until the next cue is executed at which point i want the audio and lighting to fade out. When i press go for the next cue the music just stops instead of fading out. How do i make it fade?


    What do you mean by "audio scene"? You used the "Audioplayer"?

    Quote

    3: when using a regular audio cue, i have placed a volume adjustment command as the next cue, when the audio adjustment cue is executed the volume does not fade to the new volume level, it just drops to the new level. How do i make it fade to a new volume level?


    You have to use a "command" and than do the following:
    "Audio" -> "Channel 1"(or whatever) -> "Set volume".
    And now important: Do not give a value or flag one of the boxes directly below!
    Just tick "use fade in time" and "during fade-in value decrease".
    If you now give the command-cue a fade-in-time it will fade out in that speed. Perhaps you can use that for your question #2?
    Fading on a special level is not yet supportet.
    A dirty workaround would be: set volume levels 100-95-90-85-80 with a lot of commands that automatically follow each other in a short time.
    Sorry, but DMXControl is not designed as a soundmachine or a mediaserver. Some functions are just basically supportet because it was relative easy to include it.

    Hope it helps a little bit.
    Hoc

    Mein Equipment:
    1x Hirn | 2x Augen (leicht defekt) |2x Ohren | 1x Mund |32x Zahn (zum Teil V1.5) | 1x Handundfuß-Interface
    *SCNR*

  • 1: I am trying to create a control area which houses a go and back button to run my cues, How do i create a button in the command boxes which will go back to a previous cue

    As Hoc said it's not possible. I'd say the cuelist is the part of the program where some important features are missing. At least if you are used to work on consoles.
    If you want to go back to a cue, you must select the cue in the list and then press the "play icon" twice (left icon).
    You can bind this command to a button in the command box. So the workflow would be: Select the cue you want to goto and then use the button in the commandbox.
    Unfortunately there is no direct possibility to go one cue back.
    If you use tracking (only record changes) there is absolutely no way of going back, beacuse only the content (the changes) of the cue you goto will be played back. So the look on stage isn't the same it would be if the list had run in sequence.

    Dennis

  • You have to use a "command" and than do the following:
    "Audio" -> "Channel 1"(or whatever) -> "Set volume".

    What version are you using? I do not see an "Audio" module but only "Audio Track" - I have been wanting to adjust the volume and had no idea DMXControl could do this. I am using version 2.1

    -Richard
    https://forum.dmxcontrol-projects.org/www.holdman.com/christmas

  • What do you mean by "audio scene"? You used the "Audioplayer"?

    Zitat

    I mean an audioplayer, I have created a scene in the audioplayer tool, I created a command cue which plays that audio player, and I want the next cue (a composition cue) to fade the audio and lighting from the audioplayer and bring up different lighting. I have been able to accomplish creating the audioplayer cue, creating the composition cue, making the composition cue fade the lighting from the audioplayer and bring up the new lighting. Currently the audio just cuts out when the composition cue is finished executing. How do I make the audio from the audioplayer fade out with the composition cue?

  • Newly created posts will remain inaccessible for others until approved by a moderator. The last reply was more than 365 days ago, this thread is most likely obsolete. It is recommended to create a new thread instead.