In my case, the development is driven by my own needs. I think that I have already a good set of foundational modules: oscillators, filters, envelopes. I think that I can build most of the ideas I have for patches using a small set of the existing modules (plus a few script using the VCV Prototype).
On top of the foundational modules I have a bunch of “composed” modules. Those modules may have no end; I could keep adding more features, more functionality, more of everything. That’s why I prefer to keep the scope constrained.
@chaircrusher I have some nice analog FM oscillators. I think that it would not be that difficult to model and solve the equations for the mutual feedback. I will play with the oscillators and if I get hooked on the results I may try to model them.
It is important to remember that I spent almost one year developing the VCV Drums. So I may be working on things that may not see the light of day for a long time.
Me and @pyer are working on more modules for the Geodesics Vultiverse. However, the process of refinement there is a bit slow since we do a lot of iterations to do the things as good as possible. Just last week I developed some nice algorithms for one specific purpose that I won’t reveal.
My work on hardware has been stealing a lot of time that I used to dedicate to software. Last month I released the Anima and Feigen ports. Currently I’m preparing to build the next batch of Freak modules.
Lastly, I have my real job at Wolfram. We are preparing a big release that it’s going to include the culmination of a project that I have been developing for the last 3-4 years.
Stressful days…