Sending Midi Cues to an ETC Express 24/48

[jds388]

I'm having some difficulties sending midi cues to my etc express 24/48. I'm currently using scs 9 and I believe that I have my midi controller set up properly. (I'm using an m-audio uno.) Through reading the manual for my express I've found that the midi message for a generic cue...take 5.6 since that is what is provided in the etc manual is F0 7F 42 02 01 01 35 2E 36 00 31 00 F7. Unfortunately, I'm unsure what I should set my Q list and Q path to in order to create the same midi message. Right now with both my Q list and Q path blank and my Q number set as 5.6 I get a midi message of F0 7F 42 02 01 01 35 2E 36 F7.

Any help on the proper set up so as to control my board through midi cues in SCS would be greatly appreciated.


Thanks in advance.

[Theatre III Sound]

It looks like SCS's definition of a MSC "Lighting GO" command and ETC's definition are slightly different.

First the "Q List" box in SCS corresponds to the "Faders" byte in the ETC manual, where ASCII "1" (0x31) refers to the A/B fader pair and ASCII "2" (0x32) refers to the C/D pair.

I'm guessing that the ETC board does not respond to the "Q Path" entry, so if you specify "1" for the "Q List" and "0" for the "Q Path", you will get the following MIDI message: F0 7F 42 02 01 01 35 2E 36 00 31 00 30 F7. I'll bet the ETC will ignore that 0x30 next-to-last byte.

Try it and see how it goes.

Bruce

[Theatre III Sound]

It looks like SCS's definition of a MSC "Lighting GO" command and ETC's definition are slightly different.

First the "Q List" box in SCS corresponds to the "Faders" byte in the ETC manual, where ASCII "1" (0x31) refers to the A/B fader pair and ASCII "2" (0x32) refers to the C/D pair.

I'm guessing that the ETC board does not respond to the "Q Path" entry, so if you specify "1" for the "Q List" and "0" for the "Q Path", you will get the following MIDI message: F0 7F 42 02 01 01 35 2E 36 00 31 00 30 F7. I'll bet the ETC will ignore that 0x30 next-to-last byte.

Try it and see how it goes.

Bruce

Or, you could try leaving the "Q Path" entry blank, which would yield: F0 7F 42 02 01 01 35 2E 36 00 31 F7. This message is missing the second delimiter, but since the next byte is "End of Message", it would be reasonable to assume that would act as a delimiter. Again, try and see if it works.

Bruce