Axoloti release 1.0.11

johannes · 2016-08-28 16:46:36 UTC

Release 1.0.11 is now available on https://github.com/axoloti/axoloti/releases

There is no need to update or re-install the runtime, it has not been changed since version 1.0.3.

Most important: backup your patches before upgrading, in case of undetected showstoppers, patched saved in 1.0.11 can not be opened in version 1.0.10

if you want to initially run the new version of Axoloti alongside your existing version, please see this post.

once you have installed, and started using 1.0.11, please could you complete this poll so we can track how many are using each OS version. thanks.

as this is a 'production release' it replaces all previous releases (including test releases, which are no longer supported). please report issues in separate threads, not this 'announcement thread'.
(tagging posts with 1.0.11 is useful)

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.11,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:

Improved object editor workflow, it is no longer required to close/open the editor while a patch is live, changes will propagate when the patch goes un-live.
Undo: a first implementation of undo is made, the downside is that it actually completely reloads the patch, making it a bit slow with big patches.
Improved USB-MIDI host stability.
Firmware flashing and entering sdcard-reader mode failed when a USB device was plugged in the USB host connector.
Improved graphics rendering performance, also solved the high cpu load on Mac
Random number generation is improved, making use of the on-chip true random number generator. For speed, it is not purely using the true random number generator, but I think it will be hard to detect patterns unless you're specifically looking.
When Axoloti Core is running a patch from flash memory, sdcard startup, or patch bank, the main screen will show which one is actually running. Pressing "connect" will no longer stop a running patch.

Did NOT make it into this release:

Zoom: the approach taken couldn't get stable
Linking: some experimental development is done towards interconnecting Axoloti Core's to exchange multichannel digital audio data. I have not given up on the development of this feature, but did not want to delay this release for this feature.
Code documentation using Doxygen: again, I did not want to delay this release
Theme editor - to build your own color scheme for the patch editor

And also that would not be end of ongoing efforts.

Thanks!

Huge thanks to @thetechnobear and @urklang for their significant contributions in the development!
And - while a new release is independent of the contributed object and patch libraries - I also want to express my deep appreciation for the people contributing to those parts. And really also everyone, whether involved on the forum, posting a demo on e.g. Soundcloud, organizing a local workshop, designing add-ons, or - let's not forget - just playing!

Full changelog

Full log of changes ("commits") compared to 1.0.10
https://github.com/axoloti/axoloti/compare/1.0.10...1.0.11

Note:

I'm updating the release notes to summarize discussion below. I've also trimmed the discussion and removed references to the (broken) Theme editor that is now removed from the revised release. Just to keep the discussion relevant for readers. If you have downloaded the 1.0.11 release before 29 Aug 1:30AM CEST, then Theme edit button is still enabled, no need to download and install again as long as you're aware that it does not work properly.

jaffasplaffa · 2016-08-28 16:56:16 UTC

Ahhh. This is looking great

jaffasplaffa · 2016-08-28 17:48:31 UTC

Installed and working on OSX 10.10.5. Tried a few patches using samples, wavetables etc. and everyone of them worked.

Thanks

johannes · 2016-08-28 18:39:58 UTC

If you have installed the windows 1.0.11 release already before 8:30 PM CEST today (Aug 28, 2016), it contained a critical issue: it identified itself as 1.0.10. You can verify you have the right release in menu Help->About... Build Version. The right release tells Build version: 1.0.11-0-g4ffd432
The updated build is now available.

thetechnobear · 2016-08-28 19:54:07 UTC

Note: for contributors to community library

This version no longer requires that you commit changes before the upgrade, it will automatically 'stash' your changes during the upgrade... so you just upgrade without having too worry

Obviously Ive tested it works, but I recommend you backup your changes 'just in case' there are some edge cases Ive not seen during testing.

nwmatt · 2016-08-28 22:36:12 UTC

Hi,
I updated to 1.0.11 this afternoon. It seems to work but I did a sync libraries and got this output. Can anyone tell me what I might be doing wrong?

~~~~~~~~~~~~~~~~~~~~~~~~~
Axoloti version : 1.0.11-0-g4ffd432 build time : 28/08/2016 16:23:58 UTC
Link to firmware CRC 50A29AA2
Status: factory (1.0.11,anon) : OK ( 1.0.11,clean )
Status : home : OK
Status: community (1.0.11,anon) : OK ( 1.0.11,clean )
USB device found
connected
Authentic Axoloti Core
search path : /home/matt/axoloti/axoloti-factory/objects
Firmware version: 1.0.0.1, crc=0x50A29AA2, entrypoint=0x20011000
search path : /home/matt/axoloti/objects
search path : /home/matt/axoloti/axoloti-contrib/objects
finished loading objects
Sync (pull) FAILED : factory (1.0.11,anon)
org.eclipse.jgit.api.errors.TransportException: https://github.com/axoloti/axoloti-factory.git: cannot open git-upload-pack
org.eclipse.jgit.api.errors.TransportException: https://github.com/axoloti/axoloti-factory.git: cannot open git-upload-pack
at org.eclipse.jgit.api.FetchCommand.call(FetchCommand.java:134)
at org.eclipse.jgit.api.PullCommand.call(PullCommand.java:267)
at axoloti.utils.AxoGitLibrary.pull(AxoGitLibrary.java:331)
at axoloti.utils.AxoGitLibrary.sync(AxoGitLibrary.java:70)
...

johannes · 2016-08-28 22:45:46 UTC

I can reproduce that error message if I unplug my network connection, is it possible that your internet connection was down for a moment? Might also be a temporarily outage of github. Could you simply try this again?
Or maybe a firewall blocking the connection? Are you using Windows, Mac, or Linux?

