Re: CoreMIDI SysEx & MIDIMonitor
Re: CoreMIDI SysEx & MIDIMonitor
- Subject: Re: CoreMIDI SysEx & MIDIMonitor
- From: "David A. Hoatson" <email@hidden>
- Date: Thu, 31 Aug 2006 16:00:49 -0700
- Organization: Lynx Studio Technology, Inc.
Kurt,
Well - I guess I spoke too soon.
The sleep(1) fixed the startup issue where the MIDI input thread wasn't
completely started before it received bytes.
That sounds like a really weird way to summarize the problem. More
likely, the sleep is just working around a race condition in a MIDI
driver.
OK - but that seemed like what was going on - lacking any better info. I
guess it doesn't matter - except if the 'issue' takes more than 1 second to
resolve itself :-).
I tossed all of the MIDI drivers on my system and just used the Apple
drivers. The Roland driver didn't seem to suffer from the sleep(1) problem
as much as the Apple driver. Go figure.
Finally figured out that I had a errant bit getting flipped in the SysEx
data stream and the MIDI driver was seeing that and terminating the SysEx
message prematurely. The Roland driver would spit out part of the SysEx
message, and the Apple driver would just sent out garbage without any SysEx
message. Made it seem as if there was something going on in the driver
when there really wasn't.
I agree that it would be nice to have some sort of verification tool, as
I'm not sure what my MIDI driver would do in such a case (you can bet I'm
looking at it tomorrow!).
Thanks for all your help - I hope I can return the favor soon.
David A. Hoatson
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Coreaudio-api mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden