Download noteGRABBER for Mac

In the edit

You know that moment when you drop a sample into a track and wish you could pull the notes out cleanly? noteGRABBER is the plugin that does exactly that — it analyses audio and converts it into MIDI data, so you can rewrite the melody, layer new instruments over the original, or just use the sample as a starting point for something else.

Put noteGRABBER on a bus or directly on the sample track

I put noteGRABBER on a bus or directly on the sample track. It listens to the audio, spits out MIDI notes, and from there I can send that MIDI to a synth or sampler on another track. It saves the hassle of hunting for chords by ear when the sample already has what I need.

Grab harmonic content from a loop and reassign it

Most often I use it to grab the harmonic content from a loop and reassign it to a different instrument. It also works well for pulling out basslines or melodic phrases from vocal samples. The developer built it to make sampling easier, and that is exactly what it does — no fuss, just the notes you need to keep moving.

How noteGRABBER sits alongside other Mac audio-to-MIDI tools

There are a few ways to get MIDI out of audio on a Mac, and each one has its own approach. I have used a couple of the better-known ones alongside noteGRABBER, and they all land differently depending on what you are trying to do.

One popular option is the built-in audio-to-MIDI feature in Logic Pro. It works, but it lives inside Logic and nowhere else. If you produce in Ableton, Bitwig, or FL Studio, you are out of luck. noteGRABBER runs as a plugin in any host that supports the format, so it follows your DAW rather than the other way around.

Another plugin I have tried is more of a pitch-to-MIDI converter that tracks monophonic material well but gets confused with chords or layered samples. noteGRABBER handles polyphonic audio, which is the whole point when you are working with a full loop or a sample that has bass, chords, and melody all at once.

Then there are the standalone tools that export MIDI files outside the DAW. They work, but they add steps — export audio, open the tool, export MIDI, import the MIDI back. noteGRABBER keeps everything inside the session. That might not matter for a single sample, but when you are churning through a folder of loops it saves time.

None of these are bad tools. But noteGRABBER sits in a particular spot: it is a plugin, it handles polyphonic material, and it is built by someone who makes music rather than by a large team with a different set of priorities. That independence shows in how straightforward it is.

Replaced a loud horn part with a MIDI synth

Last week I was working on a beat that needed a melodic hook. I had a dusty soul record sample I wanted to use, but the original horn part was too loud to leave in. I wanted to replace it with a synth line that followed the same contour.

I dropped the sample onto an audio track in my DAW and inserted noteGRABBER on that track. I hit play and let it run through the loop once. Within a few seconds it had analysed the notes and written them as MIDI data. I dragged the resulting MIDI clip onto a new track with a soft pad sound. The notes matched the horn line well enough that I only had to nudge a couple of them into the right octave.

From there I started experimenting. I sent the same MIDI to a bass patch to see how the chords sounded an octave down. Then I duplicated the MIDI clip, moved a few notes around, and created a counter-melody that sat underneath the original horn part, which I had decided to keep after all. The whole process took maybe ten minutes, and most of that was choosing sounds rather than figuring out the notes.

That is the kind of session noteGRABBER is made for. You are not trying to replace the sample completely; you are using what it already gives you and making it your own.

Deal with imperfect MIDI conversions on the first try

Nobody gets a perfect MIDI conversion on the first try every time. Here are a few things that come up and how I deal with them.

The MIDI notes are in the wrong octave

This happens fairly often, especially with bass samples or high-pitched vocal stabs. noteGRABBER detects the fundamental frequency, but the resulting MIDI might land an octave above or below where you want it. I just transpose the MIDI clip in my DAW until it sits right. It takes two seconds.

The output has extra notes or ghost notes

If the sample has background noise, reverb tails, or a lot of harmonics, the analysis can pick up notes that are not really part of the melody. I usually open the MIDI clip and delete the quietest notes or the ones that fall outside the range I am working with. A quick pass through the piano roll cleans it up.

Polyphonic material sounds messy

noteGRABBER handles chords, but if the sample has many overlapping parts — say, a full band recording — the output can be dense. I find it helps to work with a shorter section of the sample first. Loop a bar or two, let noteGRABBER analyse just that, and build up from there. You get a cleaner result and less editing later.

The plugin does not seem to be detecting anything

This is almost always a routing issue. Check that noteGRABBER is inserted on the correct track and that audio is actually reaching it. I have also had cases where the sample was too quiet. A small gain boost before the plugin helps the analysis pick up the notes.

Adjust the note range before starting a session

noteGRABBER comes with defaults that work for a lot of material, but I usually tweak a couple of things before I start a session.

The first thing I adjust is the note range. If I am working with a bass sample, I set the lower and upper bounds to keep the MIDI focused on the frequencies I care about. That cuts out high-frequency noise or low rumbles that would otherwise produce unwanted notes.

I also pay attention to the sensitivity control. Turning it down a little reduces the number of ghost notes from roomy or reverb-heavy samples. If the sample is clean and dry, I leave it higher so nothing is missed.

Another thing I do is set the output to a single octave range when I am just grabbing a melody line. That makes the MIDI easier to work with right away, and I can transpose it later if needed. For chords or complex material I leave the range wider.

These are small changes, but they save time on the editing side. Once you know how a particular sample behaves, you can dial in the settings in a few seconds and move on to making music.

Mac it needs

• macOS 10.12 or later
• Intel or Apple Silicon