Page 1 of 1

MIDI activation in Virtual Console do not work (QLC+ 4.7.2 & WIN7 32bit)

Posted: Sun Jun 15, 2014 1:31 am
by als
Hi Massimo,
Here is my configuration:
LoopMIDI.exe to create Midi virtual port under Windows
LoopMidi is recognized under input device: when it sends a message, the joystick appears in the Universe.
I defined an input profil in order to name each kind of Midi message.
The wizard recognized each message sent with a different number for each one.
When activating input in Virtual Console, nothing occurs. When pressing the button, the 2Dview displays lights.
Is there midi specific message to send? I used Program-Change because Control-Change is not recognized.
I send program-change 0 119 (0 for channel and 119 for value).
And QLC+ detects value 504
Is it normal?
Thanks in advance for your help
Regards
Alain

MIDI activation in Virtual Console do not work (QLC+ 4.7.2 & WIN7 32bit)

Posted: Sun Jun 15, 2014 9:58 am
by Jano Svitok
Alain,

check MIDI plugin documentation in the online help (you can see it also on the web at http://www.qlcplus.org/docs/midiplugin.html). At the end of the page there is a table of MIDI messages mapping to DMX channels. From the table you can see that program change 119 is mapped to DMX input channel 504.

CCs should be recognized as well, but there may be a bug that prevents it.

MIDI activation in Virtual Console do not work (QLC+ 4.7.2 & WIN7 32bit)

Posted: Sun Jun 15, 2014 9:46 pm
by als
Hello,
I sent thevmidi message on channel 0... but is it better to send a value of 1 for this ? The documentation explains channels values are between 1 and 16.
I will test it.
Regards
Alain

MIDI activation in Virtual Console do not work (QLC+ 4.7.2 & WIN7 32bit)

Posted: Mon Jun 16, 2014 5:30 am
by als
The value 0 is a right value for channel.
Detection is OK in input/output interca e and in detect LIDI interface.
It is more related to Virtual Console.
Regards
Alain

MIDI activation in Virtual Console do not work (QLC+ 4.7.2 & WIN7 32bit)

Posted: Mon Jun 16, 2014 6:11 am
by als
It works finally with control-change.
Maybe an issue with program-change ?
Alain