TheTechnobear's SSP/XMX development

Amazing lineup… sounds like CART is a perfect module for me to get my feet wet in lua, with some sort of a grid based touch and dials interface for on the Electra one…

Will look forward to the drops…

The SSP is becoming better and more complete as a stand alone instrument… so thank you for that…

1 Like

Wow! Amazing list of goodies! The CART sounds exciting.
And (klausfre) linking up with the Electra One would I’m sure make a super interface. Know nothing of lua but would be happy to test (hint hint) in a helpful way. :smiley:

2 Likes

Wow super exciting. Beyond words right now.

How exactly will the roll out for the SDK and the new VSTs go? Tried to find some info I’m not sure if it was posted else where.

Aside from releasing it on your Patreon page, will the sdk and the new VSTs go straight to the forum or the downloads page on the website ?

Edit; also just want to add thetechnobear- thank you for all that you do. I know you’re doing it unpaid and that means a lot. Big thanks.

2 Likes

sdk - is ‘owned’ by percussa, so will be released at same time as new image.

my vsts…
my current plan is (something like)

  • release existing vsts at same time as new image.
    (as the old vsts will not work on new image, Ive had to update to new code)
  • new vsts, I’ll release initially via ko-fi contributors , then will release publicly. (*)
  • I release my source code for a vst when I release the binary image of the vsts. (or shortly after)

(*) public releases will use existing link , and you’ll be able to get via this forum and also the ssp wiki.
contributor releases are done via ko-fi, using posts that are only accessible to those that have contributed in 30 days from that post.

sorry, I dont really have any other means to do it, and need to obviously ‘keep it simple’

as for timing…
not sure when the new ssp image is going to be released (as beta) , its close to ready… idea I believe is sometime in June… (of course, that could be potentially delayed… but that was the ‘date’ given).
there are a couple of issues outstanding.

my releases, as above, existing vsts will come out at same time as this image is released.
my first release to ko-fi contributors will also be at that same time
(or at least within day or two)
obviously, without that new image, you cannot use any of these builds so not point me releasing anything :wink:

2 Likes

Thanks! :slight_smile: I’m literally so excited. Been exploring the other modules I don’t touch as much on the SSP in anticipation.

1 Like

Release Day :slight_smile:

ok, so we now have the wonderful news of the new SSP release

which means I can release the new versions of my plugins that will work with this new release !

This release contains all the plugins Ive previously released updated to the new sdk.
There have been many small bug fixes/improvements to these plugins too.
The issue with ‘plugin midi’ (e.g. learn) has been resolved, so you can now use them without fear :wink:

there are also TWO new modules in this release…

  • MTTR : midi trigger
    allows users to specify 8 midi notes to trigger 8 gates/velocity.
    perfect for using with SAM to trigger samples from an external controller
  • VOST : voltage store
    store and recall voltages, great for ‘preset’ like behaviour within a patch… but has many other uses.
    tip: its also an attenuverter, so also interesting to use to mix audio.
    this is a module, the more creative you get with it , the more you will discover!

go to SSP Wiki for the download link. Ive also updated this wiki for two new modules.

note 1: this plugin release will NOT work with the older SSP release, only the new release linked above

note 2: this release does NOT feature all the new plugins - only the 2 listed above.
as detailed previously, I will release all of these over coming weeks,
likely 2 at a time, first via ko-fi, then publicly… so watch out on ko-fi for those!

the primary aim of this is to let users dig into each new module in a bit of time, to discover what it can be used for… rather than get lots all in one go, and not explore them all. this in turns means I hope to get valuable feedback for all the modules … rather than just the ‘obvious’ ones :wink:

anyway, enjoy the new releases !

6 Likes

What exciting news, Beta release and 2 new plugins. Downloading both now.

Great idea and thanks again for all the wonderful work you’re doing. I started to go through some Juce tutorials last week and you’ve been a big inspiration for me to look into that, so thanks for that too :+1:

1 Like

Thanks again for all your efforts on these rejigs and new plugins! I’ve got it all installed and am enjoying it very much so far.

I was playing around with the new module VOST and my patch was simple to test it out

DCG>VOST in A and activate VOST in/out A > DATA in A and activate A in DATA

I get the changes I make on the DCG indicated on the mini scope going into the VOST but it does not sample and hold or store the voltage in the out part… out remains 0v…

Where am I making a mistake?

