Hoping for a M4L device that loads NAM files - is it realistic?

[TVbene]

Hey,
as someone who has only scratched the surface of M4L I'm just curious how much trouble a NAM loader in M4L would be for a pro.
There are a few open source C++ libraries for loading neural amp modeler (NAM) files (https://github.com/sdatkinson/NeuralAmpModelerCore, https://github.com/mikeoliphant/NeuralAudio). I guess advantages compared to the VST plugin could be a better integration with Push and easier customisation. Any thoughts?

[spiritofeden]

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

[[jur]]

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

That's great news!
I was actually searching a bit about this topic yesterday but I didn't find about the already existing [neural~] external. So nice to see the work's already done and can't wait to try this out.

@TVbene, unfortunately Push SA can't run externals...

[spiritofeden]

[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’d take [Push] from a cool tool you can use with your guitar to maybe the most versatile guitar platform on the market."

My external is open source and should be fairly easy to audit.

[[jur]]

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.

Which ones? AFAIK, Push can't run externals atm.

Are you planning to update your external to A2? I heard it's been recently released.

[spiritofeden]

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 Ableton.

Yes, I have already updated my external to A2, and I'm about to release a new version of the M4L pack (just need to update the included NAM profiles to A2 versions).

[[jur]]

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 integrated as native-Max at some point? I could totally be wrong, I've to admit I tend to lose track of things lately, the ecosystem has become so large!

Can't wait for the updated A2 m4l device

[spiritofeden]

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 integrated as native-Max at some point? I could totally be wrong, I've to admit I tend to lose track of things lately, the ecosystem has become so large!

Can't wait for the updated A2 m4l device

What I'm trying to say is that technically C++ externals can and do run on Push, but which one do is controlled by Ableton. It would be great if there was a process to submit more externals to be considered for inclusion, since some of these (like neural~) enable what would be a killer feature on Push SA.

[spiritofeden]

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