Documentation

The software suite

Desktop Studio handles native production and recording. Web Studio runs in your browser. MusicScript supplies the language and standalone CLI. Go Meow Server coordinates live session clocks.

Go Meow Toolkit

Install and use gomeow-toolkit for inspection, duplicates, decoded comparison, alignment, experimental fingerprints and source-bound observation reports.

Production manuals

• Web platform manual — create, arrange, save, review, remix and prepare a release.
• Desktop Studio manual — recording, comping, MIDI/MPE, plugins, picture editing and delivery.
• MusicScript language and CLI reference — timing, declarations, calls, capabilities and toolchain workflows.
• libgms integration manual — public entry points, data contracts, host responsibilities and export inventory.

Each manual includes a Markdown download. These describe the documented software baseline; installed build, entitlement and rollout flags determine availability.

Start here

• Build your first beat — a complete, editable score.
• MusicScript language guide — syntax, timing, CLI checks and runtime boundaries.
• MusicScript reference — declaration syntax and examples shared with Studio.
• Go Meow Server and live sessions — server setup, Desktop engine following and scripting hosts.

Keep source and session files together

.gms is composition source. .gmstudio stores DAW arrangement and session state; .gmd is a Studio project format. Audio assets remain separate content that must travel with the project. Plugin state, recording takes and routing do not automatically round-trip through a MusicScript score.

What connects today

Desktop can follow Go Meow Server with one armed playback engine. The server’s browser page supplies a metronome. Web Studio and the standalone MusicScript CLI keep local transport unless a host explicitly integrates the server SDK. Shared transport does not distribute content or synchronize recording files.