coreMIDI scheduler and 10.3 weirdness
coreMIDI scheduler and 10.3 weirdness
- Subject: coreMIDI scheduler and 10.3 weirdness
- From: Robert Martin <email@hidden>
- Date: Mon, 27 Oct 2003 20:08:20 -0500
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. 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. It's as
though the scheduler stops work and flushes its cache whenever my app
executes an instruction. Has something changed?
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?
Cheers, Rob
_______________________________________________
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.