So, here goes... I have the following issue with MSC/MSysEx controlling our ETC Express 48/96 (yesyesyes, I know, ancient ;)... but it was what we could get for free, and it's reliable... ) : I want to fire specific cues rather then just a general GO, and so I made a MSC Cue with Command "GO", Device ID "3" (which is the one I set up in the console), Q Number "56.2" and Q List "2" (which refers to the C/D Fader group on the board), Q Path empty. When I fire the Cue, nothing happened. So I created a MIDI SysEx Cue and typed in the raw Hex that the ETC manual prescribes, namely: "7F 03 02 01 01 35 36 2E 32 00 32 00" with QLab adding F0 and F7, the message, recorded in a MIDI monitor, looks like this: "F0 7F 03 02 01 01 35 36 2E 32 00 32 00 F7" This actually works and does fire the desired Cue. So I looked at what the other MSC Cue sends in said MIDI monitor: "F0 7F 03 02 01 01 35 36 2E 32 00 32 F7" As you can see, the MSC frame packets are exactly identical, except for the omitted Delimiter "00" before the ending "F7". What's the go, is ETC not conforming to standard demanding the delimiter (as it does in its manual at http://www.etcconnect.com/docs/docs_downloads/manuals/Express_Two-scene_Preset_v3.1_User_Manual.pdf on page 284 (which is 298 in the pdf)? I mean, I've found a work around, but I'd rather not write 120 lighting cues in Hex if I don't have to :P. Assuming that it's not a bug (or somebody else would have mentioned it before), would there be a possibility in the preferences of either the cue or the workspace/application for a tick at "Trailing Delimiter" or something along those lines? At the moment, neither cue settings nor preferences look particularly cluttered... cheers, Freddy
Freddy Komp <busy...@gmail.com> Aug 10 06:40PM -0700
Hi Penelope,
Sorry for the late reply - yes, although I was able to make it work with
the work around of writing my own SysEx Messages as described (I ended up
writing an Applescript that would acquire an LX Number from a dialogue box
and generate the appropriate SysEx message) -
The ultimate fix (that allowed me to use normal MSC cues again) was to use
the MIDI ports of a good quality device (i.e. Edirol UA25, MOTU Ultralite
mk3...) instead of the cheap(er) MAudio Uno:
http://www.pcmusicsupply.com/images/interfaces/usbmidi/usbuno/uno_big.jpg
...
The odd thing was, that the same MAudio Uno was working fine with an ETC
Express 48/96, and then did not work for the ETC Express 24/48 (except for
SysEx)...
So, bottom line - while the MIDI Monitor showed no difference between the
MSC messages used... there is more between Heaven and Earth (er, Midi
devices and Midi devices) than one can fathom... :)...
So, hopefully, the new MIDI device will help you...
Cheers,
Freddy
On December 7, 2016 at 6:03:30 AM, Freddy Komp (busy...@gmail.com) wrote:
The ultimate fix (that allowed me to use normal MSC cues again) was to use
the MIDI ports of a good quality device (i.e. Edirol UA25, MOTU Ultralite
mk3...) instead of the cheap(er) MAudio Uno
The buffer on many MIDI devices is too small for MSC to be properly transmitted. Switching to a higher quality device is the way to go.
Sam