Parametric (AmpNet) vs Static NAM — Key Differences and When to Use Each
Two notes Capture Studio supports two distinct capture types: Static NAM and Parametric (AmpNet). While both aim to reproduce the sound of a physical amplifier, they differ fundamentally in how the model behaves and how it should be used.
Static NAM Captures
Static NAM captures represent a single, fixed state of an amplifier. During capture, the amplifier is measured at one specific set of control positions. The resulting model reproduces that exact tone with high accuracy but does not account for how the amplifier responds when controls are adjusted.
Key Characteristics
- Captures a single dialled-in sound
- High accuracy at that specific setting
- Broad compatibility with NAM-supported software and hardware
- No true control interaction beyond basic gain staging or input scaling
Best Used For
- Capturing a finished, mix-ready tone
- Sharing specific amp settings
- Building a library of fixed sounds
- Fast, simple capture workflows
Parametric (AmpNet) Captures
Parametric captures generated in the AmpNet format model how an amplifier behaves across its control range. Instead of capturing a single setting, Capture Studio records the response of each knob across multiple positions. The resulting model allows real-time adjustment of controls while preserving the amplifier’s behaviour.
Key Characteristics
- Captures control interaction and response
- Knobs remain fully adjustable after capture
- Models the behaviour of the amplifier, not just a snapshot
- Requires more captures and longer processing time
Best Used For
- Recreating the full behaviour of an amplifier channel
- Exploring different tones from a single capture
- Detailed sound design and tonal refinement
- Situations where control flexibility is required after capture
Which Should You Choose?
Use Static NAM when you want to capture a specific sound quickly and use it across multiple platforms. Use Parametric (AmpNet) when you want a fully interactive model that allows you to adjust controls after capture and explore the full tonal range of the amplifier.
Having issues?
Our support team is here to assist you! For any enquiries, please head over to our Help Desk and submit a ticket to speak directly to one of our in-house specialists.
Related Articles
Capture Studio | Reducing Training Time — CPU vs GPU Performance Guide
Training time in Two notes Capture Studio depends primarily on the hardware used to process the model. Understanding how CPU and GPU performance affects training will help you optimise your system and reduce overall processing time. CPU vs GPU — ...
Capture Studio | Identifying and Resolving Noise and Signal Issues With Amp Captures
Noise and signal integrity issues are among the most common causes of inaccurate captures. Any unwanted signal present during capture will be embedded in the model and cannot be removed during training. Ensuring a clean, stable signal path is ...
Capture Studio | Why Your Capture Sounds Incorrect — Common Causes and Fixes
Within Capture Studio, if a capture does not sound like the original amplifier, the issue is almost always related to setup, capture conditions, or configuration rather than the modelling process itself. This article outlines the most common causes ...
Capture Studio | Understanding Reamp Boxes, Loadboxes, and DI Units
To perform an accurate and safe capture in Two notes Capture Studio, it is essential to understand the role of key hardware components in your signal chain. This article explains what each device does and why it is required. Reamp Box A reamp box is ...
Common Amplifier Capture Mistakes and How to Avoid Them
Accurate amplifier capture depends on controlled conditions, correct configuration, and attention to detail. Many issues arise from a small number of common mistakes. This guide highlights these pitfalls and how to avoid them. Incorrect Gain Staging ...