oh, I totally understand where you are coming from …
first I have to say… this idea of using modular differently , I learnt the hard way.
its natural to create what you know… and I did this a LOT, and frankly, I ended up quite disappointed in eurorack generally … as everything I was creating, I could do better on my Virus TI… (and cheaper too!)
… so one day, when I was fed up, I forced myself to sit down and think about the role of modular , what was it supposed to do that was different from everything else? what was its strengths/weaknesses.
and that helped a lot.
but it also made me realise, I need to do this with ALL new gear… figure out its place.
so when I got the SSP, I basically concentrated on finding out what it COULD do, and that would define its role.
(I literally went thru every module, and decided IF/HOW it would be useful !)
and then that as a developer, led me to … “what is missing?” for that role…
so, if you look at the VSTs I have created, they obviously reflect what I felt was ‘missing’ … for ME.
I mean a matrix mixer might not be considered that vital to many users here, but for me switches and matrixes are kind of quintessential modular.
more over, go look at the SWAT algos, and you’ll find things like comparitors !
also whilst creating the VSTs , as there are so many ‘opportunities’ , Ive tried not to overlap with existing SSP modules … so whilst I recognise a Moog ladder filter would be great, its not (so far) had the priority of things which just don’t exist at all.
of course, the other issue is… there are probably as many requests for modules as there are SSP users, each from their point of view is the most important - such is the life of a software developer!
anyway the good news, is after a bit of a break, I’m back into SSP development… so new modules will be on their way.
there was also a bit of a complication for vsts releases… we found there was an issue where each VSTs you had installed on the SSP, consume a lot of memory even if you weren’t using it!
so the more vsts I released the bigger the issue, if users just install them all, which is a natural thing to do!.
but as Bert mentioned in his update post , there is a new update in the works - and this should fix that issue.
we do NOT have a date for that update (its a lot of work) , but Im now more comfortable that it’ll be resolved, so we can ‘workaround’ for now.
anyway, gotta finish off some SSP dev thats for the mid-term… but then reflect on what vsts I want to release next. (one is already done)…
perhaps have a look for some ‘quick wins’ , to do alongside the more ambitious ones I have started, or have planned.