Maybe I misunderstand something… very likely… non the less I totally see the potential as a very very powerful module if I get its purpose right…

Could it be integrated with fore example plaits and rings or any other of your midi controllable vst’s, by allowing some internal MIDI communication? Mostly to get the midi feed back like we get when connecting an external midi controller… but inside the ssp… a MAC midi (MAMI) if you like… internal midi controller like the Electra one… I’m not sure how much work this would be or if at all possible…

In all cases… The VOST opens up possibilities that is making my head spin… so very good idea not releasing all your new creations at once…

Again thanks for all your work…

yeah, VOST doesn’t work like that … perhaps the wiki description is not clear ?
(its not a sample and hold module … you can use SHQ4 for that :slight_smile: )

to use VOST you do not need any DCG…
you store the voltage within VOST, if use use pg+/- , you will see 10 pages of 16 voltages, that you can set… which page is used, is changed by select (param or cv)

the inputs are used for something different :slight_smile:
these turn VOST into kind an (16) attenuverter, e.g. OUT 1 = IN 1 * VOLT 1,
but of course, you can still use select to change those ‘volt N’ between the pages.

midi - sorry, second part of your question…
yes, ALL my plugins support midi learn for all parameters (*) using my MIDI page, accessed via both shift buttons (RS/LS)

press LS+RS, activate learn, press LS+RS (to return to ui)
twiddle parameter, twiddle midi knob (cc only currently) repeat as many times as you want.
press LS+RS… de-activate learn, press LS+RS (to return to ui)

note: with VOST , volt/page combo is different , so page 1 / volt 1, is different to page 2 / volt 1
so you could learn these individually… though that 160 (potential different cc’s :wink: )

if you just want a simple midi controlled attenuverter or one page of voltages… you can use ATTN.

(*) there are a couple of which are not ‘parameters’ eg which page you are looking at.

btw, for those wanting to see some of this functionality or have questions.
… things like midi learn are shown in my video on the SSP
link here to my channel

also there is going to be a livestream on YouTube with MATTHS next Monday
Monday 6th June , 7pm (CET) , 6pm (BST) , 5pm (UTC)

we’ll be posting an official announcement of this, once we have the YouTube link!
but book it in your diary now :slight_smile:

if we don’t get around to answering all questions then (time limits detail we can go into) , then if people are still hungry and interested - I could do my own livestream after that one.

EDIT: ah, link is good now

Ahh… I get it now… brilliant…

I see you have color coded the 10 pages,a suggestion; maybe add the page number also in future update…

So page 0 is basically off!”?.. page one to 10 controlled by page selector…

I get fractions of 0,25 turning the knobs… and having to press and hold them down to get increment’s of 0,01 is there a way to reverse this?

It’s basically an cv Electra one supercharged… without labels…amazing… and of course much more… such as presets ect…

Just wow…

The wiki is not super clear… I will dive deeper and suggest an update once I have explored a bit more…

1 Like

pages - yeah, I perhaps should introduce a page title when my plugins use multiple pages.

sorry, I wont change that… as its the same in all my plugins(encoder = coarse, push encoder = fine)
and I find user interface consistency, super important.

sure, I can see in some plugins, it might be slightly better the other way around, but if you consider something like where I use it for pitch, its be terrible to have this flipped (imho)
anyway, even here it really depends what you are doing… often coarse is still the preferred option.

not really, I’d personally say, using a voltage store as ‘preset voltages’ is just one small use-case.
however, its probably the easiest one to explain :laughing:

off-topic: Ive now created a new announcement thread (without comments) here for my release announcements.

this way users can comment here on this topic about releases and yet users not visiting less frequently can still quickly find the release info.
hopefully, this’ll also encourage more feedback in this topic, which is the important bit too.

1 Like

Ok, I understand about consistency when it comes to the encoders. thanks…

I guess I got excited as I find the SSP missing a good module where I can perform and controls several perimeters on different modules on one page and the MAC is limited to 8 and is away from the preset page…

Thanks again…

page 0, is not ‘off’ , rather its the ‘global page’ , used for settings that refer to ALL banks of presets.
currently, this is only SELECT… but I could add others here.

btw: I may change this to 16 banks (aka pages), so 16 x 16… as Ive seen a few instances where 16 (or 8) makes more sense.

indeed, VOST can be used for this… it was one of the things I use it for.

