500MB is a huge amount of space that I find myself wanting to just fill up a nested, organized “samples” folder on the SD card (which I have done) and just have access to every sound on it, preserving the file structure, so that the “Assign sample” navigating would act just like the Pool -> Load view (with a nested folder nav structure).
What I did was just Sample Player -> Load -> Multi -> (Select entire organized “samples” directory) -> Done. Waited for awhile for the IO blinking light to stop, and then I had all my ~450MB of samples ready to be loaded, except that they’re all in a single flat directory in the “Pool” making it really difficult to navigate.
I keep thinking there might be a way to reflect a nested samples folder hierarchy exactly like the Pool -> Load view, but with minimal or no mental overhead of even needing to “Load” it into the “Pool” first. Something very similar to the “multi” option that recursively loads each sample from a folder, but maybe just “points” to the folder, so instead of thinking of it as filling a bunch of memory I could just “point” the pool to a nested folder, and it would under the hood delete and load all files and folders recursively to the main memory and leave my folder structure in tact.
I hope that make sense. Just to be clear, apart from the half-baked ideas the real problem I’m trying to solve is a ginormous 450mb flat pool of every sample in my world.
Thanks! Such an amazing module