@jameslo Delay is 80ms and block size 64.
I tried lowering the delay but didn't seem to help much.

@whale-av Ouf,that sounds a bit complex yes...hehe. I will see a bit later about that.
I kind of feel it is not a midi issue though and maybe it's the whole PD engine having a bigger audio buffer? Is there a way for PD to show the latency processing?

The thing that led me to Pure Data is i wanted to try something similar to Bidule and see if it handled audio better,i had some crackling with Falcon Vst in some context with Bidule and in Pure data the crackling was gone...but it might be because the audio buffer is much larger,like changing the buffer on my audio card would make the crackles go away too but i didn't want to go above 512.
I read PD adds a bit of latency but +4096 samples latency doesn't seem normal?. I am testing this on a very old computer though and i need to test on my actual music laptop to see if it behaves the same way.
If PD doesn't end up being better for me that is ok too...i was just curious and wanted to try if it handled well my setup.

Ok did some more precise testing.
Used an external sequencer sending midi to PD triggering a click sample and did the same to Bidule triggering the same click sample....and PD is like lagging 4096 samples behind.
PD and Bidule using the same audio driver,same midi going in,same setup so i have no idea about this difference.

Hmm i may have exaggerated with 3-4 times more latency...maybe more like 2 times.
I tried with plugdata and have the normal latency,i see there's no Asio in plugdata possible?
So i switched to wasapi in PD and it seems to be ok now?
After repetitive testing of hiting my keyboard and trying to evaluate the latency by ears i am getting a bit confused...hehe,i will continue testing this a bit later!

@whale-av Thanks.

I tried a few things,different Vst,tried the [osc~] and same latency.Tried different Asio drivers,i am on windows 10 but anyway i don't have this much latency when i do the same thing in a different DAW.For example Plogue Bidule,exact same driver,same midi keyboard,same setup and the latency is the normal one i have with 512 samples where as in PD it is like 3-4 times more,well hard to measure by ears when i hit the key but it's not really playable.
I didn't intend to play live keyboard with PD but would be nice if i could get this to the normal latency with 512 samples.

That is the proper way to send midi to a synth right?

• Just to add, i used the first output of [notein] to control the frequency of an [osc~] and had the same latency.

Ok i managed to find some info,needed to use the [pack] object "i need to read on this!" with [notein] for the keyboard and played around with the [midi_note( message t0 convert the midi output of one [vstplugin~] into the other [vstplugin~]
All works but the midi has a big latency...not sure of this is normal or something in my setup.

Hello guys,
I just started using PD and really struggle in understanding basic stuff.
I come from Reaktor and damn,PD is like Chinese to me for now.
I am just trying to send midi into [vstplugin~] from my keyboard [notein] and from another [vstplugin~] outputting midi and nothing works. I can send a note on\off with the [midi_note( and [midi_noteoff( messages , that works but what am i supposed to do to make the midi works from [notein] or another [vstplugin~] outputting midi? Am i supposed to convert the midi data into something else before it connects to the inlet?