Multiple midi commands (fix in 10.6.2)

[Boswell]

Mike,
an odd one I've managed to track down, it has appeared at random interval since MIDI support was introduced.
I use SCS to control mic mutes on the Soundcraft K2 desk. Quite often I need to send out more than 10 midi commands so I make a subcue.
For neatness, I've built a small library of MIDI cues, eg stage ON, Stage OFF, Choir ON, Choir OFF, Pit ON, Pit OFF, Stage & Choir ON, Stage & Choir OFF etc
so a typical Control send Cue may contain 4 or more sub cues, each containing up to 10 commands.
I've found that sometimes a command is ignored but it is not repeatable. But if I put a small delay onto each subcue to make them run sequentially, I have no problems. ie Sub Q 1 no delay, SubCue2 0.1secs delay, Subcue3 0.2secs delay, Subcue4 0.3sec delay etc.
Does that make sense? is there any limit to the number of MIDI control subcues that can be started simultaneously ?

[Mike Daniell]

There could be an issue here. SCS has no built-in limitation on the number of MIDI commands sent in rapid succession, but looking at the code (which was written a long time ago) I see that SCS doesn't check the result after sending a MIDI message. One of the result codes that may be returned is 'not ready', and that is probably what occurred for the lost messages. I'll implement a mod to check for 'not ready' and to retry several times if necessary, up to a timeout period.

[Boswell]

This seems to be OK now Mike with 10.6.2RC, time will tell
I'm doing a midi heavy show at the beginning of Nov so it will get thrashed then.
Thanks

[Boswell]

Mike,
Midi heavy show just finished and all went OK, no lost MIDI out commands, so this mod in 10.6.2RC1 seems to be OK. (I didn't have the nerve to try RC2 on a paying audience!!)
Another problem solved,
Thanks Mike