CMS: Adding and downloading individual files to bundles with their own metadata

[RustoMCSpit]

In your example links, sounds/samples are displayed individually on the websites with a preview. This would be possible to have a single sample inside a package with a preview.

However it might be better to encourage sample packs, containing one or more groups of samples. After installing the sample pack, you have several samples to choose from e.g. different loops or one-hit samples from the same author or same group of recordings.

Either way the package format would be flexible enough to do one, or the other or both.

Great idea!

Originally posted by @kmturley in #93

People should be able to make and upload bundles of plugins, preset, projects, midi, and samples

For example, I want to add presets from here but they come in packs as you can see.

https://github.com/ironcross32/Surge-XT-Patches

I have also seen presets come in folders inside of packs, meaning two layers of files.

We have to figure out the most logical way of distributing these and how to make it uploadable via https://open-audio-stack.github.io/open-audio-stack-site in a way that isn't convoluted.

I believe users should have the option to either download a whole pack or just a sample inside, which also requires downstream design #61

[kmturley]

The package installation logic is defined here:
https://github.com/open-audio-stack/open-audio-stack-core/blob/main/specification.md#install-logic

Preset docs are here:
https://github.com/open-audio-stack/open-audio-stack-registry/blob/main/specification.md#preset-formats

Preset paths:

Linux platform | $HOME/.vst3/presets
Mac platform | $HOME/Library/Audio/Presets
Windows platform | $HOME/Documents/VST3 Presets

Example installing acme-corp/woodstock Preset, extract the archive all files into a temp directory, and only copy over valid presets files into the installation directory, e.g.
$preset_dir/acme-corp/woodstock/2.1.0/jimi.vstpreset

So I think this is already a solved problem no?
The only issues is that you need to install to a custom path. That is covered by another issue.

[RustoMCSpit]

oh presets are also uploaded as archives or installers, sorry this is a stupid issue

[RustoMCSpit]

having presets uploaded like this prevents attaching audio metadata to each preset however. it also prevent downloading a single preset in a pack.

https://presetshare.com/bundles/view?id=228

you see how theres preset audio metadata for each preset in a pack? thats impossible because of this.

the end product for downstream things like studiorack should be able to have feature parity with presetshare and other preset sharing websites. people want to be able to click into packs and see the presets individually with their own metadata and download them individually.

[RustoMCSpit]

this is a CMS issue #110 as what we would need to do would be to let users upload presets individually and add them to a specific bundle aka pack via an account #24

that means that we would need to host the files and dynamically create new .zip files every time a file was changed

please tag this issue as CMS

[kmturley]

The presetshare link you shared shows separate "packages" for each preset, as they have their own page/metadata and download links. This is possible with the current specification, just put them into separate packages.

If you want a way to submit lots of smaller presets packages quickly, then there would need to be a way to bulk select files and then extracting the metadata from each file. This would require understanding each preset format and parsing, and not all presets would have all of the information needed.

It would need an investigation to understand what is possible. If it requires a CMS then it would be something I'm interested in building personally.

Thinking about user experience, I'm not sure if want to browse and download individual presets as they are so small. Just download a package of lots, and then choose from them in my DAW

[RustoMCSpit]

This is possible with the current specification, just put them into separate packages.

yes but they wouldnt be in the same pack (aka bundle)

If you want a way to submit lots of smaller presets packages quickly, then there would need to be a way to bulk select files and then extracting the metadata from each file. This would require understanding each preset format and parsing, and not all presets would have all of the information needed.

another reason why a CMS would be useful, most of the metadata can be got simply by scanning the file.

the user experience should match that of alternatives, we need to review alternatives and see what features are needed for feature parity with all of them

[kmturley]

Examples of how the current specification already allows for enough flexibility:

Bundle/collections within a single package:
https://studiorack.github.io/studiorack-site/plugins/airwindows/airwindows
https://studiorack.github.io/studiorack-site/plugins/distrho/dpf-plugins
https://studiorack.github.io/studiorack-site/plugins/michaelwillis/dragonfly-reverb
https://studiorack.github.io/studiorack-site/plugins/audioplugins/iempluginsuite

Org/groups with separate packages:
https://studiorack.github.io/studiorack-site/plugins/sfzinstruments
https://studiorack.github.io/studiorack-site/plugins/tiagolr

Dynamic groups based on tags with separate packages:
https://studiorack.github.io/studiorack-site/plugins?search=&category=drums

I don't see a reason to change anything in the specification as it already supports bundles in those multiple ways. CMs discussion is a separate issue. Closing this request.

[RustoMCSpit]

I don't see a reason to change anything in the specification as it already supports bundles in those multiple ways. CMs discussion is a separate issue. Closing this request.

how exactly would one reach feature parity with this https://presetshare.com/bundles/view?id=228

Bundle/collections within a single package:

all files are under the same download and upload

Groups with separate packages:

things are grouped by file path, there is no way to upload file path data in OAS site. if you wanted to make this a single download, youd need a CMS to regularly re-make the zip every time a new preset was added inside the bundle.

Dynamic groups based on tags with separate packages:

you could upload everything and then tag it the same, but that would clog up the ui for all presets.

what you want is for this to have feature parity with presetshare:

• There is a view of synths on their own which you click on to select
  the synth presets you want
• There are individual presets with their own metadata (including a text metadata for a user comment)
• There are bundles with their own metadata of individual presets
• You can download an entire bundle in one download
• You can click on a bundle to view the presets inside of it individually
• You can download and upload any preset made by anyone to any bundle you have made

https://open-audio-stack.github.io/open-audio-stack-site does not let you do these things

[RustoMCSpit]