Re: MIDI Sysex and more
Re: MIDI Sysex and more
- Subject: Re: MIDI Sysex and more
- From: Doug Wyatt <email@hidden>
- Date: Sun, 17 Feb 2002 20:55:13 -0500
It's also important to know what version of the OS you're running -
10.0, 10.1, and 10.1.2 are all different. It's fine to discuss problems
here; we can help with pilot error, but if it's an newly-discovered bona
fide bug, Kurt is right, writing it up is good, and including an example
tends to put your bug nearer the front of the queue.
Doug
On Friday, February 15, 2002, at 07:37 , Kurt Revis wrote:
On Friday, February 15, 2002, at 03:09 AM, Jakob Cederlund wrote:
I'm sorry if this has already been on the list. (Is there a nice app
for reading archives? The webinterface is bit raw...)
Supposedly the mailing list administrators are working on a new archive
system, to go live in the near future.
- MIDISendSysex can't handle more than 3 bytes at a time. You can use
a completion proc to send larger packets. You have to make sure that
you end on a sysex-end, however. If not, CoreMIDI hangs the system for
a couple of seconds, and nothing is delivered to your MIDI device.
This is a bug in the MIDIMAN driver. It works correctly with other
devices--I have a MOTU 2x2 interface which sends sysex just fine. Bruno
Di Gleria posted a workaround on January 4th (subject: Re: More MIDI
sysex problems). Note that you will have similar problems if you try
to send the same sysex through MIDISend() directly (I summarized this
on the list the next day).
- MIDIPortDispose hangs forever if you call it before MIDISendSysex
has finished (which is only notified through the completion proc,
AFAIK).
I haven't tried this myself. If you can, put together a test program
and file a bug--this is the best way to get Apple to fix things.
- Occasionally, MIDIGetNumberOfSources etc. hangs, and you must kill
the MIDIServer process (e.g. by using "kill" from the terminal).
The hanging MIDIServer is probably the result of some other bug, or the
bad MIDIMAN driver. Or, you might be trying to send a packet list
which is greater than 1024 bytes, which will potentially hang or crash
the MIDIServer. (This has supposedly been fixed for a future release.)
Also it seems that sending MIDI slows down my app quite a bit.
(Checked it out using Sampler, great tool!)
Well, I've seen times when the MIDIServer process and/or the kernel
will start using lots of CPU for no apparent reason--this will also
potentially slow down other processes on the machine. This may or may
not be related to your problem--how much is "quite a bit"? (I haven't
done any particular profiling of sending MIDI yet...)
--
Kurt Revis
email@hidden
_______________________________________________
coreaudio-api mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/coreaudio-api
Do not post admin requests to the list. They will be ignored.
--
Doug Wyatt
work: email@hidden (CoreAudio)
personal: email@hidden
http://www.sonosphere.com
"Changing OS's is the corporate equivalent of molting -- you're very
vulnerable after you've done it but you have to do it to survive".
-- Ray Spears
_______________________________________________
coreaudio-api mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/coreaudio-api
Do not post admin requests to the list. They will be ignored.