Massive latency on ReaInsert plugin (SOLVED)

[srdmusic]

I can can't seem to be able to bypass the latency caused by the ReaInsert plugin.

I'm using ReaInsert to route my external synths into a midi track. When I record enable the track with the ReaInsert on, I get a massive amount of latency from the external synth audio return. I've tried to disable anticipatory processing on the the track and I've disabled PDC on ReaInsert. I've also unchecked 'Automatic device latency adjustment' on ReaInsert.

Nothing seems to disable the large amount of PDC latency caused by the plugin. It seems to be a bug as I have very minimal latency when setting up my external instruments as traditional MIDI and separate audio track returns. I believe there is a bug in the latency being reported by the ReInsert plugin and also a bug in the option to disable PDC.

Has anyone else been able to work around this?

[EpicSounds]

Maybe you've seen this already but this is how I use ReaInsert with hardware synth
https://www.youtube.com/watch?v=MKEc0bYwJe8&t=180s

[srdmusic]

Thank you for the advice. After rewatching the video I caught the part about having to start the playhead before the synths re-calibrate the latency.

They work perfectly now.

Thank you.

[Luster]

Just found this topic which is marked as solved but so far I had the same trouble. Switching to "Prevent anticipative FX for track" did help but nonetheless I don't understand what is causing this.

Fireface setting: 128 samples
ReaInsert base latency with anticipative FX on: 4800 samples

[Cloudswim]

Originally Posted by EpicSounds

Maybe you've seen this already but this is how I use ReaInsert with hardware synth
https://www.youtube.com/watch?v=MKEc0bYwJe8&t=180s

Why use Ping detect instead of the Automatic device latency detection? It comes up as a different value every time I click ping detect.

[EpicSounds]

Originally Posted by Cloudswim

Why use Ping detect instead of the Automatic device latency detection? It comes up as a different value every time I click ping detect.

is your effect in bypass?

[Cloudswim]

Originally Posted by EpicSounds

is your effect in bypass?

Sorry I'm fairly new to Reaper, when you mean bypassed, are you refereeing to the green button labeled FX? If so no, its in the green state.

[EpicSounds]

I mean your hardware effect. In the case of a synth you'd need it set with no delays, chorus, verb and attack at lowest setting.

If the detected latency is slightly different each time with the synth, it's not too much of a worry because it won't be processed in parallel.

[Cloudswim]

Originally Posted by EpicSounds

I mean your hardware effect. In the case of a synth you'd need it set with no delays, chorus, verb and attack at lowest setting.

If the detected latency is slightly different each time with the synth, it's not too much of a worry because it won't be processed in parallel.

ah it does have some fx on.

what exactly does ping detect mean? and processed in parallel?

thanks for your explainations

[EpicSounds]

ping - sends a short tone to the external device and waits for a reply. The time difference is compensated for with delays.

If that tone that comes back is altered then the detected latency could be off.

Processed in parallel like using a compressor that's mixed with an uncompressed signal. A time difference of even a sample can cause terrible phase cancellation.

[Cloudswim]

Originally Posted by EpicSounds

Processed in parallel like using a compressor that's mixed with an uncompressed signal. A time difference of even a sample can cause terrible phase cancellation.

But I don't understand why a time difference would occur when recording parallel processed materials? If I understand correctly the synth and comp output signals are going into the audio interface at the same time, even if there is a latency it should align in 2 separate tracks ?