Line 6 Proxy

From NAMFORUM Wiki
Revision as of 02:06, 1 September 2026 by NAMFORUM Sysop (talk | contribs) (Created page)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

Line 6 Proxy

Proxy is Line 6's capture and cloning technology for the Helix Stadium platform.

Proxy allows users to measure physical amplifiers, preamps, speaker/cabinet setups, and gain-based pedals and create digital models called Clones.

Proxy was introduced with Helix Stadium firmware 1.3 in March 2026.

Line 6 describes the initial implementation as Phase 1 of the Proxy cloning engine.

Overview

Proxy combines the audio hardware and routing capabilities of Helix Stadium with cloud-based model creation.

A simplified workflow is:

Helix Stadium test signal → physical equipment → Helix Stadium return → Line 6 cloud processing → Proxy Clone

The Stadium hardware sends test signals through the equipment and records the resulting response.

The collected training data is then uploaded to Line 6 servers, where the computationally intensive model creation takes place.

The finished Clone is returned to the Stadium and can be saved in its Clone Library.

Supported Clone types

The current Proxy implementation supports four primary Clone types:

  • Amp+Cab
  • Amp
  • Preamp
  • Distortion

Each represents a different portion of the physical signal chain.

Amp+Cab Clone

An Amp+Cab Clone captures an amplifier together with a physical speaker cabinet and microphone.

A typical signal path is:

Stadium → amplifier → speaker cabinet → microphone → Stadium

Line 6 states that all elements in this path become part of the Clone, including:

  • Amplifier preamp
  • Power amplifier
  • Amplifier settings
  • Cabinet
  • Speaker
  • Microphone
  • Microphone position
  • Microphone distance

This type of Clone therefore represents a complete miked amplifier signal chain.

An additional conventional cabinet IR is normally unnecessary during playback unless deliberately used as an additional creative effect.

See Cabinets and IRs.

Amp Clone

An Amp Clone captures an amplifier without the physical speaker cabinet.

This requires a suitable load box with a direct output.

A simplified path is:

Stadium → amplifier → load box/direct output → Stadium

The resulting Clone can then be combined with:

  • A Helix Stadium Cab block
  • A cabinet IR
  • Another compatible cabinet solution
  • A physical guitar cabinet with appropriate power amplification

This provides more flexibility than an Amp+Cab Clone because the cabinet portion of the signal chain remains separate.

Amplifier safety

Never connect an amplifier's speaker output directly to an ordinary Helix Stadium return input.

An amplifier designed to operate into a speaker load must remain connected to an appropriate load.

For direct Amp cloning, use a load box or other equipment specifically designed to accept the amplifier's speaker-level output and provide an appropriate direct signal.

Incorrect connection can damage the amplifier, Stadium, or both.

Preamp Clone

A Preamp Clone represents a standalone preamp or the preamp section of an amplifier.

For a standalone preamp:

Stadium → preamp input → preamp output → Stadium

For an amplifier preamp:

Stadium → amplifier input → PREAMP OUT or FX SEND → Stadium

The amplifier must provide an appropriate preamp-level output such as:

  • PREAMP OUT
  • FX SEND

This allows the preamp stage to be measured independently from the power amplifier and cabinet.

Distortion Clone

A Distortion Clone captures a gain-based pedal.

Supported targets include devices such as:

  • Distortion
  • Overdrive
  • Boost
  • Fuzz

A typical path is:

Stadium → pedal → Stadium

The resulting Clone can then be inserted into a Stadium preset as a Distortion-type Clone block.

Despite the category name "Distortion," the target does not have to be strictly a conventional distortion pedal.

Line 6 explicitly includes overdrive, boost, and fuzz devices within this category.

Combined gain chains

Proxy can also capture more than one gain-producing device as part of an Amp+Cab signal chain.

For example:

Stadium → drive pedal → amplifier → cabinet → microphone → Stadium

Line 6 states that one or more drive pedals may be placed before the amplifier when creating an Amp+Cab Clone.

