The Client’s Challenge

My client, a talented composer, had devised an elegant and efficient workflow. He loved the intuitive groove-creation tools within Logic Pro’s Drummer, which allowed him to quickly build the rhythmic foundation for his tracks. The feel, the swing, the humanisation—it was perfect. However, for the actual drum sounds, he much preferred the rich, detailed sample library of Toontrack’s EZdrummer 3.

The logical next step seemed simple: create the patterns with Logic Drummer, then drag the resulting MIDI region onto the EZdrummer 3 track. The expectation was that EZdrummer would simply play the same pattern using its superior sounds. The reality was jarring. Instead of a tight groove, he was hearing a chaotic mess of random snare hits and misplaced percussion. His creative flow was broken by a technical mystery, and the frustration was mounting.

Diagnosis: A Case of Lost in Translation

When we connected for a remote session, the first order of business was to make the invisible visible. Logic’s Drummer regions are a kind of ‘black box’—they contain performance data, but not in the standard MIDI note format you can see in the Piano Roll. The moment the client dragged the region to the EZdrummer track, Logic was converting it to standard MIDI, but the damage was already done. The problem wasn’t a bug; it was a fundamental incompatibility in language.

The Fix: Building a Universal Translator

With the root cause identified, we needed a way to translate Logic’s MIDI dialect into one EZdrummer could understand. We explored a few avenues, moving from the manual to the elegant.

1. 1

   Revealing the MIDI Data

   First, we made the problem tangible. By right-clicking the Logic Drummer region and selecting Convert > Convert to MIDI Region, we could open the Piano Roll and see the ‘wrong’ notes with our own eyes. This confirmed the diagnosis and showed us exactly which notes needed to be moved.

2. 2

   Exploring Manual and Scripted Solutions

   One option was to manually select each group of wrong notes and nudge them to their correct positions using the keyboard shortcut Option + Up/Down Arrow. This is functional but incredibly time-consuming. A more advanced solution would be to use a MIDI FX plugin, like Logic’s Scripter, to build a custom map that re-routes notes in real-time. This is powerful but requires a significant technical investment to set up.

3. 3

   The Community Solution: The Pre-Built Map

   Knowing that this couldn’t be a unique problem, we turned to the wider music production community. A quick search of the Toontrack forums yielded exactly what we needed: a user named Jordan L. Chillcot had already done the painstaking work of creating a MIDI mapping preset to translate Logic Drummer’s output for EZdrummer. After downloading the file, we simply loaded it inside EZdrummer’s mapping settings. Instantly, the Logic patterns played back flawlessly through EZdrummer. The client’s ideal workflow was now a reality.

Additional Reflections

The Power of the Community

This case is a wonderful reminder that in the world of digital music production, you are rarely the first person to encounter a specific problem. The generosity of users like Jordan, who share their solutions on forums, is an invaluable resource. Before spending hours on a manual fix, it’s always worth spending a few minutes searching to see if someone else has already built the bridge you need to cross.

Demystifying Drum Maps

While we found a pre-made solution this time, understanding the concept of MIDI drum mapping is an empowering skill. Most modern drum plugins allow you to view and edit their maps. Taking a moment to see where your favourite kit pieces are ‘located’ on the keyboard can save you enormous headaches when working with MIDI from different sources. It turns a frustrating black box of random notes into a logical, predictable system you can control.