ControlBooth
 

Go Back   ControlBooth > CB Wiki > Glossarys

Notices

 
 
LinkBack Article Tools Display Modes
  #1  

Default Cue Tracking

Please note that the title was changed from "Tracking" to "Cue Tracking" in order to make this a more focused topic.

[top]Overview


Tracking, when used and understood, makes a world of sense, particularly for moving lights. In 1975, when Tharon Musser and others were consulting with Century-Strand on the development of the Light Palette, they said they wanted a console that thought like a Lighting Designer thought. On a Piano Board, when you put a Dimmer at say 50% in a cue, the handle stays there until a different cue says to change it, regardless of how many cues there are between. So if in Q1 you bring the blue cyc up to 50% and it says that way until intermission, Q99. Cues2-98 do other things, but never affect the cyc. Then the director tells you he/she wants the cyc red during the first act. So in Q1 you record the "blue cyc" at zero and the "red cyc" at 50%. Make sure that Q99 takes the "red cyc" to 0%. No need to change anything about cues 2-98. Almost all console displays use colors to differentiate between a Channel that has tracked from a previous cue and a channel that moves in the current cue. (I don't know Strand's code). Also, for blackouts and other major cues, it's a good idea to insert a "blocking" cue (Colortran used to call this a "clean-up" cue, Express(ion) calls this an "AllFade). This is a cue that inserts a "hard value" for every channel, and thus stops all tracking. A similar outcome, for one time use, can be achieved using "record Q-only."
The best explanation of tracking, especially for moving lights, I have found is in The Automated Lighting Programmer's Handbook, Brad Schiller. Focal Press, 2004. One more thing: don't get tracking confused with HTP and LTP, they are similar, but different concepts.
There was an excellent article on the topic published in PLSN which you can read here.

[top]Example


For the following example I am using Strand's channel color scheme: Purple are channels moving up, cyan are channels that have tracked, and green are channels going down. This means that channels in cyan do not have commands on them.

Also, lets assume that channel 2 controls a special, channel 3 controls a cyc, and 1 and 4 are area lights (It is totally arbitrary). Lets assume that the cues listed comprise one scene, that ends in a blackout (Q6).

Cue NumberChan1Chan2Chan3Chan4
Q150 10FL
Q250FL10FL
Q350010FL
Q475 1065
Q50 100
Q6 0

So, say the LD wants the cyc brighter for this scene, he can just tell the channel 3 to be at 20 in cue 1 and it would track through the scene. Like this:

Cue NumberChan1Chan2Chan3Chan4
Q150 20FL
Q250FL20FL
Q350020FL
Q475 2065
Q50 200
Q6 0

Then maybe the LD needs channel 1 to be dimmer in cues 2 and 3. Since this is a tracking console the LD need only change the level in cue 2 as it will track into cue 3. It won't effect cue 4 though because channel 1 has a command in cue 4. Like this:

Cue NumberChan1Chan2Chan3Chan4
Q150 20FL
Q240FL20FL
Q340020FL
Q475 2065
Q50 200
Q6 0

Now the LD needs the special to come back to full in cue 5:

Cue NumberChan1Chan2Chan3Chan4
Q150 20FL
Q240FL20FL
Q340020FL
Q475 2065
Q50FL200
Q6 FL0

Uh-oh, looks like that special tracked into our blackout! This is where Block Cues come in handy. The trick is that if you make a cue into a block cue after channels have tracked into it, those channels will still be in it, but no new ones will track in. This is why it is good practice to lay in your black out cues as early as possible and make them block cues. For the next example we are going to assume that Q6 was a block cue before we changed the special (indicated by a "*BL*" for this example).

Cue NumberChan1Chan2Chan3Chan4
Q150 20FL
Q240FL20FL
Q340020FL
Q475 2065
Q50FL200
Q6 *BL*0000

The block on cue 6 forces a hard command on each channel. If the director changed his mind and wanted a silhouette instead of a blackout the LD might keep the cyc lit, so it would look like this:

Cue NumberChan1Chan2Chan3Chan4
Q150 20FL
Q240FL20FL
Q340020FL
Q475 2065
Q50FL200
Q6 *BL*00200
In this case the channel 3's level appears in white because even though it was riding at 20, it was now told to be there again in Q6. In Strand land this would still show up as Cyan, but for the purposes of the example, it shows there is a hard command on the channel.


Contributors: jmabray, gafftaper, icewolf08
Created by derekleffew, December 22nd, 2007 at 04:48 PM
Last edited by derekleffew, February 4th, 2008 at 12:39 PM
0 Comments , 683 Views
 

Tags
cue, tracking

Article Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On

Similar Threads
Thread Thread Starter Forum Replies Last Post
Tracking where a panel goes Dustincoc Sound 14 October 4th, 2007 07:45 PM
Gobo Inventory Tracking icewolf08 Get Organized! 19 February 1st, 2007 05:00 PM
strand 520i - Q tracking question azscanner Lighting 5 December 23rd, 2004 02:36 AM
Inventory Smatticus Get Organized! 11 May 27th, 2004 02:43 AM


All times are UTC -4. The time now is 03:40 AM.


Powered by vBulletin® Version 3.7.4
Copyright ©2000 - 2008, Jelsoft Enterprises Ltd.
Search Engine Friendly URLs by vBSEO 3.2.0
Powered by NuWiki v1.3 RC1 Copyright ©2006-2007, NuHit, LLC
Advertisement System V2.5 By   Branden

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