LOWTRACE · 1.0.1

Manual

Read the low end. Compare the same section. Know what the numbers mean.

Screenshots show earlier builds. Some version labels and example readings differ; the instructions cover 1.0.1.

Start here

LOWTRACE draws level against the DAW timeline. Use it to see how the low end changes from hit to hit, capture before and after takes, and check where kick and bass may benefit from a polarity flip.

It is a meter, not a phase corrector, compressor or normalizer. With Listen: Full selected, it leaves the main audio unchanged once any audition crossfade has finished.

  1. Put it on the kick + bass bus. Select Low end and On bus.
  2. Route the final kick to Kick and final bass to Bass. Kick enables detected-hit measurements; both inputs are required for phase readings on a bus.
  3. Play the section. Choose a range that covers the loop and use Grid Auto.
  4. Snapshot, change, compare. Capture a before take, make your change, replay the same section and capture an after take.

The trace and level statistics work without a kick sidechain. Detected kick positions and per-kick verdicts do not. Fixed beat grids remain available, but those are time slots—not proof that a kick happened.

LOWTRACE in Black theme, showing the live low-end trace with On bus selected.
Live monitoring with the kick and bass inputs present. Comparison is paused here because a chosen line is hidden or has no data.Select to enlarge

Install and update

Quit your DAW and extract the download before copying the plugin.

Windows · VST3

Copy the entire LOWTRACE.vst3 item to C:\Program Files\Common Files\VST3\. Approve the Windows copy prompt if asked. Reopen your DAW and rescan VST3 plugins if needed.

Mac · Intel and Apple Silicon

The release Mac download is universal, signed and notarized. Double-click the ZIP on your Mac to extract it. Install the format your DAW uses; Logic Pro, GarageBand and MainStage use AU.

FormatCopy this whole bundleDestination
VST3LOWTRACE.vst3~/Library/Audio/Plug-Ins/VST3/
AULOWTRACE.component~/Library/Audio/Plug-Ins/Components/

In Finder, choose Go → Go to Folder, paste the destination including the ~, and press Return. These locations install for your user account. If a folder is missing, open ~/Library/ and create Audio, then Plug-Ins, then VST3 or Components as needed.

Copy each whole .vst3 or .component bundle as it appears in Finder. Do not open Show Package Contents or copy its internal files separately. Reopen your DAW and let it scan; rescan its plugins if needed. For an AU that still does not appear, restart the Mac.

Replacing an older version

With the DAW closed, replace the old bundle in its existing installation location. Avoid duplicate copies of the same format in different plugin folders. The release retains the plugin identity used by existing projects. Keep a backup of important projects before saving them with an update.

The standalone app is optional. On Mac, copy LOWTRACE.app to Applications. The plugin inside your DAW is the normal choice for the host-timeline workflows in this manual.

On bus, On bass and routing

On bus and On bass tells LOWTRACE what is already in its main input. Set it to match where you inserted the plugin. It does not move the plugin, create a DAW send or add the sidechain to the audible output.

Low end routing
PlacementMain inputAnalysis
On bus + Kick and BassKick + bass busTraces the actual bus. Measures phase from the direct kick and bass inputs before bus effects.
On bus + Kick onlyKick + bass busKeeps detected kick positions and bus levels. Connect Bass to enable phase and component verdicts.
On bass + KickBass onlyReconstructs kick + bass for the trace and measures their relationship. The main input supplies the bass reference.

The Kick port is the first sidechain; Bass is the second. In On bus mode, both are required for phase readings. Use the host’s routing and plugin input mapping to connect them. The level trace still works without either sidechain.

In On bass, the main trace still adds the main bass input to the kick. A direct Bass sidechain is used for component diagnostics, so keep it matched to that same bass signal.

Send the final kick and bass after their individual processing, aligned in time and at the gains feeding the bus. Keep your sidechain compressor in its intended place and take the bass reference after that processing. The phase reading compares these two inputs before bus effects. Bus gain, EQ or compression can change the main trace without changing this input-phase measurement.

Input flip estimates the benefit of reversing kick polarity in that direct input pair. It does not predict the output of a nonlinear bus processor. Monitor the real bus to judge the finished result.

Check the connection

Play the kick and look for KICKS FROM THE KICK INPUT. ROUTE THE KICK IN means LOWTRACE has no active kick reference. A sidechain enabled in the host but silent for about two seconds is treated as absent.

In hosts with input pins, map the kick send to LOWTRACE’s Kick port, not the main input. For a stereo REAPER setup, channels 3/4 can feed Kick and 5/6 can feed Bass; verify the plugin’s pin mapping rather than relying on channel numbers alone.

