This guide is intended to help users troubleshoot problems with Axoloti hardware and software, this is an attempt to collect together common issues that we have seen since Axoloti has been released.
I hope that the community can extend this guide with relevant links to thread for common issues.
Note: It is intended to cover patching
important note: this is a wiki post so regular users can edit/update it, e.g. to link to other relevant topics.
please keep this post concise, and rather link to other relevant posts where necessary, as users do/will not read a massive 20 page post
If you have an issue when first installing Axoloti , it is assumed you have read, and re-read the relevant installation guide, seriously go read it again
please also remember many users are running Axoloti on the latest version of all operating systems, so if its not working on your system... something is 'different' about your system, so our task here is to work out what.
aka, before you report an issue...
I know these all seem 'obvious' but you will be amazed at the number of times we see posts that miss off these items
- check that you are running on a 'supported platform' (see installation guide)
- check that you are running the latest update for your operating system
- check that you are running the latest version of java for your operating system (Java 1.8)
- check you have the latest version of the Axoloti runtime AND patcher... (yes there are two things to install)
- gather all information about your setup, operating system version, java version , you need to include this in your post!
- search the forum for similar issues, the forums now has years worth of posts from new and experienced users, installing on various platforms... its unlikely you are the first to experience a problem.
- try to be clear on where the problem lies, and be specific
- gather any logs, or console messages - include everything, something you may think is irrelevant , may be.
seriously, reading posts like 'axoloti crashes' , axoloti does not start... gives the community zero information to help them help you... the more effort you put in describing your setup, what you have tried, what you see. Also people are generally more helpful, when they see you have already done some 'legwork'
- check your virus/firewall software, in particular has it quarantined any files
- java can allow users to have multiple runtimes installed (common for developers in particular), check your default is set to the latest 1.8 release
once you have done all of the above
Issues tend to lie in a couple of areas, and you need to narrow down where the issue is, and be able to report some simple facts.. most importantly we need to narrow down if its hardware or software issue.
If there is an issue with the patcher be clear where the issue lies
Patcher not starting up/hanging
- does axolotl patcher start at all, does it bring up the console window?
- try to start patcher without Axoloti connected, does this work ?
- try to start axoloti from command line, this gives a bunch more messages?
- trying deleting the axoloti.pref in documents directory
Patcher does not see/will not connect to hardware
- try different usb cables, one that you know carries data not just power
- can you see any device listed in 'Select device ' in axoloti
- use the operating system tools , to see if it can see the device
- try to boot put Axoloti into DFU mode and use rescue flash (details in install guide)
- see 'Axoloti Hardware' section for more
Issues taking patches live / compilation
- 90% of issues here are caused by incorrect installation of the axoloti runtime, check it again
- temporarily disable your virus checker
- check your virus software has not quarantined any files
Issues with library synchronisation, including not seeing factory objects
- if you don't see any factory objects, its because Axoloti has not been able to download the Factory library.
- you need an active internet connection during initial installation to get the libraries, see relevant posts if you want to use 'offline'
- if you have an issue with 'synchronisation', the recommend first step, is to use File->Preferences-> Libraries/Reset All.
Patcher runs patch, but then disconnects from hardware
This can have many causes, but the key thing to determine here is... is the patch still running? i.e. has the axoloti hardware crashed whilst running your patch or has the patch just disconnected?
the best way to determine this is to have the patch do something that you can 'detect' even without the patch running e.g. add an oscillator, that sends a constant tone to the output ,
some patches/functionality requires an SD card
There are a huge number of controllers reported working with Axoloti, see this thread
the most likely reason for a controller not to work is:
- its not USB MIDI class compliant
- it has an integrated usb hub (axoloti does not currently support USB hubs)
- check the compatible list to see if your device is listed
- check that its class compliant
- connect your device when axoloti is running and connected, axoloti will report details of the device to the console.
- if your device has a power inlet, test to see if it works when using it powered (rather than usb powered)
operating system versions
The best support is always going to be on the operating system that the developers use, and they will tend to use the OS that most users are on, or are likely to be moving to soon... this typically means the latest OS but not immediatly on release
new versions of operating systems, dont upgrade immediately... this is generally a bad idea, developers only have a limited number of machines to test on, and often after a new release some other (music) software is not working... so its not a great music platform.
old versions of operating systems, again... at some point developers have to move machines forward to support what the majority of users are on.
beta versions of operating systems/java etc - whilst its great getting feedback from users that axoloti is working or not, but dont expect support/fixes... there are only a few of us, and we cannot necessarily spare a machine to upgrade to the beta OS.
developers please take particular care, often development tools change the environment, or we run beta versions of software. this cannot reasonably be supported.
example: I (thetechnobear) will usually have my machines on the latest release, until a new release is made then I will upgrade one machine... then later once its obviously stable move my others e.g. on macs, I currently have all on 10.12.6... but will be upgrading one to 10.13 probably when it hits 10.13.1 or 10.13.2... then if thats successful, after a few weeks/months. I'll move the other.
(sometimes I might upgrade one machine earlier if I know there is an issue which needs to be fixed, but dont count on it )
this section should contain links to useful post regarding troubleshooting particular issues.