udp listener / input & pure headless ops
Posted: Tue Dec 27, 2016 12:48 am
hi i'm just studying qlc+ and whether it could be a solution for me...
topic is home automation / architectural lighting.
to integrate qlc+ into home automation, ideally, fixtures should individually be commandable by UDP with fixture name/value combinations. so that the abstraction of dmx channels, rgb(w) order, fading, color effects etc... happens/remains at the qlc+ level.
also, ideally the type of command/command options could contain whether to jump to a new value immediately or whether to fade and if, at what speed.
color fades should mathematically happen via a colorspace conversion (from RGB to HSL for example for smooth transitions). input would be a target hex rgb color value.
also, some further abstraction per fixture such as 0%-100% or on/off commands, resulting in the matching 0-255 dmx value would be welcome.
all of this should run purely headless / only manageable through ssh & the webinterface (and operation via udp) on a raspberry pi 3. so, even (up)loading the workspace file, checking log files etc... should all work browser or ssh-based only without the graphical output via hdmi. also some basic security/access rights on the web server would be needed (but not necessarily on the udp inputs).
maybe some of that already is doable but i couldn't determine straight away from documentation.
will certainly donate if these features would be onboard.
cheers!
topic is home automation / architectural lighting.
to integrate qlc+ into home automation, ideally, fixtures should individually be commandable by UDP with fixture name/value combinations. so that the abstraction of dmx channels, rgb(w) order, fading, color effects etc... happens/remains at the qlc+ level.
also, ideally the type of command/command options could contain whether to jump to a new value immediately or whether to fade and if, at what speed.
color fades should mathematically happen via a colorspace conversion (from RGB to HSL for example for smooth transitions). input would be a target hex rgb color value.
also, some further abstraction per fixture such as 0%-100% or on/off commands, resulting in the matching 0-255 dmx value would be welcome.
all of this should run purely headless / only manageable through ssh & the webinterface (and operation via udp) on a raspberry pi 3. so, even (up)loading the workspace file, checking log files etc... should all work browser or ssh-based only without the graphical output via hdmi. also some basic security/access rights on the web server would be needed (but not necessarily on the udp inputs).
maybe some of that already is doable but i couldn't determine straight away from documentation.
will certainly donate if these features would be onboard.
cheers!
)