File: audiotriggers.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 (111 lines) | stat: -rw-r--r-- 5,130 bytes parent folder | download | duplicates (4)
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
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<HTML>
<HEAD>
<TITLE>Q Light Controller Plus - Audio Triggers</TITLE>
<SCRIPT SRC="utility.js" TYPE="text/javascript"></SCRIPT>
<link href="style.css" rel="stylesheet" type="text/css" />
</HEAD>
<BODY onLoad="replaceqrc()">

<H1><img src="qrc:/audioinput.png" ALIGN="absmiddle"> Virtual Console Audio Triggers</H1>
<P>
Starting from QLC+ version 4.4.0, this functionality allows you to use an audio input
source such as a microphone, to add more life to your light shows.<br>

<H2>Introduction</H2>

When clicking on the <img src="qrc:/audioinput.png"> icon, an audio trigger widget will be
added to your Virtual Console.<br>
The widget's graphics area shows live monitoring of the captured audio, displaying
a number of spectrum bars and a volume bar.<br>
On the bottom you can see the range of frequencies analyzed by QLC+<br>

<H2>Configuration</H2>

When double clicking on the widget in design mode, a panel is displayed showing a complete set of options
to tune the audio trigger's functionality.<br>
The first thing you can configure is the number of spectrum bars that you want to display and that you
will need during your live show. The number accepted is between 5 and 32.<br>
Once the number of bars has been decided, you can proceed to assign a functionality to each bar. There is a list
showing the following options for the volume and spectrum bars:<br><br>

<TABLE BORDER=1 class="qlcTable">
 <TR>
  <TD><B>Name</B></TD>
  <TD>Can be "Volume Bar" or a spectrum bar shown as #number (start frequency - end frequency). Example: #5 (1250Hz - 1562Hz)></TD>
 </TR>
 <TR>
  <TD><B>Type</B></TD>
  <TD>Indicates the type of functionality the bar will control. It can be:
     <UL>
      <LI><img src="qrc:/uncheck.png"> None - No functionality assigned</LI>
      <LI><img src="qrc:/intensity.png"> DMX - Controls single DMX channels</LI>
      <LI><img src="qrc:/function.png"> Function - Controls a QLC+ function</LI>
      <LI><img src="qrc:/virtualconsole.png"> VC Widget - Controls a Virtual Console widget (at the moment only buttons, sliders, tapping of speed dials and next cue of cue lists)</LI>
     </UL>
  </TD>
 </TR>
 <TR>
  <TD><B>Assign</B></TD>
  <TD>When a type is selected, a button with a <img src="qrc:/attach.png"> icon is displayed to allow
  you to connect the bar to the desired functionality. Depending on which type you chose, clicking on
  this button will display the DMX channels, Functions or Virtual Console widgets selection dialogs.
  </TD>
 </TR>
 <TR>
  <TD><B>Info</B></TD>
  <TD>This column displays some additional information about the bar--functionality association.<br>
  Depending on the type you chose, you will find the number of DMX channels, the function name or
  the VC Widget name selected displayed here</TD>
 </TR>
 <TR>
  <TD><B>Disable threshold</B></TD>
  <TD>When selecting a Function or a VC Widget button, this column allows you to set a deactivation
  threshold percentage. When the spectrum or volume bar goes below this value, the associated function/VC button
  will be stopped/deactivated.</TD>
 </TR>
 <TR>
  <TD><B>Enable threshold</B></TD>
  <TD>When selecting a Function or a VC Widget button, this column allows you to set an activation
  threshold percentage. When the spectrum or volume bar goes above this value, the associated function/VC button
  will be started/activated.</TD>
 </TR>
 <TR>
  <TD><B>Divisor</B></TD>
  <TD>For speed dials and cue lists, this will divide the taps by the selected number - only every n-th tap
  will be actually sent to the speed dial. In other words, the tap happens only on every n-th beat. If you want
  the tap on every beat, enter 1, for every other beat enter 2. For once in a 4/4 measure, enter 4. For once in
  3 4/4 measures, enter 12. Maximum is 64.
  </TD>
 </TR>
</TABLE>
</P>

<H3>DMX channels</H3>
<P>You can choose one or more channels of the currently patched fixtures. Those channels will be set proportionally
to total volume, or volume in a particular frequency band.
</P>

<H3>Functions</H3>
<P>You can select one or more functions. Those functions are started when volume goes above the
Enable threshold in respective band, and stopped when it goes below the Disable threshold.
</P>

<H3>VC Widgets</H3>
<P>You can select only <B>ONE</B> widget here, either a button, a slider or a speed dial. Depending on the type:
<UL>
<LI><B>Button</B> is pressed when volume goes above Enable threshold, and released when the volume is
below Disable threshold (similar to functions).</LI>
<LI><B>Slider</B> is moved in proportion to the volume (similar to DMX channels). For a slider
the thresholds do not apply.</LI>
<LI><B>Speed dial</B> is tapped.</LI>
<LI><B>Cue List</B> "Next Cue" is pressed.</LI>
</UL>
</P>

<P>
For <B>Speed dials</B> and <B>Cue Lists</B>, the tap/button press happens when the volume goes above the Enable
threshold, and won't happen again until the volume falls below the Disable threshold. This probably means you
will have to set the thresholds a little closer to each other than for buttons.</P>
</BODY>
</HTML>