File: howto-input-output-mapping.html

package info (click to toggle)
qlcplus 4.14.3-1
  • links: PTS, VCS
  • area: main
  • in suites: forky, sid
  • size: 58,644 kB
  • sloc: cpp: 182,867; javascript: 7,764; xml: 2,453; ansic: 2,120; sh: 1,716; python: 634; ruby: 606; makefile: 23
file content (148 lines) | stat: -rw-r--r-- 6,144 bytes parent folder | download | duplicates (3)
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
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<HTML>
<HEAD>
<TITLE>Q Light Controller Plus Plus Documentation</TITLE>
<SCRIPT SRC="utility.js" TYPE="text/javascript"></SCRIPT>
<link href="style.css" rel="stylesheet" type="text/css" />
</HEAD>
<BODY onLoad="replaceqrc()">

<H1>Input/Output Mapping Howto</H1>

<p>This howto document tells you how to patch plugins and their input/output lines
(physical input/output devices) to QLC+'s universes.</p>

<p>
By default QLC+ provides 4 universes but you can add/remove them as needed.<br>
The input/output mapping is saved in the currently loaded project.
This allows you to port your project on another computer/OS without the need to
reconfigure it every time.<br>
If no project is loaded, QLC+ will keep the I/O mapping as a "fallback" configuration.
</p>

<H2 id="input-output-manager">Input/Output Manager</H2>

<P>
To access the Input/Output Manager, just click on the tab with the <img src="qrc:/input_output.png" width=32> icon
placed on the bottom of the QLC+ main screen.<br>
The screen is composed in this way:<br>
<ul>
 <li>On the left hand side there is the list of internal universes that QLC+ can manage</li>
 <li>On the right hand side there is the list of devices and their mapped inputs, outputs and feedback lines that QLC+ has detected</li>
 <li>On the bottom right hand side there is a panel displaying brief information on the currently selected device</li>
</ul>

Every device has a checkbox whenever an input, output or feedback line is available.<br>
Each QLC+ universe can map a single input, a single output and a single feedback line<br>
</P>

<P>
Some plugins might require configuration before they can be used' so you might
not be able to see all inputs/outputs at first. The configuration button
is place next to the information panel and it is enabled if the plugin
allows any manual setting.<br>
The button icon is: <IMG SRC="qrc:/configure.png" width=32>
</P>

<H2 "adding-universes">Adding/Removing universes</H2>

<P>
QLC+ supports any number of universes, depending on the CPU limit of the device controlling them.<br>
On the left hand side of the Input/Output Manager there is a toolbar where you can add/remove, name
and configure universes.
</P>

<TABLE BORDER=1 class="qlcTable">
 <TR>
  <TD><IMG SRC="qrc:/edit_add.png"></TD>
  <TD>Add a new universe. The universe will have a name like "Universe X",
      where X is a progressive number assigned by QLC+ (and also the Universe ID).
  </TD>
 </TR>
 <TR>
  <TD><IMG SRC="qrc:/edit_remove.png"></TD>
  <TD>Remove the currently selected universe.<br>
      <B>Please be careful with this operation as it can compromise your project and cannot be reverted.</B><br>
      When deleting a universe, if it is currently patched or some fixtures are mapped
      on it, a popup message will appear asking for confirmation if the operation should
      be completed or abandoned.
  </TD>
 </TR>
 <TR>
  <TD><B>Universe name</B></TD>
  <TD>An arbitrary string that you can set to quickly identify the meaning of a Universe</TD>
 </TR>
 <TR>
  <TD><B>Passthrough</B></TD>
  <TD>See <a href="#passthrough">below</a></TD>
 </TR>
</TABLE>

<H2 id="patching">Patching</H2>

<P>
To patch a plugin's input/output line to the selected universe, you need to place
a checkmark on that particular plugin's input/output line. You can have only one
line assigned to a universe at a time, so when you check another line, the
checkmark will <u>move</u> from its previous position to the one you just checked.<br>
If you don't see any line on a plugin, it means you don't have any device that QLC+
understands and you're left with the one and only (non-selectable) choice: <u>None</u>.
</P>

<P>
When an input/output line is checked, the corresponding universe information on the left hand side of the screen
will change and will display the new configuration set.<br>
The plugin information on the bottom right hand side of the screen will change as well and will give
you the new status of the plugin line.
</P>

<H2 id="passthrough">Universe Passthrough</H2>

<P>
When passthrough is enabled, universe just forwards what it receives in its input line to its output line.
This is useful for several things:
<UL>
<LI><B>Protocol converter</B>: when you want to use QLC+ to act as a
    "protocol" converter. For example you can use this feature to
    transparently map an ArtNet network to a DMX USB adapter or even MIDI.
</LI>
<LI><B>Monitor external data</B>: patch fixtures and watch the data in DMX
    monitor
</LI>
<LI><B>Merge data from external controller</B>: Have external lighting desk
    control some of the channels independently (for example conventionals)
    and QLC+ control intelligent lights on the same universe.</LI>
<LI><B>Raspberry Pi</B>: forward data from QLC+ on PC while programming scenes;
    when the workspace is transferred, Raspberry becomes main controller; the
    devices are always connected to RPi</LI>
</UL>

<P>Passthrough data is not affected by QLC+ grandmaster or channel modifiers.
   It is merged in HTP fashion with QLC+ output if there are any fixtures
   patched at that channel (Note: it does not use LTP/HTP channel settings).
   Blackout affects passthrough data.
</P>

<H2 id="input-and-feedback">Input and Feedbacks</H2>

<P>
When a plugin input line is checked, it gets enabled right away, so you can perform a basic test
to double check if your hardware is working properly with QLC+.<br>
Just move a fader/knob on your external device, and if everything works fine, you will see a
<IMG SRC="qrc:/input.png" width=32> icon appearing beside the corresponding universe
on the left side of the screen.
</P>

<P>
If your input device supports a return channel, QLC+ can send a visual/mechanical feedback
to it. Devices such as Behringer BCF2000 support this feature.<br>
At the moment feedbacks are supported only through MIDI, OSC and loopback.
</P>

<P>
To learn how to setup your external input device for the best use with QLC+, please
continue your reading with the <A HREF="howto-input-profiles.html">howto for input profiles</A>.
</P>

</BODY>
</HTML>