Hi,
Using the batch processor - is it possible to trim an audio file based on embedded marker data?
Thanks,
Eitan
It is not possible to trim files based on Markers in the Batch Processor. There is a Trimmer that works for audio files but that ignores markers.
You can use Auto Split (Ctrl+T) to split according to markers.
This is right, but the same tool can be used to process multiple files. So this can be seen as a batch processor too.
True, Auto Split is also a Batch Processor.
When Auto Split (Ctrl+T) is launched without active open file, it goes to opening folder by default.
Nice to know!
How about if the file has several markers, is it possible to specify which one? Or by making sure it’s trimming based on the first marker within the file?
Can you provide a screenshot and explain more of what you are trying to achieve?
What precisely do you mean by ‘trimming’? What are you attempting to do with the file? Do you mean you want to trim the start and / or end of the file according to generic markers, or something else?
What I mean is to trim the start of the file based on the first marker on that audio file.
Assuming you’re using generic markers:
P.S. USE AT YOUR OWN RISK. When processing multiple files in a chosen folder, this process is destructive with no undo. Therefore, it would of course be wise to make a backup copy of the files to a separate ‘Originals’ or ‘Unedited’ folder before processing.
1 Like
Awesome! And I can apply this to a folder with a bunch of files?
Yes. Choose folder on first page of Auto Split function (Source page).
Stingray is right
- In the picture, shown - process in place works only for regions and not for generic markers. If you want to cut head at/before generic marker you will have to save to a separate folder.
- Works when you have only one generic marker as a cue to cut head. If your file has more than one marker beyond the first marker, all markers except loop markers will be erased in processed audio files.
@Marker I don’t understand your comments. They don’t seem to bear much relation to the actual behaviour of the Auto Split function. Which version of Wavelab are you using?
Sorry, that’s not true. Did you try it? Remove Audio Outside Regions (Process In-Place) works for generic markers when using the Cut Head and Tail method. Yes, it says ‘Regions’ but it also works with generic markers and with multiple files in a chosen folder. When set to Cut Head only it uses the first generic marker found in the file and cuts the audio before that point on the timeline. The settings shown work fine to process multiple files in the chosen folder, assuming that each file contains one or multiple generic markers. Similar settings would also work for other types of markers.
If you want to keep the original files untouched, it would of course be wise to make a backup copy of the files to a separate ‘Originals’ or ‘Unedited’ folder before processing since data is being deleted.
Also not true. Did you try it? In a file with multiple generic markers, no markers are erased in the resulting audio files.
In the Auto Split processing as outlined above, the section of audio before the first generic marker is trimmed (erased), and that’s all that happens to each file.
Test.zip (7.4 KB)
Can you try with this file? For some strange reason, this works for me now after I split a long stereo file. When I tried on this initially all markers were erased except loop markers and I was not able to process in place either.
To confirm I test in WL6 with similar file, and I am unable to process in place. It was same behavior initially with WL13
I cannot test in WL6. The behaviours I described above are relevant for the latest version of Wavelab only (WL13), assuming that there are only generic markers in the file and not a mix of various marker types.
Nevertheless, I tested the file you uploaded which contained Loop markers. When testing the method outlined above set for Loop markers instead of generic markers, the result was as expected. The audio before the first Loop marker was erased. Subsequently, I added some generic markers and then tested again choosing generic or loop markers. In both cases, the results were as expected.
The process I described is intended as a basic guide. I don’t have the time to test all variations, especially with regard to multiple marker types. I also assumed that anybody using such a technique would test matters for themselves before embarking on processing multiple files. I have added a ‘use at your own risk’ disclaimer above to make it clear that this is a destructive process when processing multiple files in a chosen folder.
Could have been an MRK compatibility problem as I was testing on 6 and 13 at the same time or may be WL13 needed a warmup with a stereo file. But either way it works now on 13 and still not working in 6.
1 Like