Too bad that it’s a hardware dependency. A really awesome differentiating feature for Red Series would be to select leading-edge vs. trailing-edge dimming from a parameter.
The video also touched on another difference between various dimmers (though it didn’t highlight it specifically): dimming curves. When he noted (@ 05:52) that he couldn’t tell the difference between 75% and 100%, that sounds like a dimming curve issue: the perceived brightness does not always scale linearly with input power for all types of lights/drivers. (He also complained about the lights turning off around 35%, which means he didn’t setup parameter 5…) This does seem like something that could be done in firmware, and there’s even a Suggestions/Wishlist thread open for it. In some sense, we already do this: if parameters 5 and 6 are set to, say, 40% and 90% respectively, then the setLevel commands appear to be rescaled into the desired range. Presumably this is a linear interpolation, but this is where other functions could be used. (Interestingly, it seems that the interpolation is done with setLevel commands sent from the hub, but is not done when the level is set from a “default level” parameter/child device; but I should probably open a new thread about that one…)
That said, I’ve managed to solve most of my LED issues with a combination of minimum-level calibration and/or an Aeotec bypass.