TheTechnobear's SSP/XMX development

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

I use at least one of your VST’s in almost every patch. I just don’t record anything I make.
I wouldn’t be put off by not seeing your stuff being used, as far as I can tell very few SSP users are putting out any content at all.

1 Like

Also the Rings, Clouds, and Plaits modules are excellent, and even though I own those modules, I prefer to use them in the SSP. The big mixer is super great, as is Data.

1 Like

cool, great to hear you are using these…

yeah @BENDY , I much prefer CLDS in particular over the clouds module, just because of its modulation requirements… plaits/rings its closer, I enjoy the hardware module - however, its nice to be able to have polyphony on the SSP :slight_smile:


I must admit, I do need to get around to making some content myself around the SSP, probably when it gets cooler.
I do feel that the community has an important role for the SSP, to allow others to really see how it is used… talking feature requests is one thing, but making music is another very different thing.

at Superbooth this year, I learnt that, for many, GRA is a really important part of the SSP… kind of the ‘main thing’ thats used, and they use it almost on its own.
similarly, playback of samples is important…
(e.g. the SSP is used like a GR-1 or an assimilator , albeit being able to switch roles)

this surprised me, as whilst I do like playing with these , they are really not that important to my use-cases - for me, its all about having powerful digital modularity… which can get into some creative spaces.
… so one module is never that important, rather its how it combines.

of course, the thing here is… I suspect there are many different use-cases, given its flexibility… but we really dont see/hear them.
(and we all know its one thing to talk about how we might use something, rather than actually do it :wink: )

anyway, as I say, I should lead by example… and actually contribute some music/content myself !

1 Like

I’m still getting to grips with mine so that might be a good reason why my usage is skewed but I barely use the GRA and SAM modules I use mine more as a Recorder/interface/Utility/effects chain. I actually bought mine as my audio interface had just started constantly giving me trouble and I wanted to upgrade to something of higher quality that would interface with my modular setup the sampler was a huge plus too but for some reason it has never really gelled with me (I find it really awkward to use) so I ended up adding a Assimi8or not long after purchase.
Also like DSPaddict says I use a lot of your modules in every patch PMIX is soo good.

1 Like

SAM takes a bit of getting used to, but I think its actually very good (albeit some quirks)… and a lot easier than using the tiny screen on the Assimi8or :wink:
though again, I think the real strength is when used in combinations with other modules… as that opens up possibilities which are pretty much impossible with other sample players in eurorack (without lots of other modules)

(hmm, reminds me… I really want to have a look at turning off the scrubbing on SAM :wink: )

Yeah I’ve just been sat with the “sampler” module in the SSP since writing that last comment. So maybe I’ll find a way to get it into my workflow.
You’re not wrong about the small screen on the Assimil8or but again I’ve had a Emu sampler from the 90’s as my main workhorse sampler that thing only displays numbers as start and end points for editing so I’m more than happy to work like that. I was so excited about the Sampler in the SSP before it arrived, the high quality screen and all the other possibilities, but like I say it just hasn’t done it for me, for some reason it just seems hard work…I’ll keep chipping away at it though and it still gets used for some basic tasks so not too bad I guess.

Having the option to turn off scrubbing could be helpful :+1:t3:

really, Id question what is hard work about it? select sample , add trig … done :slight_smile:

then again, Im not a great fan of samples … I get too bored of sample management.
and honestly, for audio mangling, I’d just use my Octatrack
(the OT excels just because its solely focused on the task, and mangling audio with hardware interface)

yeah, this is something that grinds me…
I spoke to Bert about it, and it was added due to a user request a long time back.
whilst I can see its a cool ‘effect’, it hinders what you can do with SAM
e.g. Ive got patches that can use a sample as separate slices, but they are not viable, since as you switch slices, you get this tape scrub effect.

again, thats the thing about modules, imho… they shouldn’t be all powerful do everything modules, but rather things that can be combined with other modules to form something bigger.
you get the creativity in modular by combining modules, not some ‘all powerful module’ :slight_smile:
(that kind of leads to the ‘clouds sound’ syndrome… albeit I love clouds)

Haaha yeah kinda back to my point of it being a sample playback module rather than a sampler. I still find it quite painful scrolling through any large numbers on the SSP and although large samples can easily be handled by the SSP I struggle with that and just generally with the UI, scrolling start and end points for samples is still a pain and I still feel like the screen isn’t much help for getting in close. Again maybe I need to dig into it a bit more but it doesn’t fill me with much joy at present using it…just always seems like a battle.

Yep absolute no go for chopping breakbeats too as it scrubs from drum hit to drum hit!

the Assimil8or is by no means comparable with the SAM module
not in the same ballpark of sound quality
not in the feature set
and certainly not in the sample handling area (microseconds vs milliseconds)

the UI is totally different too, albeit the SSP’s generous screen estate, the immediacy and logic is way out - you can tell the Rossum people are into creating samplers for more than 40y

1 Like