Ksoloti Core

[trimardius]

As for patches, the Patcher itself comes with demo, tutorial and help patches which are comparable to the Pure Data tutorial patches.

The Patcher software comes with lots of user contributed patches (synced with GitHub). That is if this still works. I am not at my computer atm.

[Sebastian]

The Patcher software comes with lots of user contributed patches (synced with GitHub). That is if this still works. I am not at my computer atm.

You're right, I forgot about the contrib library menu thing! Aren't there some great MPE patches in there?

Just as a test I searched through the github forum backup and downloaded a few random .axp patches. Sure enough some had subparches or custom objects missing but usually those were included in the forum posts so I searched and downloaded those too, and then the patches worked without issues.

Tl;dr: If you need to find an old patch or just want to browse some patches others shared on the old forum, it isn't too hard to get them working.

[trimardius]

The Patcher software comes with lots of user contributed patches (synced with GitHub). That is if this still works. I am not at my computer atm.

You're right, I forgot about the contrib library menu thing! Aren't there some great MPE patches in there?

Tl;dr: If you need to find an old patch or just want to browse some patches others shared on the old forum, it isn't too hard to get them working.

I just checked: 1642 (!) patches. Some of them really great! For me those patches gave a me really quick start when I was first exploring Axo.
I guess these will keep working in the future?

[Sebastian]

I just checked: 1642 (!) patches. Some of them really great! For me those patches gave a me really quick start when I was first exploring Axo.
I guess these will keep working in the future?

The hardware is identical where it counts so if they work on an Axoloti board they should work on Ksoloti.

[ersatzplanet]

I am also a long time owner of an Axoloti PCB. It has basically been unused since the first week of playing with it years ago when I bought it. Had many plans to make a Eurorack module, designed faceplates and everything. Then the Akso came out but I delayed my buying of one of those until the plague and associated parts hassles brought them to a standstill too. Glad to see someone pick up the gauntlet. You have peaked my interest again. I would love for there to be a commercial product, I don't have much energy for extensive DIY projects anymore.

[poetaster]

I just checked: 1642 (!) patches. Some of them really great! For me those patches gave a me really quick start when I was first exploring Axo.
I guess these will keep working in the future?

The hardware is identical where it counts so if they work on an Axoloti board they should work on Ksoloti.

Just to say I've caught up I've tested a number of my patches which, with minor gpio adjustments, 'just worked'. A number of those use external patches from the library and some are compiled C. I'll try to finish the one hat that's 1/2 finished to report more.

[hitachii]

It used to be super cool when people would drop a bunch of modules at once. Some people were very active contributors. I almost want to seek them out and link them to this thread cuz I know I've seen them elsewhere online.

[tassie tiger]

... interested to know if there is an existing hosted library that one can download/upload patches from/into? Maybe this is buried in the aforementioned 'backup' forum and I haven't found it yet, or I have to search via the likes of github for individual patches, or something else ...
J

Many thanks for the information peeps have provided on this aspect. It gives me and, hopefully, other new #oloti users the confidence to get on the bus.

[SourShoes]

This is amazing news and I'll be there day one buying whatever you got going on. I was a big supporter of the Axoloti and Akso boards, I have 2 of each! I would spend hours making huge patches, then make midi templates on my ipad with the MIdiDesigner app to program them as standalone devices away from the patcher. I loved how it sounded and the community modules are essential to use the full power these things have. The user SSS alone had made dozens and dozens of esoteric modules of all sorts. Their grainy loopers and delays are the best. So its good to hear that'll all still be there! I'm pretty good with pushing these devices to the limits if you need anymore beta testers, ha! I had so much promise for the Akso board but the lack of din midi outlets, and the i/o just being so damn close to each other made it not really able to integrate into my setup. Can't remember the specifics of it just now, but there was something that prevented me from using the Akso purely stand alone like the original axo with my ipad templates. The increase in power and memory was a huge boon to the complexity of my patches though. So, very much looking forward to this release! Any idea how far away you are from putting it out there?

[Sebastian]

