Some notes on my new ION consoles.

So we took delivery of two IONs on Wednesday and immediately started delving into it.  We have some bug reports and questions and feature requests.

 

Patching:

If patched separately, second dimmer for a channel overwrites existing dimmer instead of becoming a second part.  Example:

    [141] [at] [1] [enter] patches dimmer 1 to Ch. 141

    [141] [at] [9] [enter] patches dimmer 9 to Ch. 141 and eliminates dimmer 1. 

It *should* put dimmer 9 as part 2 keeping dimmer 1 as part 1.  It works this way in address mode.

 

 Creating new fixture:

Cannot use touchscreen to select a specific box on spreadsheet to alter anything, we are forced to use arrow keys.  Can't click with mouse either.  Seems to be left out of the touch/mouse GUI. 

 

Can we get the ability to copy existing fixture profiles to the user folder and edit them?  It would be so, so useful.

 

Our Follow/hang button gets stuck on the Preset button.  One or the other is misaligned.  Any ideas on how to fix that?

 

Tracking of non-intensity parameters:

    Is it possible in the future (or current console) to view the levels as 0-100 instead of, for example, -28 to 50 or similar?  Are there view options to show it this way?  Can it be added in?

 

Fixtures:

   Why does it make us "exit ION", essentially log out, when clearing out/deleting fixtures from the user folder? 

 

The console became very unresponsive this morning after booting up.  There was a 5-10 second delay from either clicking with mouse or touching screen.  It made no sense as we have just turned the console on and hadn't done anything yet.  Any ideas?

 

We'll be adding bug reports, feature requests, and various other information as we play further. 

 

Nick Farwell

ACT Theatre, Seattle WA
 

Parents
  • Just set up the second ION and got both monitors working, etc.  Chose Shutdown and was given a sexy Windows error:

     

    "EOS.EXE - Application Error.  The instruction at "0x7c911e58 referenced memory at "0x040dc008".  The memory could not be "read".  Click OK to terminate the program"

     

    Besides being a candidate for the blog of unnecessary quotation marks (memory could not be "read"??), what the hell does this mean?

     

     

Reply
  • Just set up the second ION and got both monitors working, etc.  Chose Shutdown and was given a sexy Windows error:

     

    "EOS.EXE - Application Error.  The instruction at "0x7c911e58 referenced memory at "0x040dc008".  The memory could not be "read".  Click OK to terminate the program"

     

    Besides being a candidate for the blog of unnecessary quotation marks (memory could not be "read"??), what the hell does this mean?

     

     

Children
  • Anonymous
    Anonymous in reply to nfarwell

    In 1.3 we have seen a crash on shutdown.  This crash happens after the console has done all important save and disconnect operations, so it not really a big deal outside of the ugly windows error screen.  Not too get too technical about it, a "memory could not be read" message is a reference to the application trying to reference a bad part of the memory on the computer...in this case we were trying to read memory(RAM) that we were already finished using do to the shutdown process.

    When 1.3.1 is released (which is very very soon...we just got approval to distribute it yesterday) you will not see this error anymore.

    Sorry about the ugliness of the message.  If you do see this message at another time (when you are not shutting down or in future releases of the application), please contact our Tech Services department.  They will be able to help you work around the problem, and can help gather information for the development team so we can fix the problem.

    Anyway, don't worry about this error on shutdown.  Just press the "OK" button.   

    -D 

Related