MIDI causing CoreAudio overload errors?
MIDI causing CoreAudio overload errors?
- Subject: MIDI causing CoreAudio overload errors?
- From: Mark Cookson <email@hidden>
- Date: Mon, 04 Apr 2005 09:31:03 -0600
I have a report that some applications are getting CoreAudio overload
messages when playing/recording audio and playing/recording MIDI tracks.
They don't get the overload messages without the MIDI processing, so
directly or indirectly, MIDI is implicated.
I'm wondering what priority the MIDI server's threads run at. Can they
interfere with CoreAudio's threads?
What's the suggested way of transferring MIDI data from a PCI driver? The
current implementation is to use a mach message to send every byte up to a
user client that hands the byte off to MIDI Services. This seems like a bit
of overhead, but it does appear to give the best latency, which was the
primary reason for the implementation choice.
To use a shared memory buffer would require polling, and to use blocking
threads seems to be even more overhead than mach messages.
I've not had a chance to run Shark to profile the applications yet, but
that's my next stop.
Thanks for any advice,
Mark
--
Mark Cookson
M-Audio, a division of Avid
225 Locust St.
Hudson, WI 54016
_______________________________________________
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