as I said, if you want to simply map 16 values to the electra one controls, then use the electra one snapshots to change these values, then this is simpler to do with ATTN.
this was the reason I created ATTN… to allow users to map CC->CV quickly!

however, many don’t have controllers like the electra one, that can store CC values - so this is why they might prefer to use VOST.

for you, the main advantage of using VOST are :
a) the voltage are stored in the preset… so you don’t have to use the E1 snapshots.
(and I personally like this, as its all together in the preset)

b) you can modulate select
you cannot modulate E1 snapshots!

c) you can morph between voltage banks
again, no morphing between snapshots on E1, and even if it was added it would be lower resolution

d) higher resolution
32 bit resolution on SSP, though UI is 0.01. midi (learn) then maps 7 bit (0…127) to this.
my midi learn is currently 7-bit only
ATTN (and VOST) support (hi-res) slewing, so avoids ‘jumps’ , but still the steps are kind of limited by MIDI resolution.

so personally, what I like to do is store the voltages in VOST (for different values) , and then just map SELECT to a control on the E1.

but of course, the point of modular is its flexible, so different use-cases (and different users) will use things in different ways.

this is where I get confused as with 0.25 increments I get 8 different setting per knob without having to push the dial down, same with ATTN where 4 setting are possible without pushing the dial down and it’s not so useful for live performance ie filters, volume, brightness, damping ect… so as a performance module I don’t see how as it is impossible to hold down the dial and turn it harmonically playing live…

Anyway… much complexity;-) I properly just got fixated at one usage…

Thanks for your suggestion using the e1… I will try that once it’s back from repair…

Thanks

ATTN range is unipolar (0.0 to 1.0), whereas VOST is bipolar (-1.0 to 1.0) , hence full range is twice ATTN. that said, Ive been meaning to change ATTN also over to bipolar, so it’ll then be the same as VOST.

I might make the coarse/normal increment 0.1 on both (and leave fine as 0.01) , as 0.25 is a bit too coarse.

these values are chosen a bit by ‘feel’ …
I obviously do quite a bit of testing, so after a while in my presets, I get an idea of what works… and what feels too much/too little spinning of the encoder.

I will also say, I dont really like to go down to 3 decimal places… as the range just feels too much when using fine values… way to much spinning of the encoder.

what might be nice (eventually) is to do something like the ER-301, where for particular values you can edit them accurately, digit by digit… however, at the moment, I really do not have a consistent spare ‘shortcut’ in many modules to do this…
so, any combo I can think of, would not really work for some modules ( * ) as its already ‘overloaded’.
… and im, again, not willing to sacrifice consistency for such a ‘hack’ :wink:

thats the tricky bit, adding more functionality, without making it more diffcult for ‘non power users’ to use.

( * ) in particular PMIX, uses pretty much every key combo… in particular the ‘obvious’ one which is something with LS or RS and encoder.

It’s your creation and I fully understand that you have spent much time thinking these modules trough…

Would be great to have the resolution a bit less course… I for one would appreciate that :slight_smile:

Also depends on “style” currently I love to express with changing the brightness, position, harmonics and filters and with that also volume simultaneously I record these expressions and then trigger the expressions via the STE g2 while the g1 or S controls the voct via your quantizer… currently I use the MAC, I really like the encoders on the SSP. I use matrix 8’s for management feeding out into a cv looper externally in a droid module that can be triggered via the STE or buttons on the droid. needless to say I would love to be able to do this inside the SSP as I’m using 5 valuable outputs with my current setup… so hopefully the looper or a cv looper will arrive one day…

We all have different needs… ultimately these modules are your creations and I’m super happy your creations the way they are and I understand that are adapted to your needs… as they should be…I will adapt :slight_smile:

Thanks again for your consideration around making your “course” it a bit less course :slight_smile:

And thank you for all your answers… you are such a great help on this forum…

well you could do that with either VOST or ATTN.
of course, if you are using S&H, that’ll interact ‘interestingly’ (= not as you expect?) with slew/morph.

as for cv recording… thats kind of different again, Ive other ideas for that.

you may be able to use DLYD (when I release it :wink: ) for this… as it has a ‘freeze’ option. which basically means the loop stays the same…
however, DLYD goes way beyond simple freeze loop, as you have 4 taps each with feedback.

I need to check its ok with CV, in theory its ok… but I later added some filter options now, so need to check they dont ‘accidentally’ dc block.

anyway, I think cv recording, would be interesting as a separate thing - but we will see.

1 Like