nwmatt · 2016-08-28 22:57:26 UTC

Thanks for the quick response. I get the error when i try again but can ping github.com with no issue. I am using linux (gentoo) and 1.0.10 has been working fine including syncing earlier today. It could be that there is a permissions issue perhaps. Initially I had issues installing but managed to get 1.0.10 installed a while back with everything working, it could be that i forgot a step. I didn't update the runtime.

thetechnobear · 2016-08-28 23:28:35 UTC

was this the first time you ran 1.0.11? there should have been something in the console about it upgrading from 1.0.10 to 1.011...
whereas the above console looks like this has already been done?! so looks like the second run.

if its not a network issue, then yes, permission issue seems likely.

what you can do to resolve, is go to file->preferences->reset all , which will delete the factory and contrib library, and re-download them.

(I just tested the mac OS X release here, and that upgrade the libraries as expected)

nwmatt · 2016-08-28 23:51:31 UTC

I had run it and it updated the firmware with no issue. When i got the sync library error, I exited and tried again. I did a reset all but got the same error and now have no libraries.. I am not sure exactly what to do.. will experiment a little after dinner.

lokki · 2016-08-29 12:33:16 UTC

i get exactly the same error, linuxmint 18, worked perfectly fine with 1.0.10 here is the log:

Sync (pull) FAILED : factory (1.0.11,anon)
org.eclipse.jgit.api.errors.TransportException: https://github.com/axoloti/axoloti-factory.git: cannot open git-upload-pack
org.eclipse.jgit.api.errors.TransportException: https://github.com/axoloti/axoloti-factory.git: cannot open git-upload-pack
at org.eclipse.jgit.api.FetchCommand.call(FetchCommand.java:134)
at org.eclipse.jgit.api.PullCommand.call(PullCommand.java:267)
at axoloti.utils.AxoGitLibrary.pull(AxoGitLibrary.java:331)
at axoloti.utils.AxoGitLibrary.sync(AxoGitLibrary.java:70)
at axoloti.menus.FileMenu.jMenuSyncActionPerformed(FileMenu.java:264)
...

search path : /home/lokki/axoloti/axoloti-factory/objects
search path : /home/lokki/axoloti/objects
search path : /home/lokki/axoloti/axoloti-contrib/objects
finished loading objects

lokki · 2016-08-29 12:38:32 UTC

that does not work, it still fails...

johannes · 2016-08-29 12:46:33 UTC

Could you verify you have write permission to /home/lokki/axoloti/ and all folders inside that as well?
Executing axoloti as root may have created this folder with only root access permissions. Axoloti should not be run as root.

lokki · 2016-08-29 12:48:05 UTC

yep, i have write access no problem there,,

i never run axoloti as root...

lokki · 2016-08-29 12:50:39 UTC

what would be the command to run from the console to update factory and contrib at once? maybe i can try directly from the console and see if that works.

thetechnobear · 2016-08-29 13:01:38 UTC

@lokki , Im just downloading the release to check on my linux install...

@nwmatt , what linux distro/version are you using?

lokki · 2016-08-29 13:02:40 UTC

nwmatt uses gentoo as per his post...

thetechnobear · 2016-09-11 11:30:27 UTC

8 posts were split to a new topic: Linux install issue - certificates missing

electronicbattle · 2016-08-29 14:16:09 UTC

(edit - sorry lokki, meant to post it to Technobear or the list in general)

I've the same problem (Linux mint 18 based on Ubuntu 16.04, Mate edition).

Sync (checkout) FAILED : factory (1.0.11,anon)
Current factory library does not match correct version, upgrading master -> 1.0.11
Changes stashed successfully: factory (1.0.11,anon)
upgrade (fetch) FAILED : factory (1.0.11,anon)

My Java info is

$ java -showversion
openjdk version "1.8.0_91"
OpenJDK Runtime Environment (build 1.8.0_91-8u91-b14-3ubuntu1~16.04.1-b14)
OpenJDK 64-Bit Server VM (build 25.91-b14, mixed mode)

Whenever I start Axoloti I'm told I have a user version mismatch and do I want to upgrade? Answering yes or no results in the same behaviour next time I start (I get the same error box and option to upgrade or not).

I saw that ~/axoloti-factory or contribs were empty so I copied old versions in but I still get a long list of Java errors (and numerous things to do with duplicates which is presumably related to this unmanaged lib copying):

Original name: wave/play fn
Duplicate UUID! ~/axoloti/objects/wave/play fn.axo
Path: ~/axoloti/axoloti-factory/objects/wave/play fn.axo

I hope that is of some use to someone!

thetechnobear · 2016-08-29 14:31:55 UTC

you can do the upgrade, but it wont work!

ok for now, to get the libraries, and you are familiar with the command line you can do it manually

$ cd ~/axoloti
$ rm -rf axoloti-contrib axoloti-factory
$ git clone https://github.com/axoloti/axoloti-factory.git 
$ git clone https://github.com/axoloti/axoloti-contrib.git

however, this is not a solution... since as soon as you try to sync the libraries the issue will come back, as the certificate used for authentication is for some reason missing now.

Im still trying to work out why we are even in this position... its not a code change, it something to do with the build, which also has not changed. it seems something has 'changed under out feet' since 1.0.10 (which still works)

personally, Id suggest you go back to 1.0.10 for now, which gives me more time to sort it out.

Im also a bit 'limited' with time today, as I just picked up two 7 week old puppies, so they are taking a bit of my focus/attention