Sneak Cue Command

Hey all,

 

 I can't figure out the keystrokes for a set of instructions and hoping that you could help.  I updated a cue in blind in a cue, then hit go as I was updating it.  The channel that I changed was a tracking value, so therefore didn't move.  On the O2 the keystroke is [ch] [sneak] [cue], which will only move that channel in the sneak time to the blind level.  [ch] [sneak] puts it at the level that it was live, correct.  [Go to cue] slams in the cue.  I thought maybe [ch] [go to cue] but that is super buggy because it moved the whole cue except selected channel to cue 0.  I think this should be the syntax, but it currently doesn't work.  Let me know what you think.  Thanks.

 Jay 



[edited by: Jay at 6:28 PM (GMT -6) on Mon, May 26 2008]
  • Jay, there are a couple of things that I'm confused about.  There is no such thing as "update" in blind ??  What do you mean you "hit go as I was updating it."  Does that mean you were changing a level in blind and in the middle of that command you executed a Go on a playback?    Also, can you identify where you are?  And how you got the beta code for 1.4?

    Thanks much,

    Anne

     



    [edited by: Anne Valentino at 3:10 AM (GMT -6) on Wed, May 28 2008]
  • Yes by update in blind I mean changed.  

     I guess the real question is what does channel 10 sneak do?  Does it change it to the blind level?

    I was programming for David Weiner.

     

    Thanks

    Jay 

  • AHhhhh....  thanks!!  

    Sneak is a command useful in live only.  It will:

    a) return a channel to any values coming from the playbacks or

    b) if there are no values from the playbacks (including subs), sneak will home the fixture.

    But here's the thing.  Once a cue is in playback, it is not tied to blind.  So, if cue 5 is on stage, you go to blind and modify cue 5 and then sneak some channels - they go to the original cue 5, not the modified cue 5.  Playback is a different buffer from blind (for cues)

     Does this help??  If not, let me know!

    thanks,

  • Yes, that answers the question, but not the solution.

    So I've changed a cue in blind.  I hit go on a 60 second cue.  I want to update the channel that I've changed in blind, but don't want to change the time of the cue coming in.

    Channel sneak won't do it, as you mentioned.

    Go to cue in a time will do it, but slightly changes the time

    [channel] [go to cue] [enter] puts the channel level at correct position, but the rest of the cue went to cue zero. I think this is the syntax, in that it lets me type this, but the cue went to zero except that channel.  Really I'm looking for the equivalent of [ch] [sneak] [cue] on the O2.

  • Hi Jay-

    I am wondering if [Channel][Assert][Cue][Time][Enter] will do what you're looking for? I've never used the [ch][sneak][cue] function on the O2, but the Eos [Assert][Cue] functions work in much the same way. You don't need to specify the channel if you want to assert the entire cue, and you don't neeed [Time] if you want to use the console Assert time rather than the cue time.

  • Luke and Jay, that will work.  The syntax is [channel number] [Assert] [Cue number] [Time] [nnnn] [Enter].  Because you can assert from any cue, you have to specify a cue number.  If you enter the [Cue], the command line will error out - just enter a number.    We assume the [Cue] part.   In looking at it, we should probably allow a manual entry of [Cue] if you don't know we will post it for you.

    Thanks Luke.  Jay, best regards to David.  I saw him briefly last week and he said all was going well.  So, thank you very much!  

    For everyone else.... command line assert was added in 1.4.  As such, this command will not work in 1.3.1.  Look for a public release of 1.4 late this week/early next week.  Will post something here!

    Anne

     

  • Two Questions:

    Does [Assert] default to asserting the cue that is currently being output?  

    Also, is there a default [Assert] time?

     

    Explanation: 

    In both of the above examples the solution is super flexible because you can choose to assert channels from any cue in the default time, assert any channel in the current cue in a time of your choosing, or assert channels in a different cue in a time of your choosing.

    Here's how I think it should work...am I right?  (again...if I only had a console in front of me today...) 

    [Channel number][Assert][Enter] Puts the channel(s) or Group(s) back to the recorded state of whatever cue is being output in a default time.

    [Channel number][Assert][Time][nnnn][Enter] Same as above with a time of your choosing, different from the default.

    [Channel number][Assert][Cue number][Enter] Moves the channels to the level in the specified cue in the default time

    [Channel number][Assert][Cue number][Time][nnnn][Enter] Moves the....blah blah you get it.

      

     Rationalization:

    I have to think less. 

    I know that sounds funny, but the beauty of [Go To Cue] [Enter] is that it goes to the current cue, which may be a xx.xx follow or something complicated, and I don't have to A) confirm the actual location in the cuestack or B) type in all those pesky numbers.  I just hit [Go To Cue][Enter] and the computer does all my thinking for me, and puts all the channels back into the recorded state of the current cue.

    On the O2, the sneak syntax works the same.  [Sneak][Cue][Enter] puts the output back at the recorded level of whichever cue is currently active.  [(CH) XXX]or[Group][XXX]  [Sneak][Enter] returns just the channel or group of channel back to the recorded state of whatever cue is being output live.  And if you're feeling creative [Channel nummber][Sneak][Time][nnnn][Enter] Does it in a time of your choosing.


     

     

  • David, don't forget that you can use the Assert fader key (the little ones above the rate wheel) in combination with the master load button- this will re-assert the cue in the default Assert time (in Setup). This is what I would probably use if I had made a change in Blind and wanted the Obs2 Sneak-Cue function. The biggest reason that Sneak-Cue wouldn't really work on Eos is that it supports multiple cue lists, and you need to define which cuelist's current cue should be replayed.
Related