Publishing

Publishing turns an authored project into a versioned product people can use. Syntho has project revisions, builds, community module pages and content submission workflows. The complete release journey is still being developed and qualified; some beta steps are guided.

Prepare the product

Keep the module declaration, DSP, interface, presets, demo inputs and runtime assets together. Add a clear name, description, artwork, category and usage instructions. Record the rights and attribution for code, recordings, samples, models and other dependencies. Use the current licensing guidance for access and commercial terms.

A good demo explains the musical purpose. Give listeners a useful starting preset and a representative input; do not rely on undocumented processing to make the preview sound finished.

Save, validate, build, review

Save a durable source revision before requesting a release. Validate audio health, control behavior, state/preset restoration and assets. Build only the targets the module and host support, then test the actual artifacts. A browser preview, generated package and verified native plugin are different milestones. See Export and audio consistency.

Web-only projects retain that scope until their runtime is qualified for another target. Available formats and download links should come from the actual release, not a blanket platform promise.

Updates and shared content

Preserve module identity and parameter/state compatibility. Review migrations when parameter meaning, range or asset dependencies change. Shared presets need the correct module/schema and assets to remain useful; version a preset or bank alongside the content it depends on.

Keep released artifacts and their source identity traceable. Review rollback, withdrawal and existing-session behavior before replacing a release. Current availability and support should be stated on its product page.

Continue with Studio workflow, Project structure or the engine.