Dropped Buffers from mouse-menu tracking
Dropped Buffers from mouse-menu tracking
- Subject: Dropped Buffers from mouse-menu tracking
- From: William Bates <email@hidden>
- Date: Tue, 24 Apr 2012 22:58:21 -0500
I'm wondering if anyone has a good list of things that can cause input buffers from audio input devices to get dropped. I'm working on an utterly up-to-date, very fast fast desktop Mac. I have an input device read loop that runs absolutely rock-solid in realtime, no matter what else is going on, 99% of the time.
But I do annoying get glitches in two situations:
(1) The first time I mouse-down and menu track over my app's main menu, I drop one 512-sample (11ms) buffer. This happens only the first time (post app startup) the menus are tracked, as if resources are being loaded. Xcode of course reports a thread switch, but I do these all the time and they do not normally cause glitches. I've tried all kinds of things, from preloading the nib to radically increasing thread priorities, and nothing makes much difference. Historical note: OS9 had a low-memory hook for a routine that could be called during just such mouse tracking...
(2) There seems to be some degradation over time, e.g., a slow increase in random dropped buffers after the monitor program has run 5 or 10 minutes, even if I walk away from the machine.
(3) There is a possible correlation with noisy input. Drop the mike and lose a buffer.
Any insights will be appreciated.
_______________________________________________
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