If your host exposes only one sidechain source, On bus can still show kick positions and bus levels. For phase readings, use a host configuration that exposes both references, or insert LOWTRACE on the bass, choose On bass, and feed Kick.

LOWTRACE does not automatically link to LOWTUNA instances. Use DAW audio routing. If the kick is being corrected by LOWTUNA, take LOWTRACE’s kick reference after that correction so it matches the kick reaching the bus.

Low end and Full mix

Low end

Measures the low band below CROSSOVER. The main trace uses the mono average of the low end, so stereo cancellation can lower the reading. Use it for the kick and bass relationship and low-end consistency.

Crossover spans 30–300 Hz and defaults to 120 Hz. Double-click it to reset. The filter is a fourth-order Linkwitz–Riley crossover, 24 dB per octave. It is a slope, not a brick wall.

Full mix

Measures average channel power across the full mix, or within the band you choose. Unlike Low end’s mono average, wide stereo content does not cancel merely because the channels oppose each other.

The two-thumb BAND control sets high-pass and low-pass edges from 20 Hz to 20 kHz. Each active edge is 24 dB per octave. At the outer ends, that edge is Off, meaning bypassed—not a filter still cutting at 20 Hz or 20 kHz. Double-click to open the full band.

At low sample rates, active edges are limited to 0.49 × sample rate. The control shows the effective limit. The placement and kick and bass diagnostics belong to Low end; Full mix is for judging mix or band-level changes.

Changing mode, band and crossover, averaging window, routing or sample rate starts fresh live measurements. Saved takes stay intact. Compare takes made with matching measurement settings.

Full mix mode with the measured band from DC to 197 Hz and Listen Full selected.
The saved Low end takes are not comparable in Full mix. Switch back to Low end to use those takes, or capture new matching takes.Select to enlarge

Listen without guessing

ModeListen choices
Low endFull: original main input. Low: below the crossover. High: above it.
Full mixFull: original main input. Band: the selected band.

Listen always auditions the main input. In On bass placement, the trace can represent kick + bass while Listen still auditions only the main bass track. The kick sidechain is not mixed into the output.

Listen changes crossfade over about 10 ms. Once Full has settled, the output is bit-exact with the main input. The filters continue running for analysis without being inserted into that Full audio path.

Low and High add with a flat magnitude response, but their combined phase is all-pass; do not expect their sum to null sample-for-sample against dry audio. The Full option avoids that filter path entirely.

Return Listen to Full. Listen is intentionally not saved with the project and resets to Full on reopening or changing mode, so a session does not reopen with a band soloed.

Range, grid and trace view

Range

Choose 1, 2, 4 or 8 bars for a repeating sweep. Fit loop makes a shorter DAW loop fill the view. LOWTRACE uses the host’s loop information when available, or learns the wrap from a backward playhead jump.

Timeline holds the played section by musical position. Replaying a section replaces the live trace there. Follow tracks the DAW playhead, playing or stopped; it does not follow your mouse pointer in the DAW.

Grid

SettingMeaning
AutoOne slot per detected kick, using the Kick input. Best for syncopation and swing. Detection is still a heuristic, not a guarantee for every possible stem.
1/4 · 1/8 · 1/16Regular musical slots. No sidechain is needed. Empty slots and off-grid hits can make these measurements misleading on irregular patterns.
OffThe line and overall statistics without grid slots.

Move around

Trails shows faint previous passes. These are not saved takes. Clear clears live measurements without deleting the saved A–D takes.

Scale and averaging

Open the trace’s dB-scale menu for a 12, 24, 36 or 48 dB vertical span, Follow the level, and a 30, 50, 100 or 400 ms averaging setting. A short setting follows changes more closely; a long setting smooths them more.

Nothing new is recorded while the DAW is stopped. Use a complete pass after changing settings. A partially drawn loop is not a complete before and after comparison.

Scale menu with Span 24 dB, Follow the level, and 100 ms selected.
The span changes the view. Averaging changes the measurement, so keep it matched between takes.Select to enlarge

What the numbers mean

The Readings panel follows the selected target, not an average of every visible line. With a valid reference, comparison figures show target minus reference.

Level readings
ReadoutDefinition
Hit spreadLoudest valid hit or slot minus quietest. Timeline uses the 90th–10th percentile spread when at least five valid slots are available; otherwise it uses the full spread.
HighThe highest smoothed level in the measured view. Not the waveform’s sample peak or true peak.
LowThe lowest valid level above the activity gate.
AverageA power average of the valid, gated level points—not an arithmetic average of their dB values.
Dyn rangeThe 95th–5th percentile spread of valid, gated smoothed levels. Not crest factor, a DR-meter score or loudness range in LU.

