Qlcplus Midi
Giorgio Aguilar
Hi Jeff, this is acutally quite simple. Do you use a Mac? This guide is pretty helpful: -virtual-MIDI-buses-live/
I have tried it and it works great. What i have done is select the IAC-Device as the input in QLC+ and then used that to trigger certain scenes, by grabbing the midi value ableton sends and using that as a trigger. If you need any further assistance i can make some screenshots illustrating how i did it.
I've experienced similar issues. I think there's a problem with the
IAC driver. Try using a Midi Monitor tool to look into the MIDI
messaging. I get very strange behavior, sometimes one single note
press can trigger tenths of both Note On and Note Off messages. Very
weird.
I key in a MIDI note on Logic, the scene starts and the green frame is there. Hitting the key again does not make the scene stop. I also programmed an "all-stop" button. It works once every 5 or 6 times. Most of the time, there's nothing happening. Hitting any key, but there is no effect in QLC+.
It would help if you can run some MIDI logger to see what specific MIDI event Logic sends,
so that we can adjust QLC+. From the brief look at the sources, the button should be pressed when Note On comes with velocity > 0; velocity == 0 means Note off, and both are ignored.
I have used a different approach. I send the note from my DAW the entire time that certain scene needs to be triggered and set the scene to Flash function. This way as soon as the MIDI note stops being sent by the DAW the scene will stop. This is the most useful way of handling scenes, because you dont need to think of a stop command but only have to worry about the length of the note being sent.
However, I managed to implement your approach in Ableton without any problem. Could you maybe specify how your setup looks inside of Logic?
I have tested multiple versions and found out that the toggle function needs a decent space between two notes being sent. For example if you want to stop your first scene you send that specific note. Unfortunately most of the times you don't want to go dark between two scenes, so you would send a midi note to trigger the next scene at exactly the same time. I did not manage to get this to work. But: As i described above, setting the QLC+ buttons to flash, makes it possible to make an immediate transition between two scenes. Have you tried that approach? I attached screenshots of my configuration. Since i only have ableton i used that, but it is similar to Logics setup.
I finally found out why Logic Pro X behaved so weird. When creating a
new External MIDI channel, the "Record" button was automatically
turned on (colored red). This seems to create some sort of loop of
MIDI messages. Unblocking the small red R-button on the MIDI track
made Logic Pro X behave just as expected, with perfect accuracy.
This tutorial explains how to drive QLC+ via MIDI from Mixxx. Mixxx is an open source DJ application, running on Windows, Mac OSX and Linux. The light effects are geared to a disco setup and we will use the beat detection of Mixxx to drive light effects synchronized with music.
This will enable the sending of Midi events. You can now run a midi monitor, like 'kmidimon', connect it to the 'Midi Through' device and look at the all the events. Be careful, Mixxx sends 40 events 25 times per second. It to my kmdimon only a minute or two to hang because of overload.
In the Profile tab of the 'Inputs/Outputs' screen, add a new Input Profile. I called it 'Mixxx' and model 'MIDI'.
Here we need to add a Channel for each MIDI message we expect from Mixxx. The list of Midi messages is documented in the file 'VU-Meter_Info.txt' you got with the Mixxx plugin script.
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.
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).
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.
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.
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.
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 ??
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
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:
=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 - -share.com/software/multiplay/)
I hope this is able to shed some light (no pun intended) on the trigger problem.
I've been using this set up for about 2 years and it's fantastic. However I've recently added a dmx lighting system to my set up... I have used QLC+ to create my virtual lighting desk, which is powered by a midi track in Logic (notes and other midi controls to control different lights and functions)
Then I encountered an issue.. The virtual instruments I use during some songs weren't making any sound when I hit keys on my novation, but only reacting to the midi track that is controlling my lighting... I have the virtual instruments set to Midi Channel 2 and my IAC driver set to Channel 1.
ff7609af8f