Export workflow
Plan and verify Logic Pro exports.
Export planning is read-only. Execution re-checks project identity and blockers, opens Logic's native Bounce dialog, and verifies artifacts only after Logic writes them.
Evidence reviewed 2026-07-13 by the Logic Pro MCP open-source project.
Before you begin
Prerequisites
- macOS 14 or later; Logic Pro 12.3 is actively validated, with 12.0.1 and later best-effort.
- Save the project and resolve external-MIDI bounce-readiness blockers.
Verified path
Workflow
- 01
Audit
Run project audit and treat external MIDI region risks as blockers.
- 02
Plan
Use export_plan to inspect intended jobs without writing files.
- 03
Execute deliberately
Use export_run or export_resume with explicit confirmation and the expected project identity.
- 04
Verify artifacts
Use logic_audio to inspect existence, format, duration, silence, and clipping.
Observable evidence
What success means
The native Bounce dialog is observed and produced files are independently checked; a dialog-open result alone is not an exported artifact.
Current boundary
What this does not prove
The user completes Bounce settings and destination in Logic. No workflow can claim an artifact before file verification.
Primary evidence
Verify at the source
Product behavior is pinned to the v3.11.0 source. Client registration details remain owned by the client vendor.
Continue