Creating marker causes waveform panel to scroll to start of file

[Martin Baker]

This has been happening for a few weeks. 

1. Select a portion of the file and press M to create a cue marker.
2. Waveform panel scrolls back to the very start of the file but playhead position does NOT change.
3. This is super annoying!

[SteveG_AudioMasters_]

You are not exactly alone in discovering this...

[zplateson]

I have a similar problem. It happens when i create a new marker OR when I edit an existing marker's length. The Waveform panel scrolls back to the last place I edited ( for example I silenced a breathe). It is super annoying and I didn't have this problem last week!

[SteveG_AudioMasters_]

We just have to wait for another update, or revert to the previous release...

[Stevan293611226w1q]

Have the same problem... Going back to an earlier version makes sense... thanks for the suggestion... 

[SteveG_AudioMasters_]

I think it's been fixed... and also I think I know why it broke. In all probability it's because of the change to the Marker system, allowing control of them from Multitrack view - just a slight teething problem.

[Martin Baker]

Why are we still waiting on a fix for this? I'm seeing lots of updates to other apps. Nothing for Audition.

[Stevan293611226w1q]

Unfortunately as of June 2 2023 it is not fixed... I like the newest features but can't stand the this glitch as I use markers frequently. Going back to a previous verson. Couldn't recommend this application for the time being.

[Kyle Hamrick]

23.3.0.55
Still happening with every marker adjustment. 😞

[Martin Baker]

So I just wasted almost an hour on chat with tech support because I wanted to see what the official progress was on this stupid bug. The 1st agent refused to try and replicate it on his system and insisted on doing a screen share session to see the bug for himself and then trash media cache and disable plug-ins before he just disappeared. Gone!

I then got a 2nd support agent who said that it was fixed in version 23.5 (but that isn't available to me as an update). He then said I should try the beta version (which I didn't even know existed) and in the 23.6 beta it is indeed fixed.

It would have been courteous for an Adobe employee to post back to a thread if a bug is confirmed and subsequently fixed in a beta version.