UPDATED: Incorrect mapping of RGB values to black and white presets on color wheel channels

[markov]

DasLight 5 seems to have been optimized for use with fixtures with independent RGB channels. That makes total sense and works great with those types of fixtures. However many fixtures (especially lower-cost ones) use a discrete set of colors implemented as a single “color wheel” DMX channel. These fixtures work perfectly in LightRider, but RGB values in DL5 appear to get mapped to color wheel presets solely based on hue & saturation, excluding luminance. Since “black” (RGB [0,0,0], i.e. beam off) and white (RGB [1,1,1]) have the same hue & saturation, they are not differentiated and therefore do not properly map to the corresponding color wheel presets. This means that trying to use any color FX (for example) that include white on fixtures that have both black and white color wheel presets *does not work* and ruins the effect, because DL5 presently maps the RGB value for white [1,1,1] to the black color wheel preset.

I believe this to be a bug in DL5.

[markov]

Since I haven't gotten a response, I decided to open a support case (ticket #66843) and report this as a bug.

[juls]

Hello,
Do ou have an example of library which has your problem ?

Regards

[markov]

Hi juls. Yes, I submitted support ticket #66843 to the DasLight help desk and it includes
- an example project that demonstrates the behavior,
- the profiles associated with the fixture in question, and
- a link to a video demonstration.

Please let me know if you are able to retrieve them from the case. The support engineer I was working with was Gabriel M.

[markov]

I sent you an email with all of the details from the support ticket Julien.

[juls]

Hello,

It seems you use an incorrect library of this profile.
You can download an correct version in our public cloud fixtures.

Unfortunately, this kind of fixtures are not completely managed in the 2D and 3D View.
It means you can control it but the color on the ring will not be representated.

Regards

[markov]

Hi Julien. This issue happens with other fixtures that I have as well, even when using official fixture profiles created by Nicolaudie.

I created another example project for a Chauvet DJ DerbyX fixture using the official fixture profile from Nicolaudie. Using that example project, I recorded a demonstration video that shows Daslight 5 improperly mapping RGB white & black to the color presets on the fixture’s color wheel channels. The recording also includes live video of the DerbyX fixture being controlled by Daslight, which shows that the 2D preview in Daslight matches what the fixture’s beams are actually doing. Both are behaving incorrectly.

When an RGB value of white [1,1,1] is set, Daslight incorrectly selects the black preset on the color wheel channel instead of the white preset.

When an RGB value of black [0,0,0] is set, Daslight does not select the black preset on the color wheel channel, but instead leaves it unchanged.

I would expect Daslight to be able to unambiguously map white, black, or any grayscale RGB value to the nearest color wheel preset.

In case it’s helpful, when I last checked, LightRider *does* properly map white and black RGB values to color wheel presets with this same fixture & profile. This mapping problem seems to be specific to Daslight.

Here is a link to the demonstration video: https://drive.google.com/file/d/1tHBlPs ... sp=sharing

The demo project used in the video is attached here (in a zip file):

Test Case2 project.zip

Example project used in demonstration video.

(4.21 KiB) Downloaded 104 times

[markov]

I was exchanging email messages on this topic with Julien, but that has gone dark and his perspective seemed to be that the behavior being exhibited by Daslight was a problem with the fixture or its profile rather than Daslight.

To help prove that that is not the case, I created a much simpler, hypothetical fixture profile for a 4 beam fixture with nothing but a single color wheel channel for each beam. The problem occurs regardless of the number of beams in the fixture. While this particular fixture is hypothetical, I have multiple fixtures that have color channels configured this way. It is common in lower-cost fixtures to only have on/off (rather than variable) control over the red, green, and blue LEDs, leading to the ability to only represent colors that are binary combinations of those LEDs, specifically, red (R), yellow (R+G), green (G), cyan (G+B), blue (B), magenta (B+R), and white (R+G+B). Daslight 5.0.4.2 is presently not capable of properly controlling such a fixture if it includes a white preset in the color channel. The RGB values for all of the other colors map to their associated presets perfectly, but white (and black) does not.

I hope that the dev team will acknowledge that this (and the related issue with black presets) is a bug in Daslight and get it fixed in a release shortly.

Here is a video demonstrating the bug: https://drive.google.com/file/d/1tqidBb ... sp=sharing

Attached are the project and fixture profile used in the above video:

Color Wheel vs RGB Test Case.zip

Daslight 5 project file and fixture profile used in demo video

(25.13 KiB) Downloaded 156 times

[willm]

Hello all,

Thanks for the detailed reports in this case! I have made a note of all of this on our reports list, so this will be fully investigated by the developers going forward.

Kind regards,
Will

[markov]

Thank you willm!