HALLab I/O Cycle Telemetry
HALLab I/O Cycle Telemetry
- Subject: HALLab I/O Cycle Telemetry
- From: Vyacheslav Matyushin <email@hidden>
- Date: Thu, 21 Mar 2013 04:02:33 -0700 (PDT)
Hello,
I know this question has been asked here before but left unanswered.
But maybe this time Apple developers will notice it and answer :-)
I/O Cycle Telemetry Window was removed from HALLab.
Is there any alternative for audio driver developers?
How to trace "Overload", "Early", "Late", etc CoreAudio error messages and how to debug driver timestamps?
For example, I try to submit fake audio engine offset (device and audio engine run at different sample rates),
but application sometimes puts hundreds of zero samples to output.
How would I know whether it is because of CoreAudio overload, or because of audio engine offset being way too early or too late? :-)
Thanks in advance!
Vyacheslav Matyushin.
_______________________________________________
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