<commit_before><!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<HTML>
<HEAD>
<TITLE>Q Light Controller Plus - Show Manager</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:/show.png" ALIGN="absmiddle"> Show Manager</H1>
<P>
The Show Manager has been introduced in QLC+ starting from version 4.0.0, after forking the original
QLC code on November 5th, 2012.<br>
<br>
This feature is meant to give users the possibility of setting up a time driven show in a friendly and
completely graphical way.<br>
The graphic interface shows a multitrack view, typical of audio sequencers or video editing softwares,
and with it users are allowed to place QLC+ <A HREF="file:concept.html#Functions">Functions</A> at the desired
place and time in the view.<br>
Show Manager gives a lot of flexibility during a <A HREF="file:concept.html#Show">Show</a> creation thanks 
to its visual-oriented approach. Once understood the basic elements, it is very easy to create, move or edit 
the existing functions and improve a Show by adding new tracks to it.<br>
<br>
Typical use cases of Shows are those gigs where a band plays songs following a metronome and the light show has
always to be the same, following the music.<br>
Another case are visual entertainment shows, where dancers or singers follow some music and lights create
the atmosphere at the right time.<br>
<br>
The Show Manager drives users to make large use of the Sequence function. Here's the explanation
of the difference between a Chaser and a Sequence.<br>
</P>

<H2>Sequences vs Chasers</H2>
<P>
Even if the <A HREF="file:concept.html#Sequence">Sequence</a> and the 
<A HREF="file:concept.html#Chaser">Chaser</a> functions have a common ground, they're not the same thing.<br>
If not done yet, you are invited to read once again their definition in the 
<A HREF="file:concept.html">Basic Concepts &amp; Glossary</a> page of this documentation.<br>
The main differences are:
<ul>
 <li><b>Steps</b>: The steps of a Chaser can represent any QLC+ Function, while the steps
        of a Sequence represents different values of the same <A HREF="file:concept.html#Scene">Scene</a>.<br>
        In other words, a Chaser is an indipendent function, while a Sequence can exist only
        on top of a Scene.<br>
        The reason for this is, as mentioned before, the visual approach of the Show Manager.
        If a track of a Show is the graphical representation of a Scene, then it's more intuitive 
        to think that each Sequence created on that track is a function controlling the values of that Scene.
 </li>
 <li><b>Order</b>: Chasers can be reproduced in any order (Forward, Backward, Ping-Pong, Random) while
        Sequences are always reproduced from the beginning to the end (Forward).
        Again, this is related to the visual aspect of the Show Manager, where the playback
        has a natural time forward direction.
 </li>
 <li><b>Editing</b>: The editing approach between Sequences and Chaser is different too.<br>
        Normally the workflow of a Chaser is: create a Function, then add it to the Chaser as a step.<br>
        The workflow of a Sequence is: create a Scene, create a Sequence on top of it, add steps to it.<br>
        The Sequence approach might be very effective when you design a light show if you can pre-determine
        which fixtures you're going to use. A major burst on Sequence editing is also
        that when you create a new step, the values of the previous step are copied in the new one.
        So the user is basically required to adjust the differences between them.<br>
        If you are going to create 500 steps and they're all different, then Sequences and Chasers
        will take almost the same time to be created.<br>
 </li>
 <li><b>Synchronization</b>: another major advantage of using Sequences in a Show is that a Show
        can easily be extended (or reduced) while with a Chaser you will have a hard time to
        synchronize the new functions to the existing ones.<br>
        An example. Let's say your project controls 50 fixtures mixed of moving heads, PARs and scanners.
        At some point you buy a couple of lasers and you want them to activate on existing scenes
        at very precise moments in time. The Show Manager allows you to do that in a few minutes !
        You just need to add the 2 new fixtures to the project, add a track to the Shows interested
        in the change and create a few Sequences to control the lasers.<br>
        The Show Manager resume functionality will also save you a lot of time when testing the new
        changes.<br>
        With Chasers you'd probably have to deal with complex <A HREF="file:concept.html#Collection">Collections</a>
        and review the timings of a few steps before finding the right combination.
</ul>
</P>

<H2>Show Manager toolbar controls</H2>

<TABLE BORDER=1 class="qlcTable">
 <TR>
  <TD><IMG SRC="qrc:/show.png"/></TD>
  <TD>Create a new <A HREF="file:concept.html#Show">Show</A>. A Show is represented as a multitrack
  workspace where tracks, sequences and audio elements can be added</TD>
 </TR>
 <TR></TR>
 <TR><commit_msg>Documentation: updated Show Manager doc (thank to <NAME>)<commit_after><!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<HTML>
