Batch Processor Crash

I open a few files on Wavelab, I close these file tabs, and I load these files in the batch processor, the batch processor stops on error. This is resolved when I close Wavelab and open again.


I also want Wavelab to remember my settings, including highlighting last opened folder, if I select Auto Select Source to render, the next time I open Wavelab, the box is reset to default.

Subject to what PG might say, I expect that the error is generated as a consequence of the ‘output as source files’ selection. If the file has been edited before being placed in the batch processor, the companion edit files that are created and auto deleted on opening a new project or closing WL 12 can likely prevent an overwrite.

1 Like

Or could this be possible because

  1. The file is loaded in cache of Wavelab or
  2. The Name Scheme default parameter has a bug?

In WL 12 my money would be on the ‘companion’ files. For example, you generally cannot change the title of a wav file in explorer if that wav has been previously edited (you can using F2 though). You can do so once a new project is opened or WL closed. So the behavior is kind of consistent.

1 Like

True there is no option to see files other than audio files in the file - open menu. In Wavelab 6, there was any file option where you could see even. word, .pdf .gpk Also there was option to save .gpk files in separate folder which was very organized.

The option for .gpk is still in WL 12

1 Like

Here is an example of what I am calling a ‘companion file’ (I am sure it has a tech name). This is created in the same folder as the file being edited and auto deletes on close of file, project or WL. (I can’t show you the complete folder contents as it’s a major label client … but the other files are wav)
Temp File Created

1 Like

Thank you but does the associated file mean all the associated files or only gpk?

I am not sure exactly what you mean but:

On my systems the gpk files go to the specific, separate folder nominated in the ‘specific folder for gpk’

Those ‘associated’ non gpk files seem to place themselves wherever the wav file is. An analogy would be the $ files that Word uses. There maybe a way to put them somewhere else but I haven’t found it and that would be of little use because they behave like Work $ files and are auto deleted.

1 Like

I see your folder name is gpk, not sure how only the gpk file is going there and neither Wavelab mentioned in specific than saying associated files.

Ha ha yes the ‘nominated folder’ is called gpk … old audio post habits die hard (call a file a name that identifies it).

Once you set that destination (as per the screen shot above) it behaves the same way as I remember WL6 did. The only gpk files on the system are in there.

1 Like


I assigned a folder to save associated files, and I see Wavelab is still creating companion files and is routing them to that folder. The software is creating drive specific folder inside the folder I assigned. Therefore, it is not just the peak files like before.

Before it was mentioned when we uncheck undo after saving these files will not be created.

This option still exists in WaveLab 12 and is even enhanced.

1 Like

Hi PG,

Thank you for writing. The folder is not exclusive for .gpk like before, and Wavelab is creating companion files in that folder. Also why is batch processing to source folder causing write protection error?

For consistency and simplicity, a common place is used. I don’t really see a need to have these temporary files written in different locations.

I can’t reproduce this (quick test). How do you do?

1 Like

As you can see from the second image in the post, I run 10 files in batch processor to the source folder. The files that were opened in Wavelab and closed before this batch processing stops on error. If I batch process to source folder without having opened these files, there are no errors.

The problem occurs if the file, or part of it, is copied to the clipboard. In this case, the file is still opened behind the scene and can’t be overwritten.

1 Like

It happens even when Wavelab is empty. I do not understand copied from clipboard is it Ctrl+C? (which i have not used) It also happens when the file is read and displayed below in file explorer. I tested many times and now I am temporarily using Wavelab 6. Once the file is read by Wavelab, unless Wavelab is closed, and re-opened the Batch Processor stops at error.

At position 00:17 in your video, you open the wave file 009 .wav in the file browser (you can see the waveform in the file browser). Then in the batch processor, the batch fails with 009.wav because this file is still opened in WaveLab’s file browser, hence can’t be overwritten.

Try again, this time using another way to insert your files, eg. drop them from Windows/Mac explorer, or use the standard file explorer. Then you won’t get the problem.

1 Like

It is the same result when opened through the batch processor file selector through the insert audio file menu. I am yet to try drag and drop from Windows. BTW is there any way to clear the recent folder history inside the batch processor insert audio file menu?