Latency compensation not being triggered in daw

[dannytaurus]

@David-Healey Yeah, good call. It should probably be the smp value, not the ms value.

EDIT: see above

[pcs800]

@dannytaurus Ok, so put 7232 in instead of 164?

[dannytaurus]

@pcs800 Yep, see if it sounds right.

Sanity check: 7232 samples at 44.1kHz = 163.9909297052ms

[pcs800]

@dannytaurus After adding it, this is what I get with the plugin in a daw.

https://drive.google.com/file/d/1ZrUZcTNQj-GVh9GH7mndqMQTyzoaA_FO/view?usp=sharing

[resonant]

@pcs800 As I previously mentioned, the delay is not a fixed value, it depends how much pitch change applied

[dannytaurus]

@pcs800 Yep, it's probably like @resonant said - each pitch shift will cause a different latency value. The lower octaves must have less latency and the higher octaves are giving the max 7232 latency. Therefore the lower octaves will come in too early.

Just an idea...

Find the latency of each one by putting it alone in a project. Then when you have all 4 latency values you can compensate.

Example numbers:

Pitch -2 = 4000
Pitch -1 = 5000
Pitch +1 = 6000
Pitch +2 = 7000

So the max latency is 7000 samples. Now you know how much fixed delay to add after each pitch node

Pitch -2 needs 3000 delay
Pitch -1 needs 2000 delay
Pitch +1 needs 1000 delay
Pitch +2 needs zero delay
Original needs 7000 delay

That should align all the outputs and as long as you report 7000 (or whatever) to the host, everything should be in time.

That might be all nonsense, but it's worth a try.

[pcs800]

@dannytaurus Hmm, this is going to be tricky, but I will try. Thanks :-)

[pcs800]

@dannytaurus This is what I came up with

Original signal only: 7232
-1oct:3068
-2oct:2659
+1oct:6143
+2oct:7232

Max: 7232

-1oct: Needs 4164
-2oct: Needs 4573
+1oct: Needs 1089
+2oct: Needs none
Original Sig: Needs none

I'll try it

[pcs800]

@dannytaurus Worked like a charm!
Thanks for your input.

[dannytaurus]

@pcs800 Awesome!