MIDI String Macro - What Kind of MIDI Data?

Hi guys,

From the 3.0.0 manual:

Sending MIDI strings

Macro
MIDI String

Syntax
MS[node number]/[MIDI message]

Example
MSh1/90473F

The node number is ‘h’ for a console, ‘i’ for a MIDI/Timecode Processor, and its net number.
The MIDI message is in Hex.


Can *any* MIDI message be sent (assuming the node number is i) as a macro?

For example:
- Note on/off
- Controller change
- MIDI Show Control Messages
- MIDI Sync Messages (Start, Stop, Continue)

Note on/off and MIDI sync messages would be the most useful for me...

Many thanks,

Martin
  • If it cant be done already (not sure). It maybe a feature thats added with keystroke macros. A request is already filed for these. And if it isnt, im sure our good Mr Schiller will pop his head in and enlighted us all :D
  • Thanks Joe.

    What I would really like to do is send program change messages and then note on messages on a cue.

    M
  • If I remember correctly, it can OUTPUT Midi Show Control or Midi Notes. For input, it is Midi Show Control....no notes.

    That's just what I remember....
  • Ahhh notes. My mistake. To my knowledge Wholehog O/S will only chuck out MSC data. Again this could be an enhancement that you could request, MIDI notes. If midi notes help you, HES will listen to users needs and wants, then take it into consideration.
  • Yes, it will OUTPUT notes, but will not accept notes IN.
  • you can use Qlab or midiox to convert notes to sysex.

    san
  • Fantastic! Thank you everyone. I only need notes on output, not input. Input for cue triggering will be MSC.

    How about MMC though (Start, Stop, Loc) events? I am trying to go with option 2 (see the attached picture) to avoid having to use a dedicated show control PC.

    The sequencer computer is the MTC master, and transmits MSC commands and MTC to the Hog. The hog is used as the "GO" button, and on GO cues it transmits an MMC "go" signal to start the sequencer playback. The sequencer then happily plays along (playing back audio/MIDI and also the odd cue to the Hog via MSC), until a cue on the Hog (triggered by timecode) tells it to transmit an MMC "Stop" (and possibly "Loc"), whereupon it stops!

    My brain hurts... but it makes sense to me.

    (I think) :17:

    Thanks very much,

    Martin
  • Martin,

    Using the MIDI string macro is the best option as you can easily define the exact SYSEX command you want to send. What I suggest is that you create blank scenes, each with a SYSEX command. Then in your show programming you can just trigger these via comment macros within your cuelist. Plus it is easy to edit/view the SYSEX commands by opening the Scene directory and putting it in spreadsheet view.

    The other benefit is that you only have to type in the sysex commands one time and then reference the scenes via comment macros when you need them. This is exactly how I programmed the MIDI commands for the lasers on TransSiberian Orchestra.

    As your example from the manual states, you can enter any SYSEX command string after you have defined the node type and number.
  • Excellent. Thanks Brad!

    I can easily use MIDIOX to convert the sysex commands into hex.

    On a side note, your book has arrived from Amazon. She who must be obeyed won't let me have it until Xmas day though :D
  • Thanks Martin.. Have a Merry Christmas and enjoy the book and your MIDI adventure...