TheTechnobear's SSP/XMX development

k, early access for CLKD and LOGI for ko-fi supports :slight_smile:

see TheTechnobear : Release Announcements (no comments) - #3 by thetechnobear

CLKD , this is something I really have missed on the SSP , a way to have a central clock that was quick an easy to use, and also provided clock divider/multiplier functionality - its really a staple of modular patches.
with 8 outputs usually its enough on its own, but of course you can have more than one, and chain them.
it also has a mode where it can work with wonky clocks (for divisions)

LOGI, is a natural companion for CLKD ! CLKD + LOGI is an easy way to create rhythms.
but of course, Id highly recommend thinking out of the box here… combining other gates signal e.g. from a sequencer or midi, or even a sample and hold (SHQ) yields some pretty dynamic results.

have fun with these, see where you can take them :slight_smile:

3 Likes

Hi @thetechnobear, first of all, thanks for your awesome modules - they really make the SSP shine.

I have a suggestion regarding the new CLKD module. I’m using a Doepfer A 160-2 Clock Divider in my rack a lot. Besides the usual clock divisions (2,4,8,16,32 etc) it lets you dial in prime numbers (2,3,5,7,11 etc), which to my ears makes a lot of sense musically.

I couldn’t find a way to alter the current “power of 2” divisions in CLKD.

Would it be possible to press and turn an encoder to change the division range by 1? So dialing from 16 to 17 to 18 etc? IMHO it would make the module more versatile.

1 Like

for sure, the clock mechanism Ive implemented allows for any kind of division.
so the main issue, is I didn’t want lots of intermediate values that make no real sense for day to day use, hence the approach Ive used.

I’ll think about it though… as I do like using prime numbers for polymeters and polyrhythmic uses.
However, that leads me to think, perhaps, this should not be part of CLKD, rather a EUCLID module which could be driven by CLDK.

I’ve mentioned this before… but I’ll re-state, as its relevant.
when designing modules, its always a balance of flexibility/functionality and complexity.
I try to keep some of the complexity down, and increase flexibility by separating disparate functions into separate modules… this is the true spirit of module (imho)


I think often where we get sidetracked (me included :wink: ) is when we look at Eurorack modules.
something like PNW, has a ton of functions in what is essentially a clock module.
but the only reason this is true, is because its sells more of ONE module, it makes that module more attractive… (and is made possible by using digital tech to create multi functional modules)

if ALM had separated out EUCLID from PNW, they have a few issues.
the Euclid module would be more dev and distribution costs, and would have stiff competition from other modules… it would also not make PNW more ‘attractive’.

this is why Eurorack manufactures add new (kind of related) functionality to existing modules, rather than following the classic module route. this also has started to build an expectation in users of more functions in a single module…

as for doepfer, well the original a 160 did not have this feature, it was a much simpler module, again they are kind of following this trend.

anyway, point being… with virtual module, we do not have to go down this route…
we dont really need multifunctional modules within a multi functional module :wink:

… though, I make quite a few exceptions to this already :wink:

1 Like

Thanks for your insights. I fully understand your design choices. And I still can use my A-160-2, right? :wink:

1 Like

wow, where has time gone… I’ve completely forgotten to do the next release…
(k, its summer, so not really doing so much inside at the moment)

anyway… back in action - just released CLKD/LOGI as public release.

I’m going to put out a new EA release very soon… It will contained COMP/DRUM

I need to create wiki documentation, and also want to rebuild and test on the new SSP release from yesterday… so been busy updating everything here.
Hopefully, it’ll be tommorow, assuming I don’t get distracted by other things.

2 Likes

