Compatibility

Supported means tested. Everything else stays labeled.

The first beta is deliberately narrow. This matrix will move from pending to verified only after clean-machine and real-rig evidence.

Compatibility evidence is still being collected. No combination below is presented as publicly verified until a signed beta build passes the stated test.

Computer

PlatformStatusBoundary
Apple Silicon MacBeta targetarm64 release path
Intel MacNot supportedNo public v1 promise
WindowsNot supportedOutside first release
Minimum macOSPendingSet after clean-machine QA

MIDI devices

Maeztro is designed for hardware and software that accepts standard MIDI messages. Each mapping names an explicit output port, channel, and message; Maeztro does not assume that two devices expose the same controls.

Hardware MIDI

Synths, drum machines, effects, and controllers can connect over USB MIDI or through a compatible MIDI interface. Device-specific behavior must be tested on the real unit.

Software MIDI

DAWs, plug-ins, and virtual instruments can receive approved messages through macOS MIDI ports when the target exposes MIDI control.

A device enters a Live Pack only after its port, channel, message map, timing, and manual-override behavior are confirmed on the real rig. “Any MIDI device” means a compatible target can be mapped through standard MIDI—not that Maeztro automatically knows every manufacturer’s private protocol.

Profile catalog boundary

Data-only profiles currently exist for selected LiveTrak, Loopy Pro, Roland, Korg, and Moog workflows. A catalog entry is not hardware proof: every new rig begins in soundcheck required, unknown controls use local guided MIDI Learn, and unsigned or review-required mappings cannot execute.

Music software

Ableton Live is the deepest integration in the first beta. Maeztro installs an independent Control Surface for session-aware inspection and guarded tools. Live Mode may run during a Recording / Jam session; it is the real-time control authority within the wider workflow, not the workflow itself. The exact supported Live versions and editions remain pending clean-machine validation.

Other DAWs and music apps use their existing MIDI-learn or mapping systems. Dedicated integrations will be listed separately as they are verified.

What each status means

  • Verified: passed the documented clean-machine or real-rig check.
  • Beta target: implementation exists, but public compatibility evidence is incomplete.
  • Pending: no claim is made yet.
  • Not supported: outside the public v1 contract.