Delay compensation ignored on commit?

[HMA]

Does the timing of audio remain the same also on heavy delay compensation cases like committing an vocal track to WavesTune plugin.

A quick test shows that waveform moves along the timeline after commit. Or am I doing something wrong?

[Wall2Wall]

that would be unfortunate.

[HMA]

Originally Posted by HMA

Does the timing of audio remain the same also on heavy delay compensation cases like committing an vocal track to WavesTune plugin.

A quick test shows that waveform moves along the timeline after commit. Or am I doing something wrong?

If I put heavy plugins on the same vocal track, like waves tune lite, debreath and cla vocals , I can expect odd behaviour on committing the track. For example after committing to waves lite tune plugin cla vocals plugin dissappeared on the new committed *.cm track. And the audio was moved several samples earlier compared to the original ?????

But one possible reason might be that the delay compensation value is on dark red...on an instable condition i suppose.

[dankin]

No issues with Slate Trigger. Wonder if it's something to do with those plugins?

[HMA]

Originally Posted by dankin

No issues with Slate Trigger. Wonder if it's something to do with those plugins?

It is not the first time that long delay look ahead plugins are causing trouble. Debreath is one of those. Hope that in general there is no problem issue with committing to smaller latency plugins.

[HMA]

I had a lot of muted and heavy duty plugins in the track when problem appeared. After reducing the plugins even waves debreath committed right without problems waveforms in the same spot in the timeline as the original ones.

[connor@@vid]

We did a lot of validation in this area to make sure that things appear where they should. If the delay comp value is dark red it means it is beyond the maximum available amount of delay compensation so inaccurate compensation is expected. If you continue to have problems in normal conditions we'll need to get sessions (no audio needed) and attempt to reproduce issues internally. Thanks!

[johnnymacvkguitar]

Originally Posted by dankin

No issues with Slate Trigger. Wonder if it's something to do with those plugins?

I was using Slate Trigger and after committing my snare tracks they moved in my session and I found out the hard way with a client remarking the snare flams that were happening where they shouldn't be. They were committed and the time stamp is of course off from the original. How can I report this to AVID?
:-(

[H-Musikk]

Originally Posted by johnnymacvkguitar

I was using Slate Trigger and after committing my snare tracks they moved in my session and I found out the hard way with a client remarking the snare flams that were happening where they shouldn't be. They were committed and the time stamp is of course off from the original. How can I report this to AVID?
:-(

I experience the same with Drumagog...

[Pyxis360]

Hello all

I'm on 2019.5 and Mojave, committing tracks with a hardware insert creates an audio track that is out of time.

If listening in realtime it's fine.

I've tried everything. An empty project with nothing but a single track and a hardware insert, tried turning compensation blue, etc. Nothing.

Has there been any update on this?

Thanks