https://wiki.openlighting.org/api.php?action=feedcontributions&feedformat=atom&user=78.34.104.111 2026-09-23T13:15:44Z User contributions MediaWiki 1.29.1 https://wiki.openlighting.org/index.php?title=Talk:Q_Light_Controller_(QLC)&diff=4140 2012-04-27T11:36:29Z

<p>78.34.104.111: /* Additional ideas for written info */</p> <hr /> <div>The page could mention interesting features.<br /> <br /> Or how to operate QLC and its features.<br /> <br /> E.g how to modify (move or squeeze) a pattern of pan/tilt, adjust intensity or colors with a offset to intensity or CMY/RGB values.<br /> <br /> == Additional ideas for written info ==<br /> <br /> The [[DMX]] start code is fixed to 0, I think (stated on the mailing list?).<br /> <br /> No support for [[RDM]], but it is possible to code that functionality?<br /> <br /> <br /> Can QLC be remote controlled from hand-held devices, i.e. to turn lamps on/off while being on stage, a ladder, out of reach of the computer running QLC?<br /> <br /> &gt; depends on the OS you use.<br /> <br /> How well does it work with a touch screen?<br /> <br /> &gt; great. tested on resistive, SAW and multitouch screens.<br /> <br /> Can keyboard buttons and shortcuts be assigned to functions?<br /> <br /> Can steps/scenes be changed, like proceed to next step by MIDI commands?<br /> <br /> &gt; yes. Via Button / Input functions<br /> <br /> How can chase speed be controlled? Is there a tap sync for global speed and/or selected chases?<br /> <br /> Can colour/intensity/iris function values be assigned to sine/cosine/triangle/sawtooth time functions?<br /> <br /> Is it possible to offset DMX values just before the output, or to offset colour/position/etc. values?<br /> <br /> If I make many scenes/steps that uses certain positions over and over again, is it possible to store e.g. x/y positions as a pre-set (or variable) instead of a hard-coded value in each step, in a way that the pre-set is a position (set of values), that can be changed and affect all steps that use that pre-set?<br /> <br /> <br /> Perhaps the answers to these questions should go in a different page than the page with the QLC overview, perhaps name &quot;QLC Usage details&quot;.</div>

78.34.104.111 https://wiki.openlighting.org/index.php?title=Talk:Q_Light_Controller_(QLC)&diff=4139 2012-04-27T11:36:02Z

<p>78.34.104.111: /* Additional ideas for written info */</p> <hr /> <div>The page could mention interesting features.<br /> <br /> Or how to operate QLC and its features.<br /> <br /> E.g how to modify (move or squeeze) a pattern of pan/tilt, adjust intensity or colors with a offset to intensity or CMY/RGB values.<br /> <br /> == Additional ideas for written info ==<br /> <br /> The [[DMX]] start code is fixed to 0, I think (stated on the mailing list?).<br /> <br /> No support for [[RDM]], but it is possible to code that functionality?<br /> <br /> <br /> Can QLC be remote controlled from hand-held devices, i.e. to turn lamps on/off while being on stage, a ladder, out of reach of the computer running QLC?<br /> <br /> &gt; deends on the OS you use.<br /> <br /> How well does it work with a touch screen?<br /> <br /> &gt; great. test on resistive, SAW and multitouch screens.<br /> <br /> Can keyboard buttons and shortcuts be assigned to functions?<br /> <br /> Can steps/scenes be changed, like proceed to next step by MIDI commands?<br /> <br /> &gt; yes. Via Button / Input functions<br /> <br /> How can chase speed be controlled? Is there a tap sync for global speed and/or selected chases?<br /> <br /> Can colour/intensity/iris function values be assigned to sine/cosine/triangle/sawtooth time functions?<br /> <br /> Is it possible to offset DMX values just before the output, or to offset colour/position/etc. values?<br /> <br /> If I make many scenes/steps that uses certain positions over and over again, is it possible to store e.g. x/y positions as a pre-set (or variable) instead of a hard-coded value in each step, in a way that the pre-set is a position (set of values), that can be changed and affect all steps that use that pre-set?<br /> <br /> <br /> Perhaps the answers to these questions should go in a different page than the page with the QLC overview, perhaps name &quot;QLC Usage details&quot;.</div>

78.34.104.111