See below the reply from Anne regarding updating vs recording.
Update and Record Only can be used for similar purposes, with some key differences.
Update will take any
manual values and store them back to their playback source. So in the example of only one
cue on
stage, [Update] [Enter] would store any changes back to the active
cue. This would also include any
manual values that were new information for the
cue list (i.e, a
channel that had never been used would be added to the active
cue). If that
cue contains referenced data (palettes or presets), [Update] [Enter] actually modifies the palettes/presets that were used to create the
cue in the first place. This is where you will see an "R" in red superscript next to a
parameter. This is a visual clue that you have overridden a stored reference. If you don't want to update the reference, you can enter: [Update] [Make Absolute] [Enter]. This converts the referenced data overrides to absolute data. We are going to be extending that functionality to a dialogue box in the near future, so that if you always want to update the
cue but break the referenced data, that can easily become the default behavior.
If there are multiple cues/submasters on
stage, [Update] [Enter] will update
manual values back to their source. So if
channel 1
intensity was owned by
Submaster 1,
channel 1 color was owned by
Cue 1/1 and its focus was owned by
Cue 2/1. You manually modify
channel 1
intensity, color and focus, [Update] [Enter] would store the new
intensity value to Sub 1, the new color data to
Cue 1/1 and the new focus data to
Cue 2/1.
You can only update to an existing record target. You can't use update to create new record targets. You can also use update in conjuction with the
trace command (update the value and
track that change back through the
cue list to the source of the move instruction).
[Record Only] is similar - but different. There are two basic record actions. The first is [Record]. The logic of [Record] is that any channels that are not at their home position (default) and every
parameter of those channels will be included in the record activity. So let's say
channel 1 is at its home position, and you set
channel 1 to full, set it to Focus
Palette 12, don't touch its color or beam parameters (because you want them at their default values). If you press [Record]
[Enter] - all of the parameters of
channel 1 are included in the record action (the entire state of the light, no matter how it got there). Record does not care where the data is coming from; it can be
manual, from a
submaster, from a
cue. Doesn't matter - unless you selective store ([-] [1] [Record], for example) or use filters, ANY
channel not at default will be stored.
The advantage of [Record] is that you don't need to touch every
parameter of the light to make sure that the entire state of that light is going to be stored in the
cue.
[Record Only], on the other
hand, only stores
manual values. When you are working in a single
cue list, because
Eos is a
tracking console, it doesn't really matter that much. In a single
cue list environment, [Record Only] is a handy way to modify a
cue and break the references at the same time. [Record Only] [Enter] yeilds the same result as [Update] [Make Absolute] [Enter].
[Record Only] is a powerful tool when working with multiple
cue lists. So lets say you are working from you main
cue list, and you decide at some
stage that you want to create a little color sequence on a secondary
cue list. You can just set the color values and enter [Record Only] [2] [/] [1] [Enter] (for example). This will store just the
manual color values to the secondary
cue list. So you don't have to use selective storing (channels 1 through 5 color record only 2/1) to get that little color look off on another
cue list - and you don't have to use filters?
Does this make sense? If not, let me know. I'm curious about what kind of problems you are running into. Please feel free to elaborate here - because others might be having similar issues) or I'll give you a
call when I'm back in the office on Friday?
Thanks much!
Anne
