Re: Coreaudio-api Digest, Vol 6, Issue 134
Re: Coreaudio-api Digest, Vol 6, Issue 134
- Subject: Re: Coreaudio-api Digest, Vol 6, Issue 134
- From: Jens Alfke <email@hidden>
- Date: Tue, 17 Mar 2009 14:10:34 -0700
On Mar 17, 2009, at 11:12 AM, Jeff Moore wrote: From that backtrace, it seems like there is a lot of sleeping going on. Some of it looks lock related, but some of it also looks like waiting. I don't know enough about the network stack to say if this would be considered a bug or not, but it never hurts to file one and find out.
Yeah, the fact that the socket is not set to non-blocking makes me suspicious that the read call is actually waiting for a packet that hasn't arrived yet. Have you tried making the socket nonblocking?
I assume that you're doing the networking this way, with no buffering at all, to get the minimum possible latency? Normally you'd be reading packets from a separate thread and pushing the data into a queue that the audio thread reads from.
At any rate, I think your best bet is to also follow up with one of the more network and/or kernel focused lists (darwin-dev might be a good place) or to get in touch with our Developer Support folks.
or the macnetworkprog list, for the socket-specific stuff.
—Jens |
_______________________________________________
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