This article gathers various known use cases that can often be solved with a workaround, until they are corrected in a new update or the function is added.
|
If errors occur in the software or a function is missing, it would be great if they could be entered as a new ticket in our Bugtracker. |
|
Some of the workarounds described below are known and will be fixed in a future version.
An overview of the workarounds that will be achievable with a native function in a later version of DMXControl 3 can be found under Known Bugs. |
Effects and Filters
Dynamic Manipulation of Effects
Use Case
The audio level fluctuations of a group of LED spotlights or LED bars should be simulated, with the fluctuations being irregular and having various maximum values, as in reality. The base for this is the PWM-Static filter.
Manually, the fluctuations could be changed via the entered Parameter-Master. However, such an effect cannot currently be triggered via a Cuelist.
Solution
You essentially have to loop back the appropriate parameter master to directly access it from the project. This loop can be created as follows:
- Create a dummy device, patched to an unused DMX address. For example, use a Generic Dimmer or Generic RGB device.
- In the Input Assignment, create a connection set where you use the DMXC Mixer node to display the output values. Here, connect the Intensity output of the DMXC Mixer node to the Fader Value input of the Parameter-Master node.
Softdesk
Multiple Information on a Button in Softdesk
Use Case
In a Softdesk, a button should display both the icon of a gobo and also switch a corresponding Cuelist on and off. It should also visually indicate the status with two different colors.
Cause
The buttons currently have only one input, which can handle numerous different types of information:
- Status
- Button label
- Background image
- Color
If all this information is sent at once, usually only one value change is processed by the button.
Solution
To ensure the button processes all the different information, these must be passed in sequence and in a structured manner. This can be done by inserting a FiFo node before the button for the "structured transfer." Connect all signal paths that the button should handle to the inputs of the FiFo node. You may need to adjust the time value for the update rate and set it slightly higher than the default of 50ms.
Cuelist Monitor is Empty After Project Load
Use Case
In a Softdesk, one or more cuelist monitors are used to start and stop a selection of cuelists. However, these are always empty when the project is loaded.
Solution
The connection set that passes information to the Cuelist Monitor, indicating which cuelist group should be displayed, needs to be supplemented with a manual reset function. 
For an explanation, see Cuelist Monitor.
Input Assignment
Use the Same Value in Multiple Locations
Use Case
A specific value needs to be processed in several connection sets. However, this value is not coming from a MIDI controller, but is generated "within" the project.
Solution
Create a separate Parameter-Master that is solely used to receive (remember) a specific value and make it available again in any number of connection sets.
If only the value 0 or 1, respectively false or true, needs to be stored, you can work without upstream and downstream nodes.
If you want to transfer a numerical value, for example between 0 and 160, to other connection sets, set this value range centrally in the properties of the corresponding Parameter-Master in the Project Explorer. In the node that will "read" the values, change the setting "Relative Input Values" from the default true to false. This tells the Parameter-Master node to expect a value between 0 and 160 instead of the usual 0 to 1. To "read," use the output Value.