Announcements
🚀 New SynapSeq website and complete SPSQ documentation
View on GitHubAlong with the redesigned website, I'm happy to finally say something that has taken much longer than it probably should have:
SynapSeq now has complete documentation for the SPSQ language.
👉 https://synapseq.org/docs/spsq/
SPSQ documentation
This is the first time SPSQ has been documented in one complete, structured, and canonical place.
There have been several attempts to organize the documentation over the lifetime of the project: inside the repository, across different Markdown files, on earlier versions of the website, and at one point even inside the CLI itself (argh!).
That made documentation harder to maintain and, more importantly, made it unclear which source should be considered authoritative.
The new SPSQ documentation changes that.
It now covers the language from its basic structure to its more advanced features, including:
- SPSQ syntax and notation
- Options
- Presets, tracks, and timelines
- Binaural, monaural, and isochronic tones
- Noise, ambiance, music, and pure tones
- Effects
- Custom waveforms
- Transitions and trajectory steps
- Preset templates and overrides
- Per-channel amplitude
- SPSC extensions
Each feature includes its syntax, parameter constraints, behavior, and examples where appropriate.
The old SYNTAX.md documentation has been removed from the repository. From now on, the website documentation is the canonical source for the SPSQ language.
The repository will continue to contain GRAMMAR.md as a compact grammar reference, but language documentation itself lives on the website.
A new home for SynapSeq
The new website is also intended to make SynapSeq easier to discover and understand without having to navigate the repository first.
It includes:
- An introduction to SynapSeq and SPSQ
- Practical SPSQ examples
- Installation and getting-started guides
- Complete SPSQ documentation
- Programming documentation for using SynapSeq as a Go library
- AI integration documentation
- The SynapSeq Library for discovering and listening to sequences
- Information about the project, its origins, and community
Visit it here:
What's next?
Documentation will now evolve alongside SPSQ itself. New syntax and language features should be documented on the website as part of their development rather than being scattered across multiple sources.
I also want to continue improving the SynapSeq ecosystem (Remote, CLI, Go Library, etc) and make it easier for the community to share SPSQ sequences in the future.
If you use SynapSeq, this is also a good time to take another look at the documentation. There are quite a few features in SPSQ today, and some of them may be easier to discover now than they were through the old documentation.
0 replies
No replies yet. Join the conversation on GitHub.
Reply on GitHubThis is a static mirror of the SynapSeq GitHub Discussions.