The activity gate excludes points below the higher of High − 48 dB and −80 dB. That keeps silence from dominating Low, Average and Dyn range. A missing value means there is not enough valid data; it does not mean zero.

The level scale

Levels use sine-referenced mean-square measurement: a full-scale sine reads 0 dB. The selected averaging time drives three cascaded smoothing windows, each half that length; total support is about 1.5 times the setting. This is not LUFS or true-peak measurement.

Hit levels are measured within guarded parts of each slot to reduce contamination from neighbouring attacks and tails. They describe the smoothed low-end result, not the highest raw sample of the kick.

Sub is stereo

This warning appears when low-band Side energy is within 12 dB of Mid. It is a cue to check mono compatibility. It does not mean stereo bass is always wrong, or that every stereo sub will disappear in mono.

Adding gain also raises the trace. A smaller spread can come from compression or a different envelope, not necessarily better phase. Compare the same material, keep routing and gain consistent, and listen.

Per-kick verdicts

In Low end with Grid Auto, LOWTRACE detects hits from the Kick input. Phase and component verdicts also need a usable bass reference: the Bass input in On bus mode, or the main bass signal in On bass mode. Hover a hit for its explanation.

BadgeWhat it says
PHASE +x.xThe measured low-band sum could rise by the displayed amount if the kick’s polarity were flipped against the bass. Shown from +1.5 dB, with usable component levels.
KICKThe kick component is at least 1.5 dB below the median kick level of the measured hits in view.
BASSThe bass component is at least 1.5 dB below the median bass level of those hits.
BASS DIPThe bass is low on this hit and drops at least 3 dB against the preceding measurement. It may be ducking, a note change or an envelope change—not proof of compression.

PHASE is a hypothetical flip estimate, not a phase angle. LOWTRACE does not apply the flip. It does not estimate every possible all-pass or FIR correction or guarantee LOWTUNA will choose the same result.

The estimate compares the direct low-band kick + bass sum with the same pair after a hypothetical kick polarity flip, over a window of up to 150 ms ending at the next detected kick. The Readings summary calls this input flip. In On bus mode, the processed bus energy is used for levels, not for this phase estimate. Very deep cancellation is shown as a finite bound of at least 60 dB rather than an infinite number.

No flips above +1.5 dB means no measured hit exceeded the flagging threshold. It does not prove there is no cancellation. A KICK or BASS label also does not certify that a hit is phase-aligned.

These are prompts for an engineering decision. Do not flatten intentional accents or bass movement just to make every hit match.

Snapshots and comparison

Snapshot stores the current trace and analysis in one of four slots, A–D. It stores measurement data, not an audio recording. Live remains a separate trace.

  1. Play the entire section with the processing you want to compare bypassed or in its before state.
  2. Stop and click Snapshot. Rename the take so you know what it represents.
  3. Change only the processing being tested. Replay the same complete section and make another snapshot.
  4. Set the after take as target and the before take as reference. Turn Compare on.

The first snapshot becomes the reference; later snapshots become the target. With Compare enabled, the second snapshot therefore gives B versus A. You can change that pairing afterward.

Take controlAction
Click a takeShow that take’s numbers as the target.
EyeShow or hide its trace.
Right-click menuChoose target or reference; rename, recolour, show or hide or delete the take.
DeleteRemove the saved take. Clear is different: it clears only live measurements.

In Compare, a green filled gap means the target is higher; a red gap means it is lower. These colours do not mean “good” and “bad”. They are also separate from the red PHASE flags.

Keep the comparison valid

Use matching mode, band and crossover, averaging, routing and sample rate. Incompatible data can remain visible where the view allows it, but numerical comparisons are withheld. Recapture older takes that lack the metadata needed for comparison.

Older saved snapshots keep their curves, but their old phase and component verdicts are disabled. Clear the live capture, replay the same section with the current routing, and save fresh snapshots for corrected analysis. Delete an old take if you need a free A–D slot.

Saved bar and loop takes retain their musical origin when the range or loop start changes. Shorter takes repeat; longer takes crop at the matching musical position. This is not time-warping or automatic audio alignment. For a straightforward comparison, capture the same section at the same positions.

The DAW project saves the takes and their measurement settings. Snapshot is disabled when there is no valid data or all four slots are occupied; delete an unwanted take to free a slot.

