Latency problem on FX plugins...
-
@christoph-hart
I couldn't use an exported Hise instrument because it asks sample file locations. But I thinkit's only on FXes... -
I removed the obligatory sample dialogue a few weeks ago. Please make sure that problem persists on the most recent build.
-
For FX plugin don't forget to implement the usersettings (settingsButton.js) parameters because it works perfectly with me (reverb, delay, dynamics, etc. ... all compiled as FX plugins) because the most problem is the Buffer size and samplerate.
I remember a rompler made with Rackafx who only works at 44100. my friend used Ableton live with 48000 and had a semi tone up bug for the notes (played C and eared C#). i explained him to setup Live in 44100 and all was fixed.
maybe the same thing for your DAWs and your FX plugins from Hise.
Put the settings widget in your HISE plugins and take a look at your DAW parameter.
Sure it will fix it, because here not any latence problem with FX plugins.
EDIT: and yes, the last HISE commit fixed the "load samples" problem, i asked it to Christoph on one of my last last threads and he did (fixed) it ;)
-
@christoph-hart I've tested latest build and unfortunately problem persists :(
-
Is it ok now? Did you fix this latency problem? @christoph-hart
-
There is an another problem too; that I've posted before, for merged output on multi channel projects.
Thread & Video is here: https://forum.hise.audio/topic/616/merging-all-distributed-outputs-master-gain-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.
-
@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...
-
-
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.
-
@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. -
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). -
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?
Dan Korneff - Producer / Mixer / Audio Nerd
-
@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?
Dan Korneff - Producer / Mixer / Audio Nerd
-
@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...
