bug Track Desync, Wrong Latency (Delay Compensation)

[Yudaidhun]

Hi, I found the bug in latency compensation which cause desync between tracks.
Here is what I tried:

[Working Corrently 1 - In Sync]
TrackA : Instrument (no latency) + FX (has latency)
TrackB : Instrument (no latency) + FX (no latency)

[Working Correctly 2 - In Sync]
TrackA : Instrument (has lntency) + FX (no latency)
TrackB : Instrument (no latency) + FX (no latency)

[Not Working - Desync between A and B]
TrackA : Instrument (has latency) + FX (has latency)
TrackB : Instrument (no latency) + FX (no latecy)

It looks like issue happens only when both Instrument and Inserted FX plugins have latency.
Probably, FX latency is ignored in calculation when Instrument  has latency.

I hope this information is  enough to reproduce.

Using latest version of Cakewalk.
Tested on several computers, several plugins by different dev, several audio interfaces with ASIO.
I think this didn't happen in the old version of Cakewalk (or SONAR) but I'm not really sure.

[John Vere]

Not sure how you tested you don't say. Did you use a loop back test? 

https://oblique-audio.com/rtl-utility.php    This utility can be used to see if Cakewalks report matches correctly. 

It's a good idea if your curious about this topic. 

Generally 99% of the time with a good ASIO driver you will find the timing is almost right on. Close enough to not be an issue. Down to the sample level.   

But when I tested other driver modes sync was off by as much as a 1/4 note.  MME mode is the worst. 

This is why ASIO is important to overdubbing audio. Nothing else will be accurate.

Its all about the driver reporting correctly to the DAW so the DAW can adjust playback and recording sync. 

But if your finding an issue this would be a huge problem that the Staff at Cakewalk would need to deal with.

I've got to go to work but tonight I'll post a loopback test to show you what I do to test.

I have 4 ASIO audio interfaces including a brand new Motu so I was going to do this anyhow. 

Edited February 12, 2021 by John Vere

[John Vere]

Delete post. I see you talking about VST’s not Audio 

Edited February 13, 2021 by John Vere

[Bruno de Souza Lino]

I'm gonna suggest that these are probably caused by CbB sort of prioritizing drawing graphics over processing audio. If you start having too many visual elements on screen at the same time, it starts to become slow to respond. This tends to happen at the Console view quite a bit.

[Noel Borthwick]

On 2/12/2021 at 7:24 AM, Yudaidhun said:

Hi, I found the bug in latency compensation which cause desync between tracks.
Here is what I tried:

[Working Corrently 1 - In Sync]
TrackA : Instrument (no latency) + FX (has latency)
TrackB : Instrument (no latency) + FX (no latency)

[Working Correctly 2 - In Sync]
TrackA : Instrument (has lntency) + FX (no latency)
TrackB : Instrument (no latency) + FX (no latency)

[Not Working - Desync between A and B]
TrackA : Instrument (has latency) + FX (has latency)
TrackB : Instrument (no latency) + FX (no latecy)

It looks like issue happens only when both Instrument and Inserted FX plugins have latency.
Probably, FX latency is ignored in calculation when Instrument  has latency.

I hope this information is  enough to reproduce.

Using latest version of Cakewalk.
Tested on several computers, several plugins by different dev, several audio interfaces with ASIO.
I think this didn't happen in the old version of Cakewalk (or SONAR) but I'm not really sure.

@Yudaidhun Which instruments specifically are you using that have latency? By definition VST instruments are not supposed to have lookahead delay since it will be impossible to play in real time. Cakewalk has traditionally assumed that instruments do not have delay so this is not new to CbB.