I’m very new to WaveLab, so apologies if I’m missing stuff
I’m doing spacebar and ctrl+p to compare the files… But instead of always having to re-render the preview,
I’d prefer batch previewing the files in a pop-up window where it renders the selected files once, and then I can do more continuous file comparison, compare waveforms, etc.
This would be a good way I think for preview to work for Meta plugins as well.
And then, the advance preview can act as an already completed process if everything is good the user could click a button “use as final render”.
Sort of, not playback all of them consecutively, but to load them into a “buffer” preview window which maybe has some dedicated comparison features, waveform preview/overlay comparison, etc,
I agree it would be good to have a separate audio file comparator as in the picture you posted, but I also think there are risks to your concept being a part of the batch processor (files being copied to clipboard, long files, use case with a large number of files, etc.)
When working with one shot, it would be wise to batch 20 files into a temporary folder and compare in a montage, and later batch everything. This you must already be aware of.
I’m just getting into WL and I mainly got it because I needed/wanted a good audio file batch processor. So I’m sort of working/learning backwards from the Batch Processor.
I’ve been sort of doing what you’re talking about using some of the other utilities to compare…
But so far with my limited knowledge, it’s not fast enough workflow, and there’s so many handy features that could be dedicated and immediately accessible with what I’m thinking.
It is nice to know you are starting with Batch Processor.
I think it would be nice to have option to open Explicit Path/Path on completion. This can help users to drag and drop batch processed files into WL or other software.
I just got to know - the option to drag and drop from Batch Processor output is already possible. It is just that there is no option to open folder (Show in File Explorer) on completion as in Montage. Drag and drop can also move files to a different folder.
Maybe you are aware of this too, but in case you missed…
Except for Normalizer, etc… In the Audio Editor, when Master Section is Docked, you can audition for example about 20 files - use the bypass master section shortcut and create a batch processor with plugins from Master Section.
Usually when I’m interested in batch processing at least for my current use cases, i’m dealing with more than 20 files.
If my advanced preview idea was implemented, some other useful features:
Search Filter, to find specific files to compare.
Side by side waveform preview, overlay waveform preview
Metaplugin preview (essentially it runs the process as if it was doing a render, but takes care of autodeleting if the user chooses not to use the preview-process as the keeper render
Plugin/Process Settings adjustments per-file, for example if one file needs slightly different settings than the rest of the files (a fade out for example), the user can change settings just for that file and then its re-preview rendered (maybe colour coded differently to show it was adjusted, and an option to reset to the original bulk-process settings)
Data information comparison in a right panel: file size, length, RMS/Loudness, etc
Ability to print to PDF
Auto-Play files in series (search filter affects which files are played)
Name preview
Perhaps to address some of your concerns, the user would select in the main wavelab window batch file list, which files they want to do advanced preview with… They could shift+click select a series of files, or ctrl+click randomly separated files - and then engage Advanced Preview.
Wavelab (not sure since which version) has a problem with preview in general, when a file is loaded into a process window it stays open within the process window, even when file is closed.
Batch Processor is used for files ranging from your present use case (one shot) to long files. Therefore the picture you post previously may not be applicable for lengthy files.
I would say there are basic features missing relating to file information in the Batch Processor - before anything else can be added to it -
1. Format, 2. Properties and 3. Length.
I agree with you that the existing preview is not very appealing as it only play files with plugins.
However, unlike the Audio Editor and Montage, Batch Processor is used only when you are certain about the outcome - Sample Rate Conversion etc. Therefore, it is wise to test 20 files and if that works for you, you can batch everything.
In the Batch processor, there is option to import master section plugins like how you have option in the Master Section to create Batch from a Master Section Plugins.
Batch Processor works Separate and is independent of the Master Section.
Now that you came up with this new idea of a preview, I think, like how WL has Shift+T to open Audio File in a Montage (Unsaved), if there was a way to render the original and the processed file to a cache - Unsaved Audio File Tab - as in the picture below…
The mockup I provided is obviously very basic, I’d expect the waveform preview windows to have sync’d zoom capability, as well as maybe even sync’d playback following when a use is playing files.
I’m a bit of an inverted soul , while I am using Batch Processor for menial tasks for expected outcomes - I’m big on using “boring” technology for creative results… So, I’m actually sort of interested and toying with utilizing Batch Processor as a creative tool and embracing uncertainty - batch processing swaths of samples with interesting FX, or finding interesting plugin combinations to give a certain sound to entire library of game assets.
If your workflow involves rendering interesting FX other than Normalize, Trimming, etc. you can import samples to Montage and use Master Section FX for this providing the number of samples are accommodated inside the Montage.
There are different ways you can organize files within the Montage without overlap.
This way you can Audition outcome for every file and render.
, while I am using Batch Processor for menial tasks for expected outcomes - I’m big on using “boring” technology for creative results… So, I’m actually sort of interested and toying with utilizing Batch Processor as a creative tool and embracing uncertainty - batch processing swaths of samples with interesting FX, or finding interesting plugin combinations to give a certain sound to entire library of game assets.