<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>https://namforum.com/wiki/index.php?action=history&amp;feed=atom&amp;title=Neural_Amp_Modeler</id>
	<title>Neural Amp Modeler - Revision history</title>
	<link rel="self" type="application/atom+xml" href="https://namforum.com/wiki/index.php?action=history&amp;feed=atom&amp;title=Neural_Amp_Modeler"/>
	<link rel="alternate" type="text/html" href="https://namforum.com/wiki/index.php?title=Neural_Amp_Modeler&amp;action=history"/>
	<updated>2026-09-01T07:20:30Z</updated>
	<subtitle>Revision history for this page on the wiki</subtitle>
	<generator>MediaWiki 1.46.0</generator>
	<entry>
		<id>https://namforum.com/wiki/index.php?title=Neural_Amp_Modeler&amp;diff=11&amp;oldid=prev</id>
		<title>NAMFORUM Sysop: Created page</title>
		<link rel="alternate" type="text/html" href="https://namforum.com/wiki/index.php?title=Neural_Amp_Modeler&amp;diff=11&amp;oldid=prev"/>
		<updated>2026-09-01T05:59:14Z</updated>

		<summary type="html">&lt;p&gt;Created page&lt;/p&gt;
&lt;p&gt;&lt;b&gt;New page&lt;/b&gt;&lt;/p&gt;&lt;div&gt;= Neural Amp Modeler =&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;Neural Amp Modeler (NAM)&amp;#039;&amp;#039;&amp;#039; is a free and open-source system for creating highly accurate digital models of nonlinear audio equipment using deep learning.&lt;br /&gt;
&lt;br /&gt;
NAM is commonly used to model guitar and bass amplifiers, pedals, preamps, and related signal chains. Unlike a conventional algorithmic model designed specifically around a particular amplifier or circuit, a NAM model is trained from measured input and output audio representing the behavior of the equipment being modeled.&lt;br /&gt;
&lt;br /&gt;
NAM is both a technology and an open-source ecosystem. Models can be created independently, exchanged as files, and played by software and hardware that implement compatible NAM playback.&lt;br /&gt;
&lt;br /&gt;
== Overview ==&lt;br /&gt;
&lt;br /&gt;
A typical NAM modeling workflow consists of:&lt;br /&gt;
&lt;br /&gt;
# Obtaining the standardized NAM training signal.&lt;br /&gt;
# Sending that signal through the equipment to be modeled.&lt;br /&gt;
# Recording the equipment&amp;#039;s output.&lt;br /&gt;
# Training a neural-network model using the original input and recorded output.&lt;br /&gt;
# Exporting the trained model as a &amp;#039;&amp;#039;.nam&amp;#039;&amp;#039; file.&lt;br /&gt;
# Loading that model into compatible playback software or hardware.&lt;br /&gt;
&lt;br /&gt;
This separation between &amp;#039;&amp;#039;&amp;#039;capture, training, model file, and playback&amp;#039;&amp;#039;&amp;#039; is an important characteristic of the NAM ecosystem.&lt;br /&gt;
&lt;br /&gt;
A model does not have to be trained by the device that eventually plays it.&lt;br /&gt;
&lt;br /&gt;
== Open-source architecture ==&lt;br /&gt;
&lt;br /&gt;
NAM is an open-source project.&lt;br /&gt;
&lt;br /&gt;
The project separates several major functions into different software components, including:&lt;br /&gt;
&lt;br /&gt;
* Training code used to create models&lt;br /&gt;
* Core DSP used to run models in real time&lt;br /&gt;
* Plugin and standalone software used for playback&lt;br /&gt;
&lt;br /&gt;
This architecture allows third-party developers to incorporate NAM playback into their own software and hardware.&lt;br /&gt;
&lt;br /&gt;
It also allows researchers and developers to examine, modify, and extend the underlying technology rather than treating the modeling system as a closed platform.&lt;br /&gt;
&lt;br /&gt;
== What NAM can model ==&lt;br /&gt;
&lt;br /&gt;
NAM is designed for modeling nonlinear audio systems.&lt;br /&gt;
&lt;br /&gt;
Common targets include:&lt;br /&gt;
&lt;br /&gt;
* Guitar amplifiers&lt;br /&gt;
* Bass amplifiers&lt;br /&gt;
* Overdrive pedals&lt;br /&gt;
* Distortion pedals&lt;br /&gt;
* Boosts&lt;br /&gt;
* Preamps&lt;br /&gt;
* Combinations of nonlinear devices&lt;br /&gt;
* Larger signal chains&lt;br /&gt;
&lt;br /&gt;
The practical suitability of a particular device depends on whether its behavior can be represented effectively by the model architecture and training process.&lt;br /&gt;
&lt;br /&gt;
NAM should not be assumed to reproduce every possible type of audio processor equally well.&lt;br /&gt;
&lt;br /&gt;
Time-varying effects, long delays, modulation, reverberation, and other systems with behavior fundamentally different from the equipment NAM was designed around may require different modeling approaches.&lt;br /&gt;
&lt;br /&gt;
== Snapshot models ==&lt;br /&gt;
&lt;br /&gt;
Most NAM models used for amplifiers and pedals are &amp;#039;&amp;#039;&amp;#039;snapshot models&amp;#039;&amp;#039;&amp;#039;.&lt;br /&gt;
&lt;br /&gt;
A snapshot model represents the behavior of equipment at the configuration used when the training data was recorded.&lt;br /&gt;
&lt;br /&gt;
For example, if an amplifier is captured with a particular combination of:&lt;br /&gt;
&lt;br /&gt;
* Gain&lt;br /&gt;
* Bass&lt;br /&gt;
* Middle&lt;br /&gt;
* Treble&lt;br /&gt;
* Presence&lt;br /&gt;
* Channel&lt;br /&gt;
* Boost or voicing switches&lt;br /&gt;
&lt;br /&gt;
the resulting NAM represents that measured configuration.&lt;br /&gt;
&lt;br /&gt;
Playback controls can alter the signal around or after the model, but they should not automatically be interpreted as equivalent to changing the corresponding controls on the original amplifier.&lt;br /&gt;
&lt;br /&gt;
For substantially different amplifier settings, separate NAM models are commonly created.&lt;br /&gt;
&lt;br /&gt;
== Training data ==&lt;br /&gt;
&lt;br /&gt;
NAM training requires paired input and output data.&lt;br /&gt;
&lt;br /&gt;
The &amp;#039;&amp;#039;&amp;#039;input&amp;#039;&amp;#039;&amp;#039; is the known signal sent into the equipment.&lt;br /&gt;
&lt;br /&gt;
The &amp;#039;&amp;#039;&amp;#039;output&amp;#039;&amp;#039;&amp;#039; is the response recorded after that signal passes through the equipment being modeled.&lt;br /&gt;
&lt;br /&gt;
The trainer uses the relationship between these signals to learn a mathematical model that predicts how the equipment transforms incoming audio.&lt;br /&gt;
&lt;br /&gt;
For the simplified NAM training workflow, the project provides a standardized training signal.&lt;br /&gt;
&lt;br /&gt;
A typical signal path is:&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;NAM training signal → audio interface → reamp/capture path → device under test → audio interface → recorded output&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
&lt;br /&gt;
See:&lt;br /&gt;
&lt;br /&gt;
* [[Capture Signal Chain]]&lt;br /&gt;
* [[Reamping for Capture]]&lt;br /&gt;
* [[Gain Staging and Calibration]]&lt;br /&gt;
* [[Training a NAM Model]]&lt;br /&gt;
&lt;br /&gt;
== Local training ==&lt;br /&gt;
&lt;br /&gt;
NAM provides tools for training models locally on a computer.&lt;br /&gt;
&lt;br /&gt;
The simplified local GUI trainer allows the user to select the original NAM input file and the recorded output file and then train a model.&lt;br /&gt;
&lt;br /&gt;
The current documented simplified workflow uses 48 kHz, 24-bit WAV data and requires the returned recording to match the length of the supplied input file.&lt;br /&gt;
&lt;br /&gt;
The trainer also attempts to determine and compensate for round-trip latency between the input and output recordings.&lt;br /&gt;
&lt;br /&gt;
More advanced command-line training tools provide greater control over the model architecture, training data, and learning configuration.&lt;br /&gt;
&lt;br /&gt;
See [[Training a NAM Model]].&lt;br /&gt;
&lt;br /&gt;
== Cloud and third-party training ==&lt;br /&gt;
&lt;br /&gt;
NAM models do not have to be trained on the user&amp;#039;s own computer.&lt;br /&gt;
&lt;br /&gt;
The NAM project provides a Google Colab workflow for cloud-based training.&lt;br /&gt;
&lt;br /&gt;
Third-party services can also train compatible NAM models. This makes it possible to create NAM captures without maintaining a local machine-learning environment.&lt;br /&gt;
&lt;br /&gt;
The current official NAM site identifies &amp;#039;&amp;#039;&amp;#039;TONE3000&amp;#039;&amp;#039;&amp;#039; as a community model library and a service capable of training NAM models.&lt;br /&gt;
&lt;br /&gt;
== The .nam model file ==&lt;br /&gt;
&lt;br /&gt;
Trained NAM models are normally distributed as files using the:&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;.nam&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
&lt;br /&gt;
file extension.&lt;br /&gt;
&lt;br /&gt;
A &amp;#039;&amp;#039;.nam&amp;#039;&amp;#039; file contains the information required by compatible playback software to reconstruct and run the trained neural-network model.&lt;br /&gt;
&lt;br /&gt;
The format includes information describing the model architecture, configuration, weights, sample rate, and optional metadata.&lt;br /&gt;
&lt;br /&gt;
See [[NAM Model File Format]].&lt;br /&gt;
&lt;br /&gt;
== Model metadata ==&lt;br /&gt;
&lt;br /&gt;
The NAM file specification supports metadata that can provide useful information about a model and its creation.&lt;br /&gt;
&lt;br /&gt;
Depending on the file and trainer used, metadata may include information such as:&lt;br /&gt;
&lt;br /&gt;
* Model name&lt;br /&gt;
* Model creator&lt;br /&gt;
* Equipment manufacturer&lt;br /&gt;
* Equipment model&lt;br /&gt;
* Equipment type&lt;br /&gt;
* Tone type&lt;br /&gt;
* Training information&lt;br /&gt;
* Input calibration&lt;br /&gt;
* Output calibration&lt;br /&gt;
&lt;br /&gt;
Metadata is especially valuable when models are distributed publicly because the filename alone may provide little information about how the model was created.&lt;br /&gt;
&lt;br /&gt;
== Calibration metadata ==&lt;br /&gt;
&lt;br /&gt;
NAM supports calibration metadata describing the relationship between digital signal level and the analog levels used during capture.&lt;br /&gt;
&lt;br /&gt;
Two important values are:&lt;br /&gt;
&lt;br /&gt;
* &amp;#039;&amp;#039;&amp;#039;input level&amp;#039;&amp;#039;&amp;#039; — the analog level corresponding to digital full scale at the input of the modeled equipment&lt;br /&gt;
* &amp;#039;&amp;#039;&amp;#039;output level&amp;#039;&amp;#039;&amp;#039; — the analog return level corresponding to digital full scale in the recording system&lt;br /&gt;
&lt;br /&gt;
Correct calibration can help compatible playback systems reproduce the gain relationship of the original analog equipment.&lt;br /&gt;
&lt;br /&gt;
Calibration metadata is optional. A model without it can still operate, but the relationship between digital playback level and the original equipment may not be accurately reproduced.&lt;br /&gt;
&lt;br /&gt;
See [[Gain Staging and Calibration]].&lt;br /&gt;
&lt;br /&gt;
== A1 architecture ==&lt;br /&gt;
&lt;br /&gt;
The earlier standard NAM WaveNet architectures are now collectively referred to as &amp;#039;&amp;#039;&amp;#039;A1&amp;#039;&amp;#039;&amp;#039;.&lt;br /&gt;
&lt;br /&gt;
These include architectures historically described as:&lt;br /&gt;
&lt;br /&gt;
* Standard&lt;br /&gt;
* Lite&lt;br /&gt;
* Feather&lt;br /&gt;
* Nano&lt;br /&gt;
&lt;br /&gt;
The A1 terminology was introduced to distinguish the original architecture family from the newer [[NAM A2 Architecture|A2]] generation.&lt;br /&gt;
&lt;br /&gt;
Existing A1 models remain part of the NAM ecosystem and continue to be supported by compatible NAM implementations.&lt;br /&gt;
&lt;br /&gt;
== A2 architecture ==&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;A2&amp;#039;&amp;#039;&amp;#039; is the current standard NAM architecture generation.&lt;br /&gt;
&lt;br /&gt;
A2 was officially released on &amp;#039;&amp;#039;&amp;#039;June 2, 2026&amp;#039;&amp;#039;&amp;#039;.&lt;br /&gt;
&lt;br /&gt;
It superseded A1 as the default architecture for newly trained snapshot models while retaining compatibility with existing A1 models.&lt;br /&gt;
&lt;br /&gt;
Current NAM simplified training workflows, including the official Colab and local GUI trainers, can create A2 models.&lt;br /&gt;
&lt;br /&gt;
A2 support requires sufficiently recent NAM playback implementations.&lt;br /&gt;
&lt;br /&gt;
See [[NAM A2 Architecture]].&lt;br /&gt;
&lt;br /&gt;
== Playback ==&lt;br /&gt;
&lt;br /&gt;
A &amp;#039;&amp;#039;.nam&amp;#039;&amp;#039; file does not produce audio by itself.&lt;br /&gt;
&lt;br /&gt;
It must be loaded into software or hardware capable of running the model.&lt;br /&gt;
&lt;br /&gt;
NAM playback can exist in:&lt;br /&gt;
&lt;br /&gt;
* Audio plugins&lt;br /&gt;
* Standalone applications&lt;br /&gt;
* Hardware processors&lt;br /&gt;
* Amplifiers&lt;br /&gt;
* Embedded products&lt;br /&gt;
* Third-party software&lt;br /&gt;
&lt;br /&gt;
Because NAM&amp;#039;s real-time DSP implementation is available as open-source code, manufacturers and developers can integrate NAM playback into their own products.&lt;br /&gt;
&lt;br /&gt;
Not every NAM player necessarily supports every model architecture. Newer architectures such as A2 may require updated playback software or firmware.&lt;br /&gt;
&lt;br /&gt;
See [[NAM Playback]].&lt;br /&gt;
&lt;br /&gt;
== Cabinets and impulse responses ==&lt;br /&gt;
&lt;br /&gt;
A NAM model may or may not include a speaker cabinet and microphone.&lt;br /&gt;
&lt;br /&gt;
A direct amplifier NAM can represent the amplifier without a physical cabinet response. In that case, playback normally requires:&lt;br /&gt;
&lt;br /&gt;
* A cabinet impulse response&lt;br /&gt;
* A cabinet model&lt;br /&gt;
* A physical guitar cabinet&lt;br /&gt;
&lt;br /&gt;
A NAM captured through a physical cabinet and microphone may already contain those characteristics.&lt;br /&gt;
&lt;br /&gt;
Adding another conventional cabinet IR to such a model may result in unintended double cabinet processing.&lt;br /&gt;
&lt;br /&gt;
See:&lt;br /&gt;
&lt;br /&gt;
* [[Capture Types]]&lt;br /&gt;
* [[Cabinets and IRs]]&lt;br /&gt;
&lt;br /&gt;
== Model sharing ==&lt;br /&gt;
&lt;br /&gt;
Because NAM models are files rather than objects locked to a particular capture device, they can be exchanged between users and compatible playback systems.&lt;br /&gt;
&lt;br /&gt;
This has resulted in large community collections of models representing amplifiers, pedals, and other equipment.&lt;br /&gt;
&lt;br /&gt;
The official NAM website currently directs users to &amp;#039;&amp;#039;&amp;#039;TONE3000&amp;#039;&amp;#039;&amp;#039; for community model sharing and discovery.&lt;br /&gt;
&lt;br /&gt;
When distributing a model, useful documentation includes:&lt;br /&gt;
&lt;br /&gt;
* Equipment modeled&lt;br /&gt;
* Equipment settings&lt;br /&gt;
* Whether a cabinet is included&lt;br /&gt;
* Capture signal chain&lt;br /&gt;
* Calibration information&lt;br /&gt;
* Model architecture&lt;br /&gt;
* Creator&lt;br /&gt;
* Relevant notes about the capture&lt;br /&gt;
&lt;br /&gt;
A large model library becomes considerably more useful when its contents are documented well.&lt;br /&gt;
&lt;br /&gt;
== NAM as an ecosystem ==&lt;br /&gt;
&lt;br /&gt;
NAM is unusual among capture technologies because no single manufacturer controls every stage of the process.&lt;br /&gt;
&lt;br /&gt;
The ecosystem can include separate developers and services for:&lt;br /&gt;
&lt;br /&gt;
* Capture&lt;br /&gt;
* Training&lt;br /&gt;
* Model hosting&lt;br /&gt;
* Playback software&lt;br /&gt;
* Playback hardware&lt;br /&gt;
* Model management&lt;br /&gt;
* Research&lt;br /&gt;
&lt;br /&gt;
A model created using one NAM-compatible workflow can potentially be used by many different NAM-compatible playback systems.&lt;br /&gt;
&lt;br /&gt;
This interoperability is one of the most significant characteristics of the platform.&lt;br /&gt;
&lt;br /&gt;
== Limitations ==&lt;br /&gt;
&lt;br /&gt;
A successful NAM training run does not guarantee a perceptually perfect model.&lt;br /&gt;
&lt;br /&gt;
Accuracy can be affected by:&lt;br /&gt;
&lt;br /&gt;
* Training data&lt;br /&gt;
* Calibration&lt;br /&gt;
* Noise&lt;br /&gt;
* Clipping&lt;br /&gt;
* Latency alignment&lt;br /&gt;
* Model architecture&lt;br /&gt;
* Equipment behavior&lt;br /&gt;
* Capture signal chain&lt;br /&gt;
* Training configuration&lt;br /&gt;
&lt;br /&gt;
Some equipment may also exhibit behavior that is more difficult to reproduce than others.&lt;br /&gt;
&lt;br /&gt;
The resulting model should therefore be evaluated against the original equipment rather than judged solely by whether training completed successfully.&lt;br /&gt;
&lt;br /&gt;
See [[Troubleshooting Captures]].&lt;br /&gt;
&lt;br /&gt;
== Official resources ==&lt;br /&gt;
&lt;br /&gt;
* [https://www.neuralampmodeler.com/ Neural Amp Modeler official website]&lt;br /&gt;
* [https://neural-amp-modeler.readthedocs.io/ NAM documentation]&lt;br /&gt;
* [https://www.neuralampmodeler.com/the-code NAM open-source code]&lt;br /&gt;
* [https://www.neuralampmodeler.com/users NAM user resources]&lt;br /&gt;
&lt;br /&gt;
== See also ==&lt;br /&gt;
&lt;br /&gt;
* [[NAM Model File Format]]&lt;br /&gt;
* [[Training a NAM Model]]&lt;br /&gt;
* [[NAM A2 Architecture]]&lt;br /&gt;
* [[NAM Playback]]&lt;br /&gt;
* [[Getting Started with Capture Technology]]&lt;br /&gt;
* [[Capture Signal Chain]]&lt;br /&gt;
* [[Gain Staging and Calibration]]&lt;br /&gt;
* [[Capture Types]]&lt;br /&gt;
* [[Cabinets and IRs]]&lt;br /&gt;
* [[Troubleshooting Captures]]&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;[https://namforum.com/ Discuss Neural Amp Modeler on NAMFORUM]&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
&lt;br /&gt;
[[Category:Neural Amp Modeler]]&lt;br /&gt;
[[Category:Capture technology]]&lt;br /&gt;
[[Category:Machine learning]]&lt;/div&gt;</summary>
		<author><name>NAMFORUM Sysop</name></author>
	</entry>
</feed>