hello folks!
Zack here, new to the forum. I have just discovered QLC+ and am really impressed! I've been trying to figure out how I can cue my lighting scenes via Midi thru Mac's IAC Driver from another program on the same computer, Pro Presenter 6.
So right now, I have confirmed that I am getting Midi signal from Pro Presenter 6 to QLC+ because I see the joystick emblem appearing on the Universe 1 tab.
I have created a very basic 2 step chase and am trying to trigger that via Midi.
Here is what I'm doing, hopefully somebody could shed some light (no pun intended) on what I'm doing wrong
In Virtual Console, I made a cue list widget containing 2 scenes. In edit mode, I right click the widget to access properties, and under Playback, Input Universe, I have selected the Input profile I made, Channel 131, type button, in Universe 1 input 1 IAC Driver, output is uDMX.
I'm probably doing this all wrong and hoping someone can help me!
My end goal is to be able to sync my lighting scenes with Pro Presenters individual slides on screen, the new Pro Presenter 6 feature is that it can send Midi notes from individual slides, those my though was I could cue different lightings scenes with different slides.
any help would be greatly appreciated!!
Thanks for reading!!
-Zack
Trying to Cue Sequences via Midi from Pro Presenter on same computer
-
- Posts: 1331
- Joined: Mon Apr 13, 2015 7:05 am
- Location: Bratislava, Slovakia
- Real Name: Jano Svitok
- Contact:
Use separate universe for midi input (for example universe 2). Oher than that you are on good track. When that doesn't help, attach here your qxw file.
-
- Posts: 152
- Joined: Tue Apr 14, 2015 11:33 am
- Real Name: Tim Cullingworth
Hi Zack,
If you could attach your .qxw file it might help people see what is going on. Also probably less important in this case, but who knows, os and Qlc version.
The fact that you have got the little joystick is most of the battle. Have you tried using the auto detect feature?
If you could attach your .qxw file it might help people see what is going on. Also probably less important in this case, but who knows, os and Qlc version.
The fact that you have got the little joystick is most of the battle. Have you tried using the auto detect feature?
-
- Posts: 2
- Joined: Thu Jun 25, 2015 5:12 am
- Real Name: John Beckmeyer
Zack,
Did you ever figure this out?
I was trying to do a very similar thing - use Reaper and the ReaGate filter to kick out a midi note and then use that note to trigger a chaser's next cue. I failed that, but wound up getting around that by using a hardware DMX>>MIDI converter to send QLC+ midi notes.
That worked in the end but it did not solve my problem. But I did work out the mechanics of getting MIDI in to trigger chasers reliably.
Here's a couple of "learnings":
MIDI channel 1 value 1 gets picked up as MIDI 129 in QLC+ Cue List widget. QLC+'s audtodetect worked great for finding that offset in mapping.
When you set your MIDI input in the input/output tab in QLC+, _highlight the row_ that has your IAC driver, hit the tools button, and make sure the MIDI channel assigned to the IAC driver is the one that IAC is using to send towards QLC+ or the Cue List widget will never see it. IOTW, don't send a signal on MIDI Ch. 3 when QLC+ is expecting the MIDI note to come in on Ch. 1. Get QLC+ to listen on Ch. 3 if that's the channel you are sending on.
When you are selecting the MIDI channel by using the tools button on input/output tab, there is a MIDI channels 1-16 selection at the end of the list of possible MIDI channels that will allow QLC+ to pick up on any of the sixteen channels (as opposed to listening on just one channel). The values of the MIDI channels won't be what you expect as it's QLC's representation of the value. Just set the 1-16 setting then use the autodetect setting on the Cue List widget to find your note/cc/pc whatever.
Hope this helps. If you have worked out how to go from Program >> IAC >> QLC+ on the same computer, I'd sure like to hear how it was done!
Someday that might be really useful. For now, I've found that you can't stop a cue list if it's getting the midi note that triggers it. So maybe you can use different sets of midi notes when you want to run chaser 1 on some lights and then run chaser 2 on the same lights later on. If you use the same notes for chaser 1 and chaser 2, you will always have both chasers running regardless of whether you "stopped" one or even both cue lists.
Did you ever figure this out?
I was trying to do a very similar thing - use Reaper and the ReaGate filter to kick out a midi note and then use that note to trigger a chaser's next cue. I failed that, but wound up getting around that by using a hardware DMX>>MIDI converter to send QLC+ midi notes.
That worked in the end but it did not solve my problem. But I did work out the mechanics of getting MIDI in to trigger chasers reliably.
Here's a couple of "learnings":
MIDI channel 1 value 1 gets picked up as MIDI 129 in QLC+ Cue List widget. QLC+'s audtodetect worked great for finding that offset in mapping.
When you set your MIDI input in the input/output tab in QLC+, _highlight the row_ that has your IAC driver, hit the tools button, and make sure the MIDI channel assigned to the IAC driver is the one that IAC is using to send towards QLC+ or the Cue List widget will never see it. IOTW, don't send a signal on MIDI Ch. 3 when QLC+ is expecting the MIDI note to come in on Ch. 1. Get QLC+ to listen on Ch. 3 if that's the channel you are sending on.
When you are selecting the MIDI channel by using the tools button on input/output tab, there is a MIDI channels 1-16 selection at the end of the list of possible MIDI channels that will allow QLC+ to pick up on any of the sixteen channels (as opposed to listening on just one channel). The values of the MIDI channels won't be what you expect as it's QLC's representation of the value. Just set the 1-16 setting then use the autodetect setting on the Cue List widget to find your note/cc/pc whatever.
Hope this helps. If you have worked out how to go from Program >> IAC >> QLC+ on the same computer, I'd sure like to hear how it was done!
Someday that might be really useful. For now, I've found that you can't stop a cue list if it's getting the midi note that triggers it. So maybe you can use different sets of midi notes when you want to run chaser 1 on some lights and then run chaser 2 on the same lights later on. If you use the same notes for chaser 1 and chaser 2, you will always have both chasers running regardless of whether you "stopped" one or even both cue lists.
-
- Posts: 1331
- Joined: Mon Apr 13, 2015 7:05 am
- Location: Bratislava, Slovakia
- Real Name: Jano Svitok
- Contact:
The full mapping is in www.qlcplus.org/docs/midiplugin.html#channelsmappac-light wrote:MIDI channel 1 value 1 gets picked up as MIDI 129 in QLC+ Cue List widget.
In 1-16 mode, add 4096 * (channel number - 1). That means channel 1 is as in the table, channel 2 is +4096, channel 3 is +8192, etc. But as you've written, autodetect will compute it. You can also create input profile, see http://www.qlcplus.org/docs/howto-input-profiles.html. Input profile editor has form to select the desired parameters.pac-light wrote:When you are selecting the MIDI channel by using the tools button on input/output tab, there is a MIDI channels 1-16 selection at the end of the list of possible MIDI channels that will allow QLC+ to pick up on any of the sixteen channels (as opposed to listening on just one channel). The values of the MIDI channels won't be what you expect as it's QLC's representation of the value. Just set the 1-16 setting then use the autodetect setting on the Cue List widget to find your note/cc/pc whatever.