k, as promised EA release has been done containing DRUM and COMP (see this post

as I said, summer has kind of caught me napping a bit, the next EAP will be in about two weeks (probably last weekend of July) - and will contain, what is probably my favourite new module :slight_smile:

2 Likes

I get an error when I click this link?

Fixed, though it merely linked to my release post :slight_smile:

1 Like

oops, EAP was delayed this weekend…
partly because of time constraints on my side, but also because I wanted to take the opportunity of updating all plugins to use latest juce released (7.0.1) , and of course had to update all the documentation on SSP wiki.

so, now for the good news…

  • it’s all now prepared to go, done docs, built, all looking good.
  • as its been 3 weeks, since last… decided I’ll release 3 modules this time !

those modules will be:

  • CART : cartesian sequencer inspired by Make Noise Rene.
  • SRVB : simple reverb
  • HARM : 16 band harmonic oscillator

as Ive mentioned before, CART is now my favourite SSP module… it took a huge amount of work to create but Im so happy with the result…
I just love it, its equally fantastic as a quick n’ simple easy to use sequencer, or a creative inspiring sequencer… combined with CLKD/LOGI - it just is a beautiful musical journey.

I’ve never had Rene, but whenever, I saw videos on it, I was always … wow, I need this. Make Noise did something very special with it… its no surprise its a ‘classic’ in Eurorack.

so thrilled to have its inspiration on the SSP !

so yeah… its worth the wait :slight_smile:
… when is EAP released? this Friday, so you can have it for the weekend.
its all prepped to go, so I just need to upload and do the ko-fi post etc.

(if somehow I forget, and its not up by this Saturday, feel free ping me to remind me :wink: )

I’ll likely release the final 3 (DLY, LDRF, OMOD) , a couple of weeks after that.
(I’ll try to prepare it, so its ready to go… but hard in this warm summer we are having !)

Hell yeah! Can’t wait to try it out. Can CART be clocked by an external source like an Octatrack ?

Yup :slight_smile:

Use CLKD to take a midi clock into a conventional clock trig into CART.
CLKD is ideal companion, as you can do things like take a different speed clock for X and Y , and imagine what that does for C :slight_smile:

Also CART is completely happy with random ‘ticks’ - can be fun to use one CART for gates , to drive another CART , mix in LOGI ( and snakes) and you have an engine that’s ever changing but totally predictable.

1 Like

Thank you So much! I cannot wait!!!

so CART is a spinoff / re-make/re-model of René 2 ?

it’s inspired by RENE 1 and a bit of RENE 2 :slight_smile:
I wanted the simplicity/ease of use from Rene 1,
but needed a number of things from Rene 2 (but without some of its complexity)

but bare in mind:

a) RENE code base is NOT open source/available.
so ALL code is my own, and my implementation of how I believe RENE works from the manual…
b) I don’t own, and have never used RENE
so its my interpretation of how it works…

given the above, you can see how its my interpretation…
pretty much its how I would LIKE Rene to work, what I think makes it special given what I ‘know’ ( basically read in the manual, seen in videos etc) … if thats true of Rene hardware or not, I cannot say 100%

I also have taken some ‘liberties’ in my interpretation…
with hardware modules like Rene, they have to have a certain level of self contained functionality to justify their price/place… e.g. you cannot expect a user to have 2 Renes , or need/want another module along side it… as it implies more $$$, but this is at the cost of ‘modularity’
with software modules, this is not true - so an exact clone is ideal/needed… as you can use modularity without extra cost.

this is one of the reasons, Ive not done the whole Z layer aspect of Rene 2, frankly, I think on the hardware module its confusing, both in UI and concept - some times simple is better, less is more esp. if you can achieve similar using other modules.

similarly there are UI differences…
Ive implemented scales within CART, rather than just selecting notes on the ‘grid’ as Rene does…
On Rene, MN approach is nice, because not only is it flexible, but the touch pads make it quick.
On the SSP it feels a bit ‘clunky’, and scale selection felt quicker and more natural.

If anything, I see this divergence actually increasing… so its not something I apologise for, nor regret.
e.g. Ive implemented the Rene CV and MOD inputs, just because I wanted (personally) to see how they felt, and how Id used them ‘as designed’.
but reality is, CART could pretty much ditch most of the (confusing) FUN page, and I could just implement every ‘mode’ as separate CV inputs… ie. you wouldn’t not have to choose only 1 CV and 1 MOD mode, but rather could combine them.

this would be much more powerful than Rene… again the different between hardware and software, extra CV = $$ and panel space for Make Noise, but costs ‘nothing’ for the SSP.

similarly, I actually think the way X/Y CLK is used to derive C , is pretty basic on Rene.
(so much so, I confirmed it with Tony @ Make Noise :wink: ) - I originally implemented a much more interesting way… so I may add that, perhaps optionally, as a future update.

so yeah, Rene is inspiration only, from a module Ive always wanted.
at this point in time, I wanted to have it close enough for me to get a feel for it, and not to (imho) lose its feel, and what makes it special … but not slavishly ‘clone’ it.
I dont know if Ive achieved that, but I am happy that CART (as its own thing) is great.

again, Id like to re-iterate, CART took me a LOT of time to code…

Rene is a complex beast, even researching how it works, took time, esp. due to an ‘imperfect’ manual, as I say, I had to reach out to Tony at one point for clarification… as many YouTube videos just ‘gloss’ over workings… as often to USE something, doesn’t require you to know HOW it works.
then from that research, I then had to implement… with so many inputs and interactions between modes etc, this required a lot of work , and inevitably during my testing and using, I had to re-work things when I was not happy with how things ‘combined’.
so yeah, it took many weeks of development over a longer period of time… as Id put in down occasionally, just to get a break, and also ‘fresh eyes’ on the problems and goal.

