Round trip latency detect not working in WL11...is it fixed in WL13?

WaveLab
1

I’ve not been able to get any delay compensation working in WL11, for using the External Effect plugin. Using the “detect” function changes the shown delay time, but does not actually adjust anything. This makes outboard gear unusable in the montage tracks for tasks like parallel processing. Direct monitoring is off.

I’ve tried all settings in WL and interface control panels. I have multiple interfaces (Neve 1073dpx-d, Cranborne 500R8, a few Tascam interfaces, etc). The problem happens identically with all of the interfaces.

I also have Cubase 13 and 14, and the “measure delay” function for the External Effect plugin works perfectly. Absolutely zero problem with Cubase using the same functionality.

After much research, I’m still unsure of why this is happening, or if it’s a bug with WL11 that has been fixed in the current version of WL13 or not. Would gladly update to WL13 if this is no longer an issue.

Any insight/shared experiences or advice?

2

Wow, not a single response? Not a single person having similar issues?

Delay detection in the External plugin window does NOTHING, making it impossible to use outboard parallel processing in Wavelab 11.

This is a MAJOR issue, ffs.

3

@PG1 can you help with this?

4

I recommend using the External Gear plugins only in the master section, for best results.

5

I’ve been chatting with tech support about this issue, which they have confirmed:

WaveLab does implement automatic latency compensation and is intended to support latency-compensated playback and rendering. However, there are multiple forum reports (including your own) involving an External FX plug-in where measured round-trip latency appears not to be applied correctly during playback or parallel processing. Since the identical hardware setup works correctly in Cubase, my thinking is that this is a WaveLab-specific issue or limitation within the External FX implementation rather than a general delay compensation difference between the products.

So basically, the 13th version of Wavelab STILL cannot do any parallel processing with outboard gear. Absolutely ridiculous.

Using the External Effect plugin in the master section is also really bad, with “skipping” or “echoes” when starting playback, and a delay between the cursor position and what you’re actually hearing that makes any editing or pinpointing of any issues in the waveform nearly impossible.

Hard to believe a “professional” mastering program is in this state in 2026.

6

Thank you for your reply. That is the only place I have ever used them but I still can’t get the latency detector to work. Also, the latency slider has zero effect when I move it manually. Is there a solution?

7

OK, let me in on this. I’m using WL Pro 13.0.3. Within the ExtFX Send/Receive Latency ‘popup’ panel I am told that there is “No Audio Bus Defined” (located ust below the Audio Bus description, along with an option to post a picture it seems).

I have signal displayed in the Send/Return meters in the panel but every control is greyed out. And there is definitely some latency. Audio is fine, routed for playback.

Win11 262H (latest update), MOTU M6 interface (latest Driver/Firmware). WL finds my various outputs and labels them correctly. Q: Is using the ExtFX MOTU in WL still a bust, PG? Is this my problem?

As in the past, it works in Cubase Pro (15.0.30) no problem, 0.06 ms.

8

If these 4 ports are defined and are not used elsewhere for recording or playback, you should not have this message.

image
image824×641 23.9 KB

9

Well, after reading your post, PG, I opened WL and everything worked as it should. (I’m thinking restarting my PC played a part (?), something I forget about.) Thank you for the reply, your attention is always appreciated.

WaveLab 13 is a program that never fails to deliver great results, PG. (BTW, I’m running the latest Win 11 update, 262H - with no issues.)