SYSEX OSC command question

[nizer]

This may be out of the scope of this forum but I am out of ideas and I need your brains :-).

I use Qlab to wirelessly trigger my iPad and run light boards via MSC.

I use a TouchOSC app to test the set up and trigger QLab during setup and I wanted to make a button in touchOSC that simple sends out via the hard wired midi interface coming out of the iPad a test MSC command to the light board to make sure it is set up to receive and trigger MSC data. This is based on Q Number 1, Q List 1 set up.

I made a OSC button with this Sysex data. (Based on hours of reading online).

/midi/0xF0 0x7F 0x01 0x02 0x01 0x01 0x31 0x00 0x31 0xF7

This is the data from a Qlab MSC cue as seen by midi monitor. In the Qlab version there are 2 sets of double spaces and a extra set of zeros before the F0. There are also some pipes and 1's.

00  F0 7F 01 02 01 01 31 00  31 F7                    |      1 1 |

Can't get any midi to happen. Thanks for any help.

[Sam Kusnetz]

On January 22, 2014 at 2:54:04 AM, nizer (ma...@nizer.com) wrote:
>
> This may be out of the scope of this forum but I am out of ideas and
> I need your brains :-).
>

> I use a TouchOSC app to test the set up and trigger QLab during setup
> and I wanted to make a button in touchOSC that simple sends out via the
> hard wired midi interface coming out of the iPad a test MSC command

Well, if you’re talking about TouchOSC communicating with a lighting board, having nothing to do with QLab, then I’d say yeah, this is outside the scope of this forum! :)

If the show is run by QLab firing the light board, why not have the test cue be a button in TouchOSC which fires a test cue in QLab?

Cheerio
Sam
—
Sam Kusnetz
QLab Field Operative
s...@figure53.com

[Mark Nizer]

Thanks for the reply. I do what you suggested already. Just wanted to be able to make sure the board was triggerable before I started setting up the wireless network, midi set up and Qlab etc. I'll keep exploring. 

Mark Nizer/Neisser

📩 Ni...@active-media.com

📲 434-974-9699

💻 http://activemedia.org

💻 http://Nizer.com

--
--
Change your preferences or unsubscribe here:
http://groups.google.com/group/qlab

Follow Figure 53 on Twitter: http://twitter.com/Figure53

---
You received this message because you are subscribed to the Google Groups "QLab" group.
To unsubscribe from this group and stop receiving emails from it, send an email to qlab+uns...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Rich Walsh]

Did it really take hours to find this and understand it:

http://www.richmondsounddesign.com/docs/midi-show-control-specification.pdf

The double spaces and pipes are not part of the message: just formatting by MIDI Monitor. MIDI can only be hex strings.

The SysEx message you have spelled out looks right – it's sending a GO cue 1 list 1 to lighting device ID 01.

Have you done the standard basic troubleshooting steps? Can you get any MIDI out of the "hard wired midi interface" from any app? From TouchOSC? Does the interface handle SysEx properly (not all do)? Does the interface work from a Mac? What messages are coming out of the interface (plug it into MIDI Monitor, not the lighting desk)? Do the cables work? Usual stuff…

Try testing it by having it trigger QLab by MSC – there's a lot less to setup than on a lighting desk to do this.

Rich

[nizer]

Thanks for the reply. I really appreciate your expertise and help.

To answer your questions…

Did it really take hours to find this and understand it? Yes, I have no experience with SYSEX messages and trying to google the right thing and school myself was time consuming. I was also at sea in the middle of a storm where internet is sketchy. This link turned out be super helpful. http://wifimidi.com/midi-message-generator/

Can you get any MIDI out of the "hard wired midi interface" from any app? YES

From TouchOSC? YES

Does the interface handle SysEx properly (not all do)? YES

Does the interface work from a Mac? YES

What messages are coming out of the interface (plug it into MIDI Monitor, not the lighting desk)? All is well via MIDI. But no midi seen when it is sent via a OSC command /midi/0xF0 0x7F 0x01 0x02 0x01 0x01 0x31 0x00 0x31 0xF7 It DOES show up in Osculator but not in midi monitor.

Do the cables work? YES

After more research <I won't say how long ;-)>, I think the issue is that OSC doesn't get sent out to a MIDI device, even those this guy seems to be doing it. http://hexler.net/forum/viewthread/55/ Scroll down to ART, where he explains the process. And in my testing it made the OUT light flash in the MIDI interface.

