Hue and Saturation incorrect in Colour Pallet when reading .esf into 2.9

When opening a .esf file generated in 3.1.1.113 in version 2.9.1.17 the Hue and Saturation are VERY different.

these twelve CPs are from the "Standard" colours from Red round to Pink.  The above shows their values in version 3.1.1

Opening the same file in version 2.9.1.17 I see the same RGBW values but the Hue in particular is VERY different with a significant jump between CP 1005 and 1006 - there is a very distinct blue shift.

I can correct this if I update the value in 2.9 - same RGBW produces the Hue and Sat similar to version 3.1 but having to do this for ALL my CPs (many more than this 12) is a big pain.  I think the problem only happens on this "by type" channel which has a White parameter.

Is there some setting I can use that would make the Hue and Sat on opening the file be truer to the values seen in 3.1?

Parents
  • With the color format set as you have it, Hue and Saturation are calculated values from the RGBW. It is likely that in 3.1.1.113 there is newer more accurate calculations for HS for this particular fixture than in 2.9.1.

    This won't impact playback as the 'real' values are RGBW. Eos preserves data as much as possible, so in this situation when you re-apply the RGBW values in 2.9.1 it is recalculating the HS values using the color calculations in 2.9.1.

    Can you explain what the issue you are trying to resolve is here?

Reply
  • With the color format set as you have it, Hue and Saturation are calculated values from the RGBW. It is likely that in 3.1.1.113 there is newer more accurate calculations for HS for this particular fixture than in 2.9.1.

    This won't impact playback as the 'real' values are RGBW. Eos preserves data as much as possible, so in this situation when you re-apply the RGBW values in 2.9.1 it is recalculating the HS values using the color calculations in 2.9.1.

    Can you explain what the issue you are trying to resolve is here?

Children
Related