SynapSeq v4.41.0 #202
ruanklein
announced in
Announcements
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
SynapSeq v4.41.0
SynapSeq v4.41.0 expands how sequences can be created, converted, reviewed, and shared.
This release introduces AI-assisted SPSQ generation with validation and repair, an experimental SBaGen converter, an agent skill suite for creating and auditing sequences, and support for secure self-hosted SynapSeq Remote catalogs.
Highlights
AI-Assisted SPSQ Generation
SynapSeq can now generate a validated
.spsqsequence from a natural-language prompt through an OpenAI-compatible API.When no output path is supplied, SynapSeq creates a descriptive new
.spsqfile in the current directory. Supply an output path to choose the destination, or use-to write SPSQ to standard output:Validation Before Writing
AI output is never written blindly.
Every response is parsed and validated as SPSQ before SynapSeq creates an output file. Invalid responses are returned as errors and existing destination files are never overwritten.
When a model returns invalid SPSQ, SynapSeq automatically sends the validation feedback back to the model and requests a repair, up to two times. Pending requests can be cancelled with
Ctrl+C.For documented English mental-state and profile terms, SynapSeq also validates relevant sound-design constraints such as audible carrier ranges, beat ranges, and profile progression. These checks help keep generated sessions structurally coherent; they do not promise a listener outcome.
OpenAI-Compatible Providers
The AI workflow works with OpenAI and compatible local or remote providers.
The same settings are available for one command through
-ai-model,-ai-base-url,-ai-temperature, and-ai-timeout.Public Go API
AI generation is also available through the public
corepackage:AppContext.AIreturns an already validatedLoadedContext. Library callers provideTemperatureandTimeoutdirectly throughAIOptions, while model and base URL can use the same optional environment defaults as the CLI. The suppliedcontext.Contextcontrols cancellation.Experimental SBaGen Conversion
SynapSeq can now convert classic SBaGen
.sbgsequences into.spsqfiles.synapseq -sbg session.sbg synapseq -sbg session.sbg converted.spsq synapseq -sbg session.sbg - > converted.spsqWhen no destination is given, SynapSeq writes a
.spsqfile beside the source with the same name. Use-to send converted SPSQ to standard output.Public
sbgPackageThe conversion engine is also available as a public Go package for applications that need to import or automate SBaGen migration:
Use
converter.LoadContent(sbgContent)when the SBaGen source is already in memory. The returnedLoadedContextfollows the normal SynapSeq validation and rendering pipeline.SBaGen conversion is experimental. SBaGen and SynapSeq do not share every sound source, transition behavior, or media capability, so complex files can require review or produce conversion errors. Validate generated output before using it:
SPSQ Skills for AI Coding Agents
v4.41.0 ships a focused skill suite for AI coding agents that work with SPSQ files.
create-spsqexplain-spsqreview-spsqInstall the suite with the skills CLI:
The skills have distinct responsibilities. Only
create-spsqcreates complete sequence files, always at a new path.explain-spsqandreview-spsqremain read-only.Examples for Codex:
Custom SynapSeq Remote Catalogs
SynapSeq Remote now supports self-hosted catalogs while keeping the official SynapSeq Remote service as the default.
Sync a custom catalog by passing its root URL:
Custom catalogs serve their index directly at:
Set
SYNAPSEQ_REMOTE_BASE_URLto select that catalog for later Remote commands:Validation and Cache Isolation
Custom Remote URLs must be root HTTP(S) URLs. Paths, credentials, query strings, and fragments are rejected.
Each custom catalog uses an isolated cache directory derived from its host, so it cannot replace or mix with the official Remote cache.
Before caching a custom index, SynapSeq validates its JSON schema, required metadata, IDs, timestamps, durations, and sequence paths. Every downloaded SPSQ file is parsed and validated before it is cached or used by
-download,-get, or-info.This makes it possible to host and share catalogs without weakening the validation guarantees of the normal SynapSeq workflow.
Upgrade Notes
.spsqfiles continue to use the same parser and renderer.This discussion was created from the release SynapSeq v4.41.0.
All reactions