Hi Mike
There is still a problem with MIDI control.
I have various cues with Midi ControlChange commands. This works perfectly.
However, as soon as I add a cue with MIDI file somewhere, in order to create an automatic fade, the ControlChange cues are no longer sent to the mixing console. SCS supposedly runs them out, but they do not arrive at the console. Only the cue with the MIDI file comes on the mixer.
Even if I use the ControlChange command over MIDI-1 and the MIDI file via the dummyPort output, I have the same result.
Once a cue with MIDI file is inserted, all other MIDI commands are blocked, no matter what port.
The MIDI file I have previously recorded with MIDIEditor.
MIDI reception continues.
[Fix 11.6.2] MIDI Control issue?
-
- Site Admin
- Posts: 3629
- Joined: Sun Jul 24, 2005 8:58 am
- Location: Brisbane, Queensland, Australia. TZ:GMT+10
- Contact:
Re: MIDI Control issue?
There is a limitation in Windows MCI (Media Control Interface) in that it's not possible to send MIDI messages and MIDI files through the same port simultaneously. Previously, SCS would ignore MIDI messages sent via a port that was also used for MIDI file playback. I've modified SCS 11.6.2 so that if you play a MIDI file to a port that's currently open for sending MIDI messages then SCS will close that port so the MIDI file can be played. You should now be able to send MIDI messages and play MIDI files through the same port, provided you do not try sending MIDI messages while a MIDI file is playing though that port.
There should be no issues using different MIDI ports, although I am aware of an issue if you try to play a MIDI file to the dummy port - that will probably fail, and I haven't fixed that yet.
There should be no issues using different MIDI ports, although I am aware of an issue if you try to play a MIDI file to the dummy port - that will probably fail, and I haven't fixed that yet.