Concepts

Explanation of how MyoGestic fits together. Read these once to understand the runtime model; the guides and API reference become much easier afterwards.

If you haven't yet, read Anatomy of an app first - it walks through one complete tiny app in the order you write it and builds the mental model these deep-dive pages assume.

Drill in:

• Architecture - the runtime: sources → streams → context → render / predict / output threads.
• Streams - the ring buffer, get_window vs get_display, channels-first convention.
• Pipeline - extract / train / predict decorators, TrainingData, the predict thread.
• Controls - the control map, the [-1, 1] standard, in-process vs. remote targets, deferred binding.
• Recording - sessions, label tracks, the .session.zip archive layout.
• Widgets - the stateless-function contract, ImGui immediate mode, Grid layout.
• Threading - daemon threads, GIL release, the GPU contention rule.
• Design principles - the eight rules the codebase keeps to.
• Visual language - the type, colour, panel and state-cue tokens every widget uses.