<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>https://wiki-en.dmxcontrol-projects.org/index.php?action=history&amp;feed=atom&amp;title=Workarounds_%28General_Information%29_DMXC3</id>
	<title>Workarounds (General Information) DMXC3 - Revision history</title>
	<link rel="self" type="application/atom+xml" href="https://wiki-en.dmxcontrol-projects.org/index.php?action=history&amp;feed=atom&amp;title=Workarounds_%28General_Information%29_DMXC3"/>
	<link rel="alternate" type="text/html" href="https://wiki-en.dmxcontrol-projects.org/index.php?title=Workarounds_(General_Information)_DMXC3&amp;action=history"/>
	<updated>2026-05-17T00:51:45Z</updated>
	<subtitle>Revision history for this page on the wiki</subtitle>
	<generator>MediaWiki 1.39.10</generator>
	<entry>
		<id>https://wiki-en.dmxcontrol-projects.org/index.php?title=Workarounds_(General_Information)_DMXC3&amp;diff=4310&amp;oldid=prev</id>
		<title>Jkuehn: Created page with &quot;{{Manual Header   | Type = DMXC3 Main-Software   | Version = 3.3.0}}  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.  {{Manual Box | en | Important | 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 &#039;&#039;&#039;{{DMXCWebLinks|FS|Project|3|Bugtracker}}&#039;&#039;&#039;.}}  {{Manual Box | en | Hint | Some of the wo...&quot;</title>
		<link rel="alternate" type="text/html" href="https://wiki-en.dmxcontrol-projects.org/index.php?title=Workarounds_(General_Information)_DMXC3&amp;diff=4310&amp;oldid=prev"/>
		<updated>2025-03-04T20:19:26Z</updated>

		<summary type="html">&lt;p&gt;Created page with &amp;quot;{{Manual Header   | Type = DMXC3 Main-Software   | Version = 3.3.0}}  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.  {{Manual Box | en | Important | 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 &amp;#039;&amp;#039;&amp;#039;{{DMXCWebLinks|FS|Project|3|Bugtracker}}&amp;#039;&amp;#039;&amp;#039;.}}  {{Manual Box | en | Hint | Some of the wo...&amp;quot;&lt;/p&gt;
&lt;p&gt;&lt;b&gt;New page&lt;/b&gt;&lt;/p&gt;&lt;div&gt;{{Manual Header  &lt;br /&gt;
| Type = DMXC3 Main-Software  &lt;br /&gt;
| Version = 3.3.0}}&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
{{Manual Box | en | Important | 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 &amp;#039;&amp;#039;&amp;#039;{{DMXCWebLinks|FS|Project|3|Bugtracker}}&amp;#039;&amp;#039;&amp;#039;.}}&lt;br /&gt;
&lt;br /&gt;
{{Manual Box | en | Hint | Some of the workarounds described below are known and will be fixed in a future version.  &lt;br /&gt;
&amp;#039;&amp;#039;An overview of the workarounds that will be achievable with a native function in a later version of DMXControl 3 can be found under {{Manual Windowcaption|[[Known Bugs (General Information) DMXC3|Known Bugs]]}}.&amp;#039;&amp;#039;}}&lt;br /&gt;
&lt;br /&gt;
= Effects and Filters =&lt;br /&gt;
== Dynamic Manipulation of Effects ==  &lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;Use Case&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
Manually, the fluctuations could be changed via the entered {{Manual Windowcaption|[[Master DMXC3|Parameter-Master]]}}. However, such an effect cannot currently be triggered via a {{Manual Windowcaption|[[Cuelist DMXC3|Cuelist]]}}.&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;Solution&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
&lt;br /&gt;
You essentially have to loop back the appropriate parameter master to directly access it from the project. This loop can be created as follows:  &lt;br /&gt;
# Create a dummy device, patched to an unused DMX address. For example, use a Generic Dimmer or Generic RGB device.  &lt;br /&gt;
# In the {{Manual Windowcaption|[[Input Assignment DMXC3|Input Assignment]]}}, create a connection set where you use the {{Manual Objectcaption|[[DMXC Mixer (Input Assignment) DMXC3|DMXC Mixer]]}} node to display the output values. Here, connect the {{Manual Commands|Intensity}} output of the {{Manual Objectcaption|DMXC Mixer}} node to the {{Manual Commands|Fader Value}} input of the {{Manual Objectcaption|[[Parameter Master (Input Assignment) DMXC3|Parameter-Master]]}} node.&lt;br /&gt;
&lt;br /&gt;
= Softdesk =&lt;br /&gt;
== Multiple Information on a Button in Softdesk ==  &lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;Use Case&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
&lt;br /&gt;
In a {{Manual Windowcaption|[[Softdesk DMXC3|Softdesk]]}}, a button should display both the icon of a gobo and also switch a corresponding {{Manual Windowcaption|[[Cuelist DMXC3|Cuelist]]}} on and off. It should also visually indicate the status with two different colors.&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;Cause&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
&lt;br /&gt;
The buttons currently have only one input, which can handle numerous different types of information:  &lt;br /&gt;
* Status  &lt;br /&gt;
* Button label  &lt;br /&gt;
* Background image  &lt;br /&gt;
* Color  &lt;br /&gt;
If all this information is sent at once, usually only one value change is processed by the button.&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;Solution&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
&lt;br /&gt;
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 {{Manual Objectcaption|[[FiFo (Input Assignment) DMXC3|FiFo]]}} node before the button for the &amp;quot;structured transfer.&amp;quot; Connect all signal paths that the button should handle to the inputs of the {{Manual Objectcaption|FiFo}} node. You may need to adjust the time value for the update rate and set it slightly higher than the default of &amp;lt;code&amp;gt;50ms&amp;lt;/code&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
== Cuelist Monitor is Empty After Project Load ==  &lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;Use Case&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;Solution&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
&lt;br /&gt;
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. {{Manual Reference | arrow | For an explanation, see {{Manual Windowcaption|[[Cuelist Monitor (Softdesk) DMXC3|Cuelist Monitor]]}}.}}&lt;br /&gt;
&lt;br /&gt;
= Input Assignment =&lt;br /&gt;
== Use the Same Value in Multiple Locations ==  &lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;Use Case&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
&lt;br /&gt;
A specific value needs to be processed in several connection sets. However, this value is not coming from a MIDI controller, but is generated &amp;quot;within&amp;quot; the project.&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;Solution&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
&lt;br /&gt;
Create a separate {{Manual Objectcaption|[[Parameter Master (Master) DMXC3|Parameter-Master]]}} that is solely used to receive (remember) a specific value and make it available again in any number of connection sets.&lt;br /&gt;
&lt;br /&gt;
If only the value &amp;lt;code&amp;gt;0&amp;lt;/code&amp;gt; or &amp;lt;code&amp;gt;1&amp;lt;/code&amp;gt;, respectively &amp;lt;code&amp;gt;false&amp;lt;/code&amp;gt; or &amp;lt;code&amp;gt;true&amp;lt;/code&amp;gt;, needs to be stored, you can work without upstream and downstream nodes.&lt;br /&gt;
&lt;br /&gt;
If you want to transfer a numerical value, for example between &amp;lt;code&amp;gt;0&amp;lt;/code&amp;gt; and &amp;lt;code&amp;gt;160&amp;lt;/code&amp;gt;, to other connection sets, set this value range centrally in the properties of the corresponding {{Manual Objectcaption|[[Parameter Master (Master) DMXC3|Parameter-Master]]}} in the {{Manual Objectcaption|[[Project Explorer DMXC3|Project Explorer]]}}. In the node that will &amp;quot;read&amp;quot; the values, change the setting {{Manual Fields|Relative Input Values}} from the default &amp;lt;code&amp;gt;true&amp;lt;/code&amp;gt; to &amp;lt;code&amp;gt;false&amp;lt;/code&amp;gt;. This tells the Parameter-Master node to expect a value between &amp;lt;code&amp;gt;0&amp;lt;/code&amp;gt; and &amp;lt;code&amp;gt;160&amp;lt;/code&amp;gt; instead of the usual &amp;lt;code&amp;gt;0&amp;lt;/code&amp;gt; to &amp;lt;code&amp;gt;1&amp;lt;/code&amp;gt;. To &amp;quot;read,&amp;quot; use the output {{Manual Commands|Value}}.&lt;br /&gt;
&lt;br /&gt;
[[Category: Manual DMXControl 3]]&lt;br /&gt;
&lt;br /&gt;
[[de: Workarounds_(General_Information)_DMXC3]]&lt;/div&gt;</summary>
		<author><name>Jkuehn</name></author>
	</entry>
</feed>