I've got quite a few home-brew samples that I occasionally convert into sample libs in Kontakt or Halion 3. I don't do it more often because it's so frankly tedious. I was hoping to get some ideas on how to speed the process of moving the samples into either sampler.
I typically will record whatever I want in a very organised way, say a drum. I'll do a single take, striking it at 8-9 velocities, from pp to fff, then move to the next articulation. At the end, I've got, say 15 minutes with perhaps 10 articulations, each with 8 velocities. OK.
I import into Wavelab and use it's Auto-Split to create the 80 samples.
Now here's the boring, tedious part. The file naming in Wavelab is not very useful. So unless I've been VERY careful, there's no -easy- way I can figure so far to move the samples into K3 or Halion3 en masse.
The problem is that, I can't easily 'scan' through all the samples as I try to build the program in Hal or K3 so unless I know -ahead- of time which samples go where, it's -very- tedious work.
Any ideas on how to speed up the work -inside- the sampler, if one can't tell from the file name where the sound 'goes' in the program? (ie. which key, which velocity?)