ControlHub Capture Guide

Step-by-step instructions for capturing your gear accurately inside ControlHub.

ControlHub Tracer

Overview

The ControlHub Tracer is a powerful tool that allows you to capture and replicate the sonic characteristics of your hardware or software signal chains with exceptional accuracy. You can trace preamps, equalizers, compressors, limiters, and more, either individually or as complex mixing chains, to create custom presets for your account.

What Can You Trace?

The ControlHub Tracer supports three different tracing modes:

Complete Signal Chain

Capture entire processing chains from input to output

Compressor

Trace dynamic processors with optimized settings

Individual Model

Capture preamps, EQs, and other individual processors

Getting Started: Essential Setup

Before you begin any tracing session, you'll need to prepare your workspace properly.

Locating the TracerTone Audio File

The TracerTone is a specially designed audio file that serves as the test signal for the tracing process.

To locate the file:

  • Click the Locate button within ControlHub Tracer
  • Alternatively, navigate manually: Finder > Documents > STL > ControlHub > Tones

Critical Session Settings

Your DAW session settings MUST match the TracerTone audio file specifications:

Sample Rate
Ensure your session sample rate matches the TracerTone file
Bit Depth
Verify bit depth consistency between session and TracerTone file

Most DAWs will automatically convert the TracerTone upon import, but mismatched settings will prevent the tracing technology from functioning correctly.

Warning: Disable time stretching/warping when importing the TracerTone file to avoid processing artifacts.

Tracing Method 1: Complete Signal Chain

Use this method when you want to capture an entire processing chain, from a single piece of gear to complex multi-stage setups.

Step-by-Step Process

  1. Import the TracerTone

    • Import the TracerTone audio file into your DAW
    • Verify sample rate and bit depth match your session
    • Ensure no time stretching is applied

  2. Route Through Your Signal Chain

    Set up your routing to send the TracerTone through your desired hardware or software processors.

    Gain Staging:

    • Target Level: Aim for approximately -3 dBFS at the loudest peaks
    • Never exceed 0 dBFS - Digital clipping will compromise the trace
    • Extreme or deliberate clipping/distortion may produce unwanted or unpredictable results

    Parallel Processing:

    • If your gear includes parallel processing (wet/dry blend), set it to 100% wet
    • The trace must capture the fully processed signal only

    Dynamic Processing:

    • For compressors/limiters in the chain: Use moderate settings
    • Target -3dB to -12dB of gain reduction on the loudest parts of the TracerTone

  3. Record the Processed Audio

    • Play the TracerTone through your signal chain
    • Record the output back into your DAW
    • Export the processed audio file

  4. Import to ControlHub Tracer

    • Click the Import button in ControlHub Tracer
    • Select your processed audio file

    If clipping is detected, ControlHub will issue a warning. We strongly recommend addressing the clipping rather than bypassing the warning. Clipped audio will result in inaccurate traces.

  5. Configure Trace Settings

    Trace Stereo
    Select if your signal chain has subtle differences between left and right channels (e.g., stereo EQs, stereo compressors with linked controls, width processors)
    Trace Mono
    Select for mono sources or chains where L/R are identical. Note: Mono presets can be used in stereo processing and vice versa

    CPU/GPU Selection:

    • Default: GPU - Recommended if you have a dedicated graphics card
    • CPU - May provide faster training times if your GPU is low-spec or integrated
    • Quality is identical regardless of CPU or GPU selection—this only affects processing speed

  6. Save and Document Your Trace

    • Click Save when training is complete
    • Fill in the metadata fields:
    Preset Name
    Give your trace a descriptive name
    Category/Type
    Identify what was traced
    Notes
    Document key characteristics, use cases, or recommendations

Tracing Method 2: Compressor

When tracing compressors specifically, follow the Complete Signal Chain workflow with these optimized settings.

Optimal Compressor Settings for Tracing

Configure your compressor with the following parameters before running the TracerTone:

Attack Time
20ms
Release Time
100ms
Ratio
4:1
Gain Reduction
-3dB to -12dB on the loudest parts of the TracerTone

Features to Disable

  • Lookahead - Disable if available
  • Mid/Side Processing - Process in stereo or mono only
  • Parallel Blend - Set to 100% wet (fully processed signal)
  • Sidechain Filters - Disable internal sidechain EQ if possible
  • Distortion Circuits - Disable optional harmonic enhancement features

Why These Settings?

