In this article
Logic Pro separates software instruments, MIDI effects and audio effects because they do different jobs. Start by identifying the signal you want to create or change, then choose the appropriate slot. Third-party plugins must be supplied in a format supported by Logic.
Choose the track for the task
Use an audio track for a recorded voice, guitar or imported audio file. Use a software instrument track when MIDI notes need to play a piano, synth or sampler. A MIDI region contains performance information rather than recorded sound. This distinction explains why an instrument will not appear in the same menu as an audio compressor.
Understand the order of processing
On an instrument channel strip, MIDI effects act on notes before the instrument turns them into audio. Audio effects process the sound afterward. For example, an arpeggiator can turn held notes into a rhythmic pattern, while delay repeats the resulting audio. Both can create repetition, but they leave different things available for editing in the piano roll.
Explore the included tools first
Logic includes instruments for synthesis, sampling and drums, along with mixing effects. Start with one instrument you can learn well rather than changing the entire setup for each song. Save a simple patch with effects reduced, then use it to check chords and melody. A familiar sound makes it easier to hear changes in timing and harmony.
Install the correct third-party version
For Logic, choose the developer’s compatible Audio Units installation rather than a VST-only download. Follow the supplied authorization instructions and check the current system requirements. In Plug-in Manager, inspect the scan result if a new plugin is missing. Keep the DAW, operating system and plugin versions together when asking the developer for help.
Test a new plugin in a small project
Use one track, a short MIDI or audio region and a moderate playback level. Confirm that the plugin reopens correctly after saving the project, then try the specific features you need. If a tool generates MIDI, follow its Logic-specific routing or export instructions. Hearing its internal sound does not by itself confirm that another instrument is receiving its notes.
Save a setup you can maintain
Build a small template only after the signal flow makes sense. Name tracks by their musical role and keep a plain reference bounce when a sound is important. Before changing several plugins in an older project, save a separate version. The goal is a session you can reopen and understand, not a channel strip filled with processors you no longer recognize.
Try this in your project
Create one software instrument track with a piano. Add Arpeggiator in MIDI FX and a short reverb in Audio FX. Bypass each separately and describe whether it changes the notes, the sound, or the space around the sound.
Quick reference
| Focus | What to try | What to check |
|---|---|---|
| Instrument | Play a short MIDI region | Notes become audible sound |
| MIDI FX | Change notes before the instrument | The pattern changes before sound generation |
| Audio FX | Process the instrument output | Tone, dynamics or space changes |
Work with Captain Chords
Use Captain Chords to sketch the harmony, edit its voicing and rhythm, then develop the arrangement in your DAW.
Captain Plugins 8 overview
See the update video for the current canvas and editing workflow.
Useful references
Common questions
Why does my VST not appear in Logic?
Logic uses Audio Units for third-party plugins. Check whether the developer provides a compatible AU version, then inspect installation, authorization and the scan result.
Should I replace Logic’s included plugins immediately?
No. Learn what the included tools can do first. Add another plugin when you can identify a specific sound or workflow it improves.