Frank Barknecht a écrit :
Hallo, (cc'ing pd-list)
...
That's actually exactly the setup I used when I was hit with problems in netsend/netreceive: I'm using a physics engine and graphical visualisation in one Pd, then connect this to another Pd which functions as the synth engine. The synth-"patch" is very simple and small, while most of the work is done in the other Pd. Physics is more demanding than sound synthesis in this case.
do you have exemple for this? with pmpd or msd, i was able to make most of the time patch with physics using very few CPU. i'm interested to know the limitation you can find in pmpd/msd.
i personnaly choose to avoid netsend / netreceive and compute everything in the same cpu/gpu. this is more optimised thant having lots of netsend/receive, so i've got better results when i have lot's of data for audio / video synthesys...
cyrille