User Library with Sync function

#1

Hi guys!

I think the best sub patches, modules etc... should be included in the official release
or, you should create an online repository and add a sync function in the software.
a similar thing is done with the preset in the CURVE2 vst by Cableguys.
Curve2 user can rate the patches, assign a category etc ...

what do you think?

#2

yeah, we need to organise a couple of things for this:

  • explicit permission from author
  • a separate contributions repo (due to ownership issues in axoloti repo)
  • some way to determine what are the 'best'/popular
  • some 'maintenance' concept... i.e. if we start supplying 100 patches, and they need to be modified due to an update... etc who does this? (we can't be shipping broken patches), who tests the patches?

so definitely part of the plan, and Id kind of hoped this would fall out of the object database.
(this would address top 3 concerns)

#3

oh, no sync function... this would be part of the normal software update function.

#4

what do you mean? Another server?

#5

no, another github repo....
the 'issue' is contributing to the axoloti repo, hands ownership over to johannes.
but for some contributions (like this) this would be inappropriate.

its the same license/approach as used by Chibios.

no difficultly, just pointing out, how it needs to be implemented

#6

I wouldn't want patches included with the official release - it could just be linked on the official page or something and have monthly compilations. Let's keep the axo package lean and mean.

#7

But subpatches or building block are usefull IMHO

#8

yeah sure - they could also be part of compilations. Half of my instruments have custom objects so i would have to bundle those together and as I get more into it, i might have objects that have a single use. There are even default factory objects that I don't need and sometimes delete so it is easier for me to quickly slap stuff together. But yeah, more is better of course - as long as people well document their objects and subpatches. But then we would need a better system of decluttering all of that stuff. The browser in bitwig for example is a nice solution to take some notes from (favorite, categories, tags)

#9

Id be happy with a local library and the ability to absorb custom modules into that library with a menu option, sorta like how ableton works. So click a user patch, wizard says THERE ARE NEW CUSTOM OBJECTS WOULD YOU LIKE TO IMPORT. Also objects should have a version number so you can upgrade the local copy by just reloading an updated patch.