MSC, MIDI, IAC, midifiles, oh my!

76 views
Skip to first unread message

jaymez

unread,
Mar 15, 2017, 4:35:55 PM3/15/17
to QLab
Hey there,


I'm trying to control Macros on my ION with Qlab using MIDI, controlled by a midi file.  

I'm managed to get qlab speaking to my console and triggering macros if I hit "send message",  but I'm trying to trigger those quest using a midi file.   I have MIDI trigger turned on and set to the note value of the note, then piping the midi file through IAC from Qlab, but the message seems to be getting lost somewhere.  Am I missing something?   I've attached the qlab file and would be super greatful if you had any advice.

Cheers,

jaymez
CLUSTER HELLO.zip

Rich Walsh

unread,
Mar 15, 2017, 5:16:53 PM3/15/17
to ql...@googlegroups.com
Using this tool it looks like your .mid files don’t contain notes at the velocity of 127 that you have set for your MIDI triggers. Try setting them to “>0” to respond to any velocity.

The files also contain different notes from those you’ve used I think, and a mix of Note On @ 0 and Note Off for note off – so some thought is needed there too.

Finally, once you get it to trigger a single MSC Cue it follows on to fire the others: is that intended?

Rich

jaymez

unread,
Mar 15, 2017, 5:54:47 PM3/15/17
to QLab
Hey there,

I spoke to luckydave and we figured out the velocity, so that's sorted.   I changed them all to any.

The midi file does have extra notes, I just haven't added them yet as I wanted to get the system working to minimize having to change even more cues.  

I don't see where it's follows on.  They're all set to donot continue.   The problem I'm running into now is it only seems to work "monophonically" but I think that's a problem with the ion only being able to run a single macro at a time.  

I've attached the updated file
CLUSTER HELLO.cues

Rich Walsh

unread,
Mar 15, 2017, 6:08:29 PM3/15/17
to ql...@googlegroups.com
“Any” means the shorthand of using Note On @ 0 for a note off will trigger your Note On cues (“>0” doesn’t); this may or may not be a problem for you… Your test .mid file fires the “ON” macros at the start and end of the notes, for example.

I’ve attached a screenshot of what I saw when I opened your original file: lots of arrows on the right…

MSC is being generated as you’d expect, so if you’re not seeing 2 macros at once it must be down to the Ion.

Rich
Screen Shot 2017-03-15 at 21.57.41.pdf

jaymez

unread,
Mar 15, 2017, 6:22:28 PM3/15/17
to QLab
"Any" seems to work no problem and I set the NOTE OFF velocity values to 0.  Created some monophonic midi files, so that seems to work well.    

I've also got rid of those follow I guess sometime after I uploaded the file.  

Thanks for all your help rich.   Very much appreciated!

jaymez

Rich Walsh

unread,
Mar 15, 2017, 6:36:22 PM3/15/17
to ql...@googlegroups.com
The point I’m failing to make is this: a MIDI Note On message @ 0 is _not_ the same as a MIDI Note Off message (at any velocity). Some devices will treat them as the same, but QLab will not when using MIDI to trigger cues.

Your MIDI files contain both ways of marking the end of a note. Your cue “C#2 ON” is triggered by a Note On at any velocity – including 0. Your cue “C#2 OFF” is triggered by a Note Off (at any velocity in the last version you posted). “C#2 OFF” will _never_ be triggered by a MIDI file that uses Note On @ 0 to mark note ends. Conversely, “C#2 ON” will be triggered twice: once at the start, and again at the end.

Rich
Reply all
Reply to author
Forward
0 new messages