Really useful video - thanks for making it
2 Likes
It’s really great.
Thank you very much!
3 Likes
thanks, there’s more in the works…
I’m currently busy on another (non-ssp) project, but once I’ve completed that (in the next few weeks) , I hope to get some more time to get back to those ssp projects 
4 Likes
I’m always looking forward to your work.
I hope your other projects go well. 
2 Likes
I don’t like to cross-post, but this is important.
I’ve been working on an improvement for encoder feel, to reduce jitter/oversensitive.
for some this is felt slightly, others more severe.
It feels better on MY SSP, but I need it test on many different units to see if it’s beneficial to more users.
you can get more info on this topic.
whilst this is just testing with one VST (CLDS), if it proven beneficial, we can apply this to the CORE code - so it will benefit ALL parts of the SSP usage.
so…
I , more accurately the COMMUNITY, needs YOUR help.
IF, I don’t get enough testing/feedback, I am NOT going to put it in the core code, as I want it to be proven to be beneficial … rather than anecdotal … so it needs testing on as many SSP units as possible (*).
so this is a time, where the community needs to help itself. if everyone sits back, and assumes others will do it, then it is not going to happen - because I need more than one or two for testing… the more the merrier !
frankly, as a small community, its important we all get involved to help push the platform forward.
I’ve done my part… I spent many hour trying different approaches, to get to where I am.
so I hope that you will spend the 10-15 minutes (max), required to help me, help you.
(*) since mechanically, every SSP might react differently.
1 Like
Just confirming the call to action here:
- Update my VST version of CLDS to the latest one you provide.
- Compare the Feel of the encoders with that of other VSTs/modules
How are we defining Feel?
1 Like
Do you have any value jumping issue with your encoder? If you don’t have an issue, it may be difficult to define feels.
@thetechnobear 's CLDS test version is for reducing jitter noise on the encoder and improve controllability.
Action will be,
-
Check encoder’s behavior with normal CLDS provide on this thread.
-
Change CLDS to two types of test version provide on below thread and confirm how value jumping and jitter noise is improved.
1 Like
ok, Ive put up a new version… this will allow users to change the encoder filter characteristics.
so we can see if different users, can find different sweet spots.
in addition, Ive added ability of have multipole filter… between 1 and 4 (0=none) , given us the ability to change the slope of the filter.
these filters act just like an audio filter (imagine the encoders having high frequency ‘noise’ and you want to cut this out, but leave the rest of the signal as clean as possible.
the filter coefficient specified - is basically ‘cutoff’ (albeit expressed differently)
the number of poles, changes the steepness of the response curve, in the same way we have 6db/12db/24db/48db filters.
the general idea is with a steeper slope, then we can increase the cf (cutoff),
but this will only work IF the ‘noise’ is really spread over a narrow distribution.
if NOT then small number of pole (e.g. 1) will likely work best.
2 Likes
quick update, as its been a bit quiet from me on the dev front…
just to say, I’m actively working on some new plugins for the SSP, and some other SSP related things… Im excited to share what Im working on with you, definitely there will be something to hear at Superbooth, may be sooner !
the module Ive been working on over last week or so, Im particularly excited to share… its a major development, and something I many are going to love… its becoming one of my favourites already, and its not quite finished…(nearly though)
after that, Ive got some others, that’ll I think will open yet more doors…
and what I love about modular is… adding one module, is not just about one module’s function, its also about how they interact with other modules, and grow the ecosystem as a whole.
(this is something, Ive also been focusing a little on late)
Ive also some other news to share… so watch this space, and make sure you tune into to Superbooth 
make sure you are subscribed (with the silly bell icon) to my youtube channel, as I’ll likely put a reveal video around that time.
so… don’t fear, there some goodies on the (nearish) horizon…
14 Likes
Great news!! Thank you for all your hard work 
looking forward to what you have in store.
3 Likes
I’m excited for the announcement!
3 Likes
This is super exciting! It’ll be the first new update/things I put on the unit!
2 Likes
with the press release from percussa… the cat is out of the bag!
what have I been up to for the last few months ?!
the big news is, of course, the impending new release of the SSP software.
but some details, and here I want to focus on what this news contains relating to what Ive been doing.
a) new SSP update and my plugins
the update brings with it a new SSP development api.
my first task was to update ALL my plugins to this new api, including changes required,
and testing appropriately.
I also have been involved in updating this api, including update the ssp-sdk examples.
I will release an update to my existing plugins when the synthor beta/udpate is released.
b) new plugins
The other reason, Ive been quiet is Ive been working on alot of new plugins.
I don’t want to spoil the surprise of whats to come here!
Im going to show these off at Superbooth, but indeed there is (currently) 11 new plugins!
… putting that into perspective, I’m almost doubling the number of my pliugs.
I’ve now 25 plugins for the SSP - thats almost as many as factory plugins!
and yes, this has been a LOT of work, weeks and weeks of development.
these have been built on (and so require) the new api, hence why I’ve not been able release anything recently.
as for release of these new plugins after the beta/update is released.
I’m a bit undecided, generally I plan to release them intially under ‘early access’, as Ive done in the past.
I also might release them gradually over time, rather than all in one go.
this would allow me to get feedback and see if user find any issues.
I know users would prefer to just get them all in one go, but this is alot of work, and Im not sure this is the best release strategy for me.
but Im intested to hear you views !
c) collaboration with percusssa
this is also important news for the future.
the simple part is I will be on the Percussa Superbooth stand each day
current plan is I will be manning the stand in the afternoon.
so, if you want to come see the new plugins or just talk about the SSP pop by
however, bigger news is :
SYNTHOR is closed source, but I’ve been granted access. so that I can now contribute to synthor development.
this could be resolving bugs, implementing new features or whatever.
and, as mentioned above, more involvement in the ssp-sdk,
and of course, testing and checking the development release
this has been keeping me pretty busy recently!
HOWEVER, I do want to keep expectations ‘in check’ !
first some context…
my development efforts are ALL voluntary I’m not being paid to produce plugins, nor fix bugs or stuff in synthor. this is all done in MY free time…
… and this time in not insignificant, even a very simple plugin takes hours of work.
chasing bugs can be extremely time consuming, again think (many) hours.
all time , I could spend making music or on my other hobbies (or other projects! )
it is a balancing act… and one Ive not entirely made decisions on.
also, whilst having access to synthor source to help improve it is fantastic news, and being able to discuss things with Bert has been great.
lets be clear, I’m grateful for the opportunity!
however, synthor is ‘closed source’, any efforts I contribute to it are owned by Percussa.
as many know, I’m an advocate for open source dev (and that is never going to change)
normally, I would not contribute to such projects (unlesss I was hired as a consultant - which im not).
so, this is somewhat an exception for me, just because I appreciate the SSP so much, and how big a project it is for a small company (Percussa), I feel we as a community need to ‘do our bit’.
however, it means I need to balance how much effort I spend improving synthor and my continued open source development efforts.
this is why all my new modules will continue to be ‘plugins’, so I can retain ownership.
(also balancing this against all the other open source projects Ive created or am involved in)
so I’ve still yet to make up my mind on what direction I want to take.
but as I said, it is a great opportunity, and Im grateful to Percussa for it.
and Im sure this will all become clearer over time, after discussing with with others, be it at Superbooth or with others here.
again, interested to hear your views on this.
11 Likes
oh… and if you’re at Superbooth, don’t forget to come hang out with me
lots of new things to show, but I can, of course, answer any SSP questions you have - and even show you some tips n’ tricks!
(I’ve written a few interesting demo patches for superbooth)
3 Likes
Fantastic news! I’m very grateful for all of your efforts to expand the functionality of Percussa! The modules you have already released for the current version of the software are very interesting and useful. With many more modules to be released, I think an overhaul of the module selection screen is warranted. At a minimum we should be able to see the full module name. A list filter function would be useful too, so we could select to see only modules that produce sound for example. Again this is only a suggestion. I really appreciate your work to date!
2 Likes
Thank you Mark for your continued efforts on the development, and I look forward to the Beta/Release of the new software as well as your plugins. You have done so much for this community and it is very much appreciated by us all!! If I was able to go to Super Booth, I would totally stop by and say hello and hang out for a while. As far as release of the new plugins, if you feel they are stable for release, I would say just release them all at once (unless you choose not to of course ), of course this is said not knowing how the new software is going to function, so that may influence your decision as well. I also agree with @jcgam that the module selection screen could use a refresh, it is a little clunky, and both of their suggestions would be great to have, sometimes after being away from the SSP for a bit, I look at the module selection screen and forget what the modules are, full names would help a lot. Maybe have module selection on 3/4 of the screen and a small area to display a brief description on the other 1/4, I dunno just thinking out loud here, and of course you, Bert, and the rest of the team make the final decisions Thannk you again for everything you have and will be doing for us all!!
1 Like
This IS brilliant news! A huge thankyou to bert and thetechnobear for the work you’ve put in to achieve this latest update. It’s looks very exciting indeed and hopefully will attract a bunch of new SSP owners – the more the merrier right? Hope Superbooth goes well for you.
My view would be to release a few modules at a time – so we all get a chance to get stuck in, learn about them, and have discussions about them – get them bedded in and then move on to the next batch. I’m sure this would aid things your end in terms managing questions etc. Hey this keeps the excitement up for a wee while as well!
Also support the idea of a ‘filter’ or similar for module selection if at all possible.
Looking forward to Superbooth and to the end of June! 
2 Likes
Toooo bad returning on monday after Superbooth 22 back to Berlin
Will have to relay on postings and YouTube 
1 Like
Yeah, we’ve discussed this too…
I’ve nearly 60 modules on my ssp now, so indeed getting a little tricky to quickly select the one I want.
( even though I know the names well )
1 Like
ELEVEN NEW PLUGINS! I’m stoked!
3 Likes