Manual: Absolute calibration of the re-amping chain and ducking
The principle of infallibility
The measurement is performed exclusively with the anchor (snare impulse at 300% grid). The guitar remains silent during calibration. Cubase channels remain open for data flow (no mute), while external monitoring is switched off. We calculate two completely independent values on different tracks to zero the time offset between the plugin input and the hardware output (Captor X).
1. Determining the input value (digital latency)
On this track, we measure how much the plugin chain (Pro-Q 4, C6, Low Cut, Cubase Comp) delays the signal before it even thinks about the outside world or the sidechain path.
• Process: You compare the dry anchor A (on the grid) with anchor B, which has loaded the entire plugin chain.
• Measurement: MAutoAlign is placed as the last instance on anchor B.
• Result: You get the input value (E) as a positive value in milliseconds (e.g., +18.4 ms). This value represents the internal processing time.
2. Determining the output value (the real hardware delay)
We now measure the path through the hardware on a separate track. Since the Captor X and the converters take time, we must record this signal in order to have a real database.
• Process: Send the processed Anchor B through the interface, the amp, and the Captor X. Record the result on a new track: Anchor Return track.
• Measurement: Compare the recorded Anchor Return track with the original Anchor A (Grid). MAutoAlign is again the last instance on the Return track.
• Result: You get the output value (A) as a positive total value (e.g., +30.2 ms). This value is the sum of plugins and hardware.
3. The mathematical calculation for track delay
Since everything runs on different tracks, we have to calculate the difference to isolate the pure hardware delay (H). This value is used to "pull forward" the re-amping track in Cubase.
The formula is:
A - E = H
(Output value minus input value equals hardware delay)
Sample calculation:
30.4 - 18.4 = 11.8 ms
Entry: To eliminate the inadequacy of the Captor X, enter this value as a negative value (-11.8 ms) in the track delay (Inspector) of the re-amping return track.
4. Calibration of ducking in the sidechain path
The goal of this separate calculation is to perfect the ducking. Since the Cubase compressor works on the track during re-amping, we need to ensure that the trigger (ghost track) and the guitar signal arrive at the same time.
• The logic: By entering a negative value (-11.8 ms), you have physically deleted the hardware latency on the return track. The signal now "exists" again for Cubase at exactly the timestamp defined by the input value (E).
• The ghost track: Since you create the ghost track afterwards to match the drums exactly, it sends its sidechain impulse directly to the compressor.
• The result: Since the hardware latency is zero, the ghost trigger and the guitar signal (despite the detour through the real amp and Captor X) meet at exactly the same time in the compressor's sidechain path. The ducking is sample-accurate and free of any offset.
Checklist for accuracy:
• Measurement 1 (input) and measurement 2 (output) must be documented on different tracks.
• MAutoAlign must be the last instance so that all plugins (C6, Pro-Q 4) are included in the calculation.
• The negative correction value may only be the difference (H), never the total value (A), otherwise the plugin timing will be destroyed.
To control the thermal drift of the amp, you have to remeasure after each take. And enter the offset value from the output. See step 2!
Important: After each measurement, m Auto Align must be removed as a plugin. M Auto Align is only the measuring tool. Anchor and slave principle.
Each output must be measured separately!!!!
Rinaldo Funk the architect of this new System. Check it
Audio- and Mixingengineer
Rinaldo Funk
Dynamic Latency and Tube Drift Compensation / Aproved by Physics
Audio Plugin Hosts and other audio software applications discussion
Moderator: KVR Moderators (Main)
Dynamic Latency and Tube Drift Compensation / Aproved by Physics
2026-02-23T18:08:00+00:00
Manual: Absolute calibration of the re-amping chain and ducking
The principle of infallibility
The measurement is performed exclusively with the anchor (snare impulse at 300% grid). The guitar remains silent during calibration. Cubase channels remain open for data flow (no mute), while external monitoring is switched off. We calculate two completely independent values on different tracks to zero the time offset between the plugin input and the hardware output (Captor X).
1. Determining the input value (digital latency)
On this track, we measure how much the plugin chain (Pro-Q 4, C6, Low Cut, Cubase Comp) delays the signal before it even thinks about the outside world or the sidechain path.
• Process: You compare the dry anchor A (on the grid) with anchor B, which has loaded the entire plugin chain.
• Measurement: MAutoAlign is placed as the last instance on anchor B.
• Result: You get the input value (E) as a positive value in milliseconds (e.g., +18.4 ms). This value represents the internal processing time.
2. Determining the output value (the real hardware delay)
We now measure the path through the hardware on a separate track. Since the Captor X and the converters take time, we must record this signal in order to have a real database.
• Process: Send the processed Anchor B through the interface, the amp, and the Captor X. Record the result on a new track: Anchor Return track.
• Measurement: Compare the recorded Anchor Return track with the original Anchor A (Grid). MAutoAlign is again the last instance on the Return track.
• Result: You get the output value (A) as a positive total value (e.g., +30.2 ms). This value is the sum of plugins and hardware.
3. The mathematical calculation for track delay
Since everything runs on different tracks, we have to calculate the difference to isolate the pure hardware delay (H). This value is used to "pull forward" the re-amping track in Cubase.
The formula is:
A - E = H
(Output value minus input value equals hardware delay)
Sample calculation:
30.4 - 18.4 = 11.8 ms
Entry: To eliminate the inadequacy of the Captor X, enter this value as a negative value (-11.8 ms) in the track delay (Inspector) of the re-amping return track.
4. Calibration of ducking in the sidechain path
The goal of this separate calculation is to perfect the ducking. Since the Cubase compressor works on the track during re-amping, we need to ensure that the trigger (ghost track) and the guitar signal arrive at the same time.
• The logic: By entering a negative value (-11.8 ms), you have physically deleted the hardware latency on the return track. The signal now "exists" again for Cubase at exactly the timestamp defined by the input value (E).
• The ghost track: Since you create the ghost track afterwards to match the drums exactly, it sends its sidechain impulse directly to the compressor.
• The result: Since the hardware latency is zero, the ghost trigger and the guitar signal (despite the detour through the real amp and Captor X) meet at exactly the same time in the compressor's sidechain path. The ducking is sample-accurate and free of any offset.
Checklist for accuracy:
• Measurement 1 (input) and measurement 2 (output) must be documented on different tracks.
• MAutoAlign must be the last instance so that all plugins (C6, Pro-Q 4) are included in the calculation.
• The negative correction value may only be the difference (H), never the total value (A), otherwise the plugin timing will be destroyed.
To control the thermal drift of the amp, you have to remeasure after each take. And enter the offset value from the output. See step 2!
Important: After each measurement, m Auto Align must be removed as a plugin. M Auto Align is only the measuring tool. Anchor and slave principle.
Each output must be measured separately!!!!
Rinaldo Funk the architect of this new System. Check it
Audio- and Mixingengineer
Rinaldo Funk
Rinaldo
https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=786983
Post Reply
1 post
• Page 1 of 1
Return to “Hosts & Applications (Sequencers, DAWs, Audio Editors, etc.)”
Jump to
- The Main Forums
- ↳ KVR Studio Manager
- ↳ Getting Started (AKA What is the best...?)
- ↳ Instruments
- ↳ Effects
- ↳ Hosts & Applications (Sequencers, DAWs, Audio Editors, etc.)
- ↳ Guitars
- ↳ Mobile Apps and Hardware
- ↳ Soundware
- ↳ Samplers, Sampling & Sample Libraries
- ↳ Hardware (Instruments and Effects)
- ↳ Modular Synthesis
- ↳ Sound Design
- ↳ Production Techniques
- ↳ Music Theory
- ↳ Computer Setup and System Configuration
- ↳ DSP and Plugin Development
- ↳ DIY: Build it and they will come
- ↳ Music Cafe
- ↳ Sell & Buy (+Special Offers, Deals & Promos)
- ↳ KVR Experts
- ↳ KVR Developer Challenge 2026
- ↳ Everything Else (Music related)
- ↳ Off Topic
- ↳ Off Topic Classics
- ↳ Machine Learning and AI for Music Creation
- Official Company Forums
- ↳ 2getheraudio
- ↳ accSone
- ↳ Acon Digital
- ↳ AcousticsampleS
- ↳ AcousModules
- ↳ Agitated State
- ↳ AIR Music Technology
- ↳ AMG
- ↳ Ample Sound
- ↳ Antares Audio Technologies
- ↳ Apisonic Labs
- ↳ APU Software
- ↳ apulSoft
- ↳ AriesCode
- ↳ Arts Acoustic
- ↳ Arturia
- ↳ Audjoo
- ↳ AudioSpillage
- ↳ Audiority
- ↳ Best Service
- ↳ Big Tick
- ↳ Bitwig
- ↳ Controller Scripting
- ↳ Blue Cat Audio
- ↳ Cherry Audio
- ↳ CWITEC
- ↳ Embertone
- ↳ energyXT
- ↳ Eventide
- ↳ Expert Sleepers
- ↳ forward audio
- ↳ Future Audio Workshop
- ↳ FXpansion
- ↳ g200kg
- ↳ Harrison Mixbus
- ↳ HG Fortune
- ↳ Homegrown Sounds
- ↳ HoRNet Plugins
- ↳ Ilya Efimov Production
- ↳ Image Line
- ↳ Impact Soundworks
- ↳ Indiginus
- ↳ Insert Piz Here
- ↳ Ju-X
- ↳ Kirk Hunter Studios
- ↳ Kirnu
- ↳ Kong Audio
- ↳ Krotos
- ↳ Kuassa
- ↳ KV331 Audio
- ↳ LennarDigital
- ↳ Les Productions Zvon
- ↳ Liqube Audio
- ↳ Loomer
- ↳ LVC-Audio
- ↳ Maizesoft
- ↳ Manytone Music
- ↳ Media Overkill (MOK)
- ↳ MeldaProduction
- ↳ Mellowmuse
- ↳ MIDIMood
- ↳ moForte
- ↳ Mozaic Beats
- ↳ mucoder
- ↳ MusicDevelopments
- ↳ Tips & Tricks
- ↳ MusicLab
- ↳ MuTools
- ↳ New Sonic Arts
- ↳ NUSofting
- ↳ Oli Larkin Plugins
- ↳ Orange Tree Samples
- ↳ patchpool
- ↳ Photosounder
- ↳ PlugInGuru
- ↳ Polyverse Music
- ↳ Precisionsound
- ↳ Premier Sound Factory
- ↳ Psychic Modulation
- ↳ Realitone
- ↳ Resonance-Sound
- ↳ Reveal Sound
- ↳ Roger Linn Design
- ↳ rs-met
- ↳ S3A: Spatial Audio
- ↳ SaschArt
- ↳ Smart Electronix
- ↳ sonible
- ↳ SonicBirth
- ↳ Sonic Reality / eSoundz.com
- ↳ Soundiron
- ↳ SPC Plugins
- ↳ Sugar Bytes
- ↳ TAL Software
- ↳ Tokyo Dawn Labs
- ↳ Tracktion
- ↳ Tweakbench
- ↳ u-he
- ↳ u-he Linux support
- ↳ UJAM
- ↳ United Plugins
- ↳ VAZ Synths
- ↳ Virharmonic
- ↳ xoxos
- ↳ XSRDO - SynthCraft
- ↳ ZynAddSubFX
- Site Stuff
- ↳ Site Stuff
- Archived Forums
- ↳ AlgoMusic
- ↳ easytoolz
- ↳ Elevayta
- ↳ Hollow Sun
- ↳ LinPlug
- ↳ Muse Research and Development
- ↳ Shuriken
- ↳ SoHa Sound Design
- ↳ Soniccouture
- ↳ Topten Software
- ↳ Valhalla DSP
- ↳ CK Modules & VST
- ↳ Sennheiser AMBEO
- ↳ Muon Software
- ↳ Westgatesounds.net
- ↳ Squaredheads
- ↳ Sonigen
- ↳ CFA-Sound
- ↳ Back In Time Records
- ↳ Livelab.dk
- ↳ Skytopia
- ↳ audioD3CK
- ↳ Inspire Audio
- ↳ Krakli
- ↳ Drumdrops
- ↳ Futucraft
- ↳ OverTone DSP
- ↳ RaXnTraX
- ↳ solar3d-software
- ↳ Signaldust
- ↳ Soundemote
- ↳ ReleaseLab (Powered by Artist Expansion)
- ↳ Wolfgang Palm
- KVR Forum index
- All times are UTC
- Delete cookies