Re: error handling best practices with audio file streaming?
Re: error handling best practices with audio file streaming?
- Subject: Re: error handling best practices with audio file streaming?
- From: "Hamish Allan" <email@hidden>
- Date: Wed, 5 Nov 2008 23:40:54 +0000
On Wed, Nov 5, 2008 at 11:09 PM, John Zorko <email@hidden> wrote:
> I'm developing an audio stream player app, and of course it works well at my
> house on different networks. However, taking it into the real world often
> introduces gaps, pauses, hangs, etc. I basically have an NSURLConnection
> feeding an audio queue, via AudioFileStreamParseBytes() and
> AudioQueueStart() / etc. If the connection drops, I catch that and display
> an error alert, but often times the audio skips / hangs / etc. when the
> network is iffy. What is the best way to catch and handle these errors in
> the core audio code, as well as the URL connection object?
My code (which is based off the AudioFileStreamExample) simply keeps a
count of the number of buffers in use -- when it reaches zero it shows
an indeterminate progress spinner to indicate buffering, which it
hides again when the count is re-incremented.
Hope this helps,
Hamish
_______________________________________________
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