Thanks for your reply on this. Here's a few thoughts:t3toooo wrote: many all-around vst's have a specific strength but it is often confusing where it really is and when you found it,often you left out some unnecessary parameters which lead in senseless cpu consumption.
- I can't speak for other developers, but for the algorithms I design I tend to conceal the vast majority of possible parameters, in favor of a few higher level parameters. Both Eos and ValhallaShimmer would have several hundred parameters, if every value that is being adjusted was exposed. So the number of parameters has little to do with the CPU cost.
- The unnecessary parameters that you are talking about would probably be part of how I consider plugin modularity. For the most part, I like to make things as atomic as possible. By this I mean, if a plugin consists of several units that don't really rely on each other, break this up into several plugins. I could make a plugin that has a reverb run through a flanger, but I would rather turn this into a reverb plugin and a flanger plugin. The modularity works better this way. Each plugin should have the parameters it requires, and no more.
- CPU consumption will always be a huge priority for me. A lot of cool effects can be obtained with ValhallaShimmer by cascading multiple instances. This cascading wouldn't be possible without optimization - there is a lot going on inside ValhallaShimmer, and my earlier unoptimized versions of the plugin took up a lot of cycles. I started off developing real-time DSP for a Pentium II, in an environment that valued efficient code.
Sean Costello