A designer's response to the Ion

I have just finished teching my first show on the Ion/Eos (an Ion in my case) and thought that an LD's thoughts about the product might be helpful.

1.  In general, I like the consloe a great deal.  It has a number of cool new features that will prove to be powerful and time saving tools as I get to know this product.  It also retains enough of the functionality of the Obsession line that I felt pretty comfortable.

2.  The Auto-marking feature proved to be very useful for me.  It seems to work just as it should and prepped my fixtures in the previous cue with no effort.  Bravo!  One suggestion however would be the option to specify the cue that Auto-Marks or at least to force it one cue further back in the stack.  It is quite concievable that 2 cues might be close enough in time that a fixture might not have sufficient time to prep before becoming live.  I know that I can record the focus parameters in an earlier cue but then updating in the live cue doesn't seem to update the Mark.

3.  I like the independent time feature much more than I thought I would.  It will eventually probably eliminate my need for part cues which I never much liked anyway.

4.  I only began to explore the Palettes, Focus, Intensity, Color etc.  Seem like very good tools.  However, I wonder if I place them in a cue, then alter the settings in that cue and then Update the cue, have I altered the Pallette in all of it's occurences?  That would seem  to me to be a mistake.

5.  There are enough new features and concepts in this console that LD's are going to need some help getting on top of the capabilities.  While that is not a bad thing, we could use a little help.  The fact that channels now have multiple parts really condenses my hookup and I like that.  A simple glossary of terms and ideas (a "hot sheet") would be helpful as would a brief tutorial.

6.  I have a couple of seemingly trivial, but significant (to me) gripes.  The first is that the displays that I have at the RVI don't always mirror what the board operator is seeing.  I realize that I can go to my own displays from the RVI but my point is that I want to see what the operator is doing in real time.  I would learn the console more quickly and would have the comfort that I might prevent an error if I could see what was going on.  The operators DO NOT want the LD to be making changes on their own, so the lighting table philosophy will probably be "hands-off" for the LD. 

7.  The second gripe is the hard-to-read color that has been chosen for tracked levels.  I find that I cannot distinguish between 30 and 50 from more than about 2 feet away.  Could we PLEASE get a slightly brighter purple color?  PLEASE?  I should not have to ask the operator, "what level is 27 at?".  I just do not have the time in tech to spend on this.  Either a brighter color or a way to customize colors would solve this.  I think you'll find a lot of LD's having trouble with this one. 

8.  I miss the +10/-10 keys from the Obsession.  Is there a way to do this?

Parents
  • 6.  I have a couple of seemingly trivial, but significant (to me) gripes.  The first is that the displays that I have at the RVI don't always mirror what the board operator is seeing.  I realize that I can go to my own displays from the RVI but my point is that I want to see what the operator is doing in real time.  I would learn the console more quickly and would have the comfort that I might prevent an error if I could see what was going on.  The operators DO NOT want the LD to be making changes on their own, so the lighting table philosophy will probably be "hands-off" for the LD.

    ------- 

    As a designer, I understand your desire to know exactly what the programmer is doing and even thinking.  (I think this is quickly becoming an old fashion way of designing.)  But as a programmer (with the experience of many years and many consoles under my belt) you have to trust the programmer to help you accomplish your artistic vision.  As technology becomes more sophisticated and complicated, it is the programmer who is the liaison between the designer and the console, and the console and the rig.

    I may be out of line here, but Designers don't need to know everything about all aspects of the console.  Certainly knowledge is a good thing!  And the more you know about the functionality of the EOS and ION the more you can take advantage of it.  But sometimes I find it's better to tell a programmer what I want to have happen and just close my eyes and let him/her make it happen without getting invested in the programming of it myself.

  • Re:  RVIs.... right now, if you and your programmer are both user 1, you will be in the same displays as the programmer, and will see his/her command line, but will be able to have your own channel formats - a lot of designers seem to like this.   We are adding a true "mirror mode" in 1.5, which will show you exactly what the programmer is seeing.  If you are a separate user, you can work totally independent of the programmer.

    Hope this helps.

Reply
  • Re:  RVIs.... right now, if you and your programmer are both user 1, you will be in the same displays as the programmer, and will see his/her command line, but will be able to have your own channel formats - a lot of designers seem to like this.   We are adding a true "mirror mode" in 1.5, which will show you exactly what the programmer is seeing.  If you are a separate user, you can work totally independent of the programmer.

    Hope this helps.

Children
  • It's certainly an unenviable task: making designers, programmers, and board operators happy with their displays.  In the olden days, it was easy: the designer saw what the board op saw, no way to customize it.  The 1979 Light Palette had a "Designer's Remote" with almost all of the buttons of the console, but in most places (due to Union or other working rules) it was just used as a remote display.  I remember once, as a designer, putting channels on the wheel on an RFU, altering levels, and then telling the board op in the booth to record/update the cue.  He hated me for that--didn't like lights changing without his control.  And of course, I couldn't do a show without asking the Expression operator to press <Swap> at least a million times during tech rehearsals.  One of the best stories was when a designer asked me to print out a complete track sheet on a Prestige just before we broke for lunch.  When I came back, he had taped all the sheets together and said "I found the problem!  Never mess with your apparent light source!" He then proceeded to give me changes to about 10 channels in 100 cues.  Same designer was particularly fond of the levels 08%, 12%, and 17%.  Me?, I'm a 0, 25, 50, 75, FL, kind of guy.

    Today, I say professional designers with professional programmers should look at thier data however they want and trust that the programmer will achieve the final outcome they ask for, and not worry about how it gets there.  As a programmer, there's nothing more frustrating than a designer who attempts to call keystrokes at you.  I would deck a designer who watches my command line for errors.  Designers are supposed to be watching the stage, not the console!  Now I understand this may be slightly different in an educational environment, but still, it's okay to allow the board op make a mistake on the command line.  What's the worst that could happen?  Just press <Oops> or <Undo> or <Cmd-Z> a few times and start over.  That's how students learn.


    Clifton Taylor has a very good article on the various needs and requirements of remote monitors, including GMA 2 and Eos, here:  http://blog.cliftontaylor.com/2008/05/29/control-desks-continued---displays.aspx#comment-1085201

     

    DL 

  • It's never boring!  :-)  And with displays the question always is "is it bad, or is it just different."  And it always take a bit of time working with new displays to make those choices.  So, we continue to gather input... and then from our own experiences and those using the product, we just continue to refine them.   It's always a work in progress.   Thanks much for the input.  Clifton actually forwarded me a link to his blog on this.  It's now bookmarked and I check back regularly to see what he's got to say.  Always very thoughtful and well considered.

     a 

Related