thegame
Well-known member
But will A2 be a happy meal in 3 years?Fair enough, to argue is to make clear.
However, you've been eating McDonalds compared to the 5 star Michelin chef that NAM A2 is.
But will A2 be a happy meal in 3 years?Fair enough, to argue is to make clear.
However, you've been eating McDonalds compared to the 5 star Michelin chef that NAM A2 is.
Next iterations will probably come and remain at the top. Open source is the king.But will A2 be a happy meal in 3 years?
Fair enough, to argue is to make clear.
However, you've been eating McDonalds compared to the 5 star Michelin chef that NAM A2 is.
Next iterations will probably come and remain at the top. Open source is the king.
I didn't really notice a difference between A1 and A2 from an audio quality standpoint, the most noticeable thing was that the CPU load went down significantly.One nice thing about NAM is if you keep the audio files, you should be able to retrain your sounds to the new version when it becomes A3.
Can you expand on that please?Well good news, A2 can make calibrated captures where you can turn knobs.
I didn't really notice a difference between A1 and A2 from an audio quality standpoint, the most noticeable thing was that the CPU load went down significantly.
NAM A2 allows you to make a capture not of a single knob position, but somewhat the whole spectre of them. @2dor can give you more detailed info because I am broke and don’t have first hand experience.Can you expand on that please?
Along those lines, I think that NAM beats Tonex when it comes to backing off on your volume control too. It behaves more like the real amp does.Between ToneX V2 and NAM A2, they are both very good, but if you just let a chord ring out, I notice NAM has more note clarity. It is a little more hi-def, less grainy, more clear, etc...
Along those lines, I think that NAM beats Tonex when it comes to backing off on your volume control too. It behaves more like the real amp does.
I hung out with a friend who's a great in the box guy and we loaded up the NAM plugin and a basic bitch Vox AC30 Top Boost model. It sounded (and FELT) like I was hearing a Brendan O'Brien level bed track.I dont do that much, but I can believe it. It is those fine details that takes the new capturing tech from great to amazing. The pick attack is the area I am picky about. Most classic modeling devices have a squishier smooth pick attack that bugs me. I dont notice that with captures.
That was also possible with NAM A1 but a lot less people had access to a framework that would enable it.NAM A2 allows you to make a capture not of a single knob position, but somewhat the whole spectre of them. @2dor can give you more detailed info because I am broke and don’t have first hand experience.
UT2004 is free, runs great on 10+ year old integrated graphics, has team play and and voice chat.
Sounds like it's time to go to NAM!
The "calibration" bit tackles a different problem which is as follows:
- How do I, the author, make sure that this profile behaves exactly as the real amp I'm modeling across a multitude of audio interfaces / units ?
A challenge seen in early-days NAM (and amp sims suffer/suffered from the exact problem) was people were getting pretty different results when loading the same NAM capture / profile / model.
Your hard-rock JCM800 profile would sound clean for one user while another user would report that it's straight up unusable because of all the crazy amount of gain it had.
This came down to audio interfaces and how their instrument inputs are not equally "hot" across different manufacturers (and that's not even accounting for users jacking up the Gain knob on their Guitar Input haha).
If you were to generate a 1KHz 1Vrms sine tone into the instrument inputs on interfaces from different manufacturers (ie. Audient, Focusrite, RME, MOTU etc), chances are the resulting dBFS readings you'd see in the digital domain / DAW would not be the same.
And it's this exact thing that calibration wants to tackle.
It splits the responsability between:
1. the NAM profile creator: needs to ensure they know what their signal chain is calibrated for by measuring the maximum voltage value (with a multimeter) their interface puts out as the signal reaches the amp's input during the reamping process. That's the short of it; the long read is here:
https://neural-amp-modeler.readthedocs.io/en/latest/tutorials/calibration.html
2. the user or hardware / pedal manufacturer: need to ensure they know how hot their guitar instrument input is and disclose this value to the software player they're using.
For people using the vanilla NAM Gateway plugin (which is still probably the best choice for anybody starting with NAM), the guide I did last year still holds up as far as getting started (as an end-user) with calibrated profiles:
Having a good grasp on & using calibrated NAM profiles allows users to get an accurate response from stacking several NAM profiles together like:
- NAM boost > NAM amp
- NAM boost > NAM preamp > NAM poweramp
The vid that walks people through stacking calibrated profiles is below; recorded for A1 but still applies for A2 as well:
Sorry for the bedroom video production etc; I'm not a YT guy - just did it to help folks out.
Fantastic!Paradex is NAM A2, but is a method of capturing an amp with the knobs at all possible pictures. Still a work in progress though, it is in Beta testing right now.
It sure is - a lot of folks had that happen with amp sims too until @easstudios did his research / data gathering on calibration levels for them.Input calibration is so key to getting good results with NAM. I imagine that there are a bunch of folks out there who've tried NAM without adjusting their settings, and have brushed it off as not sounding all that great and completely dismissed it.
Yeah, I struggled with my G-System input changing the guitar tone for awhile, and eventually let it go for the Kemper. I never tried the second version of the G-System which apparently had improved buffering.I've been using various digital modelers for many years, starting with the first Vox ToneLab, the tabletop version, currently using a Helix Stadium XL as my modeler, and a VP4.
input gain / buffers were an issue back when I had my G-System too; and just about every digital modeler I've used.
thinking back on guitar technology of the last 20 - 30 years, it's amazing to consider the collective time, effort, investment, etc. just to recreate the sound and feel of tube amps and analog signal processing; mid-20th century tech.
I suppose once you understand how captures work, and have your capture "rig" configured, making good captures becomes easier? just as learning how your digital modeler works and how to get the sounds you want takes time to learn and become proficient makes it faster/easier.
It's still not as easy as turning on a good tube amp you like, with whatever effects pedals/racks you like.
Digital ease of use has come a long way, but it's still not tube amp simple. Tube amps just do what they do; what they've always done; simple and easy.
SMH.
The "calibration" bit tackles a different problem which is as follows:
- How do I, the author, make sure that this profile behaves exactly as the real amp I'm modeling across a multitude of audio interfaces / units ?
A challenge seen in early-days NAM (and amp sims suffer/suffered from the exact problem) was people were getting pretty different results when loading the same NAM capture / profile / model.
Your hard-rock JCM800 profile would sound clean for one user while another user would report that it's straight up unusable because of all the crazy amount of gain it had.
This came down to audio interfaces and how their instrument inputs are not equally "hot" across different manufacturers (and that's not even accounting for users jacking up the Gain knob on their Guitar Input haha).
If you were to generate a 1KHz 1Vrms sine tone into the instrument inputs on interfaces from different manufacturers (ie. Audient, Focusrite, RME, MOTU etc), chances are the resulting dBFS readings you'd see in the digital domain / DAW would not be the same.
And it's this exact thing that calibration wants to tackle.
It splits the responsability between:
1. the NAM profile creator: needs to ensure they know what their signal chain is calibrated for by measuring the maximum voltage value (with a multimeter) their interface puts out as the signal reaches the amp's input during the reamping process. That's the short of it; the long read is here:
https://neural-amp-modeler.readthedocs.io/en/latest/tutorials/calibration.html
2. the user or hardware / pedal manufacturer: need to ensure they know how hot their guitar instrument input is and disclose this value to the software player they're using.
For people using the vanilla NAM Gateway plugin (which is still probably the best choice for anybody starting with NAM), the guide I did last year still holds up as far as getting started (as an end-user) with calibrated profiles:
Having a good grasp on & using calibrated NAM profiles allows users to get an accurate response from stacking several NAM profiles together like:
- NAM boost > NAM amp
- NAM boost > NAM preamp > NAM poweramp
The vid that walks people through stacking calibrated profiles is below; recorded for A1 but still applies for A2 as well:
Sorry for the bedroom video production etc; I'm not a YT guy - just did it to help folks out.