Is is just me, or does support for HES fixtures in EOS/ION seem really, really sloppy and shoddy? The only thing I can find that is even close to a standard X-Spot is "X-Spot/CM/RG/IS-R", whatever the heck that means, and it's a channel shy of what a correct X-Spot profile should be, and two of the four parameters for gobo wheel one are greyed out, can't be deleted or edited, and don't appear on any encoder, making gobo rotation on the wheel impossible. Not to mention, the manual never even mentions a greyed out parameter in the fixture editor, what it means, and how to correct it.
X-Spot Framing personalities don't exist at all, nor do the Lithomotion personalities.
For Intellabeam, the world pretty much abandoned the 8 bit personality years ago, since moves were so jerky, but surprise! That's all that is on EOS/ION.
Studio color looks correct, but for the life of me, I can't seem to be able to access the control channel to manage the fixture (same for I-Beam and X-Spot - especially important to be able to lamp off X-Spot correctly to allow it to cool.
Another poster here has stated that the only available Cyber personalities don't come close to what a normal Cyber runs either.
And for the personalities that do appear to be close, why in the world did someone choose to rename all the parameters/ranges/etc. from the vendor nomenclature to different, less coherent names that are very confusing to those of us used to HES fixtures? Why, oh why, was something simple like "Focus" displayed as "Edge"?
Considering that HES has publicly documented it's DMX definitions for a long time, as well as it's nomenclature, and considering that I first saw ION/EOS at LDI '07, the excuse that "It's New" does not really fly that well any more . . . . .
One of the venues that I supply gear to and do a lot of work in just got an Ion, largely on my recommendation based on features and playing with it at LDI. Imagine my horror when I discover that the library is so bad that it won't support much of anything that the site has without major editing . . .
Anyone else notice this? Oh, and we are on 1.4.5, so it's not a downrev code issue either . . . .
- Tim
