Coming from Obsession world, I used [update] frequently.
On Eos I have run into some trouble using [update] to modify cues.
Currently, I use update to modify groups, palettes & presets. I use [record only] to modify cues.
What is the difference between [update] & [record only]?
thanks, Kathy
Anne,
I come from an Obsession II and Hog background. My experience with those consoles tell me that I should make any changes to ml parameters and then update the corresponding pallette (focus preset). Will update on EOS offer this option? Changes to intensity or timing or other conventional channels I would treat the same as I would in Obs II and then either update or record cue only or record to track. Do I need to change my approach to this?
Thanks.
Ok, can I add a fourth and ever confusing one?
Ch1 at full in Q1 references Preset 3 for color, beam and focus data... i grab ch1 and change to color 4, how can I hit update and get the new color parameter to be updated into preset 3? This becomes every more detailed when Ch1 is referencing Preset 1, Ch2 is referencing Preset 2, etc etc
Ideally i want to hit "update preset" enter and have the Ch's know there source presets and then update the presets with whatever value Ive given, be it a pallet or a manual change.
Thoughts?
To ask another question raised from this: I usually work in Cue only mode for our events only because when I'm designing it's usually with more than 4 pieces in one show, and I don't want to risk the tracking from a modern piece into a ballet. In Cue only mode, does update still update the references, or does it just update the cue I'm in?
is the console, in my case the Ion, still "tracking" smartly in cue only mode, but does not in effect track values?
Presets and Palettes are 'referenced' data, and nothing to do with tracking or Cue Only.
A Colour Palette is simply "This is how we make Blue" - if the Blue needs to be adjusted later, you edit the one Blue Palette and all the places it's used are automatically updated.
This same idea is applied to other palettes - A Focus Palette could be 'This is how to point at the tree', and if the director/set deisgner moves the tree you change the one Focus Palette and that updates every cue where any of the lights in that palette were aimed at the tree using that palette.
Tracking on the other hand is to do with recording and executing 'Only the things that change' - if there is no new value an attribute in the new cue, the console just leaves it alone.
In Cue Only mode, every channel is forced into the target value - one could say that 'Everything changes', even if the 'new' value is the same as the 'old' value.
A Blocking cue is a cue that again says "Everything changes" - Partial Blocking is 'These things changed'
A couple of thoughts for you - if you have multiple pieces, you could:
Record each dance number into a separate cue list or
Block the first cue of each dance piece. Blocking the cue will prevent any changes from cues "upstream" from tracking into to the start of each piece. This allows you to use tracking within the dance number safely.... which is often much, much faster than managing your cues in cue only mode.
As Richard says, when you are in Cue Only mode, this only effects how changes to cues should move forward through the cue list.
If you are using referenced data, Updating this cue will, by default, also update the reference. When you modify (for example) a focus palette, you'll notice a red "R" in superscript for those parameters. This tells you that you have overridden a reference. When you update, those changes are stored back to the source, which was the palette or preset in the cue. When you update, a dialogue box opens in the CIA. One of the buttons is "Make Absolute." If you [Update] [Make Absolute] [Enter] - you will store your changes to your cue, but break the link to the reference itself. Once you have set that update style, the desk remembers it whenever you use update.
I'd recommend to you that you play around with this in blind spreadsheet, to see how edits to cues impacts your show data. While we never try to force anyone to use tracking, once you understand how tracking will work, and how the desk can protect your show data for you, it is a much more efficient way to work.
The effect issue that you bring up is addressed in the upcoming 1.5.
Hope this helps.
a
A couple of thoughts for you - if you have multiple pieces, you could:
Record each dance number into a separate cue list or
Block the first cue of each dance piece. Blocking the cue will prevent any changes from cues "upstream" from tracking into to the start of each piece. This allows you to use tracking within the dance number safely.... which is often much, much faster than managing your cues in cue only mode.
As Richard says, when you are in Cue Only mode, this only effects how changes to cues should move forward through the cue list.
If you are using referenced data, Updating this cue will, by default, also update the reference. When you modify (for example) a focus palette, you'll notice a red "R" in superscript for those parameters. This tells you that you have overridden a reference. When you update, those changes are stored back to the source, which was the palette or preset in the cue. When you update, a dialogue box opens in the CIA. One of the buttons is "Make Absolute." If you [Update] [Make Absolute] [Enter] - you will store your changes to your cue, but break the link to the reference itself. Once you have set that update style, the desk remembers it whenever you use update.
I'd recommend to you that you play around with this in blind spreadsheet, to see how edits to cues impacts your show data. While we never try to force anyone to use tracking, once you understand how tracking will work, and how the desk can protect your show data for you, it is a much more efficient way to work.
The effect issue that you bring up is addressed in the upcoming 1.5.
Hope this helps.
a
www.etcconnect.com
