Troubleshooting Captures
Troubleshooting Captures
When a capture fails, sounds wrong, or behaves differently from the original equipment, the problem is not necessarily the capture technology itself.
A capture system is part of a larger measurement chain involving software, audio interfaces, routing, levels, reamping, the device under test, and the return path. A fault or configuration error at any point can affect the resulting model.
The most effective troubleshooting method is to work through the signal chain one stage at a time.
Start with the original equipment
Before investigating the capture system, verify that the equipment being captured sounds and behaves normally.
Check:
- Instrument and signal cables
- Power supplies
- Pedal power
- Amplifier operation
- Tubes where applicable
- Switches and channel settings
- Cabinet and speaker connections
- Load box or direct-output equipment
- Microphone and microphone preamp
- Noise, hum, or intermittent connections
If the original equipment is not behaving correctly, the capture cannot accurately represent it.
Verify the capture signal
Confirm that the correct test or training signal is being used.
Check:
- Correct file or signal
- Correct sample rate
- Correct channel
- Correct playback level
- Correct beginning and end
- No normalization
- No accidental editing
- No plugins or processing
- No fades unless specifically required
- No sample-rate conversion unless required by the workflow
Some capture systems depend on the exact relationship between the supplied test signal and the recorded response.
Do not substitute or modify a training signal unless the platform specifically permits it.
Verify output routing
Confirm that the test signal is leaving through the intended physical output.
DAW and interface routing can become complicated, particularly when software mixers are involved.
Check:
- DAW track output
- Bus or master routing
- Interface software mixer
- Physical interface output
- Hardware output level
- Reamp or capture-device input
If possible, verify the signal at more than one point in the chain.
Do not assume that meter activity inside the DAW proves the correct physical output is carrying the signal.
Verify the signal reaching the device
Confirm that the device under test is actually receiving the expected signal.
For an amplifier or pedal, listen to or otherwise monitor its response where safe and practical.
If the device receives no signal, investigate:
- Output selection
- Muting
- Interface mixer configuration
- Cable
- Reamp device
- Reamp output level
- Incorrect connector
- Pedal bypass state
- Amplifier input or channel
If the device receives a signal but reacts very differently from normal instrument use, investigate calibration and level.
See Gain Staging and Calibration.
Verify the return path
Next confirm that the output of the device reaches the intended recording input.
Check:
- Physical cable
- Load/direct-output device
- Microphone
- Microphone preamp
- Interface input
- Input type
- Input gain
- Interface software routing
- DAW input assignment
A common mistake is recording a different interface input from the one actually connected to the capture chain.
No returned signal
If the capture system receives no return signal, trace the path backward from the recording software.
For example:
Recording software ← interface input ← return cable ← device output
Determine the last point at which a valid signal exists.
Possible causes include:
- Wrong recording input
- Muted interface channel
- Incorrect cable
- Reamp or capture device connected backward
- Pedal or processor bypass/routing problem
- Amplifier standby
- Incorrect direct-output configuration
- Load-box routing
- Microphone/preamp problem
Avoid changing several things simultaneously. Find the failed stage.
Input signal too low
A return signal that is too low can result in poor signal-to-noise ratio or capture-system errors.
Possible causes include:
- Device output set too low
- Interface input gain too low
- Incorrect input type
- Excessive attenuation
- Incorrect load/direct-output setting
- Microphone preamp gain too low
- Wrong interface reference level
- Calibration error
Do not automatically solve every low-level problem by increasing the final interface gain. Determine where the unexpected level loss occurs.
Input signal too high
An excessively high return signal can cause clipping.
Possible clipping points include:
- Device output
- Load/direct-output equipment
- Microphone preamp
- Interface analog input
- A/D converter
- DAW or capture software
Remember:
A recorded signal below 0 dBFS does not prove that an earlier analog stage has not clipped.
Reduce the level at the stage that is actually overloading rather than compensating later in the chain.
Capture sounds more or less distorted than the original
If the resulting model has substantially different gain or distortion characteristics, investigate the level presented to the device during capture.
Possible causes include:
- Incorrect calibration
- Interface output level changed
- DAW fader changed
- Reamp output changed
- Interface operating level changed
- Different input used
- Software mixer attenuation
- Incorrect capture-platform calibration value
For nonlinear equipment, input level affects behavior.
The problem may therefore be a calibration error rather than a defect in the model itself.
See Gain Staging and Calibration.
Capture is much louder or quieter than the original
A level difference does not necessarily indicate poor modeling accuracy.
Investigate:
- Capture return gain
- Platform output calibration
- Normalization
- Playback level
- Model output control
- Interface configuration
When comparing a capture with the original equipment, level-match them carefully.
Small differences in loudness can strongly influence subjective judgments of tone and quality.
Capture sounds dark or muffled
Possible causes include:
- A cabinet response already exists in the capture and another cabinet IR has been added
- Unwanted cabinet simulation was active during capture
- Incorrect microphone position
- Incorrect direct-output configuration
- Sample-rate or processing problem
- EQ or filtering active in the capture chain
One of the first questions should be:
Does this capture already contain a cabinet?
See Cabinets and IRs and Capture Types.
Capture sounds excessively bright or harsh
Possible causes include:
- Direct amplifier capture being played without a cabinet or IR
- Cabinet simulation accidentally bypassed
- Incorrect IR
- Different monitoring system
- Calibration error
- Incorrect microphone position
- Unintended EQ
- Playback configuration
A direct guitar-amplifier capture without cabinet processing can sound extremely bright and unnatural when reproduced through a full-range system.
That does not necessarily mean the capture is defective.
Capture sounds thin or hollow
Possible causes include:
- Phase cancellation
- Multiple cabinet IRs
- Misaligned IRs
- Multiple microphones with timing differences
- Polarity inversion
- Parallel signal paths
- DAW monitoring combined with direct monitoring
If two versions of the same signal are being heard simultaneously with a small timing difference, comb filtering can produce a thin or hollow sound.
Check for unintended parallel paths.
Hum or buzz
Hum and buzz frequently originate from grounding rather than the capture software.
Possible causes include:
- Ground loops
- Unbalanced cable runs
- Computer and amplifier connected through different ground paths
- Power supplies
- Poor cables
- Nearby mains equipment
- Pedal power
- Lighting or other electrical equipment
Transformer isolation in an appropriate reamp device can sometimes eliminate an unwanted signal-ground path.
A ground-lift feature designed for the audio connection may also help.
Never defeat the protective mains safety earth of an amplifier or other equipment to eliminate hum.
Computer noise or high-frequency interference
Digital equipment can introduce characteristic noise into capture systems.
Possible sources include:
- USB connections
- Computer power supplies
- Displays
- Switching power supplies
- Network equipment
- Ground loops
- Poorly shielded cables
Try to determine whether the noise enters before or after the device under test.
Isolation and balanced connections can be useful diagnostic tools.
Excessive hiss
Some amplifiers and high-gain devices naturally produce substantial hiss.
Compare the capture path with the original equipment before deciding that the capture system introduced the noise.
Additional hiss may come from:
- Excessively low signal levels
- Excessive return gain
- Multiple high-gain stages
- Poor signal-to-noise ratio
- Pedal power supplies
- Microphone preamps
- Interface inputs
Noise gates can complicate capture measurements and should not be introduced casually merely to make the recorded response look cleaner.
Capture contains unexpected effects
If a model appears to contain EQ, cabinet coloration, compression, or other processing that was not intended, inspect every processing stage.
Check:
- DAW plugins
- Interface DSP
- Hardware processors
- Load-box cabinet simulation
- Amplifier direct-output simulation
- IR loaders
- Channel-strip processing
- Master-bus processing
Anything present in the measured path may influence the resulting model.
Training or capture process fails
If software refuses to complete the capture or training process, first check the platform's error message and documentation.
Common causes can include:
- Incorrect file length
- Incorrect sample rate
- Incorrect number of channels
- Missing or corrupted training signal
- Return level outside acceptable range
- Clipping
- Incorrect file format
- Incorrect trimming
- Insufficient computer resources
- Unsupported software or model version
Do not repeatedly modify the recorded response at random in an attempt to make the software accept it.
Determine what requirement is not being met.
Timing and file-length problems
Some training workflows require the recorded response to correspond precisely with the supplied training signal.
Problems can arise from:
- Recording started too late
- Recording stopped too early
- Extra material before the signal
- Missing material at the end
- Automatic latency compensation
- Manual trimming
- Fades
- Resampling
- DAW export settings
Follow the platform's specific requirements for timing and file length.
If manual editing is required, preserve the original recording before modifying it.
Model works in one player but not another
Possible causes include:
- Unsupported model architecture
- Older playback software
- File-format version differences
- Platform-specific metadata
- Corrupted download
- Incorrect file extension
- Unsupported sample-rate or processing configuration
Check the model's architecture and format against the capabilities of the playback software or hardware.
This can be particularly important as capture platforms introduce new model architectures.
Model sounds different on another device
A model may sound different when moved between playback systems even when the model itself is identical.
Investigate:
- Input calibration
- Output level
- Cabinet/IR configuration
- Sample rate
- Playback software
- Model architecture implementation
- Additional EQ or processing
- Physical playback system
- Guitar cabinet versus full-range playback
- Input impedance
- Instrument level
Do not assume that loading the same model file guarantees an identical complete signal chain.
Capture differs from the original only slightly
Perfect null-level equivalence should not automatically be expected from every capture technology.
A model is an approximation of the measured system.
When evaluating smaller differences, use controlled comparisons:
- Use the same source performance.
- Level-match the original and model.
- Use the same cabinet processing where applicable.
- Switch between them quickly.
- Avoid changing unrelated equipment.
- Repeat the test with different material.
Determine whether the difference is consistent, audible in practical use, and attributable to the model rather than the comparison setup.
Change one variable at a time
This is one of the most useful troubleshooting principles.
If a capture sounds wrong and you simultaneously change:
- Reamp level
- Interface gain
- Amplifier settings
- Training settings
- Cabinet IR
you may obtain a better result without learning what caused the original problem.
Instead:
- Establish a repeatable baseline.
- Change one variable.
- Make another capture or measurement.
- Compare the result.
- Document what changed.
Capture technology is particularly well suited to controlled experimentation because the same test signal can be repeated precisely.
Preserve evidence
Before deleting an unsuccessful capture, consider preserving:
- Original training response
- Model file
- Screenshots
- Calibration values
- Signal-chain notes
- Equipment settings
- Error messages
- Software versions
Today's unexplained failure can become useful evidence when a pattern emerges later.
Asking for help
When asking other users to troubleshoot a capture, provide enough information to reproduce or understand the problem.
Useful information includes:
- Capture platform
- Software/version
- Equipment being captured
- Complete signal chain
- Audio interface
- Reamp/capture device
- Calibration method
- Input and output settings
- Capture type
- Whether a cabinet is included
- Training settings where applicable
- Playback system
- Description of the problem
Audio examples, screenshots, measurements, and links to the model may also be useful.
A detailed report is much easier to troubleshoot than simply saying:
"My capture doesn't sound right."
Troubleshooting checklist
When something goes wrong, work through this sequence:
- Verify the original equipment.
- Verify the correct test signal.
- Verify output routing.
- Verify the signal reaching the device.
- Verify the device settings.
- Verify the return path.
- Check every stage for clipping.
- Check signal-to-noise ratio.
- Verify calibration.
- Remove unintended processing.
- Verify cabinet/IR configuration.
- Verify recording format and timing.
- Verify training or capture settings.
- Compare the model with the original under controlled conditions.
- Change only one variable at a time.
The objective is to identify where the first unexpected difference occurs.
Once that point is known, the number of possible causes usually becomes much smaller.