Quick update… Ive been pretty busy on the dev front on the Percussa SSP.
I’ve now developer 8 plugins for the SSP!
ones already mentioned are :
CLDS - MI Clouds
RNGS- MI Rings
PLTS - MI Plaits
PMIX - a performance mixer with panning, main/out outputs and aux sends
recently I also released:
MSW8 - a matrix switch - kind of like a sequential switch, but you can modulate both input and output destinations.
MMX4 - a stereo matrix mixer with cv control
and today… (as I said been busy)
SHQ - a sample and hold with optional quantiser
SWAT - a multi functional module, that has 17 different ‘algorithms’ , from display functions, delay to comparators.
the idea behind SWAT is a kind of like a dist-ing,
it actually started out as a small test/dev tool which I was using to help dev of SHQ, but realised it could be a nice way to ‘release’ simple functions very quickly with parameter and CV control, but without having to develop a full VST.
anyway… Ive still lots of other exciting ideas for plugins for the SSP.
also, Im planning on releasing some videos on my youtube channel where I hope to cover not only using these new modules but also some general patching techniques that Ive been exploring on the SSP.
on a more general front, referring to some of the comments above…
I think the SSP is fantastic.
if you read muffs etc, then for sure, there is a lot of scepticism around it - which seems to stem from a few users with ‘expectations’ issues, and also some who just did not like Bert’s (percussa owner) attitude/responses - and as often happens on muffs it all got a bit heated/flame etc.
is the UI perfect?
no… there are places it could do with some improvements.
but it’s perfectly usable, Ive been creating many patches for months now, and I’ve had no big issues with it… its also pretty fast to patch.
to give this context, I do a lot of ‘patching from scratch’ , also I think my patching is pretty advanced compared to many (given patches Ive seen, questions asked)
is it complex?
frankly, I don’t think its any more complex that what Ive seen of the ER-301, but like any complex module - you have to get used to using it… you also have to know what each module does.
factory modules / sound - good? ok?
generally most things are fine, there are a few small issues that can catch you out…
in a few places, I think the modules are a bit too focused on ‘flexibility’ rather than usability.
I think this led to disappointment e.g. the LFO module is used at audio rate, but was not really designed to be (its not bandlimited)
However… the SSP has third party DSP support via VST, so PLTs and RNGs sound fantastic thanks to the SSP fantastic hardware.
UI… ok, 4 encoders is always going to be ‘limiting’ , and a bit menu dive-y.
however, the SSP has midi support, so the UI can be extended.
(I’ve some interesting ideas for this - watch this space
)
Compared to ER-301…
well I don’t have an ER-301, but I have looked at it very closely whilst considering purchase.
so listening to demos, reading forum, and looking at the underlying hardware and software very carefully.
ok, this is an inevitable comparison but frankly it’s apples n’ oranges.
the ER-301 software is fantastic, and its a really well executed module - also developer (brian?) has really done well at updating it and adding features - its awesome, and Im not surprised its really successful it deserves to be!
the SSP has tons more potential…
but this potential and flexibility, I think at times means its not as consistent… it’s trying to be so many different things. if you want to be hard on it… you could say its not as focused, slick. (windows vs mac?)
but that’s ignoring the fact its scope is so much more over the ER-301.
sure… if you want a virtual modular that does a 4 voice synth, and fx… perhaps the ER-301 is enough (also half the price?)
but… I needed more, things the ER-301 does not provide
- 16 channel audio interface
- DC coupled outputs (so send CV from SSP to rest of your rack)
- ability to code your own DSP modules ( ER-301 is limited to combining existing modules)
- built in recorder
- MIDI support
- more processing power (*)
- open-ness (**)
(*) the ER-301 uses same chipset as the Bela, which Im very familiar with, and whilst its fine - id say its 20-25% of the SSP chipset, not only single core, but due to a pretty limited FPU.
(**) synthor software is not open, but allows VST plugins, and you can you can also access the SSP hardware directly (even stopping synthor) eg. I recently got Orca running on the SSP 
for an end-user, I do think its a tough call…
as Apple have shown, ‘ease of use’ and polish is very important to end-users, and I think really important for a musical instrument. of course, how much ‘polish’ is needed is down to the individual, their tastes, and also their background/skillsets.
anyway, Im hoping over next few months to continue to help push the SSP forward.
also as mentioned earlier, Im hoping to do some videos that start to show off the SSP, including patching techniques, and exploring what the SSP is really capable of.
I agree, most videos for the SSP are a bit tech focused - and don’t really show it off much
exception being @motoko’s awesome videos 