• Date
    bill.rios.tpac
  • Date
  • Replies 11 replies
  • Subscribers 188 subscribers
  • Views 9492 views
  • Users 0 members are here

ION Midi Trigger to Qlab- 2nd Q-list not consistent

Hey all,

I'm jumping into the wonderful world of midi and was wondering if I could get some tips/ I think I found some kind of glitch.  Here is what I'm doing.

I have successfully set up MSC so that my cue list 1 is triggering cues in Qlab no problem.

My Sound guy and I decided we didn't want to have to make the Qlab numbers match the lighting Q's so I made a Cue List 2 that would only be to send Go Cue __ to qlab. 

I assigned the Midi Cue list to be 2 in setup.

Made Cues 1/1 - 1/5

Made Cues 2/1-2/3

I assigned Cue 1/3 to execute Cue 2/1 which in turn fires Cue 1 on Qlab side.

Great, works, no problem.


I stop back to Cue 1/2 and hit go, thus executing Cue 2/1 again but no go on Qlab side.

... huh

(also good to note here that stopping back to Cue 1/3 also triggers Qlab cue 1)


I Go to Cue 0 and start the process over again and everything works as expected.

I Go to Cue 1/2.  Hit Go. Cue 1/3 rolls but nothing out to Qlab. 

Is this something I'm doing or is this just part of the syntax?

I didn't include a lot of the setup info because I know I have the midi working and I'm mostly curious about the inconsistency of the go signal to Qlab.

Also, and this is a sincere question, how hard would it be to send midi note info through a macro? And not the note info that you have to write out the Hex info into Midi Raw into a macro?  Is this something we can request in the future? It would be great to make one macro that sends a 'note on' signal and be able to designate the note and velocity and capture that over in Qlab to be your go button.  Then anytime you want throw a Go at Qlab you can just execute your macro.  Insane?  Yes no?  Thanks for the help and listening.


Happy weeeeeeeeeeee!!!!!!kend,

Bill

  • i'm not in front of a console right now, so i can't check. but why don't you open diagnostics tab (Tab 99). there you can see the MSC info that is being output. i guess the first step would be to find out, if the console claims to be sending MSC or not in those cases where you go back and forward and nothing happens.
  • in reply to ueliriegg
    In your console: go to setting/show stettings/midi control Make shure [String Midi Tx] is [disabled], make shure that [MSC transmit channel] and [Midi Tx ID] is the same in both ETC and Qlab. Make shure that midi is enabled in Qlab (with the same adresses). Kill all Q-numbers i Qlab!! (it will probably work just fine, anyway...) -- Q6 in ETC will just trigg Q6 in Qlab!!! -- ("6" is just a number, any number will do as long as it is the same in both....) Put in all the right Q-numbers that will do your trickin Qlab. - Enjoy! tøis
  • in reply to tryggve

    I can't recommend enough buying yourself a USB to Midi interface, this has saved me hours and hours when fault finding. You can get lots of free midi test software, I'm on Mac and use Midi Monitor. Midi OX is excellent on PC.

    I've not done Midi into QLab for a long time but I receive it on almost very show and it's very easy to set the Tx cue number in QLab, so I imagine it's the same on the receive side and your sound department don't want to change the number to save themselves time and work. I think you may have more luck if you set the Rx cue in QLab. Using a second cuelist is a good way to work and makes fault finding and rig check much easier.

    Midi Notes are on the list to be added but in 2.3 you'll have OSC which will be another option.

    Good luck.

  • in reply to Nick Simmons
    I am also playing with OSC and am very excited about its potentiality in our world. However, I work at a PAC and can not put beta software on our boards, so I'm trying to figure out this midi thing for the near future. Thank you all for the help. I'll get back to this after a few days off. Cheers, Bill

  • Hi Bill, Just adding / checkin.

    On the Console/Setup/Show Control do you have Midi Cue List set to 2? If its blank, all active cue lists will send a MSC command. If you have list one firing list two, in theory the console will send two midi commands almost concurrently. I wonder if Q lab sometimes gets confused if its all of a sudden getting midi strings it isn't expecting to, especially if they are for two different lists and if one of them is for a cue that doesn't exist? I sort of assume QLab can handle this, but worth looking at?

    Also, In Q lab, I THINK (I could be wrong as its been several years) if you use a MSC event, you can define what list you want a cue to listen to. So one cue is listening for list 1/12 and another cue is listening or list 27/2. So in this case if you need to / want to leave a universal MSC transmit for all lists, you can filter at the qlab level. If you feel like watching the diagnostics, I've found this Wiki Page incredibly helpful in the past as I can never remember what order commands go, and this lays it out and color codes the hex strings to make it really easy.

    Good luck,

  • in reply to travisres
    Could it be that the second cuelist is still sitting in 2/3 when you go back and run the cue that's supposed to fire 2/3?
  • in reply to ueliriegg
    Yes, that is what is happening. Thank you ueliriegg. And thank you everyone. I appreciate the help. So, the work around to the work around right now is to create a macro that does "Go to Cue 2/0" to wipe Cue list 2 and make it usable. Now if I only had some programable keys on my ION... Another question, is there a Midi Raw string that I can send that is just a 'Go' Command and does not need a specific Q number associated to it? That would be a useable system as well. Although, it has more potential to get off of track than sending specific Cue gos. Looking forward to OSC and Midi notes in 2.3! Thanks again for the help!
  • in reply to Nick Simmons
    Thanks for the advice, I will be ordering a usb midi interface soon. Cheers
  • in reply to bill.rios.tpac
    Yes, you can put midi raw into the "execute" field. Its what I've done on my current show after spending a day trying to get the too many different midi setting configured. Type Q# and one of your soft keys becomes "midi raw." You have to have an external keyboard connected to type in your cue informations. When you hit return, you'll see something like MIDI "CF 6A" in the external links column on your cue sheet.
  • in reply to thomash35

    With cue x execute midi raw you get the on-screen keyboard, so while an external keyboard is helpful, it's not a must. If you want to trigger midi notes, you will put three double digits (e.g. 92 1F 7F). You can also type a MSC command to be executed as midi raw, but that is really complicated and error prone as it takes about 10 double digits... If you want your life really to be simple, you go and have a beer or two with your sound guy and you come up with a common numbering. This solves basically all problems, except maybe for either your or the noise boy's ego... ;)

Related

www.etcconnect.com