How to use the assert and assert time ?

Move is a way to move show data around.  So you can:  [Cue] [1] [thru] [2] [0] [Move] [1] [0][0] [Enter].  All show data can be moved from one location to a different location in this manner.  When moving cues, it is important to keep tracking in mind.  So, if the desk is in track mode, and you don't want the moved data to impact cues subsequent to the new location, you need to be sure you append a [Cue Only] command to the move. 

Assert is a playback function only.  Eos is a move fade desk.  So, when you are playing back cues in sequence, only the move instructions stored in the cues are executed.  Tracked values, by default, are not recalled.  This facilitates handing off control from one fader to another fader without priority states and such on playbacks.    Assert is a way to force a tracked value to be executed when a cue is recalled.  Cues, cue parts, channels and channel parameters can all have an assert flag placed on them in any cue.  The "Assert Time" you refer to is if "assert" is executed manually.  To explain in real world terms......

Assume you have established a base setting for your cyc in the first cue of the show.  You want this to be the background value for the cyc throughout the whole show.  But in scene two, you need to do a sunset on your cyc.  You decide to do that on a secondary cue list, because nobody can decide when they want the sunset to start (-- or you simply don't want to muck about this your background cyc look).    So you write cue list 2 with your sunset.  At the proper point, you execute cue list two.  Now, we are done with the sunset.  We want the lights to go back to their "base" or "background" value from the main cue list.  But those values in the main cue list are tracked instructions from the very first cue.   So, within cue x, you place an assert flag on those channels.  When Cue x is replayed, the cyc channels will leave their last command from cue list 2 and return to their values in cue list 1, even though those values are tracked.  

You could have blocked those channels instead in Cue x..... blocked values are tracks that behave like moves.  But if you'd blocked them, you could no longer do a track edit from the first cue to change the background value on the cyc through most of the show.    This was probably a good reason to make your sunset a second cue list ..... so you could --- in one cue --- change the background value of the cyc.     

The Assert time, in setup, is if you need to manually assert a cue (now would be a good time for the cyc to return to its background state).... [Assert] & [Load] does that.  In this instance, the channels will fade to their tracked values in the associated cue lst using the "Assert" time.  

Does this make sense?  It's one of those features that is easy to show, but the more you talk about it, the more complex it seems.   Feel free to give me a ring at 201.289.0410 if you want to chat through this.

Thanks!

Anne

Move is a way to move show data around.  So you can:  [Cue] [1] [thru] [2] [0] [Move] [1] [0][0] [Enter].  All show data can be moved from one location to a different location in this manner.  When moving cues, it is important to keep tracking in mind.  So, if the desk is in track mode, and you don't want the moved data to impact cues subsequent to the new location, you need to be sure you append a [Cue Only] command to the move. 

Assert is a playback function only.  Eos is a move fade desk.  So, when you are playing back cues in sequence, only the move instructions stored in the cues are executed.  Tracked values, by default, are not recalled.  This facilitates handing off control from one fader to another fader without priority states and such on playbacks.    Assert is a way to force a tracked value to be executed when a cue is recalled.  Cues, cue parts, channels and channel parameters can all have an assert flag placed on them in any cue.  The "Assert Time" you refer to is if "assert" is executed manually.  To explain in real world terms......

Assume you have established a base setting for your cyc in the first cue of the show.  You want this to be the background value for the cyc throughout the whole show.  But in scene two, you need to do a sunset on your cyc.  You decide to do that on a secondary cue list, because nobody can decide when they want the sunset to start (-- or you simply don't want to muck about this your background cyc look).    So you write cue list 2 with your sunset.  At the proper point, you execute cue list two.  Now, we are done with the sunset.  We want the lights to go back to their "base" or "background" value from the main cue list.  But those values in the main cue list are tracked instructions from the very first cue.   So, within cue x, you place an assert flag on those channels.  When Cue x is replayed, the cyc channels will leave their last command from cue list 2 and return to their values in cue list 1, even though those values are tracked.  

You could have blocked those channels instead in Cue x..... blocked values are tracks that behave like moves.  But if you'd blocked them, you could no longer do a track edit from the first cue to change the background value on the cyc through most of the show.    This was probably a good reason to make your sunset a second cue list ..... so you could --- in one cue --- change the background value of the cyc.     

The Assert time, in setup, is if you need to manually assert a cue (now would be a good time for the cyc to return to its background state).... [Assert] & [Load] does that.  In this instance, the channels will fade to their tracked values in the associated cue lst using the "Assert" time.  

Does this make sense?  It's one of those features that is easy to show, but the more you talk about it, the more complex it seems.   Feel free to give me a ring at 201.289.0410 if you want to chat through this.

Thanks!

Anne