tidalcycles/dirt-samples

Set of samples used in Dirt

dirt-samples's Issues

WAV-within-WAV duplicate header glitch

These samples (only tried a couple of bd and sn so far, so it might not be all of them...) seem to have a double WAV header. These leads to a ~22 sample (for mono 16bit WAV) noisy click at the start of the sound as the duplicated header does not make audio sense.

$ hd sn/ST0T0S0.wav | head -n 6
00000000  52 49 46 46 9e 3d 00 00  57 41 56 45 66 6d 74 20  |RIFF.=..WAVEfmt |
00000010  10 00 00 00 01 00 01 00  44 ac 00 00 88 58 01 00  |........D....X..|
00000020  02 00 10 00 64 61 74 61  7a 3d 00 00 52 49 46 46  |....dataz=..RIFF|
00000030  72 3d 00 00 57 41 56 45  66 6d 74 20 10 00 00 00  |r=..WAVEfmt ....|
00000040  01 00 01 00 44 ac 00 00  88 58 01 00 02 00 10 00  |....D....X......|
00000050  64 61 74 61 4e 3d 00 00  52 49 d4 46 49 40 bb 18  |dataN=..RI.FI@..|

I hackily fixed my local copy by:

cat sample.wav | tail -c +45 > tmp.wav && mv -f tmp.wav sample.wav

but this assumes the outer WAV header is exactly 44 bytes and that the remainder of the file is audio data with a valid embedded WAV header of its own.

Metadata for sample packs

Shall we agree a simple metadata format for samples? We discussed before under #15 but it didn't go anywhere, and it's come up again in the forum here: https://club.tidalcycles.org/t/what-if-there-was-a-sample-pack-format-with-metadata-for-superdirt/2746/6

1. General human-readable description of the sample set
2. License and copyright information
3. Per sample dictionary. Could potentially follow something like this http://motools.sourceforge.net/doc/audio_features.html and/or just an ad-doc lookup table.

It could be json, like this (this is the first json I've ever hand-written)?

{"name": "gabba",
 "description": "Selection of samples taken from the gabba kit from the Techno xpansion board in the Roland JV1080",
 "author": "Alex McLean",
 "license": "CC0",
 "files": {
    "000_0.wav": {"description":"Distorted Kick", "centroid":4000, "keywords": ["kick"]}
 }
}

Would something like that work for SuperDirt @telephon ?

Add a license

Please add licenses for all samples. A lot of them have no license

consider rename of sample

I've come across a sample that comes alphabetically in between chin and circus that could be taken under consideration renaming. Despite the usage in the common idiom referring to a gap in one's armor, the term also unfortunately has the common usage as a racial slur. Although I don't think that's the intent here (but rather onomatopoeic), I'd be hesitant to type out the word (def in a live coding performance setting even though I don't think I'm quite there just yet...). The sample sounds somewhat like keys, coins, or a small metal chain being dropped in a dish, perhaps something like keys or coins could be used instead? Thanks!

Rationalising / reorganising / cataloguing the samples

I used rmlint --types=duplicates -p and found that there are 69 byte-identical duplicates among the files. Total 2,2 MiB in size. Some of them are even in the same folder, for example:

ls 'invaders/007_16.wav' # considered "original"
rm 'invaders/014_6.wav'
rm 'space/007_16.wav'
rm 'space/014_6.wav'

or

ls 'mash/0.wav'
rm 'mash/1.wav'

I suggest to delete them.

re-organize or remove unplayable sub-folders

The sub-folders (e.g. the 808s) aren't playable in their current structure and cause unnecessary confusion for new users.

Perl-Scripts

There are some Perl-Scripts in ./foo/PerlCans.tar.gz. Their Readme states:

PerlCans -- canon and sequence manipulation scripts

As far as I understand, they do not operate on sound files. Are they useful to somebody or can they be deleted?