Zebetz
Member
Hi there - Long time lurker, first time poster (and colleague of @Jay Ashworth ) Also - Because, as a roving designer and ME, I take every opportunity to program as much as possible before I ever hit the ground in a given city/venue. It is very much to my advantage to be able to 'schlep' Nomad around, but only in so much as that I can connect up to boards in many different venues. In some cases, the venues could just update their software but, in many cases - as with smaller venues or venues with smaller budgets - the hardware limitations prevent updates.
The point is that the onus should not be on the designer, the venue, or the electrician. The software should be able to absorb minor differences - tbch, I believe it should be backward compatible all the way back to v0.1, but I understand that's asking a lot. At a minimum, fixture libraries and software versions should be backwards compatible at least two full version numbers. It seems churlish at best (on the part of software development) for EOS to require such exact version synchrony. And a pain in my tuchus at least once every gig (eg like - literally - at this exact moment smh).
EDIT - I might add that, as a (pretty much unacceptable) work-around, I generally have two versions of the software on my mac, (2.9.0 and the latest version) but then there's the added layer of breakage that occurs when I have to update my fixture library. That is - I can have multiple versions of the EOS family on my machine, but if I update the fixture library in 3.1.x, it is also updated in 2.9.0!!!!! Which BREAKS 2.9.0 and so even my inadequate work-around is not a solution. AAAAND, EOS makes downloading fixture libraries prior to 2.9.2 (aka 2.9.0) nearly impossible - at least, I have not been able to find them so far...
Attachments
Last edited: