Latency problem on FX plugins...

[resonant]

@christoph-hart said in Latency problem on FX plugins...:

I have checked this with the most recent DynamicFX example and there is no latency issue on FL Studio for me (FL Studio 12 64bit). There is some latency (512 samples) which is added for the plugin, but this is because FL Studio is constantly changing buffer sizes and I don't feel like hacking around the entire codebase just to make it work for this particular DAW.

It's not on FL studio only, I've used it on Reaper and Studio One and it does the same latency.

• So, if this issue doesn't apper on your system; what can cause that, what do you suggest? I'm using Visual Studio 2015. And should I clean Appdata folders before building Hise?

• What about the multi out merging problem? Routing matrix doesn't merge channels. It works on Hise but not working on host (Reaper, Studio One, Cubase...)

Best regards...

[staiff]

just tried a 10 FX rack (reverb, chorus, filter, saturator, etc. ...) in 32 and 64 bits VST WIN in Studio One, reaper and cakewalk/bandlab and all working well. No latency.

made with the latest version of HISE in date.

i use ASIO (behringer WDM audio) and ASIO4all.

[resonant]

@staiff It was doing that on Dynamics FX. Did you tried it?
Tweaking attack & release knobs also weirdly changes latency. I've downloaded ASIO SDK again from Steinberg and now the latency is very low.

[staiff]

yes tried the dynamic.

i remember with my old PC all worked fine since years. but one day adding FX in studio one caused latency. i didn't change anything. never found why. never found what caused this problem.

now i've a brand new PC so fresh installs, and all work fine with no latency with the same ASIO, DAW, VST and external soundcard.

so i don't know. HISE plugs is not the problem.
It's inside your config, but really don't know why/where (like me before).

[Christoph Hart]

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.

[resonant]

@christoph-hart Yes you are right, probably it is the reason.

[Dan Korneff]

@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?

[SteveRiggs]

@dustbro I just set the min value in properties to 10ms so it never goes below

[Dan Korneff]

@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?

[Dan Korneff]

@Christoph-Hart Adjusting the Limiter attack during playback creates some nasty audio glitching. Is this a known issue?

[SteveRiggs]

@dustbro

If you set your attack sliders properties like this it will work with 10ms as the min value :)

[clumsybear]

Good to know, wasn’t aware of the lookahead functionality below 10ms

[ustk]

What if you use Engine.setLatencySamples(Engine.getSamplesForMilliSeconds(10))?
10ms attack is a big min value for a limiter...