Direct control of devices

  • Hi,

    it's not exactly the way of thinking of DMXControl but it's possible. Two ways:

    • directly connect DMX-In to DMX-Out in Input Assignment module: but it's not recommanded because not flexible
    • use Programmer as output, example below:

    This example connect the A key to the Lumos action of my device. To add a device, right click, Add, Wrapper, Devices, Device.

  • Sorry, that I did not respond earlier :saint:

    but in my environment there is no Devices in the input assignment function.

    We removed the "Devices" section from the Input Assignment completely because this was not conformal with the concepts of DMXControl 3. With that you could control devices directly but were not able to store those values e.g. in cuelists. That's the reason why we dropped this and expand the Programmer node instead. As Mikol already said you can change the value of a device property with it and this value is kept in the programmer. The way of thinking Mikol mentioned is the fact that you can run a show out of the programmer but we recommend to use cuelists because then you can use your light scenes afterwards again. With the programmer, if you clear it, the light scene in it is lost. If you need editable parameters (e.g. control the intensity of a fixture in a specific scene by an external input) then you can take a look at the masters of DMXControl 3. In DMXC 3.2.3 there are ParameterMaster and SpeedMaster which you can use in various locations e.g. for a device property. With DMXC 3.3.0 we added ColorMaster and PositionMaster as well. If you are interestet in that topic, then you can read our Did you know? article about that: https://forum.dmxcontrol-projects.org/core/index.php?article/453

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

  • Thanks Mikol and JPK , I'm getting understanding the concept of DMXC3.

    But actually, typically my project has 60+ old halogen lights (classic dimmer channels) with only 6-8 moving lights. In that case, most of my work is to control the dimmer intensity, only sometimes I use non-intensity parameter.

    So I want to control them as if I use a classic 48ch fader board.

    That's why I wanted to control specific parameters directly, and not only control, I wanted to store that scene to a cuelist.

    Does it make sense?

    Based on my usage, is there any solutions?

  • As long as parameter values are present in the programmer, you can store them in cues in a cuelist. So the way Mikol showed is the way to go. However, if you put every halogen light on a fader, this is a little bit inefficient in DMXControl 3. One of the powers of DMXControl 3 is its handling of device groups. Those are virtual fixtures and control all devices in this group at once. This even with different device types (e.g. the halogen lights and the moving heads) in the same group. A device is also not limited to only one device group. You have the total flexibility (unlimited number of device groups with unlimited amount of devices and a device can be in an unlimited number of groups). You are even allowed to add or remove lights afterwards and after restarting a cue, the newly added devices are controlled by the group as well. So instead of controlling every fixture on its own with a fader, I would combine them to good groups (sometimes a good group can have only one device too) and control the intensity parameter of the device group with a fader. Then you store the group property value. This gives you a high flexibility and that is e.g. also the way I use in my projects if I have an external control via DMX / midi board.

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

  • 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.