I am trying to control QLC+ by MIDIx and cannot get it to work.
It's a live theatre application. We use SCS for sound cues,
and would like the Midi output control from SCS to trigger
"next" cues in QLC+ for lighting changes. We have done 2 shows now with the 2 systems separate, but would now like to have sound and lighting ties together.
I can see the "joystick" appear each time a cue is started on SCS,
so the MIDI is getting to QLC+ OK.
On the INPUT/OUTPUT tab, it saya
Input 1: LoopBe Internal MIDI
Status: Open
But nothing happens to QLC+...
The setup is WIN 7 / LoopBE1 for MIDI, ENTTEC DMX PLUS for DMX / Single Universe
Your help will be greatly appreciated.
I'm getting to the last few strands of hair. :-)
Many TIA's
David
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
did you create a cue list widget, and assign proper External Input in the Next Cue page in properties?
What MIDI message does SCS send to QLC+? Does it use MIDI show control (MSC)? MSC is not currently supported, you have to use either CC, PC, or Note On (maybe few others as well).
If everything else fails, you may try running sound cues from QLC+and or sending Cue signals from QLC+ to SCS (though I'm not sure whether is it easier...).
Many thanks for the reply.
Cue List widget - Yes.
Just 2 entries as a test.
Midi message is Program Change.
(SCS can send choice of PC 0-127, PC 0-128, CC, Note on, Note Off, MSC, Free format, or file.)
I used the following procedure.
Select OPERATE mode,
Select Virtual Console,
Right-click cuelist widget,
Select Widget properties,
Select NEXT CUE tab,
Click AUTODETECT,
Go to SCS,select NEXT CUE,
which is a MIDI SEND PC, Channel 1, Program 1,
On QLC+ External Input, it saya
Input Universe 1:LoopBe LoopBe1
Input Channel 385:?
(Yes - "385:?" ) 385 Colon QuestionMark.
What does 385 mean ??
If I switch to OPERATE mode and step through cues on SCS,
there is no response for QLC+
SCS Version is 11.1.6 (Current). Version is Professional>
you are using QLC+ 4.6.1. You may try preview version 4.7.0 from the development thread. It is not recommended for production use, but since 4.6.1 wasn't very stable, 4.7.0 may be more stable.
385 means Channel 1, Program Change 1 - mapping from MIDI events to channels is described in online help in MIDI plugin page. Question mark means that no description is given to the channel (for MIDI controllers like Behringer BCF2000, you can make profile for the controls, so you'd have something like "Fader 7", or "Button 8 Top" there).
There is no MIDI binding for the next cue in your file. I'm not sure how that happened.
You may try to move the MIDI input to Universe 2 - since Universe 1 is used for DMX output (you may have different inputs and outputs for one universe technically, but let's play safe).
If everything fails, open your qxw file in text editor, and replace
Jano, how can version 4.7.0 possibly help David in this case ?
I think we haven't changed anything that might be related to his issue, which as far as I can tell from the project, seems to be a non-existant input association.
Maybe he just cliked on the window "X" or "cancel" instead of on "OK"
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I need to "click" the "NEXT CUE" button on the Cue List on the Virtual Console by sending a MIDI control send command from another program on the same PC.
or
Is it possible to go to a specific cue in the cue list on the Virtual Console by sending a MIDI control send command from another program on the same PC.
Thanks again,
David
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I think you have to do the same as you did once more, sincet he setting was not saved for some reason.
If you want direct cue control, you have to create solo frame with button for each cue. Then assign each button separate midi message (e.g. one note per button/cue).
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Have tried using both LoopB1, and LoopMidi to send cues from SCS. I've tried sending Program Change 127 cues, PC128, Control Change, and Note On messages. In all cases, I can see the "Joystick" appear, but the Cue List in virtual console remains stuck at Scene 1 and does not step to the next cue under program control.
Any suggestions ???
Thanks
David
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I don't know SCS but I had the same problem using Cakewalk Sonar. Joystick icon appears but midi was ignored. The problem was that the durations of the midi events where too short. Try longer note durations.
Last edit: Darrow 2014-03-06
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thanks for the suggestion.
I tried that, but still no joy.
Am going to do a quick Youtube showing the problem, and the process being used, in the hope someone can give me a clue as to what I'm doing wrong ??
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi, I've had a quick look at your video (it's very long, didn't have the time to watch it all)
I've got a couple of possible ideas why that's happening:
- SCS is sending MIDI signals that are too short for QLC+
- SCS is sending only the NOTE ON signal, and never a NOTE OFF. So QLC+ doesn't trigger to release the previous command
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Just a quick reply hope it help, but i use qlc+ with live, and it worked only when we told Live to send CC (control change) values and when the note were not too short
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hey mates. I think my problem is related to this. I have been trying to make a new midi controller to my projects by using Akai MPD18. QLC+ can learn all the 16 buttons plus also 3 different banks. So I would have 48 options to play around. But problem starts when I try to assign buttons to any buttons in Virtual Console. Buttons work and tricker scenes when I press them by mouse or by keyboard buttons. I can assign any midi buttons to External input and Auto Detect works, but then when I'm in opetera mode buttons do not work. I can still see the 'joystick' icon on Inputs/Outputs-page but buttons don't tricker anything. I have tried differend modes (Note velocity, Control Change and Program Change), but they don't help. Any suggestions?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
David Gemmell and others.
I have managed to figure out the problem with not getting QLC+ Cue List to react to a MIDI command.
I was not specifying Data 2 in my Multiplay audio cue program's MIDI cue properties box. This is a setting between 0-127, I think the velocity or duration of a midi instruction. Setting this will trigger play and next cue in QLC+.
I also found I needed to add a second Control Change command for each MIDI trigger cue in Multiplay with a velocity of 0 which stops the trigger in QLC+ making it ready to listen for the next trigger.
A post on the Free Styler forum was where I got my inspiration: http://www.freestylersupport.com/fsforum/viewtopic.php?f=38&t=5567
I have not experimented with CTR Electronics' CSC Show Control yet (MIDI control needs a full licence to save a show).
(Multiplay Theatre Cue Control - http://www.da-share.com/software/multiplay/)
I hope this is able to shed some light (no pun intended) on the trigger problem.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi,
I am trying to control QLC+ by MIDIx and cannot get it to work.
It's a live theatre application. We use SCS for sound cues,
and would like the Midi output control from SCS to trigger
"next" cues in QLC+ for lighting changes. We have done 2 shows now with the 2 systems separate, but would now like to have sound and lighting ties together.
I can see the "joystick" appear each time a cue is started on SCS,
so the MIDI is getting to QLC+ OK.
On the INPUT/OUTPUT tab, it saya
Input 1: LoopBe Internal MIDI
Status: Open
But nothing happens to QLC+...
The setup is WIN 7 / LoopBE1 for MIDI, ENTTEC DMX PLUS for DMX / Single Universe
Your help will be greatly appreciated.
I'm getting to the last few strands of hair. :-)
Many TIA's
David
David,
did you create a cue list widget, and assign proper External Input in the Next Cue page in properties?
What MIDI message does SCS send to QLC+? Does it use MIDI show control (MSC)? MSC is not currently supported, you have to use either CC, PC, or Note On (maybe few others as well).
Can you attach your qxw file here?
SCS: Is it this software? http://www.showcuesystems.com/ What version (Lite/Pro/...)?
If everything else fails, you may try running sound cues from QLC+and or sending Cue signals from QLC+ to SCS (though I'm not sure whether is it easier...).
Note to self: MSC spec: http://www.richmondsounddesign.com/docs/midi-show-control-specification.pdf
Last edit: Jano Svitok 2014-02-28
Hi Jano,
Many thanks for the reply.
Cue List widget - Yes.
Just 2 entries as a test.
Midi message is Program Change.
(SCS can send choice of PC 0-127, PC 0-128, CC, Note on, Note Off, MSC, Free format, or file.)
I used the following procedure.
Select OPERATE mode,
Select Virtual Console,
Right-click cuelist widget,
Select Widget properties,
Select NEXT CUE tab,
Click AUTODETECT,
Go to SCS,select NEXT CUE,
which is a MIDI SEND PC, Channel 1, Program 1,
On QLC+ External Input, it saya
Input Universe 1:LoopBe LoopBe1
Input Channel 385:?
(Yes - "385:?" ) 385 Colon QuestionMark.
What does 385 mean ??
If I switch to OPERATE mode and step through cues on SCS,
there is no response for QLC+
SCS Version is 11.1.6 (Current). Version is Professional>
QXW file attached.
Many thanks !!
David
Hi,
you are using QLC+ 4.6.1. You may try preview version 4.7.0 from the development thread. It is not recommended for production use, but since 4.6.1 wasn't very stable, 4.7.0 may be more stable.
385 means Channel 1, Program Change 1 - mapping from MIDI events to channels is described in online help in MIDI plugin page. Question mark means that no description is given to the channel (for MIDI controllers like Behringer BCF2000, you can make profile for the controls, so you'd have something like "Fader 7", or "Button 8 Top" there).
There is no MIDI binding for the next cue in your file. I'm not sure how that happened.
You may try to move the MIDI input to Universe 2 - since Universe 1 is used for DMX output (you may have different inputs and outputs for one universe technically, but let's play safe).
If everything fails, open your qxw file in text editor, and replace
with
(the numbers are one-less than you see in GUI).
Jano
Jano, how can version 4.7.0 possibly help David in this case ?
I think we haven't changed anything that might be related to his issue, which as far as I can tell from the project, seems to be a non-existant input association.
Maybe he just cliked on the window "X" or "cancel" instead of on "OK"
Hi,
I may not have made clear what I need to do?
I need to "click" the "NEXT CUE" button on the Cue List on the Virtual Console by sending a MIDI control send command from another program on the same PC.
or
Is it possible to go to a specific cue in the cue list on the Virtual Console by sending a MIDI control send command from another program on the same PC.
Thanks again,
David
You were clear enough.
I think you have to do the same as you did once more, sincet he setting was not saved for some reason.
If you want direct cue control, you have to create solo frame with button for each cue. Then assign each button separate midi message (e.g. one note per button/cue).
Hi Jano / Massimo,
Thanks for the help, but I am at a dead end.
Have tried using both LoopB1, and LoopMidi to send cues from SCS. I've tried sending Program Change 127 cues, PC128, Control Change, and Note On messages. In all cases, I can see the "Joystick" appear, but the Cue List in virtual console remains stuck at Scene 1 and does not step to the next cue under program control.
Any suggestions ???
Thanks
David
I don't know SCS but I had the same problem using Cakewalk Sonar. Joystick icon appears but midi was ignored. The problem was that the durations of the midi events where too short. Try longer note durations.
Last edit: Darrow 2014-03-06
Hi Darrow,
Thanks for the suggestion.
I tried that, but still no joy.
Am going to do a quick Youtube showing the problem, and the process being used, in the hope someone can give me a clue as to what I'm doing wrong ??
Hi folks,
If you have a chance, please check out
http://www.youtube.com/watch?v=B3KO9k7pBZc&feature=youtu.be&hd=1
It shows the problem I'm having using QLC+ with SCS via MIDI.
Any suggestions ?
TIA
David
Hi, I've had a quick look at your video (it's very long, didn't have the time to watch it all)
I've got a couple of possible ideas why that's happening:
- SCS is sending MIDI signals that are too short for QLC+
- SCS is sending only the NOTE ON signal, and never a NOTE OFF. So QLC+ doesn't trigger to release the previous command
Just a quick reply hope it help, but i use qlc+ with live, and it worked only when we told Live to send CC (control change) values and when the note were not too short
im tryin with sonar also i can see that loopb1 is communicating but nothing else
someone?
ok it does work assign midi note but the cue doesnt stop??how can i make it stop so it can play another cue?
Hey mates. I think my problem is related to this. I have been trying to make a new midi controller to my projects by using Akai MPD18. QLC+ can learn all the 16 buttons plus also 3 different banks. So I would have 48 options to play around. But problem starts when I try to assign buttons to any buttons in Virtual Console. Buttons work and tricker scenes when I press them by mouse or by keyboard buttons. I can assign any midi buttons to External input and Auto Detect works, but then when I'm in opetera mode buttons do not work. I can still see the 'joystick' icon on Inputs/Outputs-page but buttons don't tricker anything. I have tried differend modes (Note velocity, Control Change and Program Change), but they don't help. Any suggestions?
David Gemmell and others.
I have managed to figure out the problem with not getting QLC+ Cue List to react to a MIDI command.
I was not specifying Data 2 in my Multiplay audio cue program's MIDI cue properties box. This is a setting between 0-127, I think the velocity or duration of a midi instruction. Setting this will trigger play and next cue in QLC+.
I also found I needed to add a second Control Change command for each MIDI trigger cue in Multiplay with a velocity of 0 which stops the trigger in QLC+ making it ready to listen for the next trigger.
A post on the Free Styler forum was where I got my inspiration:
http://www.freestylersupport.com/fsforum/viewtopic.php?f=38&t=5567
I have not experimented with CTR Electronics' CSC Show Control yet (MIDI control needs a full licence to save a show).
(Multiplay Theatre Cue Control - http://www.da-share.com/software/multiplay/)
I hope this is able to shed some light (no pun intended) on the trigger problem.