D::Light and QLab ?

Hi everybody,

i'm looking for a light console software to use with QLab ( figure53.com ).

Basically, simply i need a light console that accept midi signals in input - and that can run the cue associated to "velocity" parameter.

Is :Light able to do that? anyone using it in association with QLab?

bye

michele

hi,

:Light is referenced on QLab site as "friendly" software.

i do not use Qlab, but :Light accept midi signal as input.

Basically, simply i need a light console that accept midi signals in input - and that can run the cue associated to "velocity" parameter.

what's your point?
velocity is 0-127 level signal. will you associate Cue 1 to 1, Cue 2 to 2, etc... ?

:Light can be triggered with NoteO, Program change, Control Change and SysEx message.

++
nico

My problem is more basic: I can't make the two program connect. I presume that in d::light midi setting, I should see "qlab" option to choose, if qlab is opened, to tell which source midi signals will come from. But I can't see any choiche. In te same way, under qlab workspace preference, tab midi, I should be able to choose d:light as destination of midi signals. But I can't see it, even i ran it before running qlab.

on Mac platform there's an internal MidiLoop called IAC bus (i don't really know the word in english).

i guess that you have to activate it.
it's in /Applications/Utility/Sound and midi configuration (at least in french....).

after in :Light menu /Display/Setup/MidiInput, you should see IaC bus as possible input.
you have to make :Light listenning on IAC and Qlab emetting on IAC.

tell if it works.

++

I am actually using QLab and :Light on MacBook Pro, and it has solved all my problems.
I confirm that QLab sends midi signals accross the IAC bus (Inter Application Communication) and that :Light receives them with no trouble.
I usually set the Midi input of :Light to "Multiple", that way it receives simultaneously from QLab and a BCR2000.

Great, thanks everybody, now works.
I had no chanche to discover by myself that i had to flag IAC on that hidden utility... if i can give a suggest, it could be documented in the manual.

Another question: is the communication langage between QLAb and :Light the same i learned for miniStageConsole - form QLab, a midi cue with "note on" signal, channel and note number 1, and velocity as a number, fires the "velocity" cue on :Light ????

Should i set up anything else?

bye
mic

Interesting... does BCR2000 works also with output from D:Light - so, faders move when D:Light changes cue? Does i need to configure it in some way? What should i choose as "Midi output" in :Light?

BCR2000 has rotary faders with light indicators for the level.
I do in fact have trouble (inconsistent behaviour) with the feedback from :Light to these level indicators.

is the communication langage between QLAb and :Light the same i learned for miniStageConsole - form QLab, a midi cue with "note on" signal, channel and note number 1, and velocity as a number, fires the "velocity" cue on :Light ????

in DL, you can use NoteOn to triger Go
you can use ProgramChange to trigger in X2 (the green register) the step you want (beware : the step, not the cue)

there's no velocity concept un DL


++
nico