-
Notifications
You must be signed in to change notification settings - Fork 64
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The future of Tonic and what you think it should be. #282
Comments
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! :) |
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?
These are excellent steps to take, I would do them first! |
Also, there are 57 forks, but it looks like only 12 contain commits that aren't in master. |
I see your point. Maybe release tag is enough,.
Hmmm. You are right! |
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. |
I just discovered Tonic and I'm about to use it in my sequencer, so add me to your users :) |
Hey Michael Chourdakis, have fun developing with Tonic. |
I'm not gone. Just overwhelmed with daily life :). |
Actually I want to make a VST out of tonic for easy GUI. |
Hey, Michael Chourdakis (Window NT), good idea to make a VST with this good old (and beautiful c++) Tonic Audio code. Which source branch are you thinking to use AND which VST version do you want to have (2.4, 3.0, etc)? Finally, do you need the VST GUI to work on Apple macOS, iOS, Linux, and all MS-Windows OS flavors? |
At the moment I 'll make a GUILess VST for my own sequencer to give my users to experiment with it a bit. |
Hi, Michael (Choudakis), Always a great idea to kick out the GUI first. I looked at your WindowsNT GitHub account, it looks awesome! For a start, in case it is of interest to you, I can publish a couple of multi-platform VSTs I have integrated back in 2012 on my OIFII-ORG, DJ-OIFII, and VJ-OIFII GitHub account https://github.com/oifii. These are all based on the ASIO SDK 2 and are either VST 2.3 or 2.4. Here are these old VST projects file names: "D:\spicode\asiosdk2" "D:\spicode\audio_spivstbifurcation" Cheers, Step |
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:
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?
The text was updated successfully, but these errors were encountered: