Ableton Forum

Standard amp modeling is done by explicitly simulating the (effects of) the many components of a physical amplifier. Some really good models have been built that way, but there are two potential hurdles:
Each new amp you want to model is kind of its own engineering project.
Even if you ...

[jur] wrote: ↑

Thu Jun 04, 2026 4:02 pm

Can't wait for the updated A2 m4l device

Here it is: https:/www.nyquistlimited.com

Just log in to Lemon Squeezy and download the new version

I have updated Live Amp Modeler to support loading the new generation of NAM models, "A2".

All included captures in the pack have also been converted to A2. This is a major improvement in both model accuracy and CPU efficiency compared to first-generation NAM profiles.

Open source external: https ...

As an example, Convolution Reverb uses multiconvolve~, an external from the HISS Tools package. I also imagine the new Softube devices


The Softube devices, yeah you're right, but they're really specific devices.
As for the HISS Tools, aren't they part of those Max externals Packages that get ...

As an example, Convolution Reverb uses multiconvolve~, an external from the HISS Tools package. I also imagine the new Softube devices use externals that contain DSP code from the corresponding VSTs. So this would suggest there are multiple externals that run on Push SA, but they're all provided by ...

[jur], is there any way to bring this up with the powers that be?

Some externals used in official packs clearly do run on Push SA, so Ableton must have recompiled them specifically for the Linux + Max setup used on Push.

I've been getting this request from multiple users. Someone recently said "It ...

I've just released Live Amp Modeler , a Max for Live pack for running neural amp captures ( NAM and AIDA-X ) and cabinet IRs natively in Ableton Live. No external plugins needed, and lower CPU usage.

Get it here: https://nyquistlimited.lemonsqueezy.com/

Demo and walkthrough: https://youtu.be ...

This exists now: https://youtube.com/shorts/mWUv7tMWVPQ

I'll be releasing it on April 28th!

It's built in the modular Ableton way (separate devices for amp models and cab IRs), leveraging racks for blending cabs, noise gating, etc.

It's also quite a bit more efficient than the official VST thanks ...

Great idea... aaand here it is! https://youtube.com/shorts/mWUv7tMWVPQ

Getting ready to release it on April 28th.

The core Max object is already on Github and it indeed uses NeuralAudio: https://github.com/apresta/neural_tilde

+1
Especially for people who go back and forth between recording live instruments and mixing, it would be such a time-saver to have total set latency shown (perhaps next to the CPU monitor). Also a switch to temporarily disable all non-zero latency devices would be great.

Question, all of you that chimed in with issues, are you on Windows or Mac OS?
None of you mention AU, and OP mentioned control s for saving so he's obviously on Windows. Maybe 15 years ago I experienced some instability with Live with a few specific plugins, but Live has not been an unstable DAW ...

Chiming in to add my +1.

Live with only stock devices is indeed a joy to use. The moment I bring in a few plugins, a project is bound to crash at some point. I've reported crashes to various plugin developers, but eventually concluded that it's something about how plugins are handled in Live. The ...

This keeps happening to me on two different Macs. I have to delete and rebuild Live's db to make the presets come back, but it only works for a limited time (maybe until anything triggers a change to the DB?).

iloyd2 if you point me to your report I can also chime in there

At least Ableton should provide a M4L API for devices to load samples from packs *without taking them out of Live*.

I just spent hours creating presets for two paid sample-based M4L devices, only to find out that my presets will become useless since they are actually accessing a temporary ...

Bumping this up. Plugin crashes are difficult to reliably reproduce. Can't Live report which plugin crashed, or at least log it somewhat clearly?