File: questionsandanswers.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 (151 lines) | stat: -rw-r--r-- 6,807 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
149
150
151
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<HTML>
<HEAD>
<TITLE>Q Light Controller Plus - Questions &amp; Answers</TITLE>
<SCRIPT SRC="utility.js" TYPE="text/javascript"></SCRIPT>
<link href="style.css" rel="stylesheet" type="text/css" />
</HEAD>
<BODY onLoad="replaceqrc()">

<H1>Questions &amp; Answers</H1>

In this page you will find the common questions that may come to mind when starting with QLC+.<BR>
Here you can either find the answer directly or find help to point you in the right direction.<BR><BR>

<TABLE BORDER=1 class="qlcTable">
 <TR>
  <TD><SPAN>1</SPAN></TD>
  <TD><SPAN id="not-detected">Q:</SPAN></TD>
  <TD>QLC+ cannot detect my USB device</TD>
 </TR>
 <TR>
  <TD></TD>
  <TD><SPAN>A:</SPAN></TD>
  <TD>QLC+ supports a wide variety of USB devices. First of all you should check if the physical connection
      is OK. Usually a LED on your device should indicate if it is powered up and working correctly.<BR>
      If you are using Windows and your device is manufactured by Peperoni or Velleman, please read the information on how to get
      them working on these help pages. For licensing issues they both need an extra DLL file to work.
      Please check <A HREF="peperonioutput.html">Peperoni output plugin</A> or <A HREF="vellemanoutput.html">Velleman output plugin</A><BR>
      If you're using Linux, please check if your distribution detected the device when plugged in. Basically, the
      "<CODE>dmesg</CODE>" command should tell you something.
  </TD>
 </TR>
</TABLE>
<BR>
<TABLE BORDER=1 class="qlcTable">
 <TR>
  <TD><SPAN>2</SPAN></TD>
  <TD><SPAN id="solo-frame">Q:</SPAN></TD>
  <TD>I've got several <A HREF="vcbutton.html">buttons</A> in my Virtual Console. I need a way to disable the currently
      active button when I enable another one. How do I do that?
  </TD>
 </TR>
 <TR>
  <TD></TD>
  <TD><SPAN>A:</SPAN></TD>
  <TD>Simply place your buttons inside a <A HREF="vcsoloframe.html">Solo Frame</A>. It does exactly that.</TD>
 </TR>
</TABLE>
<BR>
<TABLE BORDER=1 class="qlcTable">
 <TR>
  <TD><SPAN>3</SPAN></TD>
  <TD><SPAN id="osx-mavericks">Q:</SPAN></TD>
  <TD>I just upgraded my Mac to Mavericks (or later) and my USB DMX adapter doesn't transmit any data.</TD>
 </TR>
 <TR>
  <TD></TD>
  <TD><SPAN>A:</SPAN></TD>
  <TD>The problem is in an Apple driver called AppleUSBFTDI, which takes control of every FTDI based device detected in the system.<br>
      There are a few ways to solve the problem, but basically the result is the same: the Apple driver must be disabled.<br><br>
      Please check the dedicated page to understand how to <a href="disable_apple_ftdi_driver.html">disable the Apple FTDI driver</A><br>
      Otherwise, you can download the <A HREF="https://www.dmxis.com/release/FtdiDriverControl.zip">ENTTEC FTDI Driver Control tool</A>
      and try to enable/disable the Apple driver with it.<BR><BR>

      <B>Note 1: this can compromise the behaviour of other USB devices, so do it only
      if you know what you're doing! </B><br>
      <B>Note 2: every time Mac OS receives an update, you need to perform this procedure again!</B><br>
      <B>Note 3: Most likely, when you disable/enable the Apple driver, you need to reboot your Mac</B>
  </TD>
 </TR>
