I’m very new to WaveLab, so apologies if I’m missing stuff
Using ms is fine if all your files are the exact same length, but,
If I for example wanted to trim down some kick drum samples, some of which were extracted 8th beats among 1/4 beats… What I might want to trim down on 1/4 beats will be too much for the 8th.
Using % would allow the process to be relative to file length. 50% would cut the 1/4 down to an 8th, and the 8th down to a 16th.
The trimming plugin could also have a ms trim limit, allowing users to unify lengths.
I would say the batch processor is not the perfect tool for what you are looking for. For this level of accuracy, the audio editor should be the choice.
Interesting, I’ll look into the audio editor more. TBH, I got Wavelab primarily for the batch processing for managing/editing/tweaking my custom sample library. I have over 50,000 of my own recorded/extracted, edited, and processed custom sounds, all organized in MediaBay.
So, Im sort of working my way backwards from the Batch Processor and will hopefully find out more about WaveLab… I’m curious about how the Audio Editor could do this work in a way that is better than the Batch Processor and better than Cubase.
I’m not super worried about accuracy with all these batch modifications to samples, just happy averages.