This makes it possible to clone an entire gain-based signal flow rather than only an isolated amplifier.

The resulting Clone represents the combined behavior of those devices.

The individual pedal and amplifier cannot then be independently separated from that Clone.

See Capture Types.

Devices that should not be included

Line 6 recommends avoiding compression, modulation, and time-based effects in the signal path during Proxy cloning.

Examples include:

  • Compressor
  • Chorus
  • Flanger
  • Delay
  • Reverb
  • Tremolo
  • Other time-varying effects

Amplifier reverb, tremolo, and similar onboard effects should normally be disabled.

The goal is to capture the core nonlinear tone of the target equipment rather than effects whose behavior may not be represented appropriately by the Proxy cloning process.

Cloud-based training

Proxy model creation is performed using Line 6 online servers.

The physical measurement occurs through Helix Stadium, but the collected data is uploaded for processing.

This means creating a Proxy Clone requires:

  • Helix Stadium
  • Internet connection
  • Connection to Wi-Fi or Ethernet
  • Line6.com account
  • Sign-in to that account

The cloud servers perform the computationally intensive model creation.

The completed Clone is then returned to the Stadium.

Why cloud processing is used

Line 6 states that cloud processing allows Proxy to use substantially greater computing resources than would normally be available inside the floor processor.

This can allow more detailed training without requiring the Stadium hardware itself to perform the complete machine-learning process.

It also separates the model-training technology from the firmware running on the floor unit.

Line 6 states that this architecture allows the underlying Proxy technology to be improved on the server side without every improvement necessarily requiring a corresponding firmware update.

Creating a Clone

The current Stadium workflow begins from:

Main Menu → New Clone

The user then selects the target type:

  • Amp+Cab
  • Amp
  • Preamp
  • Distortion

Stadium provides on-screen connection and setup instructions appropriate for the selected target.

The exact SEND and RETURN connections differ between Helix Stadium and Helix Stadium XL, so the on-screen instructions and current manual should be followed rather than assuming one universal jack configuration.

Level setup

The Proxy workflow guides the user through level configuration before cloning begins.

Correct levels are important for two reasons:

  • Avoiding unwanted clipping or noise
  • Presenting the target device with an appropriate signal level

For nonlinear equipment, the level entering the device affects its behavior.

A distorted amplifier or pedal may therefore respond differently if the Proxy test signal drives it substantially harder or softer than intended.

See Gain Staging and Calibration.

Noise and grounding

Line 6 recommends making the cloning signal path as noise-free as practical.

Potential problems include:

  • Ground loops
  • Computer connections
  • USB connections
  • MIDI connections
  • Power supplies
  • Unbalanced audio connections

Line 6 specifically recommends disconnecting unnecessary MIDI and USB-C cables during the cloning process to reduce possible interference.

Appropriate audio isolation or ground-lift facilities on external equipment may also help resolve ground-loop noise.

Never defeat protective mains safety grounding to eliminate hum.

Collecting Device DNA

During cloning, Stadium sends test signals through the target equipment.

Line 6 describes this stage as:

Collecting Device DNA

The user should leave the target equipment controls unchanged while the measurement process is running.

Changing:

  • Gain
  • EQ
  • Channel
  • Pedal controls
  • Amplifier controls

during measurement can invalidate the relationship Proxy is attempting to learn.

Cloud processing

After the physical measurement is completed, the captured data is uploaded to Line 6 servers.

The server analyzes the measurement and creates the Proxy Clone.

This separation means the Stadium itself does not have to perform the entire training process locally.

Once processing completes, the resulting Clone is returned for comparison.

Comparing the Clone

Proxy provides a comparison stage after model creation.

The user can compare:

  • The original physical equipment
  • The resulting Clone

For appropriate Clone types, Stadium can also provide Amp or Cab blocks during the comparison process so the Clone can be heard in a useful playback context.

These comparison blocks are for auditioning and are not automatically stored as part of the Clone file.

