audio playing ahead of waveform

[cascer1]

I recently received the update for Audition CC 2018, which I immediately installed because I like new stuff. And I have to say, I've been met with nothing but issues while using it since.

One of the most annoying issues that I'm facing is that audio playback for files recorded on my computer (this does not apply to audio files imported from elsewhere) is out of sync with what the indicator on screen would suggest.

Basically, I can hear audio about half a second before the waveform starts on my screen. In the image below, I can hear the audio where the indicator currently is, even though the wave doesn't start until a later moment.

However, when I go into the waveform editor by double-clicking the track, everything seems to be running in sync. Furthermore, I can select part of the track and remove it, and the correct piece will be removed.

I honestly have no idea what might be causing this, but it's making it very difficult to edit my projects like this.

I am running Windows 10 Pro, and this happened both before and after the fall creators update. My system has 16 GB of DDR3 memory, and all audio files are stored on an SSD.

[AndreiPopa]

was this solved? I am using the latest version of Audition on a Windows 10 machine.

Everything is up to date...

Tried to restart my device several times, opened, reopened the file. The problem still exists.

I think the problem happens after I add the Reverse Effect to a section of the Audio.

However, I can't make it go away now. Please advise.

[SteveG_AudioMasters_]

Do you have hardware acceleration turned on?

[Vasile Berde Luca Stefan]

I'm sorry to let you know that this still hasn't been fixed. Latest version of Audition, audio still plays ahead of waveform, with or without effects.

[mlautens]

Confirming that I have the same issue. Whatever it was, it's back. Audio plays off-sync with the waveform.

At first, it seemed to me that it might've been the sample rate of the audio file being different from the default sample rate on my playback device, but that's not the case. I match them now, and it still happens.

Windows 10, GTX1080 video card. All drivers and Windows patches up to date, oceans of RAM and disk space, no chance this is a resource issue.

[mlautens]

Adding in the information that this occurs on Windows 10, but on my MacBook Pro running the latest Catalina macOS, it's fine. Being bidigital, I just moved the file over to edit it there and no weirdness at all. (Hoping that's useful information.)

[averypel]

Yeah this is still happening for me as well and still has not been resolved?... Any updates?