Docs

The plugin

For DropWave 2.1. The rebuilt DropWave V2 does not include a plugin yet; this page stays for anyone still using 2.1.

This describes DropWave 2.1. DropWave V2 (3.1.0) is a ground-up rebuild and doesn't include the plugin yet. Where it stands →

What it does

Insert DropWave Analyzer on any channel — a vocal, a loop, the mix bus, anything. Say yes when it asks whether it may listen. Press play.

That is the whole interaction. It reads what goes through that channel and works out the key, the Camelot position and, when there is a reliable pulse to find, the tempo. There is no Analyze button. The first reading appears after about eight seconds of audio and sharpens as you play more.

It passes audio through untouched, so it is safe to leave inserted and forget about.

Play a few different parts

This is the one thing worth knowing, and it is the difference between a good reading and a great one.

The plugin treats each stretch you play as a separate look at the track. Play the intro for twenty seconds, jump to the drop, play that — those are two independent excerpts, and the answer is worked out from both. It is exactly what DropWave does to a file on disk, where it takes three windows from three places in the arrangement rather than reading the whole thing start to finish.

One long stretch of the same section is the weakest thing you can give it, because a breakdown is the least representative minute of most records.

The reading says what it is standing on — "24 s from 2 regions" — so you can tell a confident answer from a quick one at a glance.

It asks before it listens

Nothing is captured until you agree. That is enforced where the audio arrives rather than in the window: before you say yes, not one sample is kept.

The reason is practical as much as it is about privacy. A buffer that has been quietly filling since you opened the session contains whatever was soloed twenty minutes ago, and a reading taken from that is worse than no reading at all.

Silence is not captured

Most DAWs push silence through every insert while the transport is stopped. The plugin ignores it — a paused session costs you nothing, and the capture is only ever the audio that actually played.

This is also how it knows where one region ends and the next begins.

Installing it

There is nothing to install. The plugin ships inside the app.

  1. Launch DropWave once.
  2. Open your DAW and look for DropWave Analyzer under Effects.

That is the whole setup — no second installer, no plugin folder, nothing to drag anywhere.

It is an Audio Unit, which is the word your host will use for it: Logic Pro and GarageBand read Audio Units natively, and FL Studio does once the format is enabled in its plugin manager. If it does not appear immediately, your host is caching its plugin list — see troubleshooting.

On vocals

Expect a key and, often, no tempo.

Sung material has soft transients and frequently no beat present at all, so there is genuinely no tempo to find. The plugin showing a key and declining to print a BPM is it working correctly — it would rather show you nothing than a number it cannot stand behind.

The key reading on a vocal is reliable. See how to find the key of a vocal.

Beta

The plugin is in beta, and the word is in its name so you cannot miss it on an insert. It works, it is stable, and it is being refined. Report anything odd in the Discord.

Getting started · Key · Camelot wheel