Updating cues with submaster

Joel, an non-specified update only updates content back to their original source.  And update only includes values that are manual.  

If the cue and sub are the only things on stage, you can rerecord cue 1.  That will capture the sub content.

You can also [Group] [Sub] [1] [Record] [Enter] [Enter]  will post cue 1to the command line and merge the current values from the sub into the cue.

Hope that helps.

a

Anne Valentino said:

Joel, an non-specified update only updates content back to their original source.  And update only includes values that are manual.  

If the cue and sub are the only things on stage, you can rerecord cue 1.  That will capture the sub content.

You can also [Group] [Sub] [1] [Record] [Enter] [Enter]  will post cue 1to the command line and merge the current values from the sub into the cue.

Hope that helps.

a

Maybe I'm not understanding things correctly, but this is something that has always confused me in the EOS line.  It seems that sometimes Record operations work more in an additive mode and sometimes they work in a over write mode.  That is, sometimes you can add new information like you are doing an update, and sometimes you are replacing the entire record target.  Determining which you get always confuses me.  Maybe it is just my Express console baggage tripping me up.

The (current) manual doesn't seem to help sort this out either.

Can you set me straight?

-Steve Martin, Indianapolis Symphony

Steve, perhaps this will help.

A non-specified full stage record is effectively a replacement.  Necessary zeros will be placed for lights that need to be turned off if they were active in the previous cue, but are not currently in use.  If you are programming sequentially, this should make sense.    But if you are programming non-sequentially, Eos essentially "overrides" tracking rules and forces zeros where needed.

A specified record (channel list record or - channel list record) is a merge function.  It will add to/detract from what would otherwise be stored in the cue based on tracking rules.

Record only is considered to be a "specified" record.... you are asking the desk to record only the things that are manual, in the same way that you might ask it to record channels 1 thru 10.  As such, Record Only follows all of the rules for a specified record.

Update is similar to record only - in that it uses the fact that something is manual as the determining factor for what should be stored.  However, a non-specified update (you don't give the desk a channel list or a record target), values will be stored back to their source.  To force a channel, via an update, into a record target that it is not currently its source requires a specific action by the user:  channel list update record target.

The exception to this is a "new" channel - one that is brought up manually and didn't belong to any of the active playbacks before.   A non-specified update will add this channel to the currently selected cue list.

Updating also allows you the option of maintaining the association to any references (i.e. palettes/presets) that you might have modified, while a record only always breaks that reference.

Does that help at all??

:-)

a

It helps hugely.  This lovely bit of prose should be in the manual!!  :-)

-Steve

Have not tried this yet but does that mean if i was to rerecord cue 1 it would act like a record only cue and not track the chances to the next cues until it hits a block?

thank you Anne for your response

Joel

Nope!  Cue Only and Tracking are different topics.  A record action, record only action or update will ALWAYS adhere to the tracking/cue only rules when it decides "what should this action be doing to the next cue".  Record/Record Only and Update determine what goes into a record target.  Cue Only/Tracking determines how that change should impact subsequent cue data.  Blocking is effectively a way for the desk to treat a tracked value like a move instruction when it comes to applying those changes.  

:-)

a