Plini update 2.0: Sample latency/CPU usage

@Gonzalo

Hey Gonzalo,

Any news for a new update to helps us get rid of the crackling/digital artefacts when switching presets ?

Hi @Fab. We’re currently working on the 2.0.2 version. If you want, you can send us a video clip showing the problem to support@neuraldsp.com. We’ve had difficulties trying to replicate the issue.

Ok no problem, I’ll make a video this weekend and send it to the support team !

1 Like

@Fab Awesome. Thank you.

Another plini 2.01 user weighing in with experiencing crackling from plini in over sampling mode on a regular basis.

It appears it was said in March 2020 that the 2.0.2 version was being worked on.

Also, well over a year ago NeuralDSP also said it had found an audio engine optimization to drastically reduce the CPU overhead, and would be rolling this optimization out to All plugins.
NeuralDSP announcement about audio engine - Jan 2021

It is now July 2022 and the Plini plugin was last updated in March 2020, over two years ago, and the Fortin NTS has an even older codebase - 2019.

Inside Davinci Resolve, both of these plugins will crackle/pop or refuse to work entirely if your buffer size is set below 256. That is too high of a latency for fast guitar work, and I’m a fast man.

Fortunately this does not happen in Ableton Live, but it would be nice to do everything inside Resolve since it is actually Free and can do pretty much everything in one spot, not just audio but video as well.

If we think about any of these plugins, you can really only do each amp or each artist once right? So, ongoing support and improvements to each of them should kind of be a given. You can’t buy a Tim Henson to get around a NTS Cpu load issue - they don’t sound the same.

1 Like

Hello @Gonzalo,

Same question as here: Plini CPU usage - #19 by peteliberati

Cory wong archetype and Fortin Cali have been updated in november 2021 to ATI engine, Plini archetype was supposed to be the next but it has not been updated at all.

It has been two years now that we encounter this CPU usage issue with this plugin, and 9 months since many of us are waiting for its ATI update.

Have you some news on this topic?

Thanks