Warning - I reshuffled some wav files

yaxu · 10 June 2019 07:37

I think this will only affect linux users, but there were some inconsistencies in how wav files were being sorted, so I’ve renamed some files to remove ambiguity. As a result, the following might map to different sounds:

auto birds east gretsch h if jungbass mash2 mute peri popkick print speakspell speechless toys trump ul

More details:

github.com/musikinformatik/SuperDirt

Inconsistent sorting of files

opened 08:38PM - 09 Jun 19 UTC

yaxu

It seems that given a folder with files `kicksnare.wav` and `kick.wav`, linux ba…sed systems sort the former first, and others sort the latter first. Probably because other systems ignore the extension when sorting. This means `d1 $ sound "gretsch:13"` gives a kick on some systems, and a kick-snare on others. I made a quick script for finding problem folders: ```bash #!/bin/bash for d in */ ; do diff <(ls $d|tr ' ' '_'|xargs basename -s.wav -a|sort) <(ls $d|tr ' ' '_'|sort|xargs basename -s.wav -a) >/dev/null if [ $? -ne 0 ]; then echo "$d has a problem.." fi done ``` There's quite a few: ``` auto/ birds/ east/ gretsch/ h/ if/ jungbass/ mash2/ mute/ peri/ popkick/ print/ speakspell/ speechless/ toys/ trump/ ul/ ``` Not sure of the best approach to a fix - by renaming the files to make sorting unambiguous, by fixing superdirt to sort one way or the other, or maybe this is a bug in supercollider.

khoparzi · 10 June 2019 23:13

I’ve been numbering my files for all my custom sample folders exactly like this for a while. It also lets me quickly find specific sounds in the studio without having to sit and count the output from ls -l.

BTW does this mean we should all update our SuperDirt?

yaxu · 13 June 2019 14:50

@khoparzi It shouldn’t make a difference if you’re using mac os, I don’t know about Windows. Probably worth updating dirt-samples if you’re on linux.