|
| [Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] |
I am not an expert on multi-threaded CoreMIDI client programming, but I did
write the driver in question. It sounds like you are trying to receive a
large sysex message. The driver is trying to avoid sending you every byte as
it's received from USB (actually, they arrive in chunks of 1 to 12, but
that's neither here nor there). It's accumulating bytes into a non-small
buffer (say for the sake of discussion it's 256 bytes long because I can't
remember). When the message ends OR the buffer fills, then the driver sends
the buffer up to CoreMIDI. In theory, this is supposed to reduce overhead,
because my assumption is that you can't really do anything with a partial
sysex message anyway,
and packing each byte into a Mach message that gets
shipped across at least two process barriers didn't seem like a good idea
for throughput.
Doug
_______________________________________________ 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
| References: | |
| >Re: Midi sysex request in new thread (From: Pete Gontier <email@hidden>) |
| Home | Archives | Terms/Conditions | Contact | RSS | Lists | About |
Visit the Apple Store online or at retail locations.
1-800-MY-APPLE
Contact Apple | Terms of Use | Privacy Policy
Copyright © 2011 Apple Inc. All rights reserved.