HISE pitch shift node introduces 100-200ms delay

[Straticah]

Hey there!

Maybe this is normal but i am using the HISE pitch shift node in a musical context.

As you can see it introduces a delay shifting the whole beat.

Any alternatives or external C++ ones that are worth checking out?

[dannytaurus]

@Straticah Pitch shifting causes latency. Have you tried Tools > Check latency of signal chain?

Also, this post: https://forum.hise.audio/topic/13654/latency-issuewith-fx-pitch_shift?_=1771883682066

[HISEnberg]

@Straticah ya measure the latency introduced by the pitch node, then delay the dry signal by the same amount of samples. Use Engine.getLatencyInSamples to find it, then use Engine.seLatencyInSamples. This reports the Latency introduced to your DAW and the DAW should adjust to compensate.

[resonant]

@Straticah A dynamic latency based on the pitch shift value. This has been measured before, so it will be useful for you:

https://forum.hise.audio/topic/14160/latency-compensation-not-being-triggered-in-daw/14?_=1771933207445

[dannytaurus]

@HISEnberg said in HISE pitch shift node introduces 100-200ms delay:

Use Engine.getLatencyInSamples to find it, then use Engine.seLatencyInSamples.

It's Engine.getLatencySamples and Engine.setLatencySamples (no In).

And getLatencySamples doesn't calculate the latency. It just returns whatever you set with setLatencySamples.

Use "Tools > Check latency of signal chain" to calculate the actual latency of the plugin.

@resonant Ah yes, that was the post I was looking for!

[HISEnberg]

@dannytaurus thanks for the correction!

[Straticah]

@HISEnberg @dannytaurus @resonant thanks guys!

I am actually only using 2 settings one for 1 oct aone for 2 octaves.

So the delay should be easy to detect.

Is it possible to tell the DAW we have x amount of delay and compensate for it?

[HISEnberg]

@Straticah yup checkout @resonant ’s link, someone already calculated the latency for you. So you just need an if/else statement to set the latency based on the octave amount.