Help with HALLab telemetry
Help with HALLab telemetry
- Subject: Help with HALLab telemetry
- From: "Stephen F. Booth" <email@hidden>
- Date: Thu, 23 Sep 2010 08:37:09 -0700
I'm debugging a strange issue with my audio player and I'm not sure how to interpret the HALLab telemetry results. The problem I'm having is that as soon as I start the device I immediately receive continuous overload notifications. So far the problem seems to only occur when my player is launched with the device sample set to 176.4 or 192.0; at 96.0 and below everything works as expected. I should also probably mention that for FW devices everything appears to work OK; I'm only seeing the problem with USB devices. The final piece of strangeness is that the problem only happens when I perform IO in a non-mixable format; if I stick with floats playback is fine.
Here is a representative screenshot of the HALLab telemetry:
I notice the <-Write error 0xE00002E8. I'm not certain what this error indicates; does this mean the device is returning a kIOReturnOverrun error? What do these telemetry data indicate?
Thanks,
Stephen
_______________________________________________
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