Tracking?

Hello! 

Say I record cue 1/1 , something like : All Alpha Spot 700 Intensity  Full Position Singer Color White Gobo Dots 

How do I make sure that once I playback that cue I'll always get that state back? 

I mean how do i make sure that once I play the cue 1/1 I get back that look, exactly that look I've recorded as : All Alpha Spot 700 Intensity  Full Position Singer Color White Gobo Dots 

Thanks for your kind replay 

 

Emiliano Morgia
Lighting Solutions
"Light-years ahead"

 

  • Not sure where you're having the problem, but here's a couple things:

    1). Try blocking the cue you want to keep. [Cue][x/y][Block][Enter].
    This puts a hard command on everything so that you can't track values into it from other cues.

    2). Try asserting the cue or cue list. [Cue] [x/y] [Assert] [Enter].
    This makes sure that when you play back the cue that it plays back all parameters in the cue regardless of tracked or hard values.

    HTH

    Stephen Graham
    5th Avenue Theatre
    Seattle, Wa


    [edited by: Toasty42 at 9:16 PM (GMT -6) on Sun, Jul 19 2009]
  • hi thanks for your reply , will blocking the cue put hard values in every parameters? 

     

  • Stephen, thanks!  Not being sure quite where the issue lies, it might be helpful to back up one step.

    There are two record functions in Eos/Ion - Record and Record Only.

    Record:  Stores all parameters of any channels not currently at their home value, regardless of how they got there.  So, in your first cue, if you grab a light, set intensity, put it in a focus and color, but don't touch any of its beam attributes, [Record] will store the entire state of the light, even the params you haven't touched (beam).

    Record Only:  Stores only manually set parameters of channels.  So, in the above example, [Record Only] stores only the intensity, focus and color of that fixture, but not its beam parameters.

    If you use Record Only in the middle of a cue stack, any parameters not involved in the store operation (beam for example) will track the values for those parameters in from the previous cue.

    Once you have the right data stored in the cue, as Stephen indicated, if any of those values ended up as tracked instructions, you can use an assert flag to assure the tracked values will be played back, if they happen to be under the control of another cue list at the point of playback.  Assert can be placed on the entire cue list (as indicated above), on a specific cue, cue part, channel or channel parameter. 

    Blocking is an editing only function.  It prevents tracks into cues (or beyond them backwards on a trace instruction).   It has no impact on playback.  Assert is the feature you use to assure a "tracked" or "blocked" value will be recalled on playback.

    Does this help?

    a

     



    [edited by: Anne Valentino at 8:53 AM (GMT -6) on Mon, Jul 20 2009]
  • Anne Valentino said:

    Record:  Stores all parameters of any channels not currently at their home value, regardless of how they got there.  So, in your first cue, if you grab a light, set intensity, put it in a focus and color, but don't touch any of its beam attributes, [Record] will store the entire state of the light, even the params you haven't touched (beam).

    So if I RECORD a cue 1/1 : all Alpha spot 700 intensity Full Position Singer Color White Beam Dots 

    All the parameters of all Alpha Spot will be recorded in the cue 1/1, correct?

    Thanks for your kind replay Anne 

  • Hi , well I've did that but it didn't work ... :( 

    I had an other playback where I put a FX in it . I've first play 1/1 and all Alpha Spot when on the singer with Color white and Beam dots. 

    But after I've played 2/2 witch as an Fx on Pan/Tilt in it the cue 1/1 did not when back to the singer :( 

    Instead the lights still moving. 

     

    thanks 

     

Related