These standardized settings allow the Tracer to capture the fundamental compression characteristics of your gear. The 20ms/100ms/4:1 configuration is a neutral starting point that reveals the compressor's inherent sonic signature.

Saving Compressor Traces

When prompted for metadata, provide:

Preset Name
e.g., "The Glue," "Vintage Vari-Mu"
Compression Type
e.g., "VCA Bus Comp," "Optical Compressor," "FET Limiter"
Notes
Usage tips, e.g., "Great for drum bus!" or "Smooth on vocals"

Tracing Method 3: Individual Model

Individual Models allow you to trace preamps, EQs, and other non-dynamic processors to capture their tonal characteristics, harmonic content, and saturation.

Setup and Settings

Follow the same fundamental steps as the Complete Signal Chain method, with special attention to:

If Tracing a Preamp or Channel Strip with Compression:

Use the same compressor settings as outlined in the Compressor section:

Attack
20ms
Release
100ms
Ratio
4:1
Gain Reduction
-3dB to -12dB on peaks

Features to Disable

  • Lookahead (compressors/limiters)
  • Mid/Side processing
  • Wet/dry blends - must be 100% processed
  • Sidechain filters
  • Distortion circuits (unless you specifically want to capture them)

Saving Individual Model Traces

Metadata for Individual Models includes:

Preset Name
e.g., "Brit 73," "Warm Tube Pre"
Color
e.g., "Vintage British Preamp," "Clean Solid State," "Colorful Tube"
Notes
e.g., "Pairs great with artist presets!" or "Adds subtle warmth"

The Drive Control

Individual Models feature a unique Drive knob that controls the amount of traced harmonic distortion and saturation.

Benefits:

  • Adjustable after tracing - no need to re-trace for different saturation amounts
  • Compatible with existing artist presets
  • Can be combined with other tracer presets (Complete Signal Chain and Compressor types)

Note: Tape and Tube controls found in other ControlHub modules are not available in Individual Models.

Pro Tips for Successful Tracing

Gain Staging is Critical

Always aim for -3 dBFS on peaks. This provides optimal signal-to-noise ratio without risking clipping.

Document Everything

Take detailed notes about your settings, gear used, and intended use cases. This makes your presets more valuable to other artists.

Start Simple

Begin with single processors before attempting complex chains. This helps you understand the tracing process and troubleshoot issues.

Use Consistent Settings

The recommended compressor settings (20ms/100ms/4:1) create a baseline that reveals the true character of your gear.

Test Your Traces

After creating a trace, test it on various sources to ensure it behaves as expected across different material.

Avoid Bypass Warnings

If ControlHub detects clipping, re-record your processed audio at a lower level rather than bypassing the warning.

Troubleshooting Common Issues

Clipping Detected

Problem: ControlHub warns about clipping in your processed audio.

Solution: Re-record the TracerTone through your signal chain at a lower output level. Aim for -3 dBFS at the peaks.

Sample Rate Mismatch

Problem: Trace sounds incorrect or artifacts are present.

Solution: Verify that your DAW session sample rate matches the TracerTone file. Check for accidental time stretching on import.

Trace Doesn't Sound Like Original

Problem: The traced preset doesn't accurately capture your gear's character.

Solution: Check that parallel processing was set to 100% wet, no sidechain filters were active, and gain reduction was moderate (-3dB to -12dB).

Slow Training Times

Problem: Trace is taking too long to process.

Solution: Try switching between CPU and GPU processing to see which performs better with your system specifications.

Best Practices for Presets

Naming Conventions

Use clear, descriptive names that help users understand what they're getting:

  • Include the gear type: "Neve 1073 Pre," "LA-2A Comp," "Pultec EQ"
  • Add context when useful: "Warm Vocal Chain," "Punchy Drum Bus"
  • Be specific about variants: "Clean," "Driven," "Vintage," "Modern"

Writing Effective Notes

Your notes help other users get the most from your presets:

  • Describe the sonic character: "Adds silky top end and warm midrange"
  • Suggest use cases: "Perfect for lead vocals and acoustic guitars"
  • Include any important details: "Based on hardware unit with NOS tubes"
  • Mention what works well with it: "Pairs beautifully with the Vintage Reverb"

Creating Preset Collections

Consider building themed collections:

  • Vintage studio chains from classic albums
  • Modern mastering processors
  • Specific producer/engineer signature sounds
  • Genre-specific processing chains

No results found

Try searching with different keywords

© 2025 STL Tones. ControlHub Tracer Capture Guide.