Don't include it in the DspObject header. It isn't needed in most objects and simply adds compile-time overhead.
…o deep into subgraphs as well. computeLocalProcessOrder is now more like a computeGlobalProcessOrder. Think about that.
Needs more testing, but looking good.
… to take advantage of the buffer pool. Test the concept of per-DspObject data. per-DspObject data concept needs to be tested more. Is it really faster than the usual DspObject list?
…ncluded in dsp node list.
…objects. When the input buffer to these objects is updated, they inform following objects of the buffer update.
… initialisation map in PdContext.
Variable name is shorter and more readable. Remove hasMessagesToProcess, no longer necessary.
…connection exists no work must be done.
…troduce local (float **) capable of quickly resolving output buffer changes of connecting objects. Quickly resolve multiple connections to a temporary input buffer on the stack. Allow Dsp obejcts to respond to integer or floating-point indicies in processDsp. Use local variables for most computations, instead of fetching them from the heap.
…s and outlets to be properly ordered depending on their lateral canvas position.
…jects to the inlet and outlet lists in PdGraphs.
…as only one input on a given dsp inlet, then the outlet buffer of the preceeding object is used as the inlet buffer of the receiving object. In this way a memcpy can be avoided in many cases (because many patches connect outlets to inlet serially, instead using the implicit add).