"Go to next/previous marker" feature not working with clip markers in the timeline

@dorlyn27463922 ...

No joy, for my situation. In my circumstance, I receive a project with audio stems and sequence already baked in, via the studio. I already have "show duplicate frame markers" unchecked. There's definitely a glitch in there somewhere, which I hope they locate and fix sooner, rather than later.

Thanks for the added effort.

Randy

Happy ending (for now):

Adobe customer help said to do:

Audio preference - set to no input

Sequence seetings - set to custom

On sequence wrench icon - untick show duplicate frame markers ( as was suggested here before.)

Restarted and voila! 

chazs,

You describe well the importance of this function for your workflow. I believe the original bug has been fixed in 23.2, that a limited form was not fixed, and that there is at least one more scenario (Randy's issue.) Which particular issue are you still seeing in 23.3?

1) The official Adobe description of this bug, in the fixed issues for 13.2 was: "Fixed an issue that could prevent the user from moving to the next or previous marker via keyboard shortcuts after adding a new marker." I think that was too limited: a) This bug occured whether you used keyboard shortcuts (Shft+M/Ctrl+Shft+M) or if you used the Markers menu commands or an action added to the buttons in the monitor. Also b) it does not require actually adding a marker, the main condition is that there is a clip with at least one clip marker and that clip does not start at zero on the timeline. There was confusion about what was causing the bug, since you might not immediately see the problem.

So I'll call that bug "Previous/next commands do not work if there is a clip marker in a clip that does not start at zero."

2) I discovered with the fix in 23.2 that I was actually seeing a subset of that problem, that was not fixed. I was testing with duplicate clips, and was still seeing the same symptoms if I had "Show duplicate frame markers" turned on. With duplicate frame markers off, the next marker/previous marker commands worked correctly. I wonder if that has always been the case, so I just now tested this in 22.6.2. It does not have either problem, but behaves differently. If "Show duplicate frame markers" is turned on, the next marker/previous marker goes to all markers, but also stops at the beginning of any duplicate clip - suggesting to me that there is a "marker" that operates only if that is turned on.

3) I think Randy's issue is probably different from either of those two problems. He is able to go to markers (in the main bug you can't); "all key controls or shortcuts cease to function" (only next/previous marker commands were affected); and using an arrow key to move off the embedded marker allowed regular function to resume.

Stan

Here's a visul of what I'm talking about. You can see my markers in green at the top of the timeline. In this example, the embedded marker from the studio is shown on the individual audio stems (in cyan). When the studio has numerous markers throughout the timline, it completely slows down my ability to shortcut through my markers. When I'm looking at between a total of 2000' to 4000' of timeline (feet + frames @ 35mm), it gets quite annoying to have to stop and adjust for the embedded markers. (edit: That's about all I can safely post without jeopardizing my NDAs. Apologies.)

Tried all. No improvement. 😞

I just tried it...No joy! This is a serious problem it slows editing time conciderably. Why is it not the number one bug to be dealt with? What is adobe doing?

Any other suggestions? (macbook Mmax)

To start building more real stories in hopes to get rid of this issue - quickly - i'm a commercial / music video editor of 10 years who relies heavily on markers when picking selects. So much so that I don't cut my selects out anymore until I actual want to use something because each type of select has a color coded marker to let me know which predicament to use the select in. I usually only place the markers inside of the sequence unless it's a music video. When pickling selects on a performance that matches with the song specifically in a music video - I place markers on both the sequence and the clips so that when I line up all the performances in the master sequence I'll be able to see my markers there as well. 

To conclude, 90% of my editing experience is jumping through thousands of markers quickly to find my next shot so this glitch slows me down a lot - which means it slow my money down. 

Adobe has been great to me but this issue is truly a pain.

(On another note the playhead continues to take you where it lands other than allowing you to stay in your field of view. Has been years now smh.)

Stan,

I'm on v23.3, updated 2 days ago, so I believe I am current.

Randy

Randy,

Yes, thank you for that explanation. I am experiencing a different problem than you are.

What version of PR are you running?

@Kevin-Monahan Is Randy's version of the issue one that has been addressed?

Stan

Here's how the issue affects my workflow. I receive an "animatic" (.mov file) and audio stems for a cartoon production. The animatic and audio stems sometimes have embedded markers that the studio has used for their purposes. When I work on the project, I need a completely different set of markers that I use to identify scene breaks. My added markers appear above the timeline as normal. The studio markers are embedded and cannot be modified on my end. As I move forward or backward through my markers, If I land on one of the embedded markers, all key controls or shortcuts cease to function. If I use an arrow key to move one frame forward or backward, I can again use my shortcuts to move as needed. That is, until I come to another embedded marker, then it's the same song and dance. This didn't use to be the case. Yes, my shorcut would land on an embedded marker, but it would move right along as I hit the shortcut again. Now, I have to arrow key past the embedded marker to resume moving between the markers I have placed. Yes, it's still an issue, even after all the recent updates.
Hope this helps to explain what I am experiencing in my particular workflow.