Great samples @cleary! I was wondering about clicks in the samples until I realised your demo had cunningly added a pattern of clicks on top !
What have come to be known as the 'default' samples are of mixed and sometimes unknown provenance, and for a looong time it's been an aim to start again, with a decent set of CC licensed samples.
Here's a thread about it:
Basically I'm wondering if you'd be up for adding a bit of metadata in YAML or json that superdirt could understand, in a simple in extensible way? Then we could work on making them easily addable to SuperDirt via the quarks system or something like that.
They could potentially do that, or it could be done by some automatic psychoacoustic analysis. I guess I'm just thinking that to adjust loudness of samples, we could change the metadata rather than the sample files. The metadata could be stored in an individual .json or .yaml file for each sample, or one json file for each folder that has a section for each file.
I think it's a great idea... I was debating whether I needed to normalise these flbass samples again, but I think I'll leave them as is. They've had a good run over a number of users and platforms by now and they seem to be ok
Apologies for this, but I'm going to need a more obvious pointer (shove) down the road here - is there any documentation or examples for the type of metadata or even just variables that superdirt is looking for?
I'm still not sure what I should be including (or how I should format it for inclusion) at this stage - things that seem obvious at my noobish high level are just the bits I've included in the README/file names already:
License and copyright information
per sample description
general sample set description
I can pop them in a metadata sub-folder, or I could include a metadata file per sample - I still need some guide on what the var naming should look like for superdirt compatibility though?