Hi,
Is there any reason why the minimum latency I get with Pd is more than twice the minimum latency I get with maxMSP? 460 samples - Pd 216 samples - MaxMSP
I'm trying the demo of maxMSP on winXP for the first time, and writing the same patch in both programs which simply records the [noise~] input to [dac~ 1] and the return path from [adc~ 1] to wavfiles (from which I then do interpolated cross-correlation and peak detection in matlab), the numbers I get out are astounding.
I use the M-audio 1010 which has a 'latency' control in the 'control panel' software of the driver. Playing around with Pd's 'audiobuf' values seems to have a compound effect with this 'latency' value, where unless you select '64 samples' you cannot get anywhere near good latency. This is the only thing that effects latency in maxMSP, while in Pd I have the additional parameter 'audiobuf' to play with, although even putting this to 1 or 2 still gives latency values far removed from the ones I get with max.....! Is there something going on here I don't know about? Just trying to work out if/why Pd is underperforming.....thanks.
Matt
-=-=-=-=-=-=-=-=-=-=-=-=- http://www.loopit.org/ -=-=-=-=-=-=-=-=-=-=-=-=-
Hallo, matthew jones hat gesagt: // matthew jones wrote:
Is there any reason why the minimum latency I get with Pd is more than twice the minimum latency I get with maxMSP? 460 samples - Pd 216 samples - MaxMSP
I think Pd is doing some extra buffering. At least it does so on Linux, where Pd also has latencies lower than other, low latency optimized applications like Ardour. So your numbers don't surprise me, as they are similar if you compare Pd to other apps on Linux.
Frank Barknecht _ ______footils.org__