9
« on: November 17, 2019, 02:22:09 PM »
A quick update - I tried setting the gamma in FPP instead of xLights, but it has the same effect. To make matters worse, my pixels don't light at all until they receive an absolute R, G, or B value of 3 which translates to an xLights value of 35 (under a 2.22 gamma curve) and a value of 175 (under a 2.2 gamma curve and brightness slider set to 20). This is obviously not acceptable as more than half of all the brightness values are not showing up in the display. This was less of an issue last year when most of my effects were more of an on or off, but now with shaders and using more complex color and brightness variations, nothing looks even close to the same as a 100% brightness and 1.0 gamma. I realize this must not be a hot topic for others, but I don't understand why. When you limit the brightness at the controller it doesn't clip as much info as when you limit brightness in xLights?
In image editing, brightness affects the brightness of all pixels (even black). In xLights, brightness doesn't affect black, so it's really contrast because it only affects the slope, not the height, of the curve. It appears xLights has no way to specify a vertical offset or minimum value other than a custom dimming curve from a file.
Can anyone please provide an example of the format for a dimming curve? I can't find one. For instance, this is the format for a value curve:
<?xml version="1.0" encoding="UTF-8"?>
<valuecurve
data="Active=TRUE|Id=ID_VALUECURVE_XVC|Type=Custom|Min=0.00|Max=100.00|RV=TRUE|Values=0.00:0.00;0.00:0.00;0.05:0.22;0.10:0.32;0.15:0.39;0.20:0.45;0.25:0.50;0.30:0.55;0.35:0.59;0.40:0.63;0.45:0.67;0.50:0.71;0.55:0.74;0.60:0.77;0.65:0.81;0.70:0.84;0.75:0.87;0.80:0.89;0.85:0.92;0.90:0.95;0.95:0.97
|" SourceVersion="2018.55" >
</valuecurve>
I tried changing the words valuecurve to dimmingcurve, but there is an exception error in xLights when it tries to load it. I can't seem to find an example anywhere. Can anyone help?