Re: More MIDI sysex problems
Re: More MIDI sysex problems
- Subject: Re: More MIDI sysex problems
- From: Stephen Davis <email@hidden>
- Date: Wed, 2 Jan 2002 11:37:49 -0800
On Wednesday, January 2, 2002, at 01:39 AM, Kurt Revis wrote:
I'm finding that MIDISendSysex() won't send anything to a virtual
destination endpoint. It works fine if I send to an endpoint belonging
to a USB device, though (as expected).
Has anyone else run into this problem, or gotten this to work?
Ah, I was wondering why my sysex packets were not showing up in MIDI
Monitor. :-)
Also: Should sysex be sent only through MIDISendSysex, or am I allowed
to put it in a MIDIPacket and use MIDISend() just like all other
messages? I'm finding that if I do the latter, the sysex data does go
to virtual sources as it should. However, when sending to a MIDIMAN
2x2, this causes something to freak out and hang the whole machine for
8 seconds, and the message never gets sent. (And after that happens,
even MIDISendSysex() doesn't work until I quit all MIDI apps and start
again!) I don't know if this is a CoreMIDI problem, or a MIDIMAN
driver problem, or what, although I suspect the driver...
I gave up on MIDISendSysex() and just use MIDISend() -- seems to work
just fine (mostly). I have a MIDISPORT 1x1 and it seems to work for
that device but I have had a bunch of cases where the MIDIServer process
will die on me and I can't connect to it again. Quitting my app and
MIDI Monitor seems to make things better, as you pointed out. I don't
know what the culprit is.
BTW, MIDI Monitor is way cool. Thanks a ton!
stephen