[BUG] CPU meter goes up to 150% when oepning any NAM profile in Ableton Live Suite 12

[MattRTGB]

A couple of months ago I started having this problem with NAM in Ableton Live Suite 12. Title is what happens, I don't think I can provide any more infos, other than the fact that NAM works fine in standalone and I've had this problem only when using the VST in the DAW. The thing is that I've been using NAM since December 2024 (in Live 12) and never had any problems. My DAW is also up to date.

Steps to reproduce the behavior:

1. Open the VST
2. Load ANY profile
3. CPU meter goes to 200% and (ofc) it sounds all glitchy

Screenshots

Computer & other info

• OS Windows 10
• Onboard graphics Nvidia GTX1050
• Plugin version 0.7.13
• VST3
• DAW Ableton Live Suite 12
• Audio interface Focusrite Scarlett Solo 4th Gen
• Sample rate 48.0 kHz
• Buffer size 128 samples
• Provide a model that the bug happens with: It happens with every model I've downloaded and used in the past, but I've tried these provided here (linear_10.nam and wavenet_minimal) and they work as expected (strange??)

• Does the bug not happen under some other conditions? I don't know. Like I said, I guess it's a DAW problem.

[sdatkinson]

Thanks for checking the models I linked in the issue template. Those are just lighter models to rule out that CPU issues are just due to an underpowered computer.

A few follow-up questions:

• What amount of CPU do other plugins use that I might know of?
• Do earlier versions of this plug-in have the same issue?
• Do other plugins that play NAM?

[MattRTGB]

Thanks for checking the models I linked in the issue template. Those are just lighter models to rule out that CPU issues are just due to an underpowered computer.

A few follow-up questions:

* What amount of CPU do other plugins use that I might know of?

* Do earlier versions of this plug-in have the same issue?

* Do other plugins that play NAM?

1. If we're talking about guitar plugins, I've tried Amplitube, Tonex and even Neural DSP. I can't say for sure at the moment, but CPU usage should be normal: around 10% I guess?
2. I haven't tried previous versions yet. I started using NAM with version 0.7.12 and even when I switched to the latest, it was all working fine.
3. I'm not sure I understand this question, sorry.

[sdatkinson]

1. It'd be good to check. This way I'll be able to verify that the ratio is similar on my side versus if something is actually wrong. The way i recommend doing this is to do an off-line render of 1 track of audio with only the plugin on it using a buffer size like what you'd use when playing. I'm not sure about Ableton, but REAPER provides the ability to do this.
2. For example, NAM Unviersal, Ritual, GENOME (CODEX inside), etc.