in addition to the one time per block processing of messages, incoming and outgoing messages are delayed by on block each time they pass the borders of PD to the world

in addition to the one time per block processing of messages, incoming and outgoing messages are delayed by on block each time they pass the borders of PD to the world

messages in anykind within and outof PD are emitted max. one time per DSP block. this causes slighty noticeable jitter if the blocksize is too big. maybe [block~] with lower value in subpatch can resolve it a bit more, but i havent tested it yet.

ahh...but you can use PDvst as instrument with an similar patch as mine to determine the real timing within your daw.

i don't really know. after a few coffes i remembered that the PDvst ist either an instrument or an effect. i don't think its possible as a kind of midi effect.and please believe me, 5ms are really not much. you shouldn't be able to recognize it. the human ear can recognize differences above 25 ms in an not continous signal. i would give it a try.

for example: the minimum attack stage of an envelope in vst plugins ist about 5 ms too, to surpress clicking on unsynced oscillators

and you can always download the trial for maxforlive to check if its better.

i'm not familliar with the streamin/out object, but you could try to use the [udpsend~] and [udpreceive~] from the mrpeach externals. i use them to stream audio to my beaglebones inside my audio hardware to avoid cables that immobilize my laptop. never hd any problems with them.

blocksize = 64
i get ca .+/- 5 ms in the timing on input and output. your ears shoudln't notice this difference in a bad way.

you need to lower your blocksize in the Audio-Settings of PD to the minimum. The Bangs and all control signals in PD are processed with each block of audio.

on windows i was able to do what i want within ableton / cubase / Reaktor or any program itself...no problems. but i was not really able to build something that works god as an bridge between applications (except rewire). i tried all the midi-stuff to interconnect, but it was not really usable cause i had to setup everything everytime again, and sometimes a midi bridge won't work, or i wasn't able to interface to opensoundcontrol things like touchOSC with some application (especially ableton). but my ultimate goal was to get rid of all the audio cables in my system. laptop to my mastering compressor for example. or other stuff that need a cable. so i needed a solution like jackAudioConnectionKit which can work over network which is great if you put a arm-based oneboard computer in each component of your chain and connect them over network... i hope this wasn't demotivating.

what are you exactly trying to build so that you want to control you DAW externaly vi pd

and by the way... not only in windows i changed to linux to get finally full control over what my system does, but still got a long list of things that have to be changed to be used as a serious "production tool"