</TABLE>
<BR>
<TABLE BORDER=1 class="qlcTable">
 <TR>
  <TD><SPAN>4</SPAN></TD>
  <TD><SPAN id="user-folder">Q:</SPAN></TD>
  <TD>Where is the QLC+ user folder located in my system?</TD>
 </TR>
 <TR>
  <TD></TD>
  <TD><SPAN>A:</SPAN></TD>
  <TD>The user folder is where user fixtures, input profiles, RGB scripts and MIDI templates go.<br>
      It changes depending on your operating system:<br>
      <B>Linux</B>: it is a hidden folder in your user home directory: $HOME/.qlcplus<br>
      <B>Windows</B>: it is a folder in your user (e.g. MyUser) directory: C:\Users\MyUser\QLC+<br>
      <B>Mac OS</B>: it is located in your user "Library" directory: $HOME/Library/Application\ Support/QLC+<br>
      You can reach any of these folders from a terminal with the 'cd' command. For example:<br>
      <PRE>cd $HOME/Library/Application\ Support/QLC+</PRE>
      Please keep in mind that fixures and input profiles found in the user folder will have precedence
      over the same files in the QLC+ system folder.<br>
  </TD>
 </TR>
</TABLE>
<BR>
<TABLE BORDER=1 class="qlcTable">
 <TR>
  <TD><SPAN>5</SPAN></TD>
  <TD><SPAN id="system-folder">Q:</SPAN></TD>
  <TD>Where is the QLC+ system folder located in my system?</TD>
 </TR>
 <TR>
  <TD></TD>
  <TD><SPAN>A:</SPAN></TD>
  <TD>The system folder is where QLC+ resources (fixtures, input profiles, RGB scripts, etc) are installed
      and it changes depending on your operating system:<br>
      <B>Linux</B>: it's a fixed folder named /usr/share/qlcplus<br>
      <B>Windows</B>: it is the folder where you actually installed QLC+. By default: C:\QLC+<br>
      <B>Mac OS</B>: it is a folder inside the QLC+ bundle (.app file). It is possible to browse the QLC+.app bundle contents simply with Finder.
      Just right click on the file and select "Show Package Contents".<br>
      Otherwise, the system folder can be reached with a terminal but it depends on where you installed QLC+.<br>
      For example if you dragged QLC+ into Applications it will be: /Applications/QLC+.app/Contents/Resources
  </TD>
 </TR>
</TABLE>
<BR>
<TABLE BORDER=1 class="qlcTable">
 <TR>
  <TD><SPAN>6</SPAN></TD>
  <TD><SPAN id="windows-video">Q:</SPAN></TD>
  <TD>QLC+ cannot play some videos on Windows</TD>
 </TR>
 <TR>
  <TD></TD>
  <TD><SPAN>A:</SPAN></TD>
  <TD>QLC+ relies on the Qt libraries which relies on the DirectShow filters installed in the system.<BR>
      Unfortunately the basic codecs supported by Windows are quite poor, so you need to install some extra
      codecs package like K-Lite, <A HREF="https://www.codecguide.com/download_kl.htm">available here</A>.
  </TD>
 </TR>
</TABLE>
<BR>
<TABLE BORDER=1 class="qlcTable">
 <TR>
  <TD><SPAN>7</SPAN></TD>
  <TD><SPAN id="hidpi-display">Q:</SPAN></TD>
  <TD>I have a 4k display and everything in the QLC+ interface is extremely small</TD>
 </TR>
 <TR>
  <TD></TD>
  <TD><SPAN>A:</SPAN></TD>
  <TD>You need to add an option to the QLC+ command line to tell the Qt libraries to autoscale
      the interface on a High DPI display. Examples:<br>
      <PRE><b>Linux (from terminal)</b>: QT_AUTO_SCREEN_SCALE_FACTOR=1 qlcplus</PRE>
      <PRE><b>Windows shortcut</b>: C:\Windows\System32\cmd.exe /c "SET QT_AUTO_SCREEN_SCALE_FACTOR=1 && START /D ^"C:\QLC+^" qlcplus.exe"</PRE>
      <PRE><b>Mac OS (from terminal)</b>: QT_AUTO_SCREEN_SCALE_FACTOR=1 QLC+.app\Contents\MacOS\qlcplus</PRE>
      In case, see the <A HREF="commandlineparameters.html">command line parameters page</a> for further information.
  </TD>
 </TR>
</TABLE>
</BODY>
</HTML>