here is a short demo of the auduloti oscillator (2 of them). later on the destroyer module comes into play as well (you'll notice the volume change, hehe) all modulation is done via aftertouch. played on my midi ribbon bass. cheap drum sequence is a loop from the daw. no editing or efx on the axoloti output.
Lokki contributions
lokki
#62
lokki/env/scahd
slow (cycling) ahd module.
ok, this is an ahd module that is REALLY slow at maximum settings and still quite slow at minimum settings 
use it for noise sweeps or similar.
controls:
- a = attack time
- d = decay time
- divd = divisor of decay time, so that you can get faster decay times if needed
- cycle = enable/disable cyclemode.
- h = holdtime, in cyclemode this control sets the hold time at maximum before descending again. has no effect if cyclemode is disabled
note that you can freeze the output if you disable cyclemode while the signal decays.
Really Slow ADSR
lokki
#63
lokki/string/concat & lokki/string/concat8
two objects that can concatenate strings, either 4 or 8.
useful in combination with an OLED and @SmashedTransistors object for it. allows to generate menus etc.
lokki
#64
lokki/patch/name
output the name of the current running patch (has to be on sdcard) as a string. supports patchnames up to 13 characters. it is easy to make a version that supports longer names, but currently an OLED object can only hold 11 characters and i wanted to have a small memory footprint for this. let me know if you need bigger versions (if you want to scroll the name for example)
How to read out the patchname from sd/patch
lokki
#65
lokki/modmatrix
a 10 source 22 destination matrix with mod amount for each mod matrix point that is chosen. multiple sources can go to one destination, they add up. supports bipolar and unipolar input and mod-direction can be changed with the bipolar mod-amount dials.
object is too big to fit my screen
Help, connector matrix
Hi @lokki,
maybe it is possible to split it in two sorts of objects.
- the matrix input/output object.
- the link objects
The link objects will have an objref attribute pointing to the matrix object.
This way, it would fit on screen and it would be possible to add as many link object as wanted.
jaffasplaffa
#67
I was also thinking that maybe using the srate outlet trick, where you can "stack" 16 krate signales into one srate outlet, could make it a bit smaller.
Then you would have only a single outlet for the object itself, so it won't be so hight. And then route the srate outlet to a "breakout" object, where the 16 stacked srate signals are send to its own outlets, like outlet[0], outlet[1], etc.
It will use a little but more resources, with the extra srate inlet/outlet, but will fit better on the screen
lokki
#68
hmm thanks for the suggestions @jaffasplaffa and @SmashedTransistors. i used the srate trick in a few other custom objects (not uploaded) but actually i don't mind the "highness" of the object too much, it was just not possible to create a screenshot that shows all controls