delay compensation

[Dave Beep]

Hi,

I'm using the reason Rack effect plugin in Live and it is not reporting delay compensation correctly.

According to Ableton, it adding using 64 samples / 0.73ms latency.

I am having to add around 27.5ms extra compensation manually to get the track to sync.

The effects in the rack are:
- Polar Dual Pitch Shifter
- Channel Dynamics

This is using Reason 11 and Ableton live 10.

Is this a known issue? Is it fixed in R12?

[Dave Beep]

OK so stupidly I googled and read a bit after posting this. Polar is not even delay compensated within Reason standalone and or even internally within it's own routing of the dry signal. I assume the issue is specific to that device.

[PhillipOrdonez]

Yeah polar is that weird kid at school. He's awesome once you get to know him!

[Mnaisoa]

neither the dry signal routing nor the standalone version of the program does Polar use delay compensation. It seems that the problem is isolated to that particular device.
run 3

[ShadowMatriks]

Polar came out before delay comp was a thing in Reason, so there is a buffer!

Reason Studios could update it to fit in to the latest versions of Reason as real time FX but it appears to be a low priority and something they don't do often with old RE's.

You're not the only one who's gutted!

[ShadowMatriks]

Just checked the manual which says:

Slow
This is best suited for polyphonic audio and complex sounds. “Slow” mode has the highest latency (typically around
96ms) because it needs time to correctly analyze the frequencies in complex sounds.
• Medium
This is best suited for bassy monophonic sounds and also for drums and percussion. “Medium” mode has a little
higher latency than “Fast” mode (typically around 48ms) because it should also be able to accurately detect lower
frequencies.
• Fast
This mode is best suited for less bassy monophonic sounds, like vocals. “Fast” mode has the lowest latency
(typically around 24ms) because it’s not optimized to detect low frequencies.

Typically around makes it sound as though it's variable! Anyway they could have at least printed it on the back of the device instead of hiding it in the manual.