Does anyone know how to properly compensate for the latency of the supervp.cross~ object in order to sync the dry signal back with the processed audio?

The 'getlatency' message seems to be off by around around 500-1000 samples and manual adjustment by ear is needed in order to sync the dry and wet signals.

I'm currently using a click to measure this. Maybe if there was a way of measuring the delay between the dry and wet clicks that could work but the added spectral artefacts on the wet signal might make it difficult to do this accurately.

Is anyone else working with the supervp.cross~ object in this way and found a solution to latency compensation?

I guess this would apply to any spectral or latency producing object so hopefully another solution exists and its not waiting on a bug fix from Ircam.

Does anyone know how to properly compensate for the latency of the supervp.cross~ object in order to sync the dry  signal back with the processed audio?

Hi
Does anyone know how to properly compensate for the latency of the supervp.cross~ object in order to sync the dry  signal back with the p

ircam-supervp·cross~-latency-compensation-sync-issue

A possible solution for calculating the sample-accurate latency produced by supervp.cross~ (or any delay producing object as in the example below)

For some reason, the delay calculation varies each time run and between the gen~ based counter and the [timer] object.

The gen~ based counter is from the gen~.count patch in the /Max 7/Examples/gen/ folder

Screen Shot 2017-07-22 at 14.09.14.png

Update:

A possible solution for calculating the sample-accurate latency produced by supervp.cross~ (or any delay producing object as in the example below) 

Ircam supervp.cross~ latency compensation / sync issue