'Why is the alignment not working as expected?' - One of the following may explain the behaviour you're seeing!
DAW support:
The alignment process requires the DAW to have implemented certain third-party extensions to allow Drum Gate 2 to receive track information. Without this, no tracks will appear in the Align view. Most DAWs include this functionality, however the ones we are aware of that do not include this are:
Digital Performer
Reason
Alignment Reference and Track Behaviour
Drum Gate 2's Alignment feature uses a Time Anchor and a Phase Reference to determine how drum tracks are aligned.
By default:
- Kick (Bass Drum) is used as the Time Anchor
-
Overheads are used as the Phase Reference
This default configuration is recommended for most multi‑mic drum recordings, and for best results at least one Overhead track should be included. But what if you recorded with a more minimal, less conventional mic setup? Read on!
As of Drum Gate 2 v1.02, the Time Anchor and Phase Reference are no longer fixed to these groups. Any drum group can now be assigned as the Time Anchor and/or Phase Reference, allowing alignment to be tailored to alternative mic setups or creative workflows.
Logic Pro – Alignment Stops Before Audio Is Read by the Plug‑in
The Alignment feature relies on the host DAW providing correct track properties and active playhead context to each Oxford Drum Gate 2 instance.
In Logic Pro, audio blocks are not always passed to plug‑ins until non‑silent audio is detected on a track. This can interrupt or prevent the Alignment analysis stage, particularly when working with:
- Tom tracks where bleed has already been stripped during edit or mix preparation
- Cymbal spot microphones with sparse or intermittent audio regions
Workarounds:
If Alignment stops before analysis completes, the following workflows can help:
- Perform alignment before stripping audio regions or removing bleed
- Loop a section (e.g. ~20 seconds) that contains non‑silent audio on every track being aligned, then run Alignment
Notes on Recent Improvements
Recent Drum Gate 2 updates include clearer visual cues and on‑screen guidance before, during, and after the Alignment analysis. These improvements make it easier to identify when audio is not being received by the plug‑in, and should reduce the likelihood of this issue occurring in future workflows.
Why do my time and polarity results differ per analysis?
Drum Gate 2's alignment feature has been extensively tested to deliver consistent, repeatable audible results across multiple analyses. That said, when running alignment more than once, it is normal to see small, and in rarer cases, larger differences in timing (samples) and polarity.
These variations can depend on factors such as -
- Changes to the loop being analysed.
- The length of the analysis window,
- Changes in playhead position.
- Slight changes in playhead information, which can vary in behaviour per DAW
In these cases, the algorithm is achieving the same audible improvement but arriving there through a different set of calculations, which is expected behaviour. However, if the result sounds less impactful or becomes hollow or phasey after analysis, we recommend following the troubleshooting steps outlined in the Drum Gate 2 User Guide
Changes to Track Grouping, Time Anchor, or Phase Reference
If you change track grouping, remove an included track from the session or assign a different Time Anchor or Phase Reference after an Alignment analysis has been completed, the audible results from the previous analysis will remain active.
However, the plug‑in will display a notification in the GUI indicating that the current configuration no longer matches the last analysis. To apply the updated grouping or reference settings, Alignment must be re‑analysed. This ensures that all alignment calculations reflect the most recent session configuration.
Sandboxing in DAWS
Host DAWs which provide per-instance sandboxing of plug-ins are not compatible with the Align feature. We advise turning off Sandboxing on any Drum Gate 2 instances until alignment has been completed.
DAWs that support Sandboxing include -
- Reaper
- Bitwig Studio
- FL Studio
- Fender Pro Studio