OK - I have a series of manual start cues with 2 sub-cues - one playing an audio file and the second playing a midi file in parallel. I also have a Panic hot key cue which sends a series of midi messages including two to the midi device which plays the midi file. All this is controlled through Bome midi so if I press a foot pedal to do an emergency stop Bome first sends an Escape key press to SCS to stop all cues and then 1 second later it sends the Panic hot key press to reset my lights, mixer channels etc.
With SCS 11.3.8 this all worked fine. With RC3 and RC4 of 11.4 (didn't try this with RC1 and RC2) the escape works fine, the Panic cue works fine but as soon as I try to start another audio/midi file cue I get a message saying can't send the midi file because the midi device is in use.
In case my (rather large) cue file had got a bit screwed I created a small cue file. One audio/midi file cue and a Panic hot key cue which sends a single Program Change to the midi device. Does the same thing - run the cue, press escape, press P for panic, try to restart the cue and I get device in use.
I'll email the cue file and a dump file in case it helps.
Cheers from sunny France
Richard
[Resolved] Control send Hot Key cue blocking midi device
Re: RC4 - control send Hot Key cue blocking midi device
Oh in case it helps then if after the Panic hot key press I select a different cue to run then all works fine. This means I have a work around as I have a gig at the weekend . . .
-
- Site Admin
- Posts: 3630
- Joined: Sun Jul 24, 2005 8:58 am
- Location: Brisbane, Queensland, Australia. TZ:GMT+10
- Contact:
Re: RC4 - control send Hot Key cue blocking midi device
I've tried to reproduce this problem here but must be doing something different because I don't get the "MIDI device in use" message. I've emailed you details of a tracing version to run.
Re: RC4 - control send Hot Key cue blocking midi device
After working with Mike D it looks like this must be a problem with BOME and/or my general configuration. I've sorted out a good workaround and so this should be marked "Closed" or something similar . . .
Thanks again for your help Mike
Cheers
Richard
Thanks again for your help Mike
Cheers
Richard