wish list for future versions

G G,

Number two will be shot down by security fanatics.

Number three is probably impractical... but so way cool!

Number one-  I am totally with you, and invite all to voice opinions.  If I enter a channel and press Full, the need to then press enter is really the equivalent of a dialog box that asks, "Are you sure?"  I am sure there is justification, but I wonder why the Out key is self-executing. 

I also think it would be nice to have one of the unassigned keys to be a Macro button.

Brent 

The reason we require an enter on the command line is usually so that it is possible to add additional commands to the instruction. Whenever you set a level, there are many commands that you can place after the level, before the enter, that are not possible if we auto-insert the enter. For instance, [Chan 1 Full Sneak Enter]

 There is a [Level] key next to [Full] that doesn't require enter, and by default, sets the channel to Full. You can set it to something other than full from Setup:

[Displays] [Setup] [Desk] [Manual Control] [Level]

1.  LEVEL.  That has been the self-terminating FULL of choice for years on ETC consoles.  In addition to the SNEAK add that Dan mentioned, the way it works in blind is important.  If you want to make something Cue Only or Track you add this to the end of FULL in Blind.  I personally use that all the time.  Self terminating FULL would be a big departure from ETC syntax that would not be well I imagine.  This is not an ON button...

2.  Please don't hook up my console to the internet...the fact that it's based on embedded Windows XP is scary enough.  All we need is some spyware or adware to latch on and crash the board during a performance at the Kennedy Center.

3.  oooo...backlit keys...now that would hot!  I vote for it.

The macro button exists already on the right side of the right touchscreen

My two cents.

Stu 

See, I knew the Full button would be justified.  I see what you mean about the track/cue only stuff.  As for Level, I too use that as an @Full [Enter].  But I work regularly with a Designer who insists that the Level level be set at 69%.  Not my choice...

The Macro button I want is a key that fires a Macro.  Like the User button on the Strand 500's.  I could program it to be my most common keystrokes.  Most often, @ Full [enter}, or, I guess- ON.

B

69% really.  I'm sorry.  I see your issue.

I do believe that the 3 blanks on the EOS are going to become user-programmable buttons (Address in my case!).  I don't know whether or not they plan to have the ability to make them a macro execute or not...  let Anne know that you would like that.  I second the vote for the ability to have those keys initiate macros.

Stu

Stu,

Yeah, an Address button will be a total asset.  I am glad to hear that at least there is a rumor concerning a couple user-programmable keys. 

Most everything from here on is icing and gravy.

Brent   

I disagree with the being able to send the light to X without hitting enter.... 

 Right now I can go "Channel""at""full""sneak""time"10"enter"

I would lose that syntax if the light popped to full with the press of full 

Well I have to say the lighted buttons would be fine but I was hoping for some more practical thing.

How about that fan button?  Is that going to be working soon?

 I can't tell you how great it would be to be able to span a delay on the same attribute across several instruments in the same cue.

 I know I might be going out on a limb here but multipule time code cue lists?

 What do you think?

Doug

MacStgTek:

I disagree with the being able to send the light to X without hitting enter.... 

 Right now I can go "Channel""at""full""sneak""time"10"enter"

 

I would lose that syntax if the light popped to full with the press of full 

 

 Matt, this has been brought up a number of times. Calling the question.  Not going to change from the current syntax -- for exactly the reasons that you and others have pointed out.

a 

Buckeyt:

Well I have to say the lighted buttons would be fine but I was hoping for some more practical thing.

How about that fan button?  Is that going to be working soon?

 I can't tell you how great it would be to be able to span a delay on the same attribute across several instruments in the same cue.

 I know I might be going out on a limb here but multipule time code cue lists?

 What do you think?

Doug

 Hi Doug.  Fan will be in 1.4 (mid Spring '08).... 1.4 is a major release for us  - as you might be able to tell from the number of times we say "yep, that'll be in 1.4".    More details on that as time elapses.  

Eos currently supports 32 time code event lists.  Does that work??

thanks much.  Keep it coming! 

 a 

The one big thing that I think the desk is missing is a fast way to set focus pallets. Most people who use Hog II use the heck out of the highlight key.  So the addition of a function that will put a unit at home, in open white, and at full; would be very useful. The other thing that I would really like to see in the EOS, and more importantly the ION, would be a way to configure gateways form the desk. And a way to lock people out of that function for when the desk is in a multi user environment, such as a college theatre where students are the primary users, but do not necessarily need to configure gateways.

But man they are both solid desks. I am very impressed.  

Hi Ben.  Welcome to the forum.  I'm gathering you've just spent some quality time with our Mr. Hessler?  

 Highlight will also be included in v1.4.  We do currently have a home key, which does as you describe above, except it does not set the associated channel to full.

 System config from the desk is coming - this will be for Net3 devices only.   Don't yet have an ETA on that functionality.   Also, in '08 will be security log-in.  So you'll be able to restrict access to certain features of the desk based on the user.

Thanks much!

a 

Hi Ben.  Welcome to the forum.  I'm gathering you've just spent some quality time with our Mr. Hessler?  

 Highlight will also be included in v1.4.  We do currently have a home key, which does as you describe above, except it does not set the associated channel to full.

 System config from the desk is coming - this will be for Net3 devices only.   Don't yet have an ETA on that functionality.   Also, in '08 will be security log-in.  So you'll be able to restrict access to certain features of the desk based on the user.

Thanks much!

a 

Anne,

Thank you for the update. And a great lighting console. I am just so impressed with the combination of Virtuoso DX and Obsession 2 features.  Well minus double tough . . .lol. You cats did a great job on the ION/EOS. Thank you.

usesafesets:

Anne,

 

Thank you for the update. And a great lighting console. I am just so impressed with the combination of Virtuoso DX and Obsession 2 features.  Well minus double tough . . .lol. You cats did a great job on the ION/EOS. Thank you.

Thank you so much!  We've had the luck to have a great team.  But can I also say that Eos and Ion were (and continue to be) very much framed by input from users.   The feedback that we get here, via direct contact, etc, is really, really valuable to us.  There is no "ONLY WAY".  If there were, there would only be one desk on the market.  

We welcome all comments, all questions.     Sometimes we may respond with "that doesn't really fit Eos." But always, we try to dig deep enough to understand and address what you are trying to do, not necessarily how you are trying to do it.

 Keep it coming!!

 :-)

a