Apple

From: email@hidden
To: email@hidden
Subject: RE: AUGraphStart(graph) failure
Date: Fri, 23 May 2014 08:08:00 -0400

It would be hard to say what the problem is without seeing the code for it. To me, it seems that the problem lies in the initialization of the graph. If you are frequently starting and stopping the graph, the sequence should be (on the main thread): start the graph, perform actions, stop it (based on a user action), but then you need to dispose of it, and then (based on a user action) start again. You may have too many instances and that'll cause the app to crash.

But knowing how you're setting it up would help in the troubleshooting.

-Lisa

From: email@hidden
Subject: AUGraphStart(graph) failure
Date: Thu, 22 May 2014 22:43:27 -0700
To: email@hidden

Our iOS app uses core Audio with an audio processing graph. We start and stop the graph based on user action. We find that sometimes AUGraphStart(graph)

fails with status code -66635. We currently crash the app when AuGraphStart fails. This has resulted in a bad user experience and a lot of complaints and the frequency seems to be increasing. We want to know what is the correct way to deal with the failure and what are the possible status code that may be returned and appropriate handling for them.

I tried searching for documentation on this and could not find any and hence this email. Any pointer/suggestion would be much appreciated.

Thanks,

George

_______________________________________________ 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

References:
	>AUGraphStart(graph) failure (From: George Kola <email@hidden>)