The actual refresh rate is unaffected at a verified 60FPS with a CADisplayLink. The little demo I made is drawing just two triangles with 10-15% CPU. It is only the touch that is not being updated, when I animate programmatically there is no lag at all even with unrelated touch tracking happening simultaneously. I think that somehow the MusicPlayer framework causes the thread that tracks touch (which I had assumed was the main thread) to wait on the audio render cycle. What's interesting is that the main thread doesn't get blocked, only the updating of touch events. I know that AUGraph (which is utilized by a MusicSequence by default) can block, but I don't know if that's what's happening.
Dave
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