#41

Hello Lines, I’d like to introduce my music box, the Sunbox, built upon the Axoloti pcb board which I created with Jens Borner. It’s home is on Instagram so I hope you can check it out, give it a listen, give some feedback, always appreciated. I’m pretty new to building Axo patches, but when I have time I’m familiarising myself with euclidean, turing, microtonal tunings, tones, space and colours.
~Marcus Skinner

15 Likes
#42

Hi Marcus, Welcome to lines :slight_smile:

Can you share more info and specs about Sunbox? Info about patches and patch storage, when you plan to release? etc

I believe @TheTechnobear uses the Axoloti that maybe will be able to help, there is a thread here Axoloti Core

#43

Thanks for the message Mudlogger, I’ll move across to that thread…
Yeah the Sunbox is build on the Axoloti core, and has a micro SD card for patch storage. I’ll looking at a limited run of the MkII mid to late 2019. With a lot more improvements in design, sounds and with my own patches too, a lot to do.

2 Likes
#44

One of the things I love about Axoloti is how easy it is to develop your patch with immediate feedback, starting off from blocks and being able to code your own (C code). While I love the idea of doing your development using the Norns UI, I wonder if this approach would not broaden the appeal of the Norns and derived platforms for many users.

I’d love to hear if this is something that would create additional interest in rpi based platforms and attract more visual patchers that love instant feedback while developing audio ideas.

ps: mods, not sure this is the right category

axoloti-h2so4.png1314×1196

1 Like
#45

I think this fits nicely with the direction it sounds like Norns 3.0 is going to take: Approaching 3.0: universal engine support

#46

I did produce (but not release) a version of the Axoloti UI that targeted Bela, but could as easily target the rPI + Alsa (or Jack) , which would include Norns.

However, Im not really sure its the best approach.
(the reasons for this are discussed on the Axoloti forum about the limits of targeting other hardware)

for visual programming, I think its easier to target Pure Data, which also has the advantage of a larger community useful for those learning, and a huge number of 3rd party externals.

very shortly Im going to release for norns :

  • a ‘Norns’ Pure Data external
    which provides an interface to the Norns hardware, so encoders/buttons/display.
    there will also be a simple mother patch to make it trivial to create PD patches for Norns.
  • Sidekick
    an application that allows users to launch pure data patches and other types of applications.

(the release will also contain Orac, so you could produce PD modules for that too)

combined these will provide a similar experience to the Organelle (*), which I find a really nice way to code your ideas quickly.

(*) for those wanting to do visual programming on the device, as Norns does not have HDMI output - I’ll show how you can install a VNC server, and so do live visual coding using a pc/laptop with norns.

note: this approach differs from the ‘universal engine’ approach of norns in that it does not interface to norns - it basically treats norns as one application, or many that can be started or stopped by the user at any time. (only one application may run at a time).
this approach means that the ‘application’ gains full control over the hardware and will have a very simple API to code too.
the universal engine approach has the advantage that it can leverage the norns software stack.

nether preclude the other, and I think both are valid approaches depending on your needs/experience etc, and so hopefully providing choice will give users different options.

yeah, creating objects with C on axoloti is very cool, a feature I really like too.
that said, creating pure data externals is also very easy, and with a little practice can be a very quick workflow.

9 Likes
#47

I need to get back into axoloti. I’ve started building a pedalboard, and am suddenly drooling over fancy delay pedals which don’t do anything axoloti can’t easily replicate, or at least come close to. And I’ve got several units sitting here. There’s just no excuse for this.

5 Likes
#48

yeah, funny I’ve been seeing lots of you videos on the Zoia , and its tempting, but you can achieve the same thing with things like Axoloti.

for sure the Zoia has the no-computer patching ability which is really neat, very immediate,
but on the flip side things like PD/Axoloti are a lot easier to ‘read’ once they have been created :wink:

2 Likes
#49

This is an Axoloti and it’s awesome:

11 Likes
#50

I caught that demo on the Axoloti’s forum! Incredible work, really captures that signature bongo sound of the Easel. Axoloti seems to have had new life recently. There is work on a suped up version that I have been following with excitement on the forums. It makes a great companion to Norns/Fates

4 Likes
#51

Here is a breakdown from the Axoloti forum of the upcoming changes on the new board.

  • STM32H7 processor clocked at 480Mhz, roughly 3x clock rate increase
  • 32 megabytes of SDRAM, 4x increase over Core
  • Roughly 6x more SRAM available for patch use: 640k vs 100k
  • Configurable IO
  • input 1: right mono balanced or aux stereo
  • input 2: left mono balanced or primary stereo
  • output 1: headphone or right mono balanced
  • output 2: primary stereo or left mono balanced
  • Fully compatible with legacy axoloti patches
  • USB-C for power/data and host
  • Much smaller: only about 60% of the area of Core
  • Comprehensive test points in standard orientation around edges for expansion building
  • Expansion stacking: pcb components are all small enough to fit under the height of a standard header
  • Compatible with the MIDI DIN breakout section of Core (and similar MIDI breakouts)
  • Super secret unannounced features in the areas of alternate dsp engines and eurorack/CV interoperability

Very interesting, that last part in particular. I wonder if they are planning to implement PD or something like that? The dev working on the new Axoloti is also responsible for Zrna. They’ve hinted at merging the two projects, that would be amazing if it goes in that direction.

7 Likes
#52

New Axoloti? Now you have my attention :slight_smile:

I’ve run a bunch of Eurorack stuff off an Axoloti brain. And I never did really take advantage of its marvelous sound qualities: I did everything with MIDI, trigger outputs (at the low voltage the board could natively provide!) and a Nanokontrol with paper overlays for labels. I’ve still got the reference sheets I made specifying what MIDI CC numbers all those banks of knobs referred to.

3 Likes
#53

The Nanokontrol is a really underrated piece of kit in it’s price range! I have one for Axoloti as well, and it has more than enough control for my most complex patches.

2 Likes
#54

That sounds like it might fit behind a 3u panel without modifications?

Edit

They do seem to have that goal in mind.

Looks to be a community project (eg, Johannes is aware of it, but doesn’t seem to be directly involved)

Here’s the thread:

4 Likes
#55

The next-gen axoloti with much more ram is now available. This is awesome news. It’s a bit more expensive but I think it’s worth it.

https://zrna.org/akso/shop

4 Likes
#56

That’s interesting. Is this 100% compatible with the existing Axoloti Patcher?

#57

It appears not: https://forum.zrna.org/t/will-i-need-to-install-a-separate-patcher-app/52

#58

Ah, I see. Maybe this will drive some long-overdue improvements to the Patcher.

1 Like
#59

No DIN MIDI, which is a shame.; but the 3.5mm jacks which can do cv i/o look useful.

2 Likes
#60

Hey @toneburst . Appreciate your interest in my project. I just want to clarify the compatibility question a bit more.

The new hardware is compatible in the sense that the vast majority of existing Axoloti objects and patches work directly without modification. Some objects depend on low level hardware details that are specific to the old F4 processor and have been modified to work on the new H7. There are other aspects of the firmware that have changed as well.

When I say “separate distribution” all that means is a updated version of the old patcher and libraries that targets the new hardware. The intent is for it to be able to run any existing patch or object.

To say it another way: if you have old Axoloti patches lying around, you will in most cases be able to just load them and go in the new version of the patcher.

Also, DIN MIDI is easily done with any standard breakout board. The MIDI section from the original Core board will work.

Ping me if you have other questions.

9 Likes