Sequoia Circle2 Beta

Thank you for raising this — it’s a valid concern and we appreciate you reaching out.

For context: we’ve been actively maintaining Circle since its original release on CD-ROM back in 2008. That’s over 15 years of continuous support across many operating system changes, evolving plugin formats, and CPU architecture shifts. Very few music software products have that kind of lifespan.

That said, Circle is built on a much older codebase than our newer instruments. As things evolve, keeping that legacy architecture fully up to date does become increasingly complex over time. This means updates for Circle will unfortunately move more slowly — not because it’s abandoned, but because maintaining compatibility now requires more work and time than it did years ago.

We always build with long-term support in mind and we’re grateful to have so many longtime customers, some of whom still have their original Circle CD-ROMs.

Thanks for taking the time to explain this. The extra context is genuinely helpful.

If I can offer a small suggestion, a bit more transparency would really help the community. Even light communication about update cadence, known issues, or your general direction would make users feel more reassured and involved. It does not need to be a detailed roadmap, just enough to avoid feeling left in the dark. Other long-running plugins like Omnisphere or Sylenth1, which are around between 16 and 20 years, have similar challenges, but keeping users informed makes a big difference.

I appreciate the work you have put into Circle over the years, and I hope this kind of dialogue continues.

1 Like