That should hopefully make things easier on both ends, until I get the chance to compile with a mac myself (I have access, just incredibly rarely–so pretty much not at all).
The script is mostly done, I just have to work out zip exports and polish; here’s the basic GUI:
You select the components (presets, tables, lfos, audio) you want to add to each list from a file browser and then name and export the bank. The “Auto Add From Folder” button allows you to select a folder of components to automatically add to the bank, specifying what kind of components you’re after. Let me know if there’s any additions you think would be beneficial, or if I’ve strayed too far from your vision.
I will be having an unavoidable 2 day hiatus but should still make the 5 day quota (hopefully).
Here it is! Let me know if it works for you or if you have any suggestions; I’d like to announce the utility in its own post, but having someone test it beforehand is a good idea.
AutoAdd worked correctly. Added all presets in 7 subfolders. (372)
Export - defaults to system drive. Clunky.
Would be nice if Export defaulted to the top level folder where you select your presets instead of to the system drive.
Alternately: having a preferred specified output folder would be acceptable as well.
Alternately: defaulting to last used output folder is another logical choice.
Multiple preset folders. Folders for Samples and Wavetables. “Add all” lumped Samples and Wavetables into the Samples bin. Don’t know if that’s a builder error, or whether it was a directory organization error by the preset creator.
SpeedBanks doesn’t rely on directory structure, it just looks through all the files preset and sorts them out manually.
Also, the download link for the preset seems to be down, could you send me a screenshot (window maximized) of how SpeedBanks looks? I want to see what filenames are being put into the Samples list, something like this:
This checks out. The creator of the pack intended for the audio files to be used as wavetables (something Vital handles) but AutoAdd couldn’t possibly deduce this. It is impossible to distinguish whether or not you want an audio file to be a wavetable or a sample from AutoAdd, so I will be making a button that allows you to transfer sample items over to the wavetable list and allow for audio files to be added to the wavetable list directly.
I noticed that all four of the wavetable files were extremely short.
Two were 93ms and the other two were 139ms.
If this is typical for wavetable files, perhaps you could code a differentiator to shunt all files below a certain length to the Wavetable folder.
The shortest sample length in the Samples folders is 239ms.
If there’s a consistent length size maximum cutoff, automatically shunting small wav files to either Wavetable or Sample might be doable.
If a Sample is over 1MB, it could automatically be shunted to Samples.
If it’s under 1MB, it could be checked for length in milliseconds and redirected accordingly.
Possibly, something like a audio length threshold slider; it seems like I may need to add a larger menu to the AutoAdd button. This may increase the build time to 1-2 business days.
Added two buttons:
Sample => Wavetable : Moves selected sample list items to the wavetable list
Wavetable => Sample : Moves selected audio files in the wavetable list to the samples list
I’m going to hold off on the AutoAdd wavetable detector given that the small ease of use increase doesn’ytreally justify the increased size of the program (given that larger libraries must be invoked to read the length of an audio file). Hopefully, the new buttons should make things fast and easy enough.
Here it is again, but better. Now featuring Keybinds and better button placement. If you don’t see anything else worth noting, I’m thinking of making a general announcement about the utility soon.
