Problem with recursion check in AudioProcessorGraph

[railjonrogut]

You can check out previous threads:

[FR] AudioProcessorGraph addConnections/removeConnections

Okay a report back… I made the changes and it’s dramatically improved the profiling of my plug-in… Since I rarely just make a single connection at a time… I added methods to use OwnedArray::add() instead of OwnedArray::addSorted() and defer buildRenderingSequence() like: bool AudioProcessorGraph::addConnectionUnsorted (const uint32 sourceNodeId, const int sourceChannelIndex, const uint32 destNod…

AudioProcessorGraph && ChangeBroadcaster

So in my previous thread: I derived AudioProcessorGraph from ChangeBroadcaster and that worked perfectly in 4.2 – but I just tried doing that while testing 4.3.2 and 5.1.1 and if you derive AudioProcessorGraph from ChangeBroadcaster and try and process a block you get an EXC_BAD_ACCESS run-time error when it tries to call processAudio (the error location is consistent… but didn’t help to track down the cause of the issue BTW) Any suggestions on how to send a message to the main plug-in Audio…

Chaining AudioProcessorGraphs

I’d like to add a reference to a previous thread which discusses this same issue (slow graph manipulations with a lot of nodes/connections) https://forum.juce.com/t/audioprocessorgraph-slow-manipulations Cheers, Rail

Rail