About Latency And Crashes ( Need Help )
-
@Lindon Thanks Lindon , But What's The Workaround?
-
I think setting the limiter attack time something above 10ms switches to non-lookahead mode.
-
@Christoph-Hart Thanks Christoph, I Did That, And The Result Is There Is No Latency AT All :)
-
@Christoph-Hart I tried this fix with the limiter, but it didn't work on this end. It appeared to work at first, but as soon as I adjusted the threshold, the audio became outta time
-
I'm also still getting some crashes on Mac using Ableton 10 when it's scanning the new plugin for the first time.
When on the loading screen, Ableton shuts down as soon as the scan reaches the new plugin. The next time you open Ableton you get a message saying something like:
'Abelton crashed because of 'x,y,z'.vst while scanning. Would you like Ableton to scan it again or blacklist it?'
As long as you scan it again then it appears in the folder and works fine after that. It's only on the first scan now.
The only prototypes of mine that I've noticed it crash with are ones that are using the Linkwitz-riley filters from scriptnode, and some that use normal convolution reverb.
-
@SteveRiggs Steve, I Don't Use Scriptnode At All Bro
Everything Done Using The Modules. -
@Natanr Strange. Are there any Convolution Reverb modules being used?
-
@SteveRiggs Here Is The Chain
Simple Gain > Parametric EQ > Routing Matrix > Saturator > Degrade > Shape FX > Parametrci Eq / Hp > Parametric Eq / Lp > Dynamics > Limiter > Routing Matrix > Simple Gain ( Master ) > Analyzer
Not Even A Single One !
-
Also, Scripted Lines Doesn't Do Anything With Modules, Just Simple Vectors
-
Weird. I haven't noticed crashes with any of those (so far)
-
@SteveRiggs I Never Seen Even A Single Crashes On My Macbook air 2018 Or My PC With An i3 Cpu At All.
