• Date
    BSmith
  • Date
  • Replies 3 replies
  • Subscribers 184 subscribers
  • Views 3713 views
  • Users 0 members are here

Unexpected/unfortunate tracking in Cue Only

So, some of the dance schools we do actually allow us the privilege of seeing a rehearsal on stage.  Most are having two or more mostly similar shows in different order.  Basically, every number gets one cue made from Qzero so I'm working in Cue Only Mode.  It seemed logical to assume that I could just record cues in rehearsal, then copy them into the correct order.  Surprise!  Copied cues track.

Should I have expected that?  I didn't, and I hadn't run through cues beforehand. Thankfully, after a few minutes I was able to figure out what was happening and get a handle on it as the show progressed.  Needless to say, I spent an hour before each of my next four shows pulling out the tracked values.

Is there some way to avoid this?  I thought of blocking all cues en masse, but never got around to it.  If I had, say, tried [cue 1 thru 100 Block] and then made another 50 cues, what would have happened if I had then tried [cue 1 thru 150 Block}?  Would it have unblocked 1through 100 and blocked 101 through 150?

B  

  • Brent - no, you should not have expected this behavior, if the desk is in track mode and you append Cue Only to the copy instruction.   Looks like something is pooched in the copy cue cue only command.  By default, in tracking mode, copying a cue will allow instructions to track into subsequent cues, unless appended with Cue Only.  We seem to have a bug at the moment that is allowing the values to track, even with Cue Only applied or when the desk is in Cue Only mode.  Interestingly, Move To works as expected.  Will get this on the list of things to address in 1.4.2.  

    Regarding blocks.... how this is applied is based on what's happening when you start.  If no cues are blocked, Cue 1 thru 100 Block Enter will block them all.  Block Enter again will unblock them all.  If you select a range of cues, some are blocked and some are not, the first application of block unblock all, then block enter again will block them all.   This rule, at a cue level, ignores the condition of channel/parameter blocks.

    Working with channel/parameter level blocking, though, the same rules apply.

    Very sorry about this.  We are on it.

    Anne 

     

     

     



    [edited by: Anne Valentino at 8:06 AM (GMT -6) on Thu, Jun 19 2008] [edited by: Anne Valentino at 8:05 AM (GMT -6) on Thu, Jun 19 2008]

  • CopyTo bug aside, recording to presets might be an excellent way to work with these shows.  You could assign a preset number to each piece ahead of time, record to the preset during programming, then build cues from the presets.  You could build multiple cue lists from the same presets if different nights had pieces in different orders.  The presets could also go in to a sub.  

    After designing my first show on an Ion, I realized that presets are an excellent way to save pre-actor "dry" tech work while still allowing me to actually build cues with actors on stage.  

    -Josh 

  • in reply to Anne Valentino

    Thanks Anne-  I think I can make [Move To] work for me for the time being.  And good answer about the group Blocking.

    Josh- That's an interesting idea.  I've been looking for an excuse to play with presets.  (the new definable Home Preset was really cool and handy last week.)  But is it as easy (minumum keystrokes) as Copy/Move?  I can see recording presets with labels, but what method do you use to get them into cues?  Goto zero, call preset, rec cue?  Does the label get onto the playback screen somewhere or do you relabel the cue?

    B

Related

www.etcconnect.com