Issue when exporting from Nuendo / Cubase with option to "Open in Wavelab"

Hello,

I’m on Windows 11. I work with Nuendo (and previously Cubase) and very often will select to “Open in Wavelab” once I export a project for final treatment, checks etc.

This has never been a problem (it is in fact a very helpful feature). After updating to Wavelab 13 Pro, whenever I export multiple files from Nuendo in a single job (eg. marker regions, multiple tracks, etc.) the first file opens normally in Wavelab, but the next one triggers a separate instance of Wavelab instead of simply opening in a new tab as it should.

As mentioned, this is a new issue for W13 (Pro), I had no problem with W12. A fix would be greatly appreciated!

Thanks, this is noted for review.

Strange. Not seeing that here. By coincidence I was using ‘Open in Wavelab’ in Nuendo 15 multiple cycle marker export today and all files were automatically opened in a single instance of WL13 on separate tabs, as expected.

Did you consider this may be a Nuendo issue rather than a WL issue? What version of Nuendo are you using? What were the precise settings in the Export Audio Mixdown window (screenshot please)?

1 Like

No, it is definitely a Wavelab issue for me—specifically W13, it was working fine with W12. It happens both in N14 and N15 and it started when I installed W13. I tried reinstalling too but nothing changed.

I just did an extra check, exporting two marker regions on two tracks (so four files in total). The result was that I got two files to open in a proper Wavelab Pro instance, and two other files trying to start new instances, stuck on the license check.

I tried to hit the top-left “x” to shut them down and eventually I got a new instance of Wavelab Go, with the other two files.

Maybe this has to do with changing W13 to run a unified executable? I think that wasn’t the case with W12.

OK.

I guessed you meant you have set up Nuendo’s Export Audio Mixdown as follows:

  1. select ‘Multiple’ in the Channel Selection section
  2. select two audio tracks in the Channel Selection track list
  3. select ‘Cycle Markers’ in the Export Range section
  4. select two cycle markers in the Cycle Marker list of the Export Range section
  5. select ‘Open in Wavelab Pro 13’ in the After Export menu

After guessing the settings you were using I can now confirm the issue. Wavelab 13 erroneously opens multiple instances of the program if you are exporting multiple channels from Nuendo and using the ‘After Export’ menu to automatically open WL13 after the export operation (one of the instances of Wavelab seems to be Wavelab Go even though Wavelab Pro is being used in this test). In addition, after exporting the four files only two of them are present in the first instance of Wavelab!

Wavelab 12 doesn’t do this when performing exactly the same export operation from Nuendo. In Wavelab 12 only a single instance of the program is started and all four files are successfully opened, as expected.

@PG1 FYI, as you can see, there seems to be some kind of incompatibility or regression in WL13 when automatically opening files from Nuendo after export of multiple channels, in the above manner.

Apologies if I wasn’t clear. Yes, I mean exactly that, what you are describing in your updated post: A single export of multiple channels (eg. Stereo Out + Group A) across two markers, producing four files.

However I have made further some tests and can narrow it down.

If I have Wavelab open already then there is no problem and all files open in separate tabs in Wavelab, regardless of the complexity of the export job.

But if I have Wavelab closed then we have the following results:

  • If I export several markers of a single channel (eg. Stereo Out) there is no problem. The files are exported sequentially and the first file triggers the launch of Wavelab, with each new exported file opening in a new tab within.

  • If I export multiple channels (eg. Stereo Out + Group X) on the same region (or multiple common markers), at the end of the first job, which creates at least two files at the same time, the issue is caused. One of the files (whichever Nuendo designates “first”) opens Wavelab normally. The other file triggers a new Wavelab instance, stuck at the license check. Again, pointing out that these two (or more) files are created at the same time because they are from the same region and with the same settings—not part of an export que.

So, I’m concluding that the problem occurs when two files are generated simultaneously and both try to launch Wavelab at the same time.

Hope this helps.

1 Like