Ion Custom Fixture for Colorful Lighting QueenBeam Zoom Effect LED Moving Head Issues

I have gone through and made a custom fixture with all the info from the manufacturer (Colorful Lighting).

Mostly I have been able to get the fixture to do what I want, all the channels appear to work fine, I made a few choices that don't quite match the naming on the Ion parameter with what the documentation says, but so far they function as I would expect.

I have a few questions:

First, the fixture has 3 zones or rings of LEDs that can be color mixed RGBW individually that is all great and works, but is there a way to setup a combined parameter so when I simply what all of them to be the same that I can just grab all three zones with one control? Related to that, can I get the color picker to work for each zone and/or the combined zones on the fixture?

The DMX controls are setup as:

Red Array 1 - ch 10
Green Array 1 - ch 11
Blue Array 1 - ch 12
White Array 1 - ch 13
Red Array 2 - ch 14
etc. through array 3 with each color

I chose to use the parameters red 2, red 3, and red 4 with the hope that I could use red master or the un-numbered plain red parameter or Red All as a combined control but does not seem to function that way. When I try to select it, it wants a dmx address and what I really want is a custom control that I can tell it to change all 3 channels of red with one parameter. I have tried making Red All, Red Master, and Red virtutal parameters (not all at once but one at a time), but they don't seem to tie to any of the individual arrays and I can't see a way to make them do that in the controls available to me.

Secondly, when I am in live view the parameters are all jumbled up. They are entered sequentially in the custom fixture:
number     parameter
8               red 2
9               green 2
10             blue 2
11             white 2
12             red 3
13             green 3
...
19             white 4

but they are listed in live view in this order: blue 2, white 2, white 3, white 4, red 3, color macros, color effect, green 3, blue 3, red 4 ... in no particular order that I can determine. Is there a way to rearrange that so that they are in an order that makes more logical sense or at least control sense so one page of the encoders is at least RGBW for one of the arrays?

The final question is more on how to input information, I kept wanting to hit tab to move to the next column like a spreadsheet, especially when I was entering ranges with custom names for the macros and color selectors. Is there info on a text format like xml or csv that can be used to make custom fixture profiles that can be uploaded into the Ion?

Parents
  • Hi Jonathan,

    Eos treats each channel like a single beam of light - this means that individual cell color control is a bit trickier if you patch the fixture as a single channel.

    There are two basic ways to approach this: the first is to define the profile where any red parameter is just "Red", any blue just "Blue", and so on... This allows you to control all of the color together using the color picker. However, you do not get individual control.

    The second option is to create individual profiles for the part of the fixture you want to control independently. So, if channels 1-9 are shared attributes like pan, tilt, intensity, you could patch that as a channel and then patch additional RGB fixtures for each section of the fixture you want to control separately. You'll still end up with RGB control with a color picker and have individual cell control.

    Color "All" parameters are just a label used from other fixture profiles that had DMX mappings. There isn't any console logic to link those together - one of the two options above are the way to get control as you specify.

    Multicell control is a topic that is brought up from time to time - there may very likely be changes in the future.

    The order of parameters is determined by the library and not editable in the desk. However, I agree that it would be better to at least have the "(Color) #" parameters sorted together.

    The fixture editor is the primary way to create fixture profiles - you can use the offline/Eos ETCnomad software, but it's still in the Eos app. If you have a fixture manual from the manufacturer, we can add the fixture to a future library update.

    Thanks!
Reply
  • Hi Jonathan,

    Eos treats each channel like a single beam of light - this means that individual cell color control is a bit trickier if you patch the fixture as a single channel.

    There are two basic ways to approach this: the first is to define the profile where any red parameter is just "Red", any blue just "Blue", and so on... This allows you to control all of the color together using the color picker. However, you do not get individual control.

    The second option is to create individual profiles for the part of the fixture you want to control independently. So, if channels 1-9 are shared attributes like pan, tilt, intensity, you could patch that as a channel and then patch additional RGB fixtures for each section of the fixture you want to control separately. You'll still end up with RGB control with a color picker and have individual cell control.

    Color "All" parameters are just a label used from other fixture profiles that had DMX mappings. There isn't any console logic to link those together - one of the two options above are the way to get control as you specify.

    Multicell control is a topic that is brought up from time to time - there may very likely be changes in the future.

    The order of parameters is determined by the library and not editable in the desk. However, I agree that it would be better to at least have the "(Color) #" parameters sorted together.

    The fixture editor is the primary way to create fixture profiles - you can use the offline/Eos ETCnomad software, but it's still in the Eos app. If you have a fixture manual from the manufacturer, we can add the fixture to a future library update.

    Thanks!
Children
No Data
Related