Any word on wether or not the ability to connect a subgraph to a node in the parent graph will be allowed in the future? I'm targeting Panther+ so its a little late anyway, but I'd like to encourage implementing this soon.
I was trying to use a subgraph to do exactly what it sounds like it can... encapsulate a portion of a more complex graph. It seems as though I'm running into the limitation Bill mentioned way back in 2002, when I try to connect to the subgraph to the input mixer.
This is what I would like to do. This is appealing for obvious reasons.
[ ] ---2--- [ Subgraph ] ---2--- [ ]
- 6 - [ Mixer ] ---2--- [ Subgraph ] ---2--- [ Mixer ] - 2 -
[ ] ---2--- [ Subgraph ] ---2--- [ ]
First of all, it seems like an arbitrary decision to not allow a setup like this in first place. Second, I am really surprised that this hasn't been added yet. I understand the implication of a setup like this if the subgraphs contain AUConverters. However, and correct me if I'm wrong, this should be fine with only FX units in the subgraphs.
Finally, it would be great if the documentation indicated why AUGraphConnectNodeInput can fail for subgraphs. It took me awhile to realize that the failure wasn't my fault, and then even more time to track down this old message that contains the explanation.
I did file an enhancement request. I hope others also ask for this so it can move up the list.
RADAR: 4783745
Dominic Feira / Code Monkey / Ambrosia Software, Inc.
The current restriction with the sub graphs is that you cannot connect audio
units from the sub graph into the parent graph, so what you're trying to do
can't really be done at the moment.
The SubGraph is there to really help to manage a discrete collection of
units - for eg. Each track of a mixer could be a subgraph of the parent
mixer graph. But this is not quite at the functionality of a completely
embedded patch - however this is something we're considering doing at some
stage
Bill