The error isn't really an error, just saying you don't have a auto start patch on the Sdcard
So your fine 
Note: for those upgrading that have a start.bin you will see a similar error saying start.bin is incompatible with firmware i.e. You need to re upload start patch with 1.0.11
The Console changed its font type, i liked it better as it was before.....
is there a way to change font type in prefs ?
The motivation for the console font change is to use a monospaced font.
If it looks especially ugly, which platform (Win, Mac, Linux) are you using?
Is this really a significant issue?
There is currently no way to change the font in preferences currently, only a custom build can.
Please keep the monospaced font, logs/debugs in variable width fonts are evil.
If anyone has issues with this release, can I please ask you consider keeping 1.0.11 installed, so we can work with you on the issue and get console logs etc. you can run your 'old' version alongside , see this post
i have the following issues:
subpatches with parameter on parent sometimes get their names reset to default names, so for example, if i have a dial named "bass gain" that name sometimes gets lost when i work on the subpatch. sometimes as soon as i open the subpatch from the mainpatch, sometimes when i close it.
second issue is that sometimes subpatches are not found anymore, and i get missing objects on the mainpatch. i can then replace the object and just search it again and it creates without problems...
both issues have no pattern that i could determine so far.
Hello
How ought I to get rid of all of these duplicate UUIDs? I have deleted and git cloned the axoloti and "axoloti-factory" directories but I still see many of these:
search path : /home/user/axoloti/objects
Duplicate UUID! /home/user/axoloti/objects/audio/in left.axo
Original name: audio/in left
Path: /home/user/axoloti/axoloti-factory/objects/audio/in left.axo
Duplicate UUID! /home/user/axoloti/objects/audio/in right.axo
Original name: audio/in right
(full list at http://pastebin.com/u96fed0x for a month)
this looks like you have a copy of the factory objects in ~/axoloti/objects/
if you have not developed any objects, then I suggest you delete ~/axoloti/objects....
Perfect - thanks for your help and your patience. I should have spotted that myself. Time for some new spectacles!
I'm getting a problem somewhat similar to Lokki - on my mac (10.11.5), after upgrading to 1.0.11. Similar popup as described above, then:
Axoloti version : 1.0.11-0-gc534986 build time : 28/08/2016 23:11:40 UTC
Link to firmware CRC 50A29AA2
Current user library does not match correct version master -> 1.0.11
Stash (stash) FAILED : community (1.0.11,anon)
org.eclipse.jgit.api.errors.NoHeadException: HEAD required to stash local changes
org.eclipse.jgit.api.errors.NoHeadException: HEAD required to stash local changes
at org.eclipse.jgit.api.StashCreateCommand.getHead(StashCreateCommand.java:225)
at org.eclipse.jgit.api.StashCreateCommand.call(StashCreateCommand.java:242)
at axoloti.utils.AxoGitLibrary.createStash(AxoGitLibrary.java:247)
at axoloti.utils.AxoGitLibrary.upgrade(AxoGitLibrary.java:199)
at axoloti.MainFrame$2.run(MainFrame.java:285)
at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:311)
at java.awt.EventQueue.dispatchEventImpl(EventQueue.java:756)
at java.awt.EventQueue.access$500(EventQueue.java:97)
at java.awt.EventQueue$3.run(EventQueue.java:709)
at java.awt.EventQueue$3.run(EventQueue.java:703)
at java.security.AccessController.doPrivileged(Native Method)
at java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:76)
at java.awt.EventQueue.dispatchEvent(EventQueue.java:726)
at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:201)
at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:116)
at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:105)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:101)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:93)
at java.awt.EventDispatchThread.run(EventDispatchThread.java:82)
Current factory library does not match correct version, upgrading master -> 1.0.11
Stash (stash) FAILED : factory (1.0.11,anon)
org.eclipse.jgit.api.errors.NoHeadException: HEAD required to stash local changes
org.eclipse.jgit.api.errors.NoHeadException: HEAD required to stash local changes
at org.eclipse.jgit.api.StashCreateCommand.getHead(StashCreateCommand.java:225)
at org.eclipse.jgit.api.StashCreateCommand.call(StashCreateCommand.java:242)
at axoloti.utils.AxoGitLibrary.createStash(AxoGitLibrary.java:247)
at axoloti.utils.AxoGitLibrary.upgrade(AxoGitLibrary.java:199)
at axoloti.MainFrame$2.run(MainFrame.java:297)
at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:311)
at java.awt.EventQueue.dispatchEventImpl(EventQueue.java:756)
at java.awt.EventQueue.access$500(EventQueue.java:97)
at java.awt.EventQueue$3.run(EventQueue.java:709)
at java.awt.EventQueue$3.run(EventQueue.java:703)
at java.security.AccessController.doPrivileged(Native Method)
at java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:76)
at java.awt.EventQueue.dispatchEvent(EventQueue.java:726)
at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:201)
at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:116)
at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:105)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:101)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:93)
at java.awt.EventDispatchThread.run(EventDispatchThread.java:82)
Status: factory (1.0.11,anon) : OK ( master,dirty )
Changes for: factory (1.0.11,anon)
untracked: objects/math/half.axo
untracked: objects/disp/ibar 64.axo
(and so forth... the rest of the .axo/.axh/.h files)
Is this also a certificate issue?
I had some issues with the firmware installation, not sure why: when flashing with the new firmware the leds did not stop blinking (i left the board connected for several minutes actually). I had to disconnect the cable and rescue the board with zadig.
The second flash went fine and now i have the correct firmware on the board. No errors were shown. I used the same cable and the same usb port in both occasions.
no its not a certificate issue...
it looks like you were going from 1.0.9?
but also then... you were on the master branch for factory, which is not correct for 1.0.9 either.
what version had you used before?
Im a bit confused why you were not at HEAD.
did you have outstanding changes in the community library?
had you changed any of the factory objects?
were you using a 'developer build version?'
IF so did you follow my instructions about removing sub-modules?
had you done any manual git operations?
can I see the earlier part of the console...
as I say, your setup looks like it was in a inconsistent state, to what I would expect axoloti to put you in....
I will say, I think i can make some changes so the upgrade process will use a bit more 'brute force' if users have an 'inconsistent state'.
(e.g. it looks like you don't have contribution details, so therefore I could have just trashed the community and factory folders, and re-downloaded them)
Just noticed that you can now drag and drop patches as well as subpatches to a patch.
Great 
1.0.11 is a production release.
please report issues in there own separate threads (helpdesk/software as appropriate),
we only used announcement thread for bugs for TEST releases, to avoid confusion with users not using the test release.
its easier for support/discussion to have separate threads rather than one huge thread with every issue.
(Ive moved several posts made here for this reason)
a gentle remind, can users please upgrade to 1.0.11.
(1.07 to 1.010 were test releases with the expectation users would upgrade asap, so we can drop support)
please also complete the poll on this thread to give us a better idea of take up, and also distribution across platforms.
Sincere apologies @thetechnobear for zombifying this thread (as well as not answering your questions in a timely manner). This is a while back but I believe I had snagged a dev build of 1.0.9. I had not changed any factory objects and I did NOT follow the instructions to drop the sub-modules.
So maybe that's where the problem is?
How would I go about a fresh 1.0.11 install then? I seem to get the same message at connect after the upgrade.