Hidden Layer of Complexity for Fixtures?

Question

Is there a "hidden" layer of complexity in control of parameters for library fixtures? When I make a copy of a library fixtre and attempt to edit it, there are some parameters that cannot be edited and they appear on the list of parameters as greyed-out. 
 It would appear to me that these parameters link to another level of control that a simple custom fixture doesn't have. That's what I think is wrong with the library fixture for the ArKaos VJ_v3.6.1_Fixture_HW_Full profile. 
 The "File Type" "Effect Library" and "Copy Mode" controls are greyed-out, and they would seem to link to a further division of ranges. e.g. in live mode when I change the "File Type" encoder from picture to movie , the list on the "File 1" encoder changes from pictures 1-255, to movies 1-255. When I change the "File Type" encoder to video , then the list on the "File 1" encoder changes to Layer 0, Camera 1, Camera 2 and remains there even when the "File Type" encoder is set to text . 
 There are no wheels to edit, and no other lists that I can find in the fixture creator, so where are these other lists coming from and can we edit them ?

Anne Valentino · Accepted Answer

The fixture editor does not support all of the same controls that the EOS fixture definitions support. For example, the editor does not support parameter dependencies and does not support multiple range sets for a parameter (we call these "states"). When we first built the fixture editor, users were not allowed to copy and edit an existing profile with the editor due to these issues. Users were only allowed to create and edit new fixtures. Later, we put together a collection of rules to try and protect the data within a fixture that is not exposed via the editor so the user can at least manipulate parts of an Eos fixture in the editor. It is these rules that were created that you are running into. We will look into this a bit more. But here's the real thing. It's great that you guys are all so self-sufficient! :-) However, if you encounter an error in the fixture profile (and this CAN happen), rather than fixing it yourself, we would much rather you contact us, so we can verify and fix the profile in the library. This will prohibit other users from having the same issue. Eos does a lot of work to a fixture profile to present the controls in a unified manner, provide layers of abstraction and so forth. The fixture editor was really intended for the situation when "its 7:30 on a Friday, I have a new light that has no profile and need to get some control over it." We will look at the issue you raised here and provide some feedback. 
 thanks much, 
 a