Export workflow
Plan and verify Logic Pro exports.
Export planning is read-only. Execution re-checks project identity and blockers. Observing a file in the destination does not automatically establish its producer or its stem subject.
Product sources reviewed October 5, 2026. Refer to the tagged contract for exact limits.
Before you begin
Prerequisites
- macOS 14+ for the server. Logic Pro 13.0 is the declared current version; the supported floor is 12.0.1, on a best-effort basis. Desktop Logic Pro is supported; Creator Studio is recognized, not supported.
- 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
Standalone bounce is unsupported; export_run is the automated export path. Unbound stem results remain State B; export_resume is limited to known-path artifacts.
Current boundary
What this does not prove
Export needs an existing readable destination that Logic's Export panel exposes. Eligible destination files can be analyzed, but post-snapshot files are not automatically attributed to Logic or a stem subject.
Primary evidence
Verify at the source
Product behavior is pinned to the v3.19.0 source. Client registration details remain owned by the client vendor.
Continue