User Guide
A practical overview of the current MIDIBraid workflow. Screens and wording may continue to be refined during pre-release testing.
1. The performance model
MIDIBraid is organised around Session A and Session B. Each Session can operate independently, and both may be used together. Each Session stores sixteen Voice Definitions while presenting up to eight ordinary live positions at a time through Bank 1, Bank 2 or the Palette.
2. Voice Sets
Bank 1 presents Voices 1–8. Bank 2 presents Voices 9–16. Palette presents up to eight selected references drawn from the Session's sixteen configured voices. Switching Voice Set changes new attacks; already-held notes should retain their original ownership until correctly released.
3. Overview and keyboards
The Overview brings the main Session controls together. The Mac keyboards can be played from the screen and may be detached into floating windows where supported. Theme colouring is used to make Session identity and note activity easier to read. Keyboard visuals are presentation only; they do not become the authority for the musical state.
4. Splits and controllers
Use the Session split controls to define the relevant left, main or right playing zone. Session Master transpose is applied before split classification; group or voice transpose follows. Expression, pitch bend and modulation can then be routed according to the configured voice behaviour.
5. Scenes
A Scene is a stored performance configuration. Selecting a Scene is intentionally separate from recalling it: selection is silent, while Recall is the deliberate sound-changing operation. This helps prevent accidental changes while browsing.
During testing, verify Scene Recall with held notes and sustain as well as ordinary playing. Recall should affect the state used for new attacks rather than rewriting the ownership of notes already sounding.
6. Songs and Set Lists
Songs organise Scene recalls, aliases and sections. Set Lists organise Songs in performance order. These library functions are kept outside the real-time MIDI path so browsing and editing do not need to block live routing.
7. MIDI Inspector
The MIDI Inspector provides visibility into MIDI input and output activity. It may be pinned into a floating utility window so you can continue working elsewhere in MIDIBraid while watching the diagnostic stream.
8. MIDIBraid Remote
The iPad companion is a control and presentation surface for the Mac-hosted product. The Mac remains authoritative. Reconnection should restore the Remote display from current Mac state rather than recalling a Scene or changing the sound. iPad keyboards can be shown or hidden to reduce visual distraction.
9. Backups and performance preparation
Keep backups of important performance configurations, and rehearse with the same MIDI controllers, audio host, pedal setup and Remote connection you plan to use live. Pre-release testing should include rapid playing, sustain, Scene changes, reconnects and a realistic rehearsal-length soak.