[Fix 11.3.4] Midi Problem on SCS 11 (Multiple Versions)

[Bob Healey]

I'm attempting to run a very complicated cue file for Young Frankenstein at the moment. For the hardware/software combo I've got, MIDI is just plain non-functional with V11, but works exactly as expected in 10.9.7. With 11.2.5, 11.2.6, and 11.3.0.RC2, I get to send 1 MSC command per launch of SCS. I've got over 200 MSC sends in the cue file. The hardware/software I'm using is a Dell with an Athlon chip running Vista Home Premium 32 bit with 4GB of RAM and and M Audio M Track Audio/MIDI interface. http://www.m-audio.com/products/en_us/MTrack.html At another theater that is running a production of Footloose, SCS 11.2.?? is working as expected using a Focusrite Saffire (original version of the device) for Audio/MIDI on a 64 bit Windows 7 system. I'll get a dump file from the non-working theater tonight, and exact version from the working one tomorrow.

[Bob Healey]

So, I just tried v 11.3.3.2 Build 2013/08/25 and I'm still having this problem. Only the first MIDI message in the show file is sent. After that, I'm not sure what is going out on the wire, but it is not something my receiving recognizes as valid. If I export the cue file, it opens and runs as expected in 10.9.7, except for the video cues which only work in 11+. Sticking a MIDI debugger on the line, only the first message sent after launching SCS 11 is received. All messages after the first are not recognized by the debugger.

[Mike Daniell]

Bob,

I've just run a simple test here sending three MSC messages to MIDI-OX and they were all received OK and look correct, so I've emailed you details of a tracing version to run so I can see what SCS is sending.

[Bob Healey]

Just did another test with a different system. I have no issues using the Echo Audio MIA MIDI card in the old retired SCS machine with 11.2.5 on it, but on its replacement system with assorted different M-Audio MIDI devices, I have the described problem. Have same problem at another theater with an SCS license and the same M-audio devices too.

[Bob Healey]

Trace run emailed.

[Mike Daniell]

Fix ready for 11.3.4, and fix confirmed by Bob.

The error was due to SCS 11 appending a null byte to the end of all MIDI SysEx messages. Some MIDI drivers ignore this extra null byte, but others don't, and that extra byte shouldn't have been there anyway! If anyone else needs this fix prior to the release of 11.3.4, let me know.