Re: [steem] the dreaded Sysex
- From: "Steem Authors" <steem@xxxxxxx>
- To: <steem@xxxxxxxxxxxxx>
- Date: Fri, 14 Dec 2001 17:05:28 -0000
Hi Stephen,
> 2. Delay between the program ordering the message to be sent, and the
actual
> transmission through the MIDI OUT port. As I understand it, this is
because
> Steem checks that it is a proper message (ends in F7H) before starting to
> send it, and for long Sysex messages this may take a few seconds, by which
> time the program may timeout (get bored with waiting).
Unfortunately this isn't quite the problem. The way Windows handles MIDI
sysex messages is a bit problematic, when a program sends out a sysex
message it can't do it byte by byte, it must be sent in one chunk (and then
in another thread Windows sends it byte by byte through the MIDI port). For
an ST emulator that is getting the sysex byte by byte from the ST this means
a large delay for big messages, as it has to receive the whole message
first. The problem for sysex input is the same but the other way round,
Windows gets it byte by byte until the end of the message before it presents
it to Steem and then Steem feeds it byte by byte to the ST (long delay
between when the sysex starts and when the ST gets the first byte). This
particular situation isn't helped by any of the current MIDI options as I
have no ideas what I can do about it, any ideas are very welcome! :-)
Sincerely,
Russ
--
Manage your list membership - //www.freelists.org/
Steem - http://www.blimey.strayduck.com/
Other related posts:
