Re: AUGraph deadlocks
Re: AUGraph deadlocks
- Subject: Re: AUGraph deadlocks
- From: Brian Willoughby <email@hidden>
- Date: Fri, 02 Dec 2011 18:04:52 -0800
I would say that the bigger question is why you're trying to change
parameters or manipulate the graph from within the rendering callback.
Brian Willoughby
Sound Consulting
On Dec 2, 2011, at 12:25, patrick machielse wrote:
So, is the implementation wrong, is the documentation wrong, or is
my interpretation wrong…?
Or in other words: should I file a bug report?
Which AUGraph API _is_ safe to use?
I'm using AUGraphNodeInfo() to fetch unit instances from the graph
before changing their parameters. Should I cache naked unit
pointers instead of the nodes?
Op 2 dec. 2011, om 21:09 heeft Doug Wyatt het volgende geschreven:
AUGraphNodeInfo is (obviously) taking a lock and so it shouldn't
be called on the audio render thread. I'd suggest fetching and
caching whatever information you need from it beforehand.
On Dec 2, 2011, at 8:01 , patrick machielse wrote:
In my app I'm using an AUGraph. This graph can be manipulated /
inspected from both the audio rendering thread and the main thread.
_______________________________________________
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