Re: [PD-dev] why must one never send a message from a perform routine ?

2023-08-22 Thread Christof Ressi
I've always been puzzled by the fact that everything runs on a single thread in Pd. By default, Pd operates in "polling mode", i.e. the scheduler runs in its own thread (the main thread) and communicates with the audio callback via two lockfree ringbuffers (one for input, one for output).

Re: [PD-dev] why must one never send a message from a perform routine ?

2023-08-22 Thread Joseph Larralde
Thanks Christof for the additional insight. I've always been puzzled by the fact that everything runs on a single thread in Pd. I guess this single thread IS the audio thread because it processes audio, and I've always heard that one must never perform too many non-audio operations during an

Re: [PD-dev] why must one never send a message from a perform routine ?

2023-08-22 Thread Christof Ressi
How well does it work? It seems to work quite well. With synthetic benchmarks I can get a 6x speedup on my 8 core machine, but I need to do some more practical testing and benchmarking. It looks like the repo is based off of 0.52? I think it's based on 0.53. I want to rebase it on 0.54, but

Re: [PD-dev] why must one never send a message from a perform routine ?

2023-08-22 Thread Day Rush
How well does it work? It looks like the repo is based off of 0.52? Multithreaded DSP would have been much higher on my list than multi-channel, so I'm wondering if I could get away with using your tree as my basis for a while :) - d On Tue, 22 Aug 2023 at 01:17, Christof Ressi wrote: > To