But Im happy with the result… as I say, I now use it on pretty every SSP patch… not only for traditional sequencing functions, but also for modulation (tip: use glide when using as a sequenced modulator :wink: )

I’ll also say, it gave me a much better appreciation for the work Make Noise have done on Rene, sure some may find it a bit daunting, but its no doubt a classic. definitely worth the 550 euros!

I’ve considered buying one… but ironically, Ive learn that I love the simplicity of Rene 1 over Rene 2, but Rene 2 has some features Id miss… thats why CART is kind of a hybrid of the two.


btw: I should point out, that Rene is not the only cartesian sequencer around… but rather the most well known/classic in Eurorack :wink:

2 Likes

ok, as promised, CART, SRVB and HARM have been released as EAP today.

my plan is to release the final 3 (DLYD, LDRF, OMOD) in 3 weeks time… likely Friday 26th August.
(as Id like to start to do releases on the Friday, in time for the weekend)

likely, I’ll do the public release of everything roughly 4 weeks after that, given other commitments, it’ll probably be first week in October.

as Ive mentioned above, summer is slow for my dev time, as I prefer to get out n’ about in the summer.
so this will nicely ‘clear the decks’ for fresh stuff in autumn/winter.

a nice place to be, so I can review what ideas I have for the SSP, both modules and more generally, and see which I decide to focus on.
that said, I do other dev projects, ideas, and commitments (non-ssp), so will have to come up with a ‘balanced’ plan.

top tip :
actually, as this is all ‘not for profit’ , frankly, I often do what I feel motivated/encouraged about.
I’m not sure about you, but I find motivation/inspiration/enthusiasm/positivity is infectious…
frankly, the move love I see for (e.g.) the SSP, the more active I see the community… the more love I tend to give it :wink:

anyway, I hope you are having a great summer, enjoy the new modules.

Mark aka TheTechnobear.

4 Likes

I just love the modules you have developed. Stellar work. Thank you.

2 Likes

thanks, Im glad you are enjoying… 3 more left to release, which’ll ‘clear the decks’ a bit.

I’ve lots of other ideas for new modules, and improvements for existing modules.
after the summer, I’m going to ‘review’ what projects I want to focus, including what plans I have for the SSP etc.

I have to admit, Im a bit surprised in the lack of feedback on new modules.
are users actually using? where’s the demos/musics? example patches?

as I mentioned before, the effort to create is substantial…
so I want to avoid the whole ‘Pokemon’ concept, of just creating/collecting to make up ‘numbers’

( *) this is partly in jest, but honestly, I did feel this a bit, when I used to have 100s of VSTs, and also in vcvrack, where I similarly had 100s of modules… felt more like I was collecting modules/vsts than actually making music :wink: sometimes limitations are good !

I hear you, and let me be the first to say, each one of these modules (as well as the stock SSP modules) has a purpose or solves a need. The power with all modular is in the interaction of modules, so the more modules we have the more powerful the system becomes.

Speaking for myself, it takes a little extra time to integrate new SSP modules into my workflow. Partly because I am not as fluent in using the machine as I’d like to be, and partly because I am mostly using it for audio sampling and granular processing. (And I have NO idea what the abbreviations for most modules are, so I feel like I’m blindly guessing to try modules.)

The first couple new modules that I have been using are the compressor and the new reverb. They are super useful and will be part of ALL my future patches.

1 Like

lol, just goes to show how we are all different :slight_smile:

I really don’t use COMP that much… I really only created it, as some had asked for a compressor, and I know for their musical taste its important.


thats why I created the wiki, so we have this information to hand for all modules (factory and mine!)

yeah, I get that… again, interesting, different use-cases.
until I was on stand at Superbooth, I didnt realise how many use GRA as the ‘main purpose’.
whereas as for me, its just one small module… perhaps because I tend to use a Qubit Nebulae as my go to granular… and even CLDs covers most of my needs.

for me , I see the SSP as extension of modular, which is more about creative modularity, connecting things in different ways, with lots of modulation…
so things like CART, OMOD are much more exciting to me :slight_smile:
this is also why, things like the matrix mixers were among my first modules to implement (MMX4), for me, they are classic modular techniques… that just can’t be done in ‘traditional’ synths/fx boxes

1 Like

I’ve not had a chance to re-re-flash my card. Hoping to get that done soon. I look forward to using these when I do!

1 Like