Getting Started - TheTechnobear/SSP GitHub Wiki

Overview

This page details some information about how to get started with your new SSP :)

Before anything....

Make sure you update your SSP software !

updates are always posted on the forum here

Check for updates there, as this post MAY be out of date!

there are TWO parts to the software

  • the operating system aka 'image'

  • the 'application' you see, which is called SYNTHOR.

  • optionally, you can also install 3rd party plugins

a) latest image

this replaces the entire SD Card with a new OS installation, and is needed before the SYNTHOR install it is a large update - many gigabytes, but happen less frequently.

as of now, it is : here

b) SYNTHOR updates

these are very small, more frequent, and need to be install on the LATEST image (see above)

currently, the above image, also contains the latest version of SYNTHOR.

c) 3rd party plugins you may want to install other plugins, see modules for details. note: it is highly likely thee will only work with last SYNTHOR!


Important Note:

The software is always moving forward, so things change...

therefore, the following videos and resources, may show things slightly different from how you see on the latest version. however, the basic workflow and the knowledge they impart are still very useful, and you will find relevant even if it looks a bit different.

Patching the SSP

(TB : this is bit temporary.. I need to do a better example/video !)

It can be a bit daunting for newcomers how to patch, but it's very quick once you get used to it. as a quick introduction, I'll walkthrough the quick patch I do in my SSP video, which you can find here on you tube.

in my video, Im taking a my hardware RINGS module, and feeding it into the SSP which is running my version of clouds (CLDS. here Im going to walkthough the example...as you will see in video, you can become VERY quick when you get used to the process

note: this walkthrough may seem a bit 'long' , but its not, just detailed with practice, you could do all the following in less than 30 seconds !

the best way to learn is: create this patch on your SSP by following thru with the video slow down video in YouTube, and pause as you do each step. READ the walkthrough below as it has some troubleshooting hints.

( you could use DLY if you dont have CLDS installed.. or just install my modules 😆 )

clear the patch, do it again ...

clear the patch, do it again without watching the video/reading text ;)

seriously, get familiar with this process.. and you'll find patching a LOT of fun on the SSP. and if you don't get familiar enough , and it will just be frustrating

connection example 1

a) add INP I first add the INP module to take input from eurorack

b) add CLDS this is going to be used to process the audio

c) bind (or connect) INP to CLDS Im on INP (slot 1) , so I press Left shift + button 2 (slot 2) note: this is a bi-directional connection order turns blue to show its done

d) take in jack 1 to clouds (CLDS) (send audio/cv) Im on INP module, right display shows all connection possibilities, make possible by bind from step c! so Out1: CLDS: In L

if you don't see any connection possibilities (or the one you want), its because you didn't bind the modules.

e) enable input on clouds.(receive audio/cv) go to CLDS module, on left side, we see all inputs. click on In L to enable it, it will invert the background to show its enabled.

in brackets, you will see number of inbound connection, this should now be 1.

if this is ever zero, its because either you have not connected something, se step d!

important note: you can actually do step d and e, the other way around... as we will see below

connection example 2

now lets continue, with another connection example... lets output sound from CLDS to physical jack (stereo, jack 1/2)

a) add output module OUT I put in module slot 5 (where I number 1-4,5-8 on left side)

b) bind CLDS to OUT Im on CLDS (slot 2), OUT is in slot 5 so Left Shift + button 5 connects you'll notice how the possible connections immediately show up (e.g. Out L : OUT: in 1 etc)

important note.. this list includes all combos of CLDS to OUT and CLDS to INP, remember I said all binds are BI directional.

so...we could have connected OUT to CLDS by being on OUT (slot 5), and then pressing Left shift + button 2 (CLDS!)

c) enable input on OUT (receive audio/cv) select OUT module, on left side, enable in1/in2 by clicking on them

d) connect clouds output to physical jacks (send audio/cv) go to CLDS module, on right side, connect : Out L : OUT 1 Out R : OUT 2

important tip!

in first connection example, I first connected signals (INP to CLDS), THEN enabled input. in second connection example, I enabled inputs THEN connected signals (CLDS to OUT)

you can do either way around.

for beginners... I recommending connect signal first THEN enable input. the reason is... if you don't see the signal listed when you go to connect. you know you have forgotten to bind modules.

but over time, you'll be faster at patching, if you switch between two approaches, as you can minimise moving around the patch ;) but see troubleshooting below... as its easy to start forgetting steps ;)

summary of steps..

for a reminder later.. make sure you watch video with above walkthrough.

a) add modules b) bind two modules together c) enable input on module to receive audio/cv in left panel. d) send (aka connect) audio/cv on right panel

note you can reverse steps c and d!

trouble-shooting - aka it doesn't work, no audio or cv

watch video and read walkthrough again - lol but here's trouble shooting

go to module receiving audio/cv on left side, select (don't click!) the input you are expecting a signal do you see waveform moving? does it have number of connections expect? eg. 1 not 0! if its zero, you either have : not enabled it (click it), or bound modules? or made a connection?

go to module sending audio/cv in right panel do you see connections to module you expect? if not.. then you have not bound the two modules together!

advance trouble-shooting

use the scopes ! if in doubt, always check the scope on the modules receiving audio/cv on the input (left side)

be aware some modules will optimise performance by not creating an output when its not connected, but others will always create a signal on the output.. so this can be a bit 'misleading' if you are not sure.


Videos

Percussa

MATTHS

Matthew Hodson (aka MATTHS ) did a series of 4 livestreams for Percussa on the SSP

note: the titles above are indicative, these were livestreams so covered many topics, and answered questions posed at the time. I'd recommend going through each in turn.

Documentation

Official Percussa Forum

The forum is THE place to get the latest software, latest information and also ask the community questions and seek help.... it holds a wealth of information that you can search.

This WIKI :)

here, we aim to give information about all modules and other tips n' tricks.

Starter Tutorial document by community member "Riggar"

https://forum.percussa.com/t/starter-tutorial-for-percussa-ssp