NAM: Neural Amp Modeler

[Dom Mcsweeney]

Dialling it in with or without 'calibration' is totally valid.
One is more about accuracy, the other is more about creatively dialling in your own tones how you see fit.

Ultimately, the end goal is to a) not clip the inputs, b) sound good.

Whatever floats your boat is the right choice.

 

[volkan]

This is where these conversations always confuse me also. This is how you are supposed to use interfaces. I don't know why people recommend static values. You should set your interface based on your pickups, to where it is just under clipping.

I mostly use ToneX, but I basically set the knob on the interface to just under clipping based on which guitar I am using, and then in the ToneX software I set the input to just under clipping after that. That always gives me a good input range into the amp captures. If I want more or less gain at that point, I will use the input knob that is programmable for that preset.

This is i used to do until know. i will try to match thats been told here.

 

[MirrorProfiles]

This is where these conversations always confuse me also. This is how you are supposed to use interfaces. I don't know why people recommend static values. You should set your interface based on your pickups, to where it is just under clipping.

This isn't opposing knowing your headroom, they are 2 seperate things.

You can have your gain at 0 and have a perfectly optimised signal - this is how most interface manufacturers are designing their instrument inputs these days. Setting it to 0 means you can just use your specs to know your input headroom and you dont have to measure anything. It also means plugin manufacturers are able to design their plugins around a known variable. This is why you can use essentially the same input level for NDSP/UAD/Line 6 etc plugins.

 

[Shask]

This will likely hit quite some captures too hard. Not IK's own, though, as they seem to be made for pretty high levels (their hardware input default settings let one suggest that as well).

If it is too much gain then I would turn down the input on the capture itself (Gain knob on the ToneX), or use a different capture with a more appropriate gain range.

 

[2dor]

There's a guide here, which can be used in part or in whole, to work out all of these questions (especially if combined with the other links people have shared), including how to use a multi-meter:

How to determine the calibration levels of your recording setup — neural-amp-modeler 0.12 documentation

I think this is stellar information _BUT_ only / mostly for profile creators.. It's too technical for users imho.

 

[Dom Mcsweeney]

Yep quite true, however they did ask how to use a multimeter so I thought it might help in someway.

 

[Richard_G]

@2dor and @MirrorProfiles The two of you have the patience of a saint!

 

[2dor]

@2dor and @MirrorProfiles The two of you have the patience of a saint!

We've all been there & this topic's really instrumental to the overall user experience with plugins.

Just paying it forward.

 

[Sascha Franck]

If it is too much gain then I would turn down the input on the capture itself (Gain knob on the ToneX), or use a different capture with a more appropriate gain range.

Sure, but you might get a wrong impression of some captures when initially loading them.

 

[2dor]

Sure, but you might get a wrong impression of some captures when initially loading them.

Exactly!

Captures / profiles reamped with high dBu / headroom may sound way overgained that what unity gain should be.

The thing with these profiles is that they benefit from seeing a larger range of signal amplitudes at training so that the profiles can react properly when you put a boost in front; the neural network _knows_ how to respond & doesn’t halucinate an answer.

 

[Richard_G]

@2dor and @MirrorProfiles The two of you have the patience of a saint!

We've all been there & this topic's really instrumental to the overall user experience with plugins.

Just paying it forward.

Yeah. Absolutely!

And to be clear, I wasn’t just thinking about this thread, but about your continuous effort in addressing these issues in many settings and across boards and media, often despite what one could describe as tilting at windmills.

I just wanted to thank both of you for the effort. We’re all better off with these insights being spread.

 

[Orvillain]

wheeeeeeeeeeeee

 

[[Nathan]]

View attachment 57032


wheeeeeeeeeeeee

Let’s make an “unsolicited advice”
Thread about what could/should be added to a nam player plugin, that will definitely be a harmonious and sane experience

 

[DrewJD82]

I just got a CIOkS budle that had a Valeton GP-5 in it, which I saw loads up NAM profiles, so I guess I'll be giving these a shot soon.

 

[Ross Davies]

yes please @Ross Davies

Hi Guys, sorry for the late reply, I have been out of the office on annual leave — sadly without the Neural DSP Specs, I am not best placed to advise on this one. If you need our GENOME figures, I am your man! We actually have a helpful support article here for this if anyone is interested: https://helpdesk.two-notes.com/portal/en/kb/articles/calibrating-genome-s-input-your-audio-interface

 

[jle]

Hi guys, Ive been considering lately switching to a dedicated Mac Computer mainly as a NAM plateform, but I came across this issue on the github of the plugin : https://github.com/sdatkinson/NeuralAmpModelerPlugin/pull/599
It has been fixed but is yet to be included in a new release. Im not sure to understand in which context the bug applies exactly, but it seems to say that the standalone client crash at startup because of it. Does anyone here with v0.7.13 Nam plugin installed on a Mac can cofirm if the standlone client is working or not ?

 

[2dor]

Hi guys, Ive been considering lately switching to a dedicated Mac Computer mainly as a NAM plateform, but I came across this issue on the github of the plugin : https://github.com/sdatkinson/NeuralAmpModelerPlugin/pull/599
It has been fixed but is yet to be included in a new release. Im not sure to understand in which context the bug applies exactly, but it seems to say that the standalone client crash at startup because of it. Does anyone here with v0.7.13 Nam plugin installed on a Mac can cofirm if the standlone client is working or not ?

I'm running NAM v0.7.13 right now on an M2 Max 14" machine inside Reaper alongisde a slew of other plugins and it works perfectly fine.

 

[Dom Mcsweeney]

Hi guys, Ive been considering lately switching to a dedicated Mac Computer mainly as a NAM plateform, but I came across this issue on the github of the plugin : https://github.com/sdatkinson/NeuralAmpModelerPlugin/pull/599
It has been fixed but is yet to be included in a new release. Im not sure to understand in which context the bug applies exactly, but it seems to say that the standalone client crash at startup because of it. Does anyone here with v0.7.13 Nam plugin installed on a Mac can cofirm if the standlone client is working or not ?

Hey @jle - The NAM Plugin (vst/au) is generally very stable. The issue you've linked above is only related to the standalone app as far as I know. The standalone app is generally stable, but sometimes these edge cases do pop-up.

When you do eventually switch over to a new Mac (highly recommended for music production) - let us know how you get on!
(and if anything please report issues to the github issue / bug tracker).

 

[Elf]

Up to date M1 machine here, the stand alone latest NAM App crashes at startup most of the time, it works as expected in Logic.

 

[Dom Mcsweeney]

Up to date M1 machine here, the stand alone latest NAM App crashes at startup most of the time, it works as expected in Logic.

Hey @Elf, if poss, can you please make a new report about your experience with standalone crash?
you can do that here: bug tracker

any help like that goes along way to helping improve these little edge cases =)