Should Logic Pro users start with AU or standalone?
Most Logic Pro users should start with the AU plug-in route because it keeps chord generation, instruments, recording, and arrangement inside one Logic project.
Logic Pro / 01
MIDI chord generator plugin workflow for Logic Pro.
If you want a chord generator workflow in Logic Pro, Harmonimo now has a direct path: load the AU plug-in in Logic, trigger full chords from single notes, and keep the rest of the session inside Logic instead of building an external routing chain first.
Format
Direct AU workflow inside Logic Pro 11
Best for
Chord writing, one-handed harmony, and controller-led performance
Optional route
Standalone routing is still there for wider MIDI setups
Quick answer
How do you use a MIDI chord generator plugin in Logic Pro?
Use Harmonimo as a direct AU plug-in in Logic Pro when you want one-note chord generation, playable voicings, and controller-friendly harmony inside the project. The standalone route is still useful for external synths or wider MIDI rigs, but most Logic sessions should start with the native AU workflow.
Section 01
How does direct support work inside Logic Pro?
The setup is simpler now.
Harmonimo now supports Logic Pro directly through AU, so the normal starting point is a native plug-in workflow inside the project. That keeps chord generation, instrument choice, recording, and arrangement decisions in one place instead of splitting them across separate apps.
In practice, that means Logic users can load Harmonimo, play a note, shape voicings and extensions, and keep moving without setting up a virtual MIDI bus first.
- Native AU workflow inside Logic Pro 11
- No virtual MIDI bus required for standard Logic sessions
- A better fit for writing, recording, and arrangement in one project
Section 02
Where does Harmonimo fit in a Logic workflow?
The Logic advantage is keeping the harmony work close to the session.
Logic users usually want quick progression sketching, one-handed harmony, and controller access without breaking the flow of the arrangement. Harmonimo fits well there because you can keep your keys, synths, and arrangement decisions inside the same session while the plug-in handles the harmonic translation.
That is especially useful when you want to test extensions, inversions, strum, and spread against the same patch. You can move between cleaner pop voicings and richer neo-soul or jazz colors without rebuilding the MIDI by hand every time.
- Progression sketching without note-by-note chord entry
- One-handed chords while the other hand handles melody or automation
- Controller-friendly harmony shaping inside Logic
Section 03
When does standalone routing still make sense?
The direct AU route should be the default, but it is not the only option.
Standalone routing is still useful when you want a separate performance surface, an external synth path, or a more modular multi-app MIDI setup. Harmonimo Standalone plus a virtual MIDI bus remains a valid route when you deliberately want that flexibility.
For most Logic users, though, the native AU path is the cleaner start. Use virtual MIDI only when you intentionally want to split the harmony engine away from the main project.
- Use AU directly for standard Logic sessions
- Use standalone when you want external or cross-app MIDI routing
- Use the virtual MIDI guide when you need exact routing steps
For most Logic setups, start with the direct AU workflow. Reach for virtual MIDI when you intentionally want a wider routing rig.
FAQ
What else should you know?
When is standalone routing better for Logic Pro?
Standalone routing is better when Harmonimo needs to act as a separate performance surface, drive external synths, or feed a wider cross-app MIDI setup.