Using StudioPilot in Logic Pro: a setup and workflow guide

Logic Pro handles plugins a little differently from the rest of the field: it speaks Audio Units, it validates them once on launch, and after that a plugin simply becomes part of the furniture. StudioPilot fits that model cleanly. This guide walks the whole path: installing the AU, letting Logic scan it, and a first real session where you generate a part, compare two takes, and drag the winner into the tracks area. If you can insert a compressor on a channel strip, you can do everything on this page.

What you need

• Logic Pro 10.7 or later, running on macOS 13 or newer.
• The StudioPilot plugin, free from studiopilot.tech/download. The macOS installer ships both VST3 and AU; Logic loads the AU, and the installer puts it exactly where Logic expects to find it.
• Or skip the install entirely. The same tool runs in the browser at vst.studiopilot.tech, the fastest way to hear it before touching your plugin folder. Everything below about generating applies there too.

Setup: three steps

1. Run the installer. It places the Audio Unit in the standard system location, no manual copying, no folder hunting.
2. Restart Logic. Logic scans for new Audio Units when it launches, so quit and reopen it once. StudioPilot passes validation and shows up in the plugin menu under Audio Units.
3. Insert it on a track. Add StudioPilot to an audio or instrument track like any other plugin. The full interface opens in the plugin window, and that window is where the rest of this guide happens.

That is the entire setup. No account linking inside Logic, no environment objects, no companion app running in the background.

Tempo: nothing to configure

StudioPilot reads Logic's project tempo automatically. If your session sits at 84 BPM, the plugin already knows, and Make Beat follows the project BPM without you typing a number anywhere. Change the session tempo and the plugin follows along. This sounds like a small thing until you have spent an evening retyping BPM values into a browser tab; in practice it is the difference between a tool that lives in your session and one that visits it.

A first session, start to finish

Here is the loop you will actually use, in the order you will use it.

1. Bring in your audio

Load or drag your own audio into the plugin, anything up to five minutes: a bounced idea, a rough vocal, a guitar loop, a half-finished arrangement. That clip becomes the context everything else is generated against. You can also start from nothing with Make Beat or Make Loop if the project is still empty.

2. Ask for the part you are missing

• Add Instrument layers a generated instrumental part on top of what you loaded: keys under a vocal, a bass line under a beat, a lead over a chord loop.
• Add Vocals does the same for a vocal line, sung against your existing audio.
• Change Style restyles a clip: same musical idea, different production, useful when the writing is right but the sound is not.
• Make Loop builds loops and one-shots from a description, handy for filling a sampler or grabbing a texture.

3. Pick a take

Every generation returns two takes, A and B. They are two different readings of the same request, so audition both before judging the idea itself. Often one take has the right energy and the other has the right sound, and hearing them side by side tells you what to ask for next. Keep the one that works.

4. Drag it into the tracks area

Take the winner and drag it straight from the plugin into Logic's tracks area. It lands as regular audio on a regular track, which means everything you already know applies from that moment on: flex it, chop it, bounce it in place, run it through your channel strip. The generated part stops being special the second it hits the timeline, and that is exactly the point.

What generating costs

Generation runs on credits, and the pricing is flat and easy to hold in your head:

• Add Instrument, Add Vocals, Make Beat, Change Style: 10 credits each.
• Make Loop: 4 credits.
• Analyze: free, always.

A free account starts with 100 credits and asks for no card, which is enough room to run this whole guide several times over before deciding whether the tool belongs in your template.

A note on GarageBand

GarageBand loads Audio Unit plugins the same way Logic does, so StudioPilot is expected to work there too. We have not formally tested it, so treat that as a likely yes rather than a promise. The nice part: if you start in GarageBand and later move up to Logic, nothing changes, same plugin, same account, same credits.

Where it fits

The honest way to think about StudioPilot in Logic is as one more insert in the chain, not a second workstation. Logic stays the boss: it owns the tempo, the arrangement, and every edit after the drag. The plugin's job is narrow on purpose, to hand you the part you could not play, in your session, at your tempo, without a browser round-trip. And if you also work in Live, the same walkthrough exists for Ableton Live.