Loading 1.3 samples and scenes

[Lizard-of-Oz]

@schinji

I will also say, I’m a little displeased that each engine (GRAIN, WAVS, DWA) uses its own sample library folder–since most of the samples I’m going to pull for each of those engines is going to be the same library

That may be the case for GRAINS and DWA, but WAVS uses wavetables, and those won’t be much use for GRAINS and DWA, just preview some of them on your computer and you’ll see what I mean.

Also I’m pretty sure the limit of 250 files per directory and the small screen will bite you long before you can fill up the SD card.

Personally I appreciate the separation, but I also think that the best way to handle this is letting the user choose their own structure of possibly nested sub-directories. Which incidentally would also get around the limit of 250 samples per engine, too.

There’s a wish for sub folders, we could easily edit it to accommodate your needs, too:

Allow for sub folders for samples and wavetables

What is the problem? As a user with a short memory and little time, but access to a literal shitton of samples and wavetables, I’d like to organize my samples and wavetables in folders so that it is easier to keep them sorted and identify find those I want to use. What should this feature achieve? ^ This. And since presets and scenes are also merely files in a filesystem, these too might benefit from supporting folders. Since the Preset Browser and the Scene Browser are navigated via the clic…

@tomfabinski

if one were to copy the samples into one of the existing folders, would it be the GRAIN or WAV folder?

these are “normal” samples, so you can use them in the GRAINS engine, but they’d sound rather weird and glitchy in the WAVS engine (which expects wavetables, and would assume these files contain 256 waveforms, see p. 64 in the manual).

Definitely a worthwhile experiment.