Audiotool board archive

1

I have been thinking about the addition of a Modular synth reminiscent of the pulverisateur. My original concept was to add modules within the synth and to connect them with wires like other virtual instruments, which I think could work. A modular synth would have many sound possibilities and could even overshadow both synths. But if it had the same design of the pulverisateur, the user interface would be too crowded. Today I tried to make my own design of this concept so It could fit some extra controls in each module, until I had a eureka moment. It would be even better if the synth modules were separate devices instead of a singular synth, then the UI wouldn't be so crowded and the sound design could be even more flexible, having an IMMENSE range of sounds! It even makes sense for this design since audiotool is designed to have a modular structure. Though, the devices should be able to receive multiple inputs as other modular virtual instruments can, which would require the Splitter and Merger to send more than just audio data. Both of the synths we have now can be recognizable however they are configured, the only way you can change your sound is by adding effects, that's why adding effects in the synth of itself is unnecessary because of audiotool's dedicated effect devices. Having module devices would make full use of the effects between module devices for even more detailed sounds! These devices could even be used for advanced textured sounds, sound effects, or ambiance, and could even grow over the years with new module additions. Additive synthesis like the hisenburg could be achieved by merging customizable waveform modules to make even more complex and diverse sounds that the community has been asking for. The synths we have would not need to be improved any further by adding new features to the community's liking, because separate modules would do just that, and no more synth simulations would need to be added. It might even save cpu speed by only using modules that you need. And lastly, this would make the website less intimidating for new users, making the interface simpler.

2

I'm not sure what Audiotool is capable of because I don't know how it was programmed, but this feature could be game changing. I can share concept designs if the audiotool team thinks this addition could be a possibility, I have plenty of concepts I would like to share, not limited to this one. I am also interested in helping out the team, I think designing a digital audio work station is fascinating and I would like to learn everything I can to help out the team as a hobby. I also have Ideas to help the audiotool workflow by improving it's visuals, design, accessibility, midi capabilities, controls, etc. I am not a very experienced coder, but I would be dedicated to helping out the team on the website I love. I am very passionate about audiotool, and I would work tirelessly to perfect the DAW. An online DAW is a amazing concept that needs to go in the right direction. If audiotool became a public project, it could receive a lot of help so that it could become a professional audio workstation instead of becoming an abandoned indie project in a few years. Maybe the future of audiotool will be finding a way to connect the website to an external program so that it's not limited to what can be accomplished on the internet, but what a personal computer is capable of. The website's limits will be what can and cannot be optimized I figure, so it is also important for me to be aware of these limits. I would appreciate it if the team would let me know what programming language(s) I should start studying or any other requirements I should be familiar with so I can be qualified enough to start working with them, as well as any software I might need. I plan on understanding how the website was programmed too, and using that knowledge to work on new projects or to help with anything that needs to be improved or fixed, and to know what the website is and isn't capable of.