LOWTRACE comparison with Lowtuna off as target and Lowtuna on as reference, showing red gaps.
This example deliberately reads off minus on: the target is Lowtuna off, the reference is Lowtuna on. Red shows where the off take is lower. Select the on take as target to read the change in the other direction.Select to enlarge

The live ROUTE THE KICK IN hint can appear while playback is stopped even when saved takes contain valid kick measurements. It describes the current input, not whether the snapshots originally had a kick feed.

Compare a LOWTUNA correction

  1. Put LOWTRACE on the kick + bass bus. Choose Low end → On bus.
  2. Send the kick after LOWTUNA to LOWTRACE’s Kick input. Keep this feed matched to the kick reaching the bus.
  3. Send the final bass, including any bass-channel processing or ducking, to LOWTRACE’s Bass input. Match its timing and gain to the bass feeding the bus.
  4. Set the crossover, range, averaging and Auto grid. Keep them unchanged for both passes.
  5. Turn LOWTUNA’s Correction off, play the complete section, then Snapshot A.
  6. Turn Correction on, wait for LOWTUNA to be ready, replay the same section, then Snapshot B.
  7. Compare B against A. Check the trace, spread, component levels and flip flags, then listen in context.

Use LOWTUNA’s Correction switch for the comparison so its compensated dry path stays in place. Do not change the bus gain between passes. LOWTRACE’s crossover band and LOWTUNA’s scoring bands differ, so their dB figures need not match.

A trace can show recovered low-end energy and changes in consistency. It cannot prove the correction is inaudible, that the attack improved, or that every hit should have the same level.

Menu and image export

Click the LOWTRACE wordmark to open its main menu.

Menu itemOptions
ThemeDay, Night or Black.
Size80%, 100%, 125%, 150% or 200%.
TooltipsShow or hide hover explanations.
Reduce motionReduce animation without changing measurement.
Export image…Save a 2× PNG of the plugin view for a comparison or report. It does not export audio.

LOWTRACE has no separate Glow effects menu item. Theme and size are display preferences, not measurement settings.

The top-right transport indicator shows whether LOWTRACE is following the DAW or stopped. Without a host clock, the standalone view is free-running at 120 BPM in 4/4; do not mistake that for a detected song tempo.

LOWTRACE 1.1.4 main menu with the Black theme selected and Export image available.
Open the wordmark menu for display preferences and image export.Select to enlarge

If something looks wrong

The trace works but Auto shows no kicks

Route the isolated kick to the Kick sidechain and confirm the input mapping. LOWTRACE deliberately does not guess kick hits from the combined bus. Check that the kick feed is active, not simply enabled in the host.

The bass-only track produces strange readings

Select On bass and route the kick to Kick. The main input supplies bass; LOWTRACE reconstructs the sum for analysis. On bus would instead trace only the signal arriving at the main input. The placement button does not create routing.

Need audible Bass input for phase

In On bus mode, connect the final bass to the Bass sidechain and play a section where bass is present. Kick alone gives positions and bus levels. Check the actual input mapping and signal, not just whether the sidechain is enabled.

PHASE numbers look implausible

Check that Kick and Bass carry the intended final stems with matching timing and gains. Clear and replay after correcting routing. The input flip figure measures their direct low-band sum before bus effects, so it need not match the change after bus compression or saturation, or LOWTUNA’s differently weighted result.

A ringing kick was counted more than once

Version 1.0.1 fixes repeated detections inside ringing kick bodies and waits for the next attack before finalizing a measurement window. Update, clear the live capture and replay. If a stem still gives extra or missed hits, check that Kick receives only the kick and retain a short example for a bug report.

Numbers disappear when I compare takes

Check that the takes share mode, frequency settings, averaging, routing and sample rate. Old takes without enough validity metadata need to be recaptured. Keep both passes complete and over the same section.

The trace is frozen

Check the DAW transport. Measurements stop with playback. In Timeline, Follow tracks the actual playhead; moving the mouse over the DAW timeline does not move LOWTRACE.

The graph shows kick + bass but I only hear bass in Listen

That is expected in On bass placement. Analysis reconstructs the sum; Listen filters only the main input, which is your bass track. Monitor the real bus to hear kick and bass together.

High does not match another peak meter

High is the maximum smoothed, sine-referenced level in the selected band or view. It is not sample peak, true peak or LUFS. Check that the other meter uses the same definition before comparing numbers.

A menu disappears or will not open

Use the current 1.0.1 release, which includes the earlier menu fixes. If it still happens, report the DAW, OS, plugin version, display scaling and whether the plugin is bridged or sandboxed. Include which menu or submenu failed.