The future of Tonic and what you think it should be.

[kallaballa]

I have put a lot of thought about how to revive Tonic and i think all work on future versions should continue in a separate repository. I don't have a figure for how many projects use Tonic as it is, but there are 57 forks. That means to me that many people had to adapt tonic to their needs but it also means that overall what Tonic has to offer is great. Because of that I'd give retaining compatibility with the existing code base the highest priority. My suggestion would be to reject any API breaking changes and new features. We should also try to avoid changes that effect sound synthesis maybe even when the synthesis would be more correct. Security related issue should still be accepted.
I'd like to do something like this:

• Rename Tonic to Tonic1
• Create a project named Tonic2 which initially is a copy of Tonic1
• Initially focus on creating benchmarks and tests for Tonic2 and hunt down problems
• Find out what the users need. Dig through the forks.
• Define goals based on those findings.
• Reevaluate existing issues based on those goals and fix where it makes sense.
• Here be dragons

You are all invited to continue in your respective roles in the new repository. If you want a different role that's alright with me.

I think your input would be very helpful. What do you think?

[hamoid]

Hi @kallaballa ! @thinium and I joined the Tonic audio team with plans to work on C++ based audio synths, but those projects did not go forward and I'm not using C++ at the moment. Your plans described above sound good to me and I wish Tonic a great future! :)

[Dewb]

I don't really have a stake either way, but purely from a GitHub best practices standpoint, if you don't plan on breaking API compatibility or taking the library in a different direction, I think the sensible choice would be to continue working in this repo. Unless there's something making that impossible?

• Find out what the users need. Dig through the forks.
• Define goals based on those findings.

These are excellent steps to take, I would do them first!

[Dewb]

Also, there are 57 forks, but it looks like only 12 contain commits that aren't in master.

[kallaballa]

I think the sensible choice would be to continue working in this repo. Unless there's something making that impossible?

I see your point. Maybe release tag is enough,.

• Find out what the users need. Dig through the forks.
• Define goals based on those findings.

These are excellent steps to take, I would do them first!

Hmmm. You are right!

[oifii]

Hi all,

I am a Tonic Audio user and developer of my own local copy. I love Tonic and would love to have feedbacks, in here, about all the changes of other branches.

I am using (and fixing) Tonic this fall for a polyphonic sampler application I am developing. I am experiencing a small glitch happening on note off (when the note is still sustained right before the midi note off).

I suspect the bug could be because the Tonic Synth voice does not go into release phase after it is triggered to off (when sustaining). But I am not certain just yet. I should know by the end of this fall.

My brother is also a user and developer, he plans on using Tonic along with my Tonic-based audiospi production applications to replace its dependencies on various DAWs he's got simultaneously opened in his real-time live multiple computers environment.

So we should be pretty much active as Tonic Audio users this fall.

We work under Windows 10 and Windows 7 building Tonic with VS2013, VS2017 and VS2019.

[WindowsNT]

I just discovered Tonic and I'm about to use it in my sequencer, so add me to your users :)

[oifii]

Hey Michael Chourdakis, have fun developing with Tonic.

[kallaballa]

I'm not gone. Just overwhelmed with daily life :).
have fun! and if you find issues i'll try to keep up.