Axoloti release 1.0.12

#1

I'm uploading release 1.0.12 now, available here.

Important: Backup your patches and objects before upgrading in case of undetected showstoppers, patched saved in 1.0.12 can not be opened in version 1.0.11.
There is no need to update or re-install the runtime if you had installed Axoloti before, it has not been changed since version 1.0.3.

Known Issues:

  • on Linux you need to run
    sudo cp /etc/ssl/certs/java/cacerts /opt/Axoloti/runtime/lib/security/cacerts
    in a terminal to resolve this error Sync (pull) FAILED : factory (1.0.12,anon) org.eclipse.jgit.api.errors.TransportException: https://github.com/axoloti/axoloti-factory.git: cannot open git-upload-pack
    see this post for details.

Changes

  • added detection of stack overflows and unstopped threads that would cause temporary corruption of the board
  • The log screen does not scroll horizontally automatically anymore
  • The log screen stops auto-scolling when scrolled up, scrolling fully down will re-enable auto-scrolling. Error messages (in red) also re-enable auto-scrolling.
  • discard midi data sent to the usb host port when there is no usb-midi device connected
  • initializes patch load index
  • removed the tiny drum sampleset from flash (wave/flashplay), replacement object auto-uploads the same samples to sdcard and then into sdram
  • and more...

Full changelog

Full log of changes ("commits") compared to 1.0.11 can be found here.

#2

Hmm, I see a bunch of Mutable Instrument firmware commits...

#3

You'll find a collection of oscillators in osc/brds/..., and some effects in fx/rngs/, they're adaptations from Mutable Instruments' Braids and Rings code. They're not 1:1 behavioral copies, for instance Braids runs at 96kHz while Axoloti runs them at 48kHz, and Braids bundles combinations of oscillators in "macro oscillators", which makes inefficient use of resources when only one specific oscillator is needed - not a concern when the whole hardware is only supposed to do one thing...
Thanks to Olivier Gillet/Mutable Instruments for publishing his code. To avoid a misleading perception of Axoloti offering the same as the Mutable Instruments modules, the objects refer to the module names but without vowels, hence "brds" etc.

#4

removed the tiny drum sampleset from flash (wave/flashplay), replacement object auto-uploads the same samples to sdcard and then into sdram

...but does this result in patches using the 'tiny drumset' not working without SD-card anymore?
(gotta change some patches,if so)

#5

Do I need to do anything else than just install Axoloti 1.0.12 to my computer to use it? Im asking because i cant build any patches with it and it shows "no Sd card" in axoloti main window:

Pasted image1984x1934 406 KB

The version 1.0.11 works properly

#6

I'm having the same issue that i had with 1.0.11 : the flashing does not come to an end (red led continues blinking indefinitely. I unplugged the board and tried to rescue with zadig, except this time the rescue failed (the winusb driver was installed correctly by zadig, but axoloti could not recognize the board.
I tried to go back to 1.0.11, rescued and everything turned out okay.

Solved: i did the flashing from 1.0.11 in rescue mode (plugged the board holding S1, board -> firmware -> flash (Rescue)

#7

It looks like you have renamed the application to something that contains a space character, could you try replacing that space character with something else, like an underscore or -?
"No SDCard" simply means there is no sdcard inserted in the Axoloti Core.

#8

Okay, with the naming issue you are probably right. I named it 'axoloti 2'. Have to try renaming when i get back to the device. But the sdcard is definitely in the slot. It works properly when i open the 1.0.11. Then i close it nd open 1.0.12 and get 'no sdcard'. Tried rebooting both computer and axoloti but no effect.

#10

I can't reproduce this, anyone else seeing this? Here it shows "SDCard mounted"/"no SDCard" as soon as I insert/eject an sdcard.
Rebooting your computer will not solve anything.

#14

No problem updating here, and thanks for all the great work. I'm loving these new Mutable Instrument modules, great addition for the axoloti platform.
Thanks Johannes and Mark for this delightful surprise !

#15

I track master and have pulled the recent changes and recompiled, but I can't convince the patcher that it's 1.0.12, so it keeps checking out the 1.0.11 library when I start it up no matter what I do. Very frustrating! What's the solution?

#16

[begin developer-talk, people using the installer should not need this]

src/main/java/axoloti.Version.java contains the version info, and is created by build.xml from the git tag.
Launching ant should recreate it.

[end developer-talk]

#17

Yeah, found that, only got it to work after rm'ing all the built classes. Weird.

Development mode app and library version
#18

So err, what's the difference between rngs/reverb and lmnts/reverb? They seem to sound the same.

#19

Their algorithm is slightly different, compare https://github.com/pichenettes/eurorack/blob/master/rings/dsp/fx/reverb.h to https://github.com/pichenettes/eurorack/blob/master/elements/dsp/fx/reverb.h
But I'm not sure how this translates into a difference in sonic space...

#20

Really like the Mutable Instruments objects.

Had to flash my Axoloti in DFU mode. First firmware update somehow crashed, and the LEDs on my board didn't flash when powering up.

#21

yes big up nice stuff , didnt check the fx though

#22

Good stuff @johannes & crew.
Updating went fine but do run into a problem when i try to go live with wrps object, have included a photo.
Since im not coding expert i cant figure it out.

Another thing.. there is quite a lot of white noise when turning up the reverb in clds object.

Other than that great update :slight_smile:

AXO warps problem.png1366x768 57.4 KB

#23

Hey @Kalle :slight_smile:

If you check the help file, it says the the warps object doesnt work at the moment.. Was just trying it myself:

"note: not currently workng CCSRAM issue"

#24

Ahh had not checked out the helpfile, thx.
:slight_smile: but super then its not anything here thats making troubles