# AudioProcessorGraph && ChangeBroadcaster

**URL:** <https://forum.juce.com/t/audioprocessorgraph-changebroadcaster/23776>\
**Category:** General JUCE discussion\
**Created:** [August 17, 2017, 7:34am UTC](https://forum.juce.com/t/audioprocessorgraph-changebroadcaster/23776 "2017-08-17T07:34:39Z")\
**Posts on this page:** 1\
**Showing post:** 39

<div class="post-metadata">

**Author:** ![railjonrogut](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/railjonrogut/32/505_2.png) [@railjonrogut](https://forum.juce.com/u/railjonrogut)\
**Post date:** [December 1, 2017, 9:59am UTC](https://forum.juce.com/t/audioprocessorgraph-changebroadcaster/23776/39 "2017-12-01T09:59:31Z")

</div>

> [@jules](#):
>
> Between your changes and mine, we’ve tried a lot of different approaches to this and they’ll all have different performance characteristics with different use-cases! I’m really slammed this week but will try to come back to have a look at this when I get chance.

The answer may be to allow a graph to be a child of another graph… allowing MIDI in and out, etc. That would let us reduce the number of connections needing to be resorted.

> [@Chaining AudioProcessorGraphs](https://forum.juce.com/t/chaining-audioprocessorgraphs/12702):
>
> Does anyone have a simple example of how to hook up the output of one AudioProcessorGraph to a Node in another AudioProcessorGraph? I have: AudioProcessorGraph::AudioGraphIOProcessor\* m\_subProcIn; AudioProcessorGraph::AudioGraphIOProcessor\* m\_subProcOut; AudioProcessorGraph::Node::Ptr m\_subProcInputNode; AudioProcessorGraph::Node::Ptr m\_subProcOutNode; m\_subProcIn = new AudioProcessorGraph::AudioGraphIOProcessor (AudioProcessorGraph::AudioGraphI…

Cheers,

Rail

---

_[View the full topic](https://forum.juce.com/t/audioprocessorgraph-changebroadcaster/23776)._
