• State Not Answered
  • Date
    Ranger
  • Date
  • Replies 5 replies
  • Subscribers 186 subscribers
  • Views 4693 views
  • Users 0 members are here

Custom LED bi color 16 bit patch on Ion with latest updates.

Using generic bi-color leds on 4 channel 16 bit encoders. With the basic 16 bit patch they appear to work ok. But to use the "true"16 bit potential I'm under the impression that I have to use decimal for smoother dimming curves at low levels. When I change the intens user max to 255 it auto resets to 100% . So I tried converting the warm white and white to intensity 2 and 3 and make a master intensity but still will not allow 255.  Am I wrong to assume I can use decimal for user max with these basic decoders? I have converted and am using arri sky panels with this decimal adjustment. And they work great.  It apears as if the intens is just a percentage of the two leds therefore will only give 100 percent options.

What I hope to achieve is to color blend the two leds and then use intensity to move level and keep color unchanged.  Thanks in advance.

  • 0
    I think I understand what you are looking for.
    If you are using a profile that has DMX and LDMX addresses then the console will use both of those to build a 16bit channel. You still use the 0-100% for control but it interpolates the two and when they are used together in the fixture you get the fine control. If you hold down the data key while changing the value you can see the sub% value changing. If you hold the shift key the values will change at a slower rate so you can get the minute change you are looking for.
    What profile are you using with the lights.
    When you change the overall intensity with low levels of one or the other of the colors they will drop out at some point. bicolor control of white light sorta sucks. You can't just set a color temp and then drastically change the intensity and expect it to be accurate. Also my experience with most units that are just using WW/CW emitters is that you are great at either end of the color spectrum but when you mix the two the CRI goes bad.
    You can set DMX levels on a attribute using the @// to get DMX on the command line and then enter a DMX value there.

    Hope this helps.
  • 0 in reply to Druuka
    That kind of answers my question. So I'm using 16 bit version of generic LED Ww Cw. Also using a RGBAW generic 16 bit profile. Both behave the same way. If I use decimal 255 for user max on both they only dim from 100 down on both so 100 to 255 user max no change. I figured the 255 would give more points in between to give smoother dimming. Or does it not matter, 16 bit means it's as smooth at it gets?
  • 0 in reply to Ranger

    16 bit means you have 65535 steps between 0 and full.  This is as smooth as you are going to get a 16bit fixture to dim no matter what the user max value is.  255 is just the max value for one dmx channel.  The console and fixture use two of these together to make the 65535.

     

  • 0 in reply to Druuka
    i think the issue is the virtual dimming. as long as there is native dimming in the moving light, the manufacturer decides, if it should be 8 or 16 bit. but if it's virtual, it's up to the combination of console and fixture manufacturer.
    virtual dimming means, that the fixture has no direct intensity parameter but only color parameters. if virtual intensity is at full, all color values are passed to the fixture. if virtual dimmer is at 0, no color values are passed along. with virtual dimming at 50, only half the value of each color parameter makes it to the fixture.
    so the question is, with virtual dimming and 16bit color parameters, does Eos multiply with 100 steps, 255 or 65536?
  • 0 in reply to ueliriegg
    >>so the question is, with virtual dimming and 16bit color parameters, does Eos multiply with 100 steps, 255 or 65536?

    Eos will treat the virtual intensity as 16 bit in this case and fade with 65536 steps, not 255. We just checked this out to confirm it too.
Related

www.etcconnect.com