Thanks for the link, food for thoughts.
In my setup, everything is centered around bitwig studio, which sometimes is synced to traktor, sometimes running standalone for just making music (grooveboxes, synths). Ideally, bitwig controls lighting gear as if that was "just another synth". So that is what I look for in lighting desk software: Define atomic elements, like a certain shutter or dimmer setting, then build makros, like "all scanners blue 80%" and finally create scenes that can be called via MIDI Notes from bitwig. Like you build a sound using OSCs, LFOs, Envelopes etc. Keeping number intensive things local to avoid the MIDI bus getting clogged: Like a synth has LFOs, some can sync to BPM, others run freely. If one were to create that within bitwig and then send tons of CC over the wire... you get the idea. So ideally, a lighting software does not think in SMPTE/MTC, but in MIDI clock, bars, quarters etc. Not many do, though.
Given this atom-macro-scene structure, it´s also possible to mix bitwig playback with live interaction: call some existing, non-overloaded scenes to create a basic mood (all bars red at 50%), then fingerdrum macro elements (all scanners white 100%) over it by hand. It´s interesting how much more intensive that gets if you, for example, follow a lead sound not just in tempo, but also flash elements as long as notes are played. It´s a similar step up as in: unsynced light to light in sync.
And now that I get more into LED territory, I´m looking for the right software package to fit into the big picture.