Roadmap and Future Direction for SynapSeq

[ruanklein]

🚧 Roadmap and Future Direction for SynapSeq

Since the beginning of SynapSeq, I’ve been focused on refactoring the original codebase, removing legacy pieces from SBaGen while rewriting the entire engine with a cleaner, modern and more maintainable structure.

There were many rewriting attempts (visible in the refactoring/core branch). Like sketching an idea over and over again, I’d often scrap everything and start fresh when complexity took over or the structure didn’t feel right. Each iteration helped clarify what the project truly needed.

Rewriting a software born in the late '90s isn’t trivial. SBaGen was extremely flexible, almost to a fault, with a rich but cryptic syntax and many entangled features. Simplifying it to something more direct, clear and accessible is a challenge of its own.

One key turning point was when I removed the real-time playback engine. This reduced complexity by about 70%. SynapSeq no longer depends on audio drivers or OS-specific integration. Starting from version 2.1.0, SynapSeq became a pure audio generation engine, not a playback tool. Like the classic Unix tools, its philosophy became: do one thing, and do it well.

This minimalist philosophy is what truly sets SynapSeq apart from SBaGen. Fewer options, more focus on what really matters. The syntax has also been revised to reflect that simplicity and purpose-driven usage.

---

🚀 What’s next: SynapSeq 3.0 in Golang

After careful consideration, I’ve decided to rewrite SynapSeq in Go. Here’s why:

✅ Why Go?

• 📜 Text parsing: Ideal for reading .spsq files.
• 🎧 Audio manipulation: WAV I/O is easy using standard libraries.
• 🧮 Math and data structures: Structs and slices replace C’s complex constructs cleanly.
• 🛠️ Portability: No more #ifdef T_WIN32 nightmares.
• 🔋 No dependencies: Truly standalone binary.

✨ Benefits of switching to Go:

• No manual memory management.
• No pointer arithmetic.
• Strong type safety and better error handling.
• Easier to maintain, contribute to, and extend.

⚠️ In this first version, support for MP3 and OGG will be dropped due to lack of official decoding libraries in Go. WAV will be the only supported background format, simplifying build and eliminating external dependencies.

If MP3/OGG support is important to your workflow, you can continue using version 2.x from the Releases tab, which will remain available as the legacy C version.

---

🎯 Purpose and Audience

SynapSeq is evolving into the most efficient and focused brainwave entrainment engine for CLI, APIs, and audio pipelines.

At this moment, the current feature set already covers a wide range of use cases and meets the needs of most users. The focus is on stability, clarity, and portability.

New features may be considered for versions beyond v3.1, but no additional functionality is planned until the core refactor is finalized and fully tested. The project is very much alive, but intentionally focused.

The current stack already includes:

• Brainwave types: binaural, monaural, isochronic
• Noise types: white, pink, brown
• Audio effects: spin (legacy from SBaGen) and pulse (new)
• Custom waveforms: sine, square, triangle, sawtooth
• Minimalist, human-readable syntax

This set of features is powerful enough to serve users creating personalized brainwave sessions, whether for personal use, client work, or part of larger projects.

---

⏳ Development Timeline

The Go version is under development and will take some time to be completed.

SynapSeq is evolving with a long-term vision in mind. This rewrite is being carried out with intention and care, ensuring a stronger and more maintainable foundation for the years ahead.

---

📘 What’s next

• Commit ROADMAP.md with goals and future direction.
• Create CONTRIBUTING.md to guide new contributors.
• Continue migrating the core logic to Go.
• Drop MP3/OGG support and simplify WAV usage.
• Focus on portability, stability and code clarity.

---

💬 Thank You

I’ve been genuinely impressed by how the community has started to interact:

• Some are creating sequences with the new syntax
• Others are submitting pull requests and build improvements
• Many are sharing ideas for future directions

I couldn’t be more grateful. Let’s keep building this together.

Stay tuned!