Axoloti Patches Archive

#1

Hi!
As a G2 user i found the patches archive on electro-music.com very usefull. (http://electro-music.com/g2patches.php)
therefore i propose to create a section on the site where each user can share their own patch, it could be organized in this way (we accept suggestions)

Axoloti Patches

  • Categories (better a tag system, a patches can be in more than one category)
    • Acoustic
    • Audio In
    • Bass
    • Classic
    • Drones
    • Drums
    • External Control (GPIO)
    • Fantasy
    • Lead
    • Organs
    • Pads
    • Piano
    • Sequencer automatic (generative, AI, noodles)
    • Sequencer interactive (like groove box etc)
    • Synth

Every patches must have

  • name
  • description
  • author name (if it's a fork It would be nice to keep track of the original author)
  • presets
  • screenshot
  • ratings (from the community)
  • comments from other user
  • upload is permitted only for complete and working patch

In the G2 archive, someone has developed an interface that render the patch on the web (pure genius) http://electro-music.com/patchviewer/?URL=/forum/download.php?id=40305

Axoloti Subpatches (aka utility or building block)
usefull subpatches that can be used in other larger patches like BPM block, multi mode filter, multi osc etc...

Optionals
option to download a full archive updated daily or weekly

What do you think?

#2

It's a great idea, it would be a big help for the beginners with more examples to study.

#3

I have thought about the exact same thing. I am also a keen user of electro music page. Very nice one. Endless resources for the G2 smile

We should build a library a bit like over there. Building blocks makes way more sense as a category in Axoloti world cause you can compile them into subpatches...

For example I made stereo mixers with 1-2-3-4 inputs, crossfaders with amount knobs. Stuff like that. Stuff that is boring compiling over and over again but you use them all the time.

I am down smile

#4

where is a good place to host it? i am leaning towards github to be honest - to keep in line with the open source nature (tracking changes, forking, etc).

#5

Category "Sampler" would be nice too. Or "Sample player"

#6

Here? smile

Make some subcategories to patch library and we are good to go smile I think this is better than github, cause you can communicate with the author or just other users.

#7

yes, better place is on the website
user are already registerd ecc...

maybe a section of this forum (but i don't see tags options)
if the community needs help, i propose myself as moderator for this section smile

#8

Ok, in the 'discourse' web site (discourse is the engine of this forum)
i have found a plugin for the TAGS smile
is a good news!

#9

Cool idea. The Audio In section could break into other sub-sections - delays, reverbs, echos, distortion, etc.

#10

Ive been throwing some ideas around about this with @johannes as always its a bit of a trade off with time to implement/usability etc. and had already noticed that the contributions are starting to stack up on the forum, which is very cool!

whilst using an existing forum structure is 'easy', its not really very searchable and you its a little limited in where we can go, we also have a minor 'issue' with discourse, that the files loose their names (they get a random id), so its ok for now, but not ideal
(finally there is a potential issue with disk space, and avoiding 'abuse')

github we considered, but the issue is contributors have to be github collaborators, and thats a pain to administer, or fork with pull requests... and that is a pain too (alternative is you frontend with a web process, but users then lack github functions) and frankly, github is going to confuse some users not used to version control system, and for most objects/patches largely unnecessary.

personally, Id lean towards a dedicated web front end, with a database to provide searchabiity, perhaps hosting the files on github (but the user won't see this, it'll just be a file store)
something like http://maxforlive.com (or native instruments user library)
this is not particularly complicated to build, if you have the right set of web dev skills...

anyone out there who has the skills, and would like to help out on this?
(personally I don't have much time to devote to the web dev side, and probably more useful on the firmware/ui side anyway)

but all this is open... as there are countless options... e.g. perhaps it would be better to have the searching within the Axoloti UI, (hitting a centralised database/patch store). (I've just added a feature so that patches can be directly open with a URL)

also the other consideration, is perhaps some kind of 'community selection' of moving patches into the main deliverable. (or perhaps as an optional 3rd party contributions... and of course assuming original author agrees)

there are also other considerations, to do with upgrading/versioning objects, but won't bore you with this.

(ps. id agreeing tagging is more powerful than categories, if you limit the tags, and potentially you can also create hierarchy of tags)

#11

for my website i create a patches section (for registered user)
for sharing various synthesizer patches

http://noisecollective.net/index.php/nspa

but is in joomla.

It will be usefull a version in php/mysql, i have some experience but not enough for this kind of project.

#12

I could help out in coding a patch library.
(in Django or PHP)
I would prefer something like the NI user-library (but without the bugs).
Unsure how much time it would take to create it, but I can do some research on that.
For me, the most important features would be :
- voting (5-stars)
- useful categories
- search functionality
- comments
- sound example (mp3)
- clear layout/design

@thetechnobear , what is coding language currently used for this forum? because the users of the community and a user-library should somehow be synced (or use the same db) .

#13

Discourse is Ruby on Rails. It has a plug-in system that could be used.

#14

yeah as @rvense said its discourse, so this does have an integration API. user integration would be nice, and also linking a topic to an object would be useful.

I think if its done as a plugin, it will need a bit of chatting over at meta.discourse.org as I find their documentation almost non-existent. (don't get me wrong, love discourse, but finding information about it seems hard work)

also if anyone wants to have a go, obviously chat with @johannes first, check what his latest ideas/plans are.

#15

I don't like hacking stuff into discourse (or even writing in RoR) so I can't help you then.
I can make a patch-library in django/python , but then someone else should find a way to authenticate users to this Forum.

#16

i don't know django/phyton or RnR but, I believe there is some session cookies that can be used
here you get some user data https://sebiik.github.io/community.axoloti.com.backup/users/johannes.json
but there is not information about the session...

#17

I'd prefer something very, very small. Like the minimal extension to make a forum thread serve as patch storage. I haven't used NI's user library for ten years, but from my point of view a forum has 90% of the features needed.

#18

What about a pinned "container" topic in the forum?
Let me explain: i create a dedicated topic for my patch (with descriptions, tutorials, downloads, images, etc), then i provide the link via PM to the moderator, that periodically updates the container topic.

In the end we should have a topic that looks like

Synthesizers:
Mega Bass - community.axoloti.com/link1 - [bass] [phase modulation]
Hyperstellar - community.axoloti.com/link2 - [pad] [FM] [poly]
Skreamer - community.axoloti.com/link3 - [lead] [Sync]

Samplers:
Zampler1 - community.axoloti.com/link4 - [drum sampler]
Monster - community.axoloti.com/link5 - [granular]

Utility:
ClockDivider - community.axoloti.com/link6 - [clock]

Effects:
NeatCompressor - community.axoloti.com/link7 - [dynamics]

Patch of the month:
NeatCompressor - community.axoloti.com/link7 - [april 2160] [dynamics]

Latest additions:
ClockDivider - community.axoloti.com/link6 - [clock]
...

Etcetera

The topic is pinned, so if i need to search something i just have to open it and browse the stuff i need.

What do you guys think?

#19

@rvense , @Sputnki
no, that won't work anymore when there are thousands of items.
As it gets bigger you'd want a search functionality. And after that you'd want some ranking system to filter by quality. and date. and user. etc...
Unfortunately, these things are never simple and should be designed up front.

#20

That would be a really nice goal to reach, but i frankly doubt it will be any time soon, consider that not everyone with an axoloti will share patches (hopefully), since many users will only download stuff.

An archive would be a really useful thing to have right now, therefore we should try to keep our feet to the ground when planning it
Also, if we mantain the archive near the community, there's more room for confrontation between users.