Category for the community library
( you need Axoloti 1.0.10 installed to use the community library , see this post)
About the community library
The community library is a way to share object and patches with the community. Sharing is done by a simple synchronisation feature available with the Axoloti UI, providing an easy way to both contribute and use contributions without having to download files manually.
This category is used to allow contributors to provide more information about their objects and patches in the library, and for other users to comment/ask questions etc.
This feature is new, so there will be more coming, to allow better management and also for better browsing of the library especially for patches.
Note: please do not post files directly on the forum, its much easier to for everyone to access and maintain if they are store in the online library.
Accessing the library
Since 1.0.7 all users can access all community library objects directly from the Object Search dialog, just like the factory objects. Patches can be found the subdirectory axoloti-contrib/patches in your axoloti home directory. (a patch browser is planned for a future release)
to keep you library up to date, you will need to use the 'synchronise libraries' option found in the File menu.
alternatively, you can turn on auto-sync in the library preferences, found in the preferences dialog, once enable this will automatically synchronise your libraries each time you start axoloti.
Note: objects can either be AXO or AXS files, however they should be 'generic' objects, i.e. objects that can be reused by other patches.
AXS files which are specific to a patch, should be stored in the same directory as the AXP (within the patches sections)
Each contributor is allowed one topic only, the first post will be used to list their contributions, and references to further details about their objects/patches etc.
If other users have questions or issues about these contributions they should post on that same thread.
an example for how I (@thetechnobear) organise mine is linked here
The idea behind this organisation is:
- few topics, so easy to browse
- contributor can monitor their own topic, to support their own contributions.
(we will move and combine posts/topics to keep these goals)
in particular, this is NOT the place to make request for objects etc, or other discussions.
Contributing to the community library
anyone can access the community library from the Axoloti UI, no user account etc is necessary
However, to contribute to the community library you will need to do the following:
- create an account on github.com
- be added as a contributor to the user library, see this post
- create a contributor post , see my example here
adding/updating objects/patches to the user library
- simply put your new object in the appropriate place in the directory,
this is [objects/patches]/[your prefix]/[category]/object or patch
- synchronise the library to upload the new objects
- update your contributor post here, so that users know about it, and you can supply details of how to use etc.
It is highly recommended contributors use the latest released version of Axoloti for contributing.
Its a good idea to follow a similar heirarchy for objects (e.g. midi/in , env , osc, lfo) since in the future, the object browser may compress these into a single hierarchy, or we may use as a 'seed' for tag creations.
Important note: you should only add and update objects/patches under your own prefix do NOT attempt to update other users objects, as this can lead to conflict errors, which may require 'support intervention' to resolve.
removing entries or more advanced file operations e.g. rename are possible using git tools directly, please only do this if you are experience with such tools, if not PM us. users must not do any git operations that affect any objects/patches outside their own prefix.
if in doubt PM either @johannes or I (@thetechnobear)
(this restricted workflow is intended to minimise the chance of git issues, which are difficult for users with little git experience to resolve... and obviously we cannot expect (or want) users to need to know the complexity of version control systems)
Contributors upgrading Axoloti
Before you upgrade axoloti to a new version, it is recommend you commit your changes to the community library i.e. do one last sync before you upgrade.
note: when you commit changes, they are available immediately to all user using the version you are using. If you are using an old version of axoloti, then this changes will be copied to newer versions periodically... so you do not (and should not) do this yourself, but this may mean that its not available in the latest versions for a day or so. This is why we recommend contributors use the latest version of Axoloti.
Ive created a series of videos which show how libraries are used in general and also particular the community library
(please note: some changes have occurred since these were made, but the contents is generally correct still)
Introduction to libraries
Contributing to the community library
Using your own libraries
Obtaining the factory library without internet connection