Listen for differences in:

  • Gain
  • Frequency response
  • Pick attack
  • Dynamics
  • Compression
  • Low-frequency response
  • High-frequency response
  • Sustain
  • Cleanup

Level matching is important when comparing the Clone and original equipment.

Saving a Clone

If the result is satisfactory, the Clone can be saved to the Stadium Clone Library.

The creator enters a Clone name and can provide metadata including:

  • Brand
  • Product
  • Notes

Notes can document information such as:

  • Amplifier channel
  • Gain
  • EQ settings
  • Pedal settings
  • Intended use
  • Other capture information

This metadata is also used by Stadium's search system.

Good metadata becomes increasingly important as the user's Clone library grows.

Clone Library

Helix Stadium can store up to 2,048 Clones internally.

Clones can be:

  • Created
  • Imported
  • Exported
  • Browsed
  • Searched
  • Added to presets

Clone files are managed similarly to other user content within the Stadium ecosystem.

Clone blocks

Clones appear in the appropriate Stadium model categories.

An:

Amp Clone

appears in the Amp category.

An:

Amp+Cab Clone

also appears in the Amp category.

A:

Preamp Clone

appears in the Preamp category.

A:

Distortion Clone

appears in the Distortion category.

This allows Clones to be used alongside Line 6's conventional modeled blocks.

Clone controls

Clone blocks provide controls similar to other Stadium Amp and Effect models.

Available controls include Gain and EQ parameters.

Clone parameters can also participate in Stadium features such as:

  • Snapshots
  • Stomp control
  • External pedals
  • External switches
  • Triggers
  • MIDI control
  • User Defaults
  • Favorites

The existence of these controls should not automatically be interpreted as meaning that Proxy recreated every physical control circuit of the original device.

The Clone fundamentally represents the measured device configuration.

DSP usage

Proxy Clones require significant DSP resources.

Line 6 states that a Clone block can require approximately the same DSP resources as an Agoura Amp model.

A Stadium preset can contain up to:

four Clone blocks

with a maximum of:

two Clones per main path

subject to the overall DSP requirements of the preset.

Mono processing

All Proxy Clone blocks are currently mono.

If a stereo block is placed before a Clone, the signal entering the Clone is summed to mono.

This is important when designing Stadium presets containing stereo effects.

Stereo processing intended to remain stereo should generally be placed after the Clone unless there is a specific reason to sum it beforehand.

Cabinets with Amp Clones

An Amp Clone does not include a speaker cabinet.

When used through a full-range system, a Cab block or IR will normally be placed after it:

Amp Clone → Cab/IR → output

Line 6's Model List workflow specifically notes that an Amp Clone will typically be followed manually by a Cab block.

An Amp+Cab Clone already contains the measured physical cabinet and microphone.

See Cabinets and IRs.

Physical guitar cabinet playback

A direct Amp Clone can also be used with an appropriate physical guitar cabinet.

A possible signal chain is:

Instrument → Amp Clone → suitable power amplifier → physical guitar cabinet

In this situation, additional virtual cabinet processing is normally unnecessary because the physical guitar cabinet supplies the speaker and cabinet response.

CustomTone

Proxy Clones can be shared through Line 6's CustomTone community.

Users can upload and download:

  • Helix Stadium presets
  • Proxy Clones

This allows Clones created by one Stadium owner to be used by other compatible systems.

As with other community capture libraries, useful metadata makes shared models much easier to evaluate and organize.

Import and export

The Helix Stadium application provides librarian functions for managing Clones.

Users can:

  • Import Clone files
  • Export Clone files
  • Browse the Clone Library
  • Organize content

This allows Clone collections to be backed up and transferred independently of individual presets.

Helix Stadium Native

Helix Stadium Native supports Proxy Clone loading.

This allows Proxy Clones to be used in a DAW environment as well as on Stadium hardware.

The plugin includes the Stadium amp, cabinet, and effects environment together with:

  • Cabinet IR support
  • Proxy Clone loading
  • Preset compatibility with Stadium hardware

