[Record Only] Help

Question

The manual tells me this can be use to create a new cue list. (We only ever use one cue list - I ma not even sure why one would use multiple cue lists, maybe because we only run linear plays) And, it will save only 'manual' values. I'm a bit hazy over the whole issue. If I have a cue that has some refocused MLs and a color change, will [Record Only] save just my color changes? When would I use [Record Only] as opposed to [Record}? Some examples would be appreciated and a comparison of manual and none manual data would help put this one away.

sktusing · Answer

I use multiple lists to separate out parts of my rig, and to do different things: 
 
 Main Show List 
 MIDI/OSC Cue Triggers 
 Haze 
 Followspots 
 ML Checkout 
 Conv Checkout 
 MIDI Checkout 
 SMPTE Checkout 
 
 Are some of the things that I use multiple lists for. In the case of the MIDI/OSC cue triggers, when I am interfacing with another product (d3 video servers) it is easier to put those triggers in a different list so that I can see exactly what information I am sending to them. 
 I use the Haze list so that I don't see the haze effect number in every cue in my main list. 
 The followspots are in their own list so that the ALD in charge of them can see what those lights are doing - and so that they don't interact with the main list. 
 
 Checkouts are all split up so that multiple people can run checkout at the same time - we can have someone on the console, and two poeple on iPads checking things all at the same time. 
 
 Sometimes if I need a specific effect to run in a super specific manner I will split that out into its own list so that I have more control over it. This happens less and less with each update to the effects engine however... 
 
 There are a lot of ways for multiple lists to be helpful - it's not necessarily about how the show plays back, but also about how multiple lists can speed up the overall flow of the show.

[Record Only] Help

Top Replies