• Date
    David
  • Date
  • Replies 5 replies
  • Subscribers 182 subscribers
  • Views 10711 views
  • Users 0 members are here

Making Part Cues

The syntax for making part cues needs to be like the  obsession.  On the obsession to put channels into a part I just had to navigate to the part and type [CH##] [ENTER].  On the Eos I have to type [CH##] [@] [VALUE] [ENTER].  This makes making parts a tedious process, and uses up valuable programming time.  The problem is when dealing with moving lights and putting different attributes into different parts, or putting multiple channels with different values into the same part. 

 Is there something here I'm missing?

Parents

  • In blind, if you are in the part you want, [CH##] [Part] [Enter] will put the channel into that part. One more keystroke than Obsession. I can't think of a reason to have the extra [Part] but if there is I'm sure someone will tell us.

     

    Tim

  • in reply to Tim Wilson

    Hmm.....Interesting.

     Well that's not as bad as the way that I was doing it, so that helps a lot. 

     Like you said though, its still one more keystroke than I think we need.  Lets keep it simple!

  • in reply to David
    Hey guys.  On Obsession - just the act of selecting a channel pulls that channel into the selected part.  We can't really do that, because the chances are slim that you would want the entire channel (in the case of a moving light) in the part that happens to be selected.   Thinking of this in blind at the moment.

    So if you are in cue x, part y and say chan 1 color palette 3 enter - it pulls channel 1 color parameters into part y - but it doesn't pull the rest of the channel in.  

    If you want to leave the data as is, but move a parameter into a part, you have to tell us what you want.... 1 focus part enter will move channel 1 focus into the selected part.  1 part enter will move the whole channel.  Sorry - I realize its an extra keystroke in blind, but I really can't think of any other way to do it....

    ??

    a
  • in reply to Anne Valentino

    Anne,

     All of the examples that you gave make perfect sense, but I don't see how the [part] keystroke is actually necessary in any of them.  In the first example you listed, a channel is being put into a part by giving it a value, so the part button isn't used, and only the selected attributes are in the part.

    In the second example, you can delete the [Part] keystroke and get the same results, since the channel isn't actually selected until you hit [@] or [Enter]. 

    [1] [focus] [enter] Moves the focus into the part you have selected, and [1] [enter] moves the entire channel into the part. Either way the user has to have thought to say what he or she wants, but has to press one less button to get there.

     

Reply
  • in reply to Anne Valentino

    Anne,

     All of the examples that you gave make perfect sense, but I don't see how the [part] keystroke is actually necessary in any of them.  In the first example you listed, a channel is being put into a part by giving it a value, so the part button isn't used, and only the selected attributes are in the part.

    In the second example, you can delete the [Part] keystroke and get the same results, since the channel isn't actually selected until you hit [@] or [Enter]. 

    [1] [focus] [enter] Moves the focus into the part you have selected, and [1] [enter] moves the entire channel into the part. Either way the user has to have thought to say what he or she wants, but has to press one less button to get there.

     

Children
  • in reply to David

    On a related note: I understand why the console is asking me if I'm sure when I create a cue in Blind by typing [Cue] [##] [Enter] (when the cue doesn't already exist) But does it really need confirmation when creating a part?  The cue is already there...  

    I'd be interested to find out if other users want the console to prompt for confirmation at this step.

Related

www.etcconnect.com