I would love for there to be a commercial product, I don't have much energy for extensive DIY projects anymore.

Glad you like it! I just aim to make the platform available again and also make it more accessible with ready-made "frontends", probably in kit form (PCB SMD assembled), where users solder headers, pots and jacks themselves.

I've tested a number of my patches which, with minor gpio adjustments, 'just worked'. A number of those use external patches from the library and some are compiled C.

Thanks poetaster, still amazed how stable it is despite the code spreading between Java, C, C++ and assembly.

The user SSS alone had made dozens and dozens of esoteric modules of all sorts.

That is probably SirSickSik who was very prolific in sharing his contrib objects. I have heard some amazing reverbs there. With some of his demos it is hard to believe it is just one Axoloti board, like this one: https://soundcloud.com/sirsicksik/axolo ... mic-breaks.

Can't remember the specifics of it just now, but there was something that prevented me from using the Akso purely stand alone like the original axo with my ipad templates.

I believe there was a MIDI bug and other instabilities in the Akso firmware/ Akso patcher because it was based on beta version 2.0. Axoloti and Ksoloti run stable on version 1.0.12.

[poetaster]

I just got the one component board and io finished and thought about new library objects for IO (since I had to remap). Then I thought, hmm, well, publishing those won't help anyone since they're an old revision. As it is, the boards I have are 'backups'. My original axolotis work fine, but I've been using them regularly (at least once a week) for years, so, better safe than sorry

Soooo, if the pin assignments are stable, I'd like to get a newer revision so I can start pushing patches and externals to a repo. I'd also love a gill/s board if / when that's available. a DM?

Otherwise, I thought about asking technobear at https://community.polyexpression.com if we could arrange to get stewardship of the github repos transferred. Then one could re-activate syncing in the patcher.

[Sebastian]

I just got the one component board and io finished and thought about new library objects for IO (since I had to remap).

Have you added the Ksoloti objects to the patcher?
BTW there is a first simple install guide at https://ksoloti.github.io/.

Soooo, if the pin assignments are stable, I'd like to get a newer revision so I can start pushing patches and externals to a repo. I'd also love a gill/s board if / when that's available. a DM?

Sure, I'll let you know when!

Otherwise, I thought about asking technobear at https://community.polyexpression.com if we could arrange to get stewardship of the github repos transferred. Then one could re-activate syncing in the patcher.

