Personal tools
The Open Lighting Project has moved!

We've launched our new site at www.openlighting.org. This wiki will remain and be updated with more technical information.

Difference between revisions of "Talk:Q Light Controller (QLC)"

From wiki.openlighting.org

Jump to: navigation, search
(New page: The page could mention interesting features. The following is take partly from the old web site at qlc.sf.net: Features * Device-oriented interface * Control one DMX Universe, up to 512 ...)
 
(Additional ideas for written info)
 
(4 intermediate revisions by 2 users not shown)
Line 1: Line 1:
 
The page could mention interesting features.
 
The page could mention interesting features.
  
The following is take partly from the old web site at qlc.sf.net:
+
Or how to operate QLC and its features.
Features
 
  
* Device-oriented interface
+
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.
* Control one DMX Universe, up to 512 DMX or Analog channels
+
 
* Define your own fixtures with the device class editor™
+
== Additional ideas for written info ==
* Create fast changing or smoothly fading scenes, chasers and sequences
+
 
* Easy programming of moving lights through a pattern generator
+
The [[DMX]] start code is fixed to 0, I think (stated on the mailing list?).
* Conjure your favourite lighting desk layout with the virtual console™
+
 
 +
No support for [[RDM]], but it is possible to code that functionality?
 +
 
 +
 
 +
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?
 +
 
 +
> depends on the OS you use.
 +
 
 +
How well does it work with a touch screen?
 +
 
 +
> great. tested on resistive, SAW and multitouch screens.
 +
 
 +
Can keyboard buttons and shortcuts be assigned to functions?
 +
 
 +
Can steps/scenes be changed, like proceed to next step by MIDI commands?
 +
 
 +
> yes. Via Button / Input functions
 +
 
 +
How can chase speed be controlled? Is there a tap sync for global speed and/or selected chases?
 +
 
 +
Can colour/intensity/iris function values be assigned to sine/cosine/triangle/sawtooth time functions?
 +
 
 +
Is it possible to offset DMX values just before the output, or to offset colour/position/etc. values?
 +
 
 +
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?
 +
 
 +
 
 +
Perhaps the answers to these questions should go in a different page than the page with the QLC overview, perhaps name "QLC Usage details".

Latest revision as of 04:36, 27 April 2012

The page could mention interesting features.

Or how to operate QLC and its features.

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.

Additional ideas for written info

The DMX start code is fixed to 0, I think (stated on the mailing list?).

No support for RDM, but it is possible to code that functionality?


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?

> depends on the OS you use.

How well does it work with a touch screen?

> great. tested on resistive, SAW and multitouch screens.

Can keyboard buttons and shortcuts be assigned to functions?

Can steps/scenes be changed, like proceed to next step by MIDI commands?

> yes. Via Button / Input functions

How can chase speed be controlled? Is there a tap sync for global speed and/or selected chases?

Can colour/intensity/iris function values be assigned to sine/cosine/triangle/sawtooth time functions?

Is it possible to offset DMX values just before the output, or to offset colour/position/etc. values?

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?


Perhaps the answers to these questions should go in a different page than the page with the QLC overview, perhaps name "QLC Usage details".