<HEAD>
<TITLE>Q Light Controller Plus - Show Manager</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:/show.png" ALIGN="absmiddle"> Show Manager</H1>
<P>
The Show Manager has been introduced in QLC+ starting from version 4.0.0, after forking the original
QLC code on November 5th, 2012.<br>
<br>
This feature is meant to give users the possibility of setting up a time driven show in a friendly and
completely graphical way.<br>
The graphic interface shows a multitrack view, typical of audio sequencers or video editing softwares,
and with it users are allowed to place QLC+ <A HREF="file:concept.html#Functions">Functions</A> at the desired
place and time in the view.<br>
Show Manager gives a lot of flexibility during a <A HREF="file:concept.html#Show">Show</a> creation thanks 
to its visual-oriented approach. Once understood the basic elements, it is very easy to create, move or edit 
the existing functions and improve a Show by adding new tracks to it.<br>
<br>
Typical use cases of Shows are those gigs where a band plays songs following a metronome and the light show has
always to be the same, following the music.<br>
Another case are visual entertainment shows, where dancers or singers follow some music and lights create
the atmosphere at the right time.<br>
<br>
The Show Manager drives users to make large use of the Sequence function. Here's the explanation
of the difference between a Chaser and a Sequence.<br>
</P>

<H2>Sequences vs Chasers</H2>
<P>
Even if the <A HREF="file:concept.html#Sequence">Sequence</a> and the 
<A HREF="file:concept.html#Chaser">Chaser</a> functions have some common ground, they're not the same thing.<br>
If not done yet, you are invited to read once again their definitions in the 
<A HREF="file:concept.html">Basic Concepts &amp; Glossary</a> page of this documentation.<br>
The main differences are:
<ul>
 <li><b>Steps</b>: The steps of a Chaser can represent any QLC+ Function, while the steps
        of a Sequence represents different values of the same <A HREF="file:concept.html#Scene">Scene</a>.<br>
        In other words, a Chaser is an independent function, while a Sequence can exist only
        on top of a Scene.<br>
        The reason for this is, as mentioned before, the visual approach of the Show Manager.
        If a track of a Show is the graphical representation of a Scene, then it's more intuitive 
        to think that each Sequence created on that track is a function controlling the values of that Scene.
 </li>
 <li><b>Order</b>: Chasers can be reproduced in any order (Forward, Backward, Ping-Pong, Random) while
        in the Show Manager, Sequences are always reproduced from the beginning to the end (Forward).
        Again, this is related to the visual aspect of the Show Manager, where the playback
        has a natural time forward direction.<br>
        On the other hand, Sequences created with the Function Manager can have the 
        same order properties of Chasers.
 </li>
 <li><b>Editing</b>: The editing approach between Sequences and Chaser is different too.<br>
        Normally the workflow of a Chaser is: create a Function, then add it to the Chaser as a step.<br>
        The workflow of a Sequence is: create a Scene, create a Sequence on top of it, add steps to it.<br>
        The Sequence approach might be very effective when you design a light show if you can pre-determine
        which fixtures you're going to use. Another major advantage of Sequence editing is
        that when you create a new step, the values of the previous step are copied in the new one.
        So the user is simply required to adjust the differences between them.<br>
        If you are going to create 500 steps and they're all different, then Sequences and Chasers
        will take almost the same time to be created.<br>
 </li>
 <li><b>Synchronization</b>: another major advantage of using Sequences in a Show is that a Show
        can easily be extended (or reduced) while with a Chaser you will have a hard time to
        synchronize the new functions to the existing ones.<br>
        An example. Let's say your project controls 50 fixtures that are a mixture of moving heads, PARs and scanners.
        At some point you buy a couple of lasers and you want them to become active in existing scenes
        at precise moments in time. The Show Manager allows you to do that in a few minutes !
        You just need to add the 2 new fixtures to the project, add a track to the Shows affected by
        the change and create a few Sequences to control the lasers.<br>
        The Show Manager resume functionality will also save you a lot of time when testing the new
        changes.<br>
        With Chasers you'd probably have to deal with complex <A HREF="file:concept.html#Collection">Collections</a>
        and review the timings of a few steps before finding the right combination.
</ul>
</P>

<H2>Show Manager toolbar controls</H2>

<TABLE BORDER=1 class="qlcTable">
 <TR>
  <TD><IMG SRC="qrc:/show.png"/></TD>
  <TD>Create a new <A HREF="file:concept.html#Show">Show</A>. A Show is represented as a multitrack
  workspace where tracks, sequences and audio elements can be added</TD>
 </TR>
 <TR></TR>
 <TR>
{'fraction_non_alphanumeric': 0.0753456435000464, 'fraction_numerical': 0.004639510067736847, 'mean_word_length': 3.7396657871591907, 'pattern_counts': {'":': 0, '<': 179, '<?xml version=': 0, '>': 179, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '4400843', 'n_tokens_mistral': 3022, 'n_tokens_neox': 2846, 'n_words': 1566}