MIDI workflow
Compose MIDI with an honest verification boundary.
MIDI messages can be sent precisely, but a send-only success is not proof that Logic created an audible region. Verified workflows use import or region readback where available.
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.
- Create or open a project and identify the target software-instrument track.
Verified path
Workflow
- 01
Inspect the target
Read tracks and project identity before selecting a destination.
- 02
Create or import
Use logic_tracks and logic_midi with explicit note, channel, duration, and port values.
- 03
Wait for each result
Do not chain another import until the preceding operation returns its evidence envelope.
- 04
Verify the region
Use project region readback when the operation supports it; otherwise retain the State B limitation.
Observable evidence
What success means
A verified import reports the created region; send-only operations report State B with the no-readback reason.
Current boundary
What this does not prove
GM Device or External MIDI lanes can be silent during bounce and are not accepted as audible evidence.
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