Getting started
Start with the rig. Continue in one conversation.
The refactored Maeztro interface routes setup, session work, Live control, jam markers, and arrangement requests from a local conversation attached to the current project.
Never download Maeztro from an unverified mirror. Public beta builds will be Developer ID signed, notarized by Apple, and published with a SHA-256 checksum.
1. Install the signed app
- Open the signed `.dmg`Drag Maeztro into Applications. Public builds will not require Python, Rust, Homebrew, or Terminal.
- Open MaeztroGrant microphone access only if you plan to speak requests. Text uses the same agent route.
- Connect the existing interfaceMaeztro uses your Mac’s current audio/MIDI interfaces; it does not create a proprietary device.
2. Describe the rig in the conversation
Tell Maeztro which instruments, effects, mixer, looper, controllers, and music apps belong to the setup. It reconciles that description with detected ports, separates controllable equipment from acoustic sources, and returns an inline review. Onboarding does not create tracks, route audio, start recording, or otherwise change the Live Set.
If no signed profile exists for a control, guided MIDI Learn listens for the exact port, channel, and CC. It sends no MIDI while learning and cannot silently overwrite an existing mapping.
3. Soundcheck before compiling a Live Pack
- Verify identityConfirm the real device, physical port, channel, clock source, and target parameter.
- Test one bounded actionUse dry-run first, then verify the real response and manual override on the connected rig.
- Compile the Live PackOnly soundchecked profiles, aliases, and rehearsed commands become eligible for Live.
4. Ask for the next studio move
There is no required production sequence in the UI. Safe reversible requests can execute directly; ambiguous, destructive, or capability-dependent requests stop for a typed decision or confirmation. Broader musical requests can become short Studio plans, while the Composition Compiler resolves theory and device limits before anything enters the session.
Local Qwen 3 through Ollama and customer-owned OpenAI are optional planning routes. Known commands stay deterministic, and model output never calls Ableton or MIDI directly.
5. Arm Live and log the jam when needed
Live is an explicitly armed authority, not a workflow tab or final phase. It resolves only precompiled commands in memory and may remain active while a jam is recorded. Your mixer, looper, or recorder remains responsible for audio; Maeztro’s Performance Log keeps musical metadata such as commands, markers, bar position, and state snapshots.
Test the Live Pack offline from providers, confirm physical manual override, and retain a keyboard or pedal emergency stop before a creative session or performance.
6. Prepare source-preserving arrangement versions
After synchronized stems exist as Session clips, Arrangement Assistant can turn exact markers into a draft. It asks when multiple takes exist, refuses mismatched or occupied destinations, and requires explicit confirmation before copying anything.
Version blueprints build on duplicated tracks and roll back all new tracks if a region fails. Original Session clips are never moved, cut, replaced, or deleted.
Ableton compatibility alias
During the beta, the dedicated Control Surface may still appear as MaestroAI in Settings → Link, Tempo & MIDI, with Input and Output set to None. This is Maeztro’s current technical compatibility alias.