Posted
I'm trying to create libraries for the various Drum VSTs that I own, however it's very time consuming and I feel it shouldn't be.
For example, the structure on the hard drive is a folder for Pop, another for Funk, Rock, etc.
Inside each of these folders are further folders, e.g. 01 Groove, 02 Groove, etc.
Inside each of those are the actual MIDI grooves.
I have to go to the lowest level each time to select a MIDI file, and import each folder individually. I would like to be able to select the Pop folder, which would create a library called Pop, and within it would be each sub-folder (the grooves) containing each loop.
Additionally, each time I select a MIDI file, I have to remember to tick 'Import all files in a directory' and 'Put in a single folder', and un-tick 'Keep takes' (which doesn't seem to make any difference as the takes are still there).
At the end, I then have to 'Clean up for shipping' to delete the takes.
However, the biggest time-consuming problem is that the resulting library is twice as big as it needs to be. This is because the Master Take is retained, and the only way I can see to delete this is to select each file individually and 'cut' the take. I thought the cleanup should take care of this but it doesn't.
The only way on import to not get two takes is to de-select 'Create phrase pools', but unfortunately doing this does not inherit the name of the MIDI file so it is no good.
Fri, 2014-02-21 - 12:06 Permalink
Thanks for your suggestions. I'll check that for possible bugs.
Importing a folder tree with all its implications would be difficult to setup. Libraries only support one top-level folder anyway. An option to delete the master take after import however, is a great idea. I noted this on our list.