Features

Everything it does. And proves.

bounceBuddy automatically scans and bounces your Logic project, online or offline, organising every track and all of its nested routing. No templates needed: it adapts to every session and every user, automatically.

What it does.

Every track, every route

  • Audio, instrument & Session Player tracks
  • Summing & folder stacks, bounced as the groups they are
  • Bus groups & aux sub-mixes, printed through their bus processing
  • Colour groups: track & region colours become stems
  • Logic track groups & channel groups
  • Multi-output & multi-timbral instruments, with their aux lanes
  • Drum Machine Designer kits: pads bounce as the kit
  • Shared strips, split mono L/R, stereo pairs

Sends, outputs and the tidy-up

  • All FX sends: reverbs, delays & parallel buses auto-detected
  • Mix-level FX, Dry, or Wet + Dry (two files per stem)
  • Output tracks: optional auto-muting of limiters & bus compressors
  • No clean-up needed: muted, disabled, hidden, empty & no-output tracks exclude themselves
  • Solos cleared, click silenced before every run
A 10-stem session mapped automatically
A different rig, mapped in seconds

What nothing else does.

Project data, not the screen

No pixel matching, no window flapping, no "hope the mixer was visible". It decodes Logic's own project file.

Printing the mix as you hear it

Hear it and check it

The details engineers ask about.

The bounce itself

Handing it over

It works on a copy, not on your session.

Every decision bounceBuddy makes (what the stems are, how they group, what shares a bus with what) is worked out from a duplicate of your project data, offline, before Logic is asked to do anything at all. bounceBuddy never writes to your project. The only thing that ever writes to it is Logic, and the only thing it writes is a save. The same one you'd have pressed yourself before handing the session to anybody.

Nothing in your arrangement is added, deleted, moved, renamed or re-routed. Not a track, not a region, not a send. During the bounce it does drive the things a bounce needs (mutes, solos, mix-bus plugins), and every one of them goes back the way it found it when the run finishes.

That's the whole reason it's built this way. A tool you have to check by hand afterwards isn't saving you anything.

How I know it reads your session right.

Every build is checked against real sessions from my own work, with stem lists I've signed off by hand. If a single stem comes out different, that build doesn't ship.

Buy it once. It's yours.

Coming soon Join the free beta

Free beta · no subscription · macOS 14+ · Logic Pro 12+ recommended (works on 11+) · Logic in any of its languages