• 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

  • I feel the same way. Some of these fixtures should be fairly easy to implement (particularly the older ones like the Intellibeam13).

    I can write the profile myself, but I don't have the tools to set up lamp control (reset) functions. So if/when I do write a13ch profile I'll be dependent on macros to first, close the shutter, then issue the right code on the control channel, then release. The 8 channel version doesn't even support control functions - which is pretty much a necessity on a ten year old fixture.

    Just my $.02

    -Dave

  • in reply to zorlack

    I guess I have not gotten to the point to understand your comment about the control functions on ION/EOS in case they are implemented differently than other consoles - as far as the fixtures are concerned, there aren't any macros or anything else needed to run the control on these fixtures - just set the control channel to what you want, dimmer closed, and close the shutter and it executes . . . . that's it!  What I have not seen on the ION/EOS is access to the control channel period . . . . if it were there, I would be a happy camper, since I would then have the same level of control/access that I have on my Hog, which has served me well over the years . . . .

     

    - Tim

  • in reply to tadawson

    On a device profile which has been implemented by ETC you have a range of "Lamp Control" options. These options are not shown with the regular IFCB encoders, they have their own section.

    We have a Robe Colorspot 250AT which has a wide variety of lamp control functions. IE you can reset the fixture, or tell it to relamp without resetting etc...

    I don't think there's any way to write a profile which has lamp control options, but I could be wrong. I think you'd have to put reset functions in a custom parameter. Am I right about this?

    -Dave

Reply
  • in reply to tadawson

    On a device profile which has been implemented by ETC you have a range of "Lamp Control" options. These options are not shown with the regular IFCB encoders, they have their own section.

    We have a Robe Colorspot 250AT which has a wide variety of lamp control functions. IE you can reset the fixture, or tell it to relamp without resetting etc...

    I don't think there's any way to write a profile which has lamp control options, but I could be wrong. I think you'd have to put reset functions in a custom parameter. Am I right about this?

    -Dave

Children
  • in reply to zorlack

    I would think that if you were to use a parameter type for the control channel that showed on an encoder, you would be good to go - simple as that.  At lease in HES stuff, there is *zero* magic in running control . . . if you have access to the shutter, control channel and dimmer, you have all you need.

    Yes, the errant label would be annoying, but I can't see why it couldn't be done . . .

    - Tim

Related

www.etcconnect.com