Me again - sorry!.. One of the main reasons I bought the Ksoloti was to take advantage of the increased SDRAM size for live looping. However, the objects that we have currently, understandably, have the old ram limits imposed on them. I tried to unpick some code on the looper_mono_demo patch by RBRT but it was read-only. Is it possible to get in and edit code to take advantage of the increased memory capacity of Ksoloti? Thanks!
1 Like
If it is an .axp, you can do File → Save as… and edit the copy.
If it is an object or subpatch, you can embed it in your patch (right-click → Embed as subpatch/object) and edit that local copy as you like. Knock yourself out!
By the way, there are updated table and delay write objects allowing for bigger numbers at ksoloti/table and ksoloti/delay, respectively.
Did I upload the “enter custom sample number” ones yet? Looks like I didn’t. Those can save you some memory and help achieve precise delay buffer lenghts
1 Like
Genius! I used your new objects to replace the buffer size and it works a treat! Thanks so much. I also just found a discussion about sharing the midi port between AXO and KSO on Mod wiggler so that will help enormously. Thanks again!
1 Like
wait what, we have more Sdram on ksoloti?? this has always been so limiting on my looper. thats incredible news!
btw I’m in contact with Rbrt. He’s been working on some interesting evolutions of his looper blocks.
I’m also working a lot on this myself, so hopefully we can share sth in the next months 
1 Like
Yeah, I saw something about the SDRAM being the same but I think Seb decided to quadruple it. I’ve been using it today and, for a live looper like me, it’s great for recording long motifs. I’ve been using rbrt’s demo looper and just substituted one of Seb’s table allocation objects for the original and it allows me to allocate up to 8m of memory which TBH is plenty, (though it is in mono). Let me know how you get on… BTW did you hook the midi up to 2 Ksolotis after? I’m dithering on it since I don’t want to brick the system…
Yeah Same. I’m alyways anxious to hit the max loop time in a live seting. I also just changed my looper system to stereo. I used ai to rewrite rbrts looper objects. So this bump in looping time is much apreciated.
I know that he is working on a system that allocates the sdram more dynamcally. each loop just takes it’s own sample size in ram. Which would give you even more space.
Currently I have 2 Ksolotis connected through pins A2 and A3, sending midi back and forth with custom objects, that are based on hugos’ xtra midi io patch.
Cool. I’m using a frenkenlotl with an AXo/KSo pairing - trying to get the best of both worlds. I’m gonna try connecting the 5 midi pins, (VBUSEND, TX, RX, 5v and gnd) from the Axo to the Kso and see what happens. I’m a bit confused as to which is the TX and RX since the image I have has some crossing out on it but I figure if it doesn’t work then i’ll swap them over. When that’s working I want to connect some sort of 2 way connection between its analogue ins and outs though I can’t see any analogue inputs on the pins of the Ksoloti so this may not be possible. I"m not terribly technical so all this is a bit over my head…
Midi In = RX
Midi Out TX
If you are confused on axoloti, you can take a multimeter and confirm which pin is ground. from there you can know in which order they are.
I can really recommend pairing 2 ksolotis though. With Spi link you can send audio and control rate signals back and forth.
1 Like
Thanks again. This is useful. So Spi link can’t work on the old Axoloti board then?
no not as of now. The firmware would have to get updated for that.
Ok. Thanks for letting me know. I’ve got plenty to explore with this setup and don’t really have the cash for another Ksoloti right now. MIDI next then…