It's an experimental feature and has been replaced by the master lightness, at the last minute we decide to keep it for testing, who knows...I think we will suppress it, except if someone found something useful on it.
The value need to be a float and not an int (I can change it easily to support both if we keep that feature) from 0.0 (no effect) to 1.0 (and not 1) for a black out.
And that's true there is not control in the main UI for that, so the name of the keyword is not correct ('ctrl' are supposed to exist in the main UI)
I agree this is maybe not a t-shirt issue, but you win a t-shirt for you effort !
EDIT: I put a exemple module in the garagecube lib. : Fade to Black and Lightness (EXPERIMENTAL)
ghostofelvis100 wrote:new keyword ctrl_master_fadeToBlack does not seem to do anything, or even register as a keyword in the Direct Event module.
I guess I am doing the correct thing? Sending an integer boolean value to to the keyword (e.g.. val = 1 or val = 0):-
There's no info in the keyword browser to explain the keyword, plus there's no button in the interface for this yet.
Output Lightness values below 0.5 increase lightness to full on white out at 0. Should this not also fade to black at zero?
Little things, of little importance in what is otherwise an amazing work.
Not suggesting this is a t-shirt worthy bug, but a small/medium mens will do nicely ; )