To bring this over to Qlab with the goal of sending a MIDI message via a OSC cue, I have attached a sample workspace with MIDI and SYSEX messages. It does some crazy stuff. 

If you fire Cue 4, it skips Cue 5 and goes to Cue 6.

Cue 6 and Cue 7 are identical but show totally different output in Osculator.

Maybe this will help with my Quest or at least get the brain juices flowing.

[nizer]

Here is the file. 

[Rich Walsh]

You always seem to miss out critical information in understanding your issues. Why are you sending an all-call GO to devices 0 when trying to prove a lighting device ID 1? If you trigger a cue in QLab that tells QLab to GO it will of course double GO, won't it? What's the external interface doing? Looping round?

Specifically, if you PREVIEW your cue 3 for example it will make QLab GO, which makes cue 3 GO (since it's highlighted), which stands by the next cue and then GOes it as it receives the GO sent out when cue 3 GOed. Do you see how you're creating a big mess to test anything with? In fact, as the next cue is also a GO you'll get a triple GO if the interface loops round…

On 23 Jan 2014, at 16:29, nizer <ma...@nizer.com> wrote:

Thanks for the reply. I really appreciate your expertise and help.

To answer your questions…

Did it really take hours to find this and understand it? Yes, I have no experience with SYSEX messages and trying to google the right thing and school myself was time consuming. I was also at sea in the middle of a storm where internet is sketchy. This link turned out be super helpful. http://wifimidi.com/midi-message-generator/

Can you get any MIDI out of the "hard wired midi interface" from any app? YES

From TouchOSC? YES

Does the interface handle SysEx properly (not all do)? YES

Does the interface work from a Mac? YES

What messages are coming out of the interface (plug it into MIDI Monitor, not the lighting desk)? All is well via MIDI. But no midi seen when it is sent via a OSC command /midi/0xF0 0x7F 0x01 0x02 0x01 0x01 0x31 0x00 0x31 0xF7 It DOES show up in Osculator but not in midi monitor.

That narrows it down to your SysEx message not making it out of the interface, doesn't it? This is therefore an OSC issue: so you need to find someone who knows how OSC code is supposed to be expressed. A very brief skim through the thread you mention implies that you need to send OSC messages via the network to a Missing Link hardware device that translates these from network packets into MIDI messages to spit out of its MIDI socket. Is that what you're trying to do? Surely the OSC tab of a button is about sending OSC messages, which are network messages not MIDI messages. Is your hardware MIDI interface capable of converting network strings to MIDI strings? If not then you're wasting your time trying to get this to work.

If you've got an iOS MIDI Device why don't you use myMSC to send MSC to it? It doesn't look like TouchOSC has the ability to send SysEx to a MIDI interface. A Missing Link can convert OSC on the network to MIDI, but that's not what you describe using.

Do the cables work? YES

After more research <I won't say how long ;-)>, I think the issue is that OSC doesn't get sent out to a MIDI device, even those this guy seems to be doing it. http://hexler.net/forum/viewthread/55/ Scroll down to ART, where he explains the process. And in my testing it made the OUT light flash in the MIDI interface.

If the light flashed then MIDI came out. What MIDI? Did you test it in MIDI Monitor – or perhaps SysEx Librarian so you can see the actual data?

To bring this over to Qlab with the goal of sending a MIDI message via a OSC cue, I have attached a sample workspace with MIDI and SYSEX messages. It does some crazy stuff. 

If you fire Cue 4, it skips Cue 5 and goes to Cue 6.

Cue 6 and Cue 7 are identical but show totally different output in Osculator.

Are they completely different but always the same, or do they toggle no matter what order you fire the cues in?

Rich

[nizer]

Thanks for the reply.

@rich Sorry I have the reputation as "always seem to miss out critical information in understanding your issues." Sounds like my psychologist.  Do you support mental health as well now? lol

On to the actual OSC-MIDI-QLAB puzzle. Here is what I learned.

To send OSC as MIDI is only possible using THE MISSING LINK device. So this OSC command:

 /midi/0xF0 <YOUR MESSAGE HERE> 0xF7 is useless without it.

The first 3 cue in the sample I sent were simple test cues to make sure midi monitor was working and just random.

The advice to use myMSC is the answer. I never heard of it before. Maybe TouchOSC will be updated sometime.

Thanks for the support and I'll work thru "understanding your issues" with my mental health provider. ;-)