Full Full vs. At At

Can anyone tell me why Full Full serves to take me to my default level, but At At serves to take me to Full.

I like the use of the double click to avoid having to reach for [enter], but these two particular examples seem counterintuitive.  If I'm taking a channel to full, I'm going to type my channel selection followed by [full] [enter].  So I was never headed toward the [at] button.  And if I wanted to go to a level other than full, I would have followed my channel selection with [at].

So my question is why doesn't [full] [full] take me to full and [at] [at] take me to level?

  • IMHO...

    When an LD is asking for a channel and says channel 10 at......(pause).....Full....

    You'll already, have typed the channel and @....so hitting @ again, has always been the quickest response to the request.

    W.

     

  • But...

    If a designer has given me the command without the pause, I don't type the [at]; I go straight for [full].  And if the designer has given me the command through "at" and then pauses, I've already moved back to the numeric section and am anticipating the level s/he is about to give me--probably hovering over the most recent level used or the most recent level for that channel.  So in either case, I'm not hovering around the [at] key.

    It's also counterintuitive, which just doesn't make sense for a console like Eos/Ion built on the premise of 'all you have to do is tell the console what you want'.  It I hit [park] [park], I go to Park.  If I hit [group] [group], I go to the Group List.  Reason suggests that if I hit [full] [full], I should end up with Full.

    I might also argue that [full] [full] and [at] [at] should only work without a pause between clicks as in the [park] and [group] applications.  If a designer says "channel 4 at...(pause)...at 25 enter" and they are working with a less experienced board op who is simply pressing the buttons they are told, you suddenly end up with channel 4 at full and channel 25 selected in your command line.

  • Personally, I think it is fine the way it is.  If you want <Full> <Full> to work, just set your "at level" value to full and you get the behavior you want.

    I personally loath the commands the work differently depending on the length of time between key strokes.

     

    Steve Martin

    Indianapolis Symphony

  • I've found the best thing to do when the LD hesitates is to hit "Enter" instead of "@".  It autopages the RVI and is more macro friendly, especially if you have  a couple of rows of "@ (level) " macros above the CIA. I seem to recail that "@@" was a Strand method of going to full as well.



    [edited by: 33boardop at 1:08 PM (GMT -6) on Fri, Apr 23 2010]
  • I think simply pressing "@" will also page the RVI as you await a level instruction from the designer.

Related