Re: coreMIDI scheduler and 10.3 weirdness
Re: coreMIDI scheduler and 10.3 weirdness
- Subject: Re: coreMIDI scheduler and 10.3 weirdness
- From: Doug Wyatt <email@hidden>
- Date: Wed, 29 Oct 2003 14:17:03 -0800
Hi Rob,
On Oct 27, 2003, at 17:08, Robert Martin wrote:
One of the functions in my app plays midi files - spraying out the
timestamped packets in a loop, and relying on the coreMIDI scheduler
to post them off to a device at the right time.
Under 10.2.x it works flawlessly, allowing the file to play while the
user does other useful stuff elsewhere.
But under 10.3, the events are never sent out by the scheduler.
I have a test tool that plays a MIDI File, waking up every 100 ms or so
to schedule events in the near future, and it works fine on Panther.
If I insert a breakpoint after the play loop, the file plays properly,
so the events certainly got to the scheduler with the correct
timestamps - but any executed statement immediately cancels the
stream.
This is really bizarre. It sounds like something is blocking the
scheduler's thread. I verified that it's running at priority 97
(according to ps axM), so it's not being preempted.
It's as though the scheduler stops work and flushes its cache whenever
my app executes an instruction. Has something changed?
The server's scheduler code hasn't changed since Jaguar.
All immediate messages (zero timestamps) are working fine. It makes no
difference whether I build with PB on 10.2 or with XCode on 10.3. -
all builds work fine on 10.2 but not on 10.3.
I'm at a loss...any ideas?
I assume the problem happens without a debugger in the picture.
Can you construct and send me a test case (or your whole app if you
don't mind), offlist? I can then debug inside MIDIServer and see what's
going on.
Doug
_______________________________________________
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.