Version 1.4

Brent, 1.4 is scheduled to be released by the end of May.  It will support NPs on submasters, I-Masters on both submasters and playback faders, but not yet effects on subs.  That will be in a follow on release.

Hope that helps.

anne

So...I've been waking up these last couple of mornings and the first place I log into is right here!  Hoping that I'll see v1.4 update!  I'm taking delivery of my Ion on Saturday (yeah!) and want to update before I start working!

Pat 

It looks like the v1.4 release notes are still there, but nothing else.  Yikes!  I took my brand new ION out of the box and updated to v1.4...should I be concerned?

Pat

:-)  cursed early adopters!  :-) 

as2k:

Worst case you can always reinstal 1.3.1.

releasenotes 1.4.0 says:... 

CAU T I O N : Eos show files are forward compatible to v1.4.x. However, v1.4.x show files are
not backward compatible to v1.3.x and previous. Once you load a v1.3.x show file
and then save it under v1.4.x software, you may lose some show data if you try to
revert the show file to v1.3.x software.

- maybe there will be some official comments soon..?

As the upgrade seems to have been pulled from the site can we get some sort of comfirmation from ETC as to what the  situation is. I cannot remember this ever happening before and always regard upates as ready to go. Hopefully this is just a minor slip but I am leaving my system alone until someone tells me what is happening.

Malcg

Hi Malcolm (and everyone else!!  Man, you guys are fast).  There was a slight blip in the version numbering that was posted late Friday.  We'll have it back up first thing Monday.   We will also have the Mac Offline download posted.  It is a different download from Windows.  For you the few of you who managed to grab the software before we pulled it, please update to the release build we will post tomorrow.

 Regarding backwards compatibility - we make library changes in each release that could cause problems with certain fixtures if you programmed on a later version of the library and then went to an earlier version... might end up needing to do some reprogramming.  This is the reason for that statement.   

 We will begin shortly posting documents to advise you of library changes, additions and deletions from one release to the next.  

Thanks!

Anne 

Hi Anne,

Thanks for that, I notice what appears to be a new Revolution fixture in the library is this a new all modules included version?

 Malcolm

Yes, that was at the request of several of our users. 

a 

I was one of them - fantatsic. I'm swapping modules mid show at the moment so that will save some fiddling.

Malcolm

Hi Derek,

We run a changing repertoire programme and offer LD's the Revolution as a basic tool but allow them a choice of modules. Sometimes this works well but on other occasions not. At the moment we are running with the shutters in permanently and swapping the iris and gobo modules as needed. On the Obsession it was easy as our profile allowed for all possibilities. Now that the same thing exists for Eos (subject to checking when I install the real 1.4 ) those changes we had to make will no longer be needed.

Malcolm

I downloaded and installed the new version this morning. For Mac:

http://www.etcconnect.com/docs/docs_downloads/offline/Eos%201.4.0.9.0.71.mpkg.zip 

It works!  Of course, I don't know what to do with it, not having access to an Eos or Ion, but still, Mac-native lighting software is a huge step in the right direction.

derekleffew:

I downloaded and installed the new version this morning. For Mac:

http://www.etcconnect.com/docs/docs_downloads/offline/Eos%201.4.0.9.0.71.mpkg.zip 

It works!  Of course, I don't know what to do with it, not having access to an Eos or Ion, but still, Mac-native lighting software is a huge step in the right direction.

Of course porting an offline version of a console that is still under development to another platform is more important that fixing the gaping holes that exist in the Eos / Ion software. An offline version is a LUXARY not a right. Of course ETC must make sure that the Jobs' boys are happy.... who cares about the guys that want more fixes / features on the physical console.  ETC have a finite number of coders therefore a finite ammount of code can be produced. If a coder is working on a port of Eos offline to Mac (or any other platform; WinPC Unix etc) then that is a coder not working on the console software. The more platforms that are deployed increase the no of bugs. That is why there is no Mac version of Hog2PC, Hog3PC, MAXXYZ PC, etc. Those writing code have better things to do than pander to a minority of users (this is not an anti Apple / Unix thing purely statistical) who want to use code written for a different OS. The more platforms (OS's) that are supported the slower builds (and bug fixes) for the real colsole will be as those builds have to be tested on every platform. Hey, can I have Eos OL for my PSP? Of course, but all other builds will slow to a stop, whilst the console OS is ported to the other hardware.

Those professionals in this industry understand this. There was nerer (to my knowledge) a PC port of the Icon or Artisan software. What ETC has done is laudible but at what real cost to the speed of incrementation of the console. Every build now has to be tested on 3 hardware platforms and at least 6 Operating Systems (with all their incremental builds).

To be honest any port to any offline vesion is bad news for the console user. Personaly I would prefer all console manufacturers to work only on the hard version of the console (even if it is MS Windows, OSX based) and get the console version right without having to waste time f&%^ing around with personal computer versions with all the inherent problems with screen resolution, system conflicts etc. In other words give me a fully working bug free console first, then, and only then, think about poorting it to open platforms.

Offline versions are great to pre programme / learn / play with a console OS, but if the Real console suffers, which inevitably it does, why bother? We used to manage before, why not now.

Waiting for a bug free 1.4.0.?

Adam
 

as2k:

Having looked further at the build released (1.4.0.1.0.71) I would recomend reinstalling v1.3.1. There seem to by quite a few interesting thing happening in 1.4.

 Just installed 'official' build - no difference. As I said. Stick to 1.3.1. Less bugs.