Neyrinck Soundcode LTRT Latency Issue

[digidub]

I've been using Soundcode LTRT for a number of years now, and been having a constant issue. The plugin strangely adds about a half frame of latency to ANY mix I process with it. In other words, there will be about .5 frame extra audio at the top, and the 2pop will fall at about 00:59:58:00.5

I've been manually fixing this for years, but its gotten to be a drag after a while. Does anyone else have this issue, or does anyone know if the new LTRT Tools fix this?

[mikevarela]

Yep, can confirm. Sucks huh?

and even worse, it's not exactly 1/2 frame so you can't just nudge back .5

i print tones before move so I can see where change happened.

[Nate Hoffman]

It's unfortunately not fixed in Tools. I have to move it back every time!

[TVPostSound]

Set your H/W buffer to 128 before printing.
Delay compensation will now work better.

I print my stems using (Anymix Pro Native) 5.1 DX MX FX PrintMaster and M&E. Downmix (Neyrinck LtRt Tools Native) to 2.0 DX MX FX PrintMaster, and M&E, down to Mono DX MX FX PrintMaster.
Delay compensation is all green and blue. Slight phasing between 5.1 and 2.0
low enough to pass NBC, and Technicolor QC.
On a TDM HD2!!

Now using my personal studio HDX system, offline bounce, my stems are sample accurate!!

[Nate Hoffman]

I should mention that I only have this issue when using the audiosuite Neyrinck encoder. Printing and bouncing seem fine.

[Rich Breen]

Perhaps you should send Paul Neyrinck a link to this thread? He's usually pretty responsive.

[digidub]

I tried contacting him via his website, but I get an error message when trying to send...not sure if he's receiving my messages.

Totally right, it's not exactly .5f so I also use the 2pop or tone to line up the audio and duplicate/re-render.

Perhaps I'll try to change my workflow and also print the LTRT with the stems/PMs.

I tried offline bounce on a feature last year and was getting digital clicks in the files so I haven't used it since, but perhaps I'll give it a whirl again in the near future.

[Rich Breen]

[email protected]