Latency problem on FX plugins...
-
Ah now I understand. The dynamics module has a "lookahead" mode when you turn the limiter attack below 10ms (or something like that). In this case it needs to analyse the future signal hence introduce latency.
-
@christoph-hart Yes you are right, probably it is the reason.
-
@Christoph-Hart said in Latency problem on FX plugins...:
The dynamics module has a "lookahead" mode when you turn the limiter attack below 10ms (or something like that). In this case it needs to analyse the future signal hence introduce latency.
I'm just noticing this now. Is there a way to compensate for the "look ahead" latency?
-
@dustbro I just set the min value in properties to 10ms so it never goes below
-
@SteveRiggs said in Latency problem on FX plugins...:
I just set the min value in properties to 10ms so it never goes below
is 10ms the actual value?
-
@Christoph-Hart Adjusting the Limiter attack during playback creates some nasty audio glitching. Is this a known issue?
-
@dustbro
If you set your attack sliders properties like this it will work with 10ms as the min value :)

-
Good to know, wasn’t aware of the lookahead functionality below 10ms
-
What if you use
Engine.setLatencySamples(Engine.getSamplesForMilliSeconds(10))?
10ms attack is a big min value for a limiter... -
i had to set eh latency upto 80ms, for the sample to sync. inside flstudio and reaper