SynthMakerTomC ·
Howdy folks, I'm now using SynthMaker seriously for one month, so I feel educated enough to write my findings concerning code modules in general and 2 severe functional limitations:
• Add a FLOAT code module:
• I've implemented a XOR for integers and all those > 100 connections could be replaced by one line of code • Loops are a must. I've implemented a one-way hash algorithm (for copy protection and stuff) and it's very weak because float/integer elements won't let me loop.
• Existing code module:
• Dynamic loops: loop (index) {...} • Dynamic arrays: float myArray[size]; • Floats, Arrays and Mem as input: floatin myFloat; arrayin myArray[size]; memin mybuffer[size];
• Wireless connectors: I never got why they only work downwards. Wireless goes in all directions, so add upward/same level wireless connectors (maybe with selectable direction (up/down/same/all levels)). That would simplify the schematics a lot. • Convolution. If you have a closer look over the professional VST/VSTi world 2007 it's THE way effects work these days. Of course I could implement convolution with the extensions I mentioned above, but that'll be on the more slower side to put it nicely. Offer convolutions modules (stream input, IR sample input) and do your FFT/iFFT stuff in highly optimised assembler/C++ code, there are enough reference implementations available. The Reaktor-users alone will make you rich and famous! Big market!
The changes mentioned above are essential for efficient plug-in development. Right now I feel limited by the tool I use, and it should be the other way around.
If I have some more time I'll post my 'nice-to-have' list as well, but that'll be lengthy 😉
Tom