Element - problem with using submasters with S4 Luster 2 LEDS

I'm running an element 60-500 with software version 2.2.1 and a mix of S4 conventional fixtures and S4 Luster 2 LED fixtures. I can program LED fixtures into submasters with color palettes and levels and each sub will work properly. When I have one sub up and bring up another sub from 0 to even 01, the first sub loses it's color setting and goes to full white. I can push the bump button on the other sub and the first sub will return to normal.  Both subs will then work properly as long as the second sub is not set back to 0 and then raised again. I've set the subs to I-master.  I'm trying to use the subs to build looks, so need to use them together.  I've got a home Q that initializes everything, including the color parameters, to 0.  Is there a way to eliminate this problem.

Thanks,

Pete Dursin - ME - City of Bowie, Md.

Parents
  • It's been a while since I sat at the programming desk, but I'll give this a go.

    How are you recording the submasters? Are you just hitting: Record + Sub + [Number] + Enter?
  • Has someone at ETC done a wiki article on this? It seems to come up fairly often. Also please jump in if I've missed a point.

    The issues is that color is an LTP property and Intensity is an HTP. Add to that, most fixtures have white (all LEDs full) as their 'home' setting. I-masters have color saved in them unless you clear it out on purpose. So color acts much like an effect where you can use the bumps to de/activate that setting. Submasters have gotten significant upgrades in the last few updates to help with smoothly applying colors set in them, but it's still a confusing area.

    There are several solutions; make a new fixture profile with the color home values at 0, clear out the color levels and have only one color address on each submaster. If you had an Ion or better you could set a home preset. (for others reading this) I like to put intensity on a separate sub from color information. That way I can know clearly which set of information I'm changing.

    Note that color formats get a huge re-write in v2.3 so you probably don't want to do something with HS values until you upgrade. And I strongly recommend updating, I am in awe of the new color tools as they now work the way I think about color.

    Is that clear?

  • I'm running S4 Luster 2 fixtures in Hue - Saturation - Intensity mode. The saturation at zero with an intensity above zero and any hue produces white light. My basic set up for all of the fixtures places a "hard" zero in each fixture's hue, saturation and intensity field. My real problem is that bringing up a color setting in one channel is wiping out the color setting in a different channel that is not referenced in the submaster that causes the problem. Color is an LTP but only on the channels that are specifically being changed. I don't have this problem with cues. I'm also not having any problem with intensity control - each sub controls only it's assigned channels. The sub I-master setting is supposed to "lock-in" the color settings so that they won't change with the intensity. That seems to work as I don't get color changes on an individual sub as I change the intensity.

    I'm looking at V2.3. We do 9 productions per year here and I have to have a schedule gap to bring up a new release. At this point, I can get any custom or gel color the designer wants from the color picker and direct edit capabilities in V2.2.1, so that's not an issue.
  • HSI mode will not allow anything other that LTP fades regardless of their source.

    Did you know that you can program in HSI while the fixtures are set to Direct? In v2.3 you can jump from HSI to native to RGB to CIExy at any time. Then there are Color Paths, I'm still trying to get that into my head.

  • Pete, I will read through you posts on a bit, but what caught my eye is that you have heard zeros in stuff you don't want to control, instead you should have nothing there. Nothing and zero is not the same thing
Reply Children
No Data
Related