NAM_models
NAM_models copied to clipboard
pelennor2170
Turn this repository into an index of repositories
Basically, got this idea from: https://github.com/chriskempson/base16-templates-source
This goes like this: Instead of storing the files here, you create some guidelines on how people can create a repo and store their models.
After that, they can send you PRs including their repo into your main LIST (readme) as submodule, making this a central list of repositories.
This is great because you only accept those who follow guidelines, like naming schema and so on.
Once this is done, a PR can be sent to NAM project including this one as a "Project using NAM". I believe this section will be created at some point.
In general I like this idea. But if you as a user just want to have an easy way to mass-find and download the nam models, you would also need to standardize on the structure of the linked repositories. And provide some tool / script that allows you to mass select and download. Or you do this in a CI/CD script and provide the result(s) in your releases section.
Right now, it's really convenient to just download this repo and already get everything.
If you think about standardizing - it would be nice to also do that on file names and categorizations. E.g. "amp only", "amp + cabinet", "distortion pedal", etc.
So, the story is that there's a number of developers working (in their free time away from their day jobs) on a tone sharing website called tonehunt, primarily for NAM captures, but in theory could work with any similar tech. It's very close to initial release, so my thinking is it will be a great system to use going forward as a capture repository.
If you're interested in the specifics, if you're not there already, highly suggest getting on to the NAM discord at https://discord.gg/gZ34U46B , we'll also announce on the NAM facebook group once we go live.
@pelennor2170 Interested in this project, seems like the discord link is dead?
@Fannon, re: "just download this repo and already get everything" - to me it means to getting lost in a growing number of files with disorganized naming convention, directory structure, etc. Who has time to audit all these files. Please organize this depot better before it is too late and it starts to resemble a pile of spaghetti code. @38github link is an example how it could be done.
Thanks to all the contributors sharing their results, they deserve to be accessible in an organized manner.
