MIDI trigger from ETC Express console for Cue numbers over 127

  • Hello All,

    I have upgraded to Core 1.3 OF 24 and am having trouble with midi values over 127 as triggers from an ETC Express console.  The pluggins don't seem to be working.  Are there newer versions of those actors?


    g5 dual 2.5g OS 10.5.8

  • What actors are you speaking of specifically?

    MIDI values are inherently between 0 and 127, so you can never have a value higher than 127\.  ETC Express consoles send MIDI values based on the current cue number when the GO button is pressed.  For cues 1-127, it sends a control change message on channel 1, control number 77 and value equal to the cue number.  For cues 128-255, it sends a control change message on channel 1, control number 78 and value equal to the cue number less 128\.  For instance for cue number 150 it would send a control change message on channel 1, control # 78, value 22.

    I have not tested this in 1.3 since I no longer have easy access to an Express, but there is no reason why it shouldn't work.
    Does this answer your question?


  • Thanks for the response. I had been using a user actor mark created for etc recall cue.  I will try this for the 1.3 and let you know.

    Thanks again,


  • Beta Tester

    Doesn't the express support MIDI Show Control? Wouldn't that be easier to use?

  • ETC Express consoles do NOT support MIDI Show Control.  It only supports MIDI control change as described above.  Newer ETC consoles running the EOS software support MIDI Show Control but NOT standard MIDI.

    Confusing, I know.
  • Beta Tester

    I don't think you're correct. According to ETC the Express can both send and recieve MSC lighting commands.

  • Apparently you are right Matthew, although I was sure I had tried to do this before and it didn't work.

    For further information on how MIDI and MSC work on the Express console, read the manual under the MIDI section at:

  • Note that on the Express series consoles, the commands sent out will always use 01 (lighting command) in the "command format" byte position.  See section 4.1 of the MSC 1.0 spec for info about command formats http://www.richmondsounddesign.com/docs/midi-show-control-specification.pdf