That would be really cool but would there be an advantage in creating a separate repo for "ksoloti-contrib" (to avoid incompatibility when you're using an Axoloti board)?

[NastyFuego27]

Very much looking forward to the development of the hardware and possibly of the patcher. I have 3 Axoloti's, ready to be taken from under the dust.

[adnauseam]

I'm really excited to get my hands on a couple of Euro module versions.

I'd really be interested to know if there's a way to link two modules for passing MIDI. Can you say "polyphonic monster synth"?

Imagine having a multi timbral, midi controllable bank of these!

[mrseanoconnell]

super keen to play with this new board when it is ready, and happy to send cash forward for development and a couple of boards whenever it is needed…. truly appreciate the crazy work involved - thanks for reviving the amazing axo ecology….

[windspirit]

fwiw I think this is a great project and will probably pick one up when they are available. I hope that helps with your market research.

[Paranormal Patroler]

Just jumping in to say that I have been following the thread over at Lines and already have a Ksoloti board at home. Glad to see the discussion continue here, and following with interest for its future.

[hyena]

yah, it was working in the v2 beta, but that thing was hellishly bug infested... it was really nice tho to be able to patch live, even if my first use case is standalone. anyway, really glad this project is alive! i'd like to pair my original axoloti with one of these!

[tIB]

...it was really nice tho to be able to patch live...

This! Any word on whether that could be an option for the future or is this a hardware project relating to the already stable v1 software?

[Sebastian]

I'm really excited to get my hands on a couple of Euro module versions.

Good to know that there is interest at all! This project actually started out as a Eurorack daughterboard, hence the size and header arrangement. It will take some time to get the hardware tight though I am 75% there. But currently focusing on the Core and Gills and how to make the boards available, heh.

link two modules for passing MIDI

You mean for the Eurorack module? You'd have several options I guess:
1. MIDI in and out are available via TRS jacks. Probably the most straightforward way. MIDI output is buffered so I guess you can chain things this way too.
2. MIDI via USB host. Funny thing is that Axolotis can connect to each other (or any other class compliant MIDI host/device) via USB MIDI. But then there is no chaining I suppose.

thanks for reviving the amazing axo ecology….

Thank you too, really ... If it weren't for all the other people out there who never forgot Axoloti I'd probably given up years ago and went to design something less cool haha.

hyena wrote: ↑Fri Oct 06, 2023 1:06 pm
...it was really nice tho to be able to patch live...

This! Any word on whether that could be an option for the future or is this a hardware project relating to the already stable v1 software?

Ah good question. It is all quite far away but the working code was there. Can't make any promises because I am just one guy and not even a professional coder.

Currently working on the SPI link feature for v1.0.12 and almost there.

[poetaster]

I just got the one component board and io finished and thought about new library objects for IO (since I had to remap).

Have you added the Ksoloti objects to the patcher?
BTW there is a first simple install guide at https://ksoloti.github.io/.

Soooo, if the pin assignments are stable, I'd like to get a newer revision so I can start pushing patches and externals to a repo. I'd also love a gill/s board if / when that's available. a DM?

Sure, I'll let you know when!

Otherwise, I thought about asking technobear at https://community.polyexpression.com if we could arrange to get stewardship of the github repos transferred. Then one could re-activate syncing in the patcher.

That would be really cool but would there be an advantage in creating a separate repo for "ksoloti-contrib" (to avoid incompatibility when you're using an Axoloti board)?

Ah, I hadn't seen the Ksoloti objects. Sigh. But are those v0.2 or later? I'll have a look at the page, of course.

Well, as for ksoloti-contrib, I'm not sure it makes that much sense since one can move back and forth. It could be the case that there will be enough drift in the future, that's true. One could also do a straight fork and add a ksoloti-contrib git 'sub-module'. I'll give that a go when I have a minute.

[poetaster]

Ah, of course I have the ksoloti objects! there just (still) called noloti And the mapping I meant is vis. my old wrapper objects, one for the old axo control layout (with a couple of modifications) and one custom one. There I had to make a new version and use the new 'noloti' gpio objects.

EDIT: This is the old axo control object which I had to edit , not such a big deal.


EDIT: AND it all 'just works'

[weasel79]

peng peng peng peng 21 gun salute

[Sebastian]

EDIT: AND it all 'just works'

That's great! Looking at the patch there really isn't anything that needs changing.

So far the only situation where edits are needed is when an object relies on any of pins PC0, PC2, PC3. Those are not available on Ksoloti as they are used by the SDRAM. You can just use some other GPIO on the Ksoloti. For example if your old hardware used any of those three PC* as analog inputs you can use PF6...9 instead.

For future patching it is safe to use the ksoloti/gpio/*** objects because you can't select any wrong pins there.

Are there any OSX users here who used or are using Axoloti? I have never used OSX so I am not sure about compatibility. The old installation guide says

Code: Select all

macOS Catalina is NOT supported at this time.
(we are looking into compatibility issues at this time, and do not have a timeframe on resolving this yet)

Which sounds serious, Catalina itself isn't even maintained yet and seems to be like four versions behind the most current MacOS version!

[trimardius]

EDIT: AND it all 'just works'

Are there any OSX users here who used or are using Axoloti? I have never used OSX so I am not sure about compatibility. The old installation guide says

Code: Select all

macOS Catalina is NOT supported at this time.
(we are looking into compatibility issues at this time, and do not have a timeframe on resolving this yet)

Which sounds serious, Catalina itself isn't even maintained yet and seems to be like four versions behind the most current MacOS version!

I have been using the patcher on MacOS since 2018 without any issue. Currently my Mac is on Sonoma (latest OS) and the patcher is running great.
There was a post on the forum explaining some extra steps for the installation for Catalina and later, but I can't remember the details...