• Date
    tadawson
  • Date
  • Replies 25 replies
  • Subscribers 187 subscribers
  • Views 34391 views
  • Users 0 members are here

High End Systems fixture library entries

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

Parents

  • Try taking an existing fixture witch is close to what you want/need, and copy it. You will then be able to edit the copy to your own preferences; dmx-mapping, bits, names, ranges, home values etc... maybe even keeping the lamp options.(?!) I'm very unshure if you keep the color-calibration from the original fixture(?). - On a lucky day you might succeed,  :-)

    (you might have to restart your console in between operations... - but I think they are working on it )

  • in reply to tryggve

    Well, that is part of the problem . . . for the X-Spot profile, for reasons undocumented, three critical parameters are greyed out in the definition, and can't be changed or deleted in any way, even in a copy.  They happen to include the gobo rotate functions for wheel one, which are incidentally identical in definition to wheels two and three, which ironically work.

    So, making a copy provides no help - the bad parameters are still locked, and the docs say nothing about what/how/?? is going on to get in that state . . . leaving the only other choice to start from scratch, which is no fun on a 38 channel fixture . . . . .

    For the 13 channel I-Beam, I may try your suggestion, since the main diff is that pan and tilt become 16 bit, but alas, the 13th missing channel is the control channel, so there is nothing to steal from the 8 channel profile. 

    I read that the imported fixture personalities are ASCII files . . . anyone seen a document on the structure of these files?  Myself, I find the fixture editor in the console cumbersome and annoying, and would personally prefer to be able to create ASCII files, since then I could import data from the Mfg. or other console definitions and not have to type every last bloody character . . . .

    - Tim

Reply
  • in reply to tryggve

    Well, that is part of the problem . . . for the X-Spot profile, for reasons undocumented, three critical parameters are greyed out in the definition, and can't be changed or deleted in any way, even in a copy.  They happen to include the gobo rotate functions for wheel one, which are incidentally identical in definition to wheels two and three, which ironically work.

    So, making a copy provides no help - the bad parameters are still locked, and the docs say nothing about what/how/?? is going on to get in that state . . . leaving the only other choice to start from scratch, which is no fun on a 38 channel fixture . . . . .

    For the 13 channel I-Beam, I may try your suggestion, since the main diff is that pan and tilt become 16 bit, but alas, the 13th missing channel is the control channel, so there is nothing to steal from the 8 channel profile. 

    I read that the imported fixture personalities are ASCII files . . . anyone seen a document on the structure of these files?  Myself, I find the fixture editor in the console cumbersome and annoying, and would personally prefer to be able to create ASCII files, since then I could import data from the Mfg. or other console definitions and not have to type every last bloody character . . . .

    - Tim

Children
No Data
Related

www.etcconnect.com