Documentation of Default IFCB Parameters List in Eos

Would it be possible for ETC to provide documentation of the default Parameter names in Eos, and on which encoder page they reside? As a lighting programmer in film/tv, I find myself working more and more with software-based Media Servers and 'prototype' fixtures. These generally ship with highly 'creative' GDTF schema, i.e. totally made-up parameters that all drop into the Form pages. Or they ship with nothing at all.

So, it would be great to have a reference 'library' to vet out these profiles before bringing them in to a working showfile. Erring on the side of utility, Eos is quick to add these bootleg Parameters to the showfile's database. 

And on that subject, what's the best way to clean these out? New showfile + merge?

Parents
  • You are touching on a deeper problem with the library at ETC. There is a lack of vision in how the library is built and maintained at the moment and it is getting worse with more and more plain GDTF imports. There seems to be no deeper understanding in what a parameter actually does at the library department, so parameters may end up with the marketing names of a manufacturer or are they are being placed in a seemingly random category.
    An example would be the many ways a “parameter that changes the colortemperature” can be named (look it up, it is really a lot!). Or the historic reason “Fan Speed” is in the color category (reason: color scrollers used to have fans!). 

    Apart from the problem you are having with finding on which page the parameter ends up, it is also really difficult to swap a fixture type on an existing show, or use macros (that address certain parameters) in your default showfile, to name a few things.

    in other words, something needs to change.

  • Be that as it may, and I don't disagree that the library needs work, it feels like there must be a document somewhere that lays out the Eos base parameters in their categories.

    For now, I don't mind having fan speed under 'color,' and I'm happy to build and rebuild fixture profiles as needed. I just want the parameters to respond to the right nudge, 'temperature' for CCT as an example, and to lay out properly on-screen.

Reply
  • Be that as it may, and I don't disagree that the library needs work, it feels like there must be a document somewhere that lays out the Eos base parameters in their categories.

    For now, I don't mind having fan speed under 'color,' and I'm happy to build and rebuild fixture profiles as needed. I just want the parameters to respond to the right nudge, 'temperature' for CCT as an example, and to lay out properly on-screen.

Children
No Data
Related