On 3/24/25 18:23, Pier Bar wrote:
You would typically use it for offloading audio processing to another CPU core, in particular if a single CPU cannot handle the full workload.
So it seems intended for audio rather than control signal operations...
i see how you come to this conclusion by christof's wording.
however, i wouldn't say that this is necessarily true.
the important fact to understand is, that the output of [pd~] is still fully deterministic (by keeping the operations *synchronous* with the parent Pd).
therefore, it is ill-suited for asynchronous offline processing (like training a neural network for 10 minutes at "full speed").
instead i would say that it is a good tool if you can formulate the problem like this: "I have a cool patch X that works great with the desired latency. I have another cool patch Y that also works nicely. But if I use them together, things start to fall apart." then you could run e.g. patch Y in a separate [pd~] instance.
fgdam IOhannes