Midi Show Control with Jester ML 48

[Joshua]

Hi,
I'm trying to control the cue stack on my jester ml 48 (firmware version 4.1) via midi show control but for some reason the jester is not recognizing the msc messages.
I'm sending midi notes from reaper to bome's midi translator and translating them into msc messages, those then get sent via a usb to midi converter to the jester, all of those steps work fine (the out light on the converter flashes with each sent message) but for some reason the jester is not responding to the message. The same setup works with normal midi notes so I was wondering if the msc messages need to be formatted differently than the standard but I haven't found anything about that in the manual.

The message I'm trying to send is F0 7F 00 02 01 01 F7  (send GO to midi device id 00)
I also tried to do the same thing from python with the same result, midi notes work but msc doesn't.
Any help would be greatly appreciated
~Joshua

[Jon Hole]

10 hours ago, Joshua said:

those then get sent via a usb to midi converter

What converter are you using? Does it look like this: http://www.arvydas.co.uk/2013/07/cheap-usb-midi-cable-some-self-assembly-may-be-required/

[Joshua]

9 hours ago, Jon Hole said:

What converter are you using? Does it look like this: http://www.arvydas.co.uk/2013/07/cheap-usb-midi-cable-some-self-assembly-may-be-required/

Yes, this is exactly what it looks like, I'm suspecting that it might be the issue here, when I connect the Input to the through port on the jester MIDIOX displays a constant stream of note off messages.
Can you recommend any higher quality converters? I'm pretty new to midi and have no idea what to look out for.

[Edward Z88]

Hi Joshua,

Welcome to the Zero 88 Forum.

41 minutes ago, Joshua said:

Yes, this is exactly what it looks like, I'm suspecting that it might be the issue here,

As per the link @Jon Hole posted, devices that look like this rarely work with the MIDI Show Control protocol.

42 minutes ago, Joshua said:

Can you recommend any higher quality converters? I'm pretty new to midi and have no idea what to look out for.

Any MIDI interfaces from reputable manufacturers should be compatible with the MIDI Show Control protocol. For testing and demonstrations, we use a MOTU MIDI interface.

If you have any questions, please let us know.

Edward

[Joshua]

1 hour ago, Edward Z88 said:

Any MIDI interfaces from reputable manufacturers should be compatible with the MIDI Show Control protocol.

Thanks,
I'm looking at buying the Roland UM-One MkII since I've seen this recommended a lot and I'm 99.9% sure that it will work. Do you have any experiences with that particular device?

[Edward Z88]

Hi Joshua,

1 minute ago, Joshua said:

I'm looking a buying the Roland UM-One MkII since I've seen this recommended a lot and I'm 99.9% sure that it will work. Do you have any experiences with that particular device?

I haven’t used this device in the past, and haven’t heard of any Jester users using this device. It appears to be designed for MIDI Notes, but it may work with MIDI Show Control. 

Apologies I can’t provide any further guidance than that!

Edward

[Joshua]

The Roland UM-One MkII just arrived and I can confirm that it works flawlessly, thank you for your great support.

Joshua

[Edward Z88]

Hi Joshua,

53 minutes ago, Joshua said:

The Roland UM-One MkII just arrived and I can confirm that it works flawlessly, thank you for your great support.

Thanks very much for the update. Really glad to hear this works with the Jester.

If there's anything else we can help with, just let us know.

Edward

[Joshua]

Hi, I have another question regarding MSC
The manual states that I can send Cue numbers as the data of the GO, TIMED_GO and LOAD commands, when I do that any Cue numbers sent are ignored (go and timed go advance to the next memory in the cue and load doesn't do anything).
The sysex message I'm sending is F0 7F 00 02 01 01 06 F7 (this should activate the sixth memory in the stack). Do you know what could be the issue here?

Joshua

[Edward Z88]

Hi Joshua,

14 hours ago, Joshua said:

(go and timed go advance to the next memory in the cue and load doesn't do anything).

MSC Load commands must have a cue number. It therefore sounds like the cue numbers you are sending are invalid, and the command is not working.

14 hours ago, Joshua said:

The sysex message I'm sending is F0 7F 00 02 01 01 06 F7 (this should activate the sixth memory in the stack). Do you know what could be the issue here?

I've written this command out with the function of each byte:

• F0 7F - MSC Message
• 00 - Device ID
• 02 - MSC Message
• 01 - Lighting command format
• 01 - Go Command
• 06 - Cue 6
• F7 - Sysex Closed

(Please correct any you think are incorrect)

Can you confirm you have a cue number 6, and the desk is set to MSC Device ID 0?

It is a rather dry read, but the original MIDI Specification may give you some pointers...

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

Let us know how you get on.

Edward

[Joshua]

6 hours ago, Edward Z88 said:

Can you confirm you have a cue number 6, and the desk is set to MSC Device ID 0?

Yes, I've programmed memories 1 through 34 and the device ID is 0 (I've tried settings it to 2 and sending F0 7F 02 02 01 01 06 F7 instead but that didn't make any difference)
 

Quote

It is a rather dry read, but the original MIDI Specification may give you some pointers...

This is the document I used when writing the command, I'm pretty sure the 00 delimiters are not needed when not sending Cue list or Cue path, I've tried 00 after the 06 but that also doesn't make any difference.

Do you have download links to old versions of the jester ml software so that I can test if it works with earlier versions?