This extends Proxy playback beyond the physical floor processor.

Creating versus playing Clones

There is an important distinction between creating and playing Proxy Clones.

Creating a Clone currently requires compatible Helix Stadium hardware because the Stadium performs the physical measurement and interfaces with the cloud cloning system.

Once created, Clones can also be loaded by compatible Line 6 software such as Helix Stadium Native.

A system capable of playing a Clone should therefore not automatically be assumed capable of creating one.

Proxy and Agoura

Proxy should not be confused with Line 6's Agoura amplifier modeling.

Agoura is Line 6's conventional amplifier-modeling methodology used to create detailed predefined amplifier models for Helix Stadium.

Proxy is a user-driven capture technology.

The two can coexist in the same Stadium preset:

Agoura model = Line 6-developed amplifier model

Proxy Clone = measured model created from physical user equipment

This distinction is similar to the difference between algorithmic amplifier models and user-created captures on other platforms.

Proxy and legacy Helix modeling

Helix Stadium also retains compatibility with the established Helix/HX amplifier and effects ecosystem.

Proxy therefore does not replace conventional Line 6 modeling.

A Stadium preset can combine:

  • Legacy Helix/HX models
  • Agoura models
  • Proxy Clones
  • Cabinet models
  • IRs
  • Effects

This makes capture technology one component of a broader modeling and effects platform.

Proxy and NAM

Proxy and Neural Amp Modeler both use measured data to reproduce physical audio equipment, but they are separate technologies.

A Proxy Clone is not a .nam file.

The systems differ in:

  • Capture signal
  • Training process
  • Model architecture
  • Model format
  • Playback engine
  • Distribution
  • Hardware integration

NAM provides an open-source model and playback ecosystem.

Proxy is a proprietary Line 6 technology integrated with Helix Stadium and Line 6 cloud infrastructure.

Proxy and Neural Capture V2

Proxy and Neural Capture V2 share one broad architectural concept:

physical measurement on hardware + computationally intensive cloud training

The implementations remain independent.

Neural Capture V2 uses Cortex hardware, Cortex Control, and Cortex Cloud.

Proxy uses Helix Stadium hardware and Line 6 online servers.

Neither model format is interchangeable with the other.

Proxy and TONEX

Proxy and TONEX can both create models of amplifiers, pedals, and complete amplifier/cabinet rigs.

The model formats and playback systems are different.

TONEX Modeler can preserve physical capture data and perform training separately, while Proxy currently integrates the physical measurement and cloud-training workflow directly through Helix Stadium.

Phase 1

Line 6 describes the Proxy implementation introduced in Stadium 1.3 as Phase 1.

This wording is significant.

The initial release supports:

  • Amp+Cab
  • Amp
  • Preamp
  • Distortion

but should not necessarily be treated as the final scope or capability of Proxy.

Future firmware, cloud technology, target types, or workflow capabilities may expand the system.

Documentation should therefore distinguish between the current Proxy implementation and assumptions about future development.

Troubleshooting

If a Proxy Clone does not reproduce the expected sound, check:

  • Device connections
  • Clone type
  • Send and return levels
  • Load-box configuration
  • Microphone path
  • Grounding
  • Noise
  • Unwanted effects
  • Amplifier settings
  • Cabinet configuration
  • Comparison level

If cloning cannot begin or cloud processing fails, also check:

  • Internet connection
  • Wi-Fi or Ethernet
  • Line6.com account login
  • Stadium firmware
  • Line 6 service availability

If a Clone sounds correct during comparison but different in a preset, check:

  • Cab block
  • IR
  • Input level
  • Additional effects
  • EQ
  • Signal routing
  • Stereo-to-mono summing
  • Output configuration

See Troubleshooting Captures.

Official resources

See also

Discuss Proxy Clones, Helix Stadium, and cloning workflows on NAMFORUM

Retrieved from "https://namforum.com/wiki/index.php?title=Line_6_Proxy&oldid=19"