1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<HTML>
<HEAD>
<TITLE>Q Light Controller Plus - Parameters Tuning</TITLE>
<SCRIPT SRC="utility.js" TYPE="text/javascript"></SCRIPT>
<link href="style.css" rel="stylesheet" type="text/css" />
</HEAD>
<BODY onLoad="replaceqrc()">
<H1>Parameters tuning</H1>
<P>
This section explains how to manually get at and tune some QLC+ parameters not available from the UI.<br>
Keep in mind that if you cannot change them from the UI, it means there is a good reason for it.
<H2>Warning: DO NOT edit the configuration files manually unless you know what you're doing. Any misplaced change can cause
program crashes or awkward instability.</H2>
</P>
<H1 id="location">1 QLC+ configuration location</H1>
<H2>Linux</H2>
<P>
Configuration files are located in your user $HOME directory, in the .config/qlcplus folder.<br>
Here's the quick command to access it from a terminal:<br>
<code>cd $HOME/.config/qlcplus</code><br>
You will find both QLC+ and Fixture editor configuration files.
</P>
<H2>Windows</H2>
<P>
Configuration parameters are stored in the Windows registry.<br>
To access it, run the "regedit" tool and search for the key named "qlcplus".<br>
</P>
<H2>Mac OSX</H2>
<P>
Configuration files are located in your user $HOME directory, in the Library/Preferences folder,
which is by default hidden by OSX.<br>
Here's the quick command to access it from a terminal:<br>
<code>cd $HOME/Library/Preferences</code><br>
The QLC+ configuration file is called <code>net.sf.Q Light Controller Plus.plist</code> while the Fixture editor
configuration file is called <code>net.sf.Fixture Definition Editor.plist</code>.<br><br>
<B>Please note that preferences are cached!</B> Basically OSX loads all the plist files in memory at boot,
and if you change them manually it will ignore the changes. Even worse, periodically it refreshes the files,
so it overwrites your changes.<br>
The solution is, after changing a .plist file, open a terminal and type this:<br>
<code>killall -u yourusername cfprefsd</code><br>
Where <code>yourusername</code> is the name of the user you use to access your Mac. The command forces OSX
to reload the preferences, including your changes.
</P>
<H1 id="reset">2 Configuration Reset</H1>
<P>
Sometimes it might be necessary to reset the QLC+ configuration and bring QLC+ to a "Factory defaults" state.<br>
To do so, locate the configuration as explained in the first paragraph, then do the following:
<ul>
<li>On Linux and OSX use the <code>rm 'filename'</code> command to delete the configuration file</li>
<li>On Windows delete the whole 'qlcplus' KEY using regedit</li>
</ul>
</P>
<H1 id="syntax">3 Parameters syntax</H1>
<P>
Due to Qt differences on different platforms, parameters are stored in different ways depending on
your Operating System.
<H2>Linux</H2>
Parameters are stored in a plain text file that you can modify with a plain text
editor like gedit, kwrite, kate, nano, vim or similar. They are presented as follows:
<PRE>
[category]
name=value
</PRE>
<H2>Windows</H2>
Parameters are stored in the Windows registry and can be modified with the regedit tool
included in every Windows version. They are presented as follows:
<PRE>
"category" is displayed as a folder
"parameter" is contained in "category" and is represented as a key. It is most likely that all QLC+ keys are an integer type.
"value" is the actual value of "parameter"
</PRE>
<H2>Mac OSX</H2>
Parameters are stored in a plain text file that you can modify with a plain text
editor like <a href="https://www.barebones.com/products/textwrangler/">TextWrangler</a> or similar. They are presented as follows:
<PRE>
<key>category.name</key>
<string>value</string>
or
<integer>42</integer>
</PRE>
</P>
<H1 id="list">4 Parameters list</H1>
<P>
Most likely you will not find the following parameters in a standard QLC+
configuration. To make them effective, you need to <B>add</B> them at the end
of your configuration file.
<H3 id="SimpleDesk">4.1 Simple Desk</H3>
<PRE>
<B>Category:</B> simpledesk
<B>Name:</B> channelsperpage
<B>Type:</B> integer
<B>Description:</B> Set the number of DMX channel sliders displayed per page
<B>Default:</B> 32
</PRE>
<PRE>
<B>Category:</B> simpledesk
<B>Name:</B> playbacksperpage
<B>Type:</B> integer
<B>Description:</B> set the number of playback sliders displayed per page
<B>Default:</B> 15
</PRE>
<H3 id="EnttecOpenChannels">4.2 DMX USB Enttec Open channels number</H3>
<PRE>
<B>Category:</B> enttecdmxusbopen
<B>Name:</B> channels
<B>Type:</B> integer
<B>Description:</B> Set the maximum number of DMX channels transmitted by Enttec Open (and similar) devices.
In some cases this could solve flickering issues. For example you might try with 256.
<B>Default:</B> 512
</PRE>
<H3 id="uDMX">4.3 uDMX frequency</H3>
<PRE>
<B>Category:</B> udmx
<B>Name:</B> frequency
<B>Type:</B> integer
<B>Description:</B> Set the DMX frame frequency in Hertz for uDMX devices
<B>Default:</B> 30
</PRE>
<H3 id="uDMXChannels">4.4 uDMX channels number</H3>
<PRE>
<B>Category:</B> udmx
<B>Name:</B> channels
<B>Type:</B> integer
<B>Description:</B> Set the maximum number of DMX channels transmitted by uDMX devices.
In some cases this could solve flickering issues. For example you might try with 128.
<B>Default:</B> 512
</PRE>
<H3 id="MasterTimer">4.5 Master Timer frequency</H3>
<PRE>
<B>Category:</B> mastertimer
<B>Name:</B> frequency
<B>Type:</B> integer
<B>Description:</B> Set the QLC+ core timer frequency in Hertz
<B>Default:</B> 50
</PRE>
</BODY>
</HTML>
|