Marker Dialogue Box automatically opening whenever I Add Marker

[maxa62701748]

Using CC 2025...whenever I add a marker while the playhead is paused, it automatically opens up the Marker Dialogue Box (where you can fill in comments, etc.) This is a bit annoying, as I have to close it each time. Usually in the past, I would have to click the add marker shortcut (M in my case) twice to open the dialogue box. Any reason why this is happening?

[IanB_360]

Hi @maxa62701748 

Welcome to the Premiere Pro forums! To better help you on this issue, we need a few more details to try to help with the issue. Please see, How do I write a bug report?

Could you possibly add a short reference video on the message board showing us the issue that is happening ? It would be extremely helpful to us solving the problem.

Thank you

Ian

[kg77]

I am experiencing the same issue. I have filed a bug report, and included a GIF screen recording.

https://community.adobe.com/t5/premiere-pro-bugs/keyboard-shortcuts-for-markers-are-doubling/idi-p/1... 

[Stan Jones]

@maxa62701748,

I am not seeing this on Win10/PR 25.0.0. The marker is added without the dialogue box opening, whether I use the "M" shortcut or the menu system - Markers -> Add Marker.

I see that there is a shortcut (with no default shortcut set) for Edit Marker. But I think this would just not work if it were assigned to "M".

If you add using the menu command, do you get the same result?

Stan

[kg77]

I just switched to default keyboard shortcuts, and they work fine. So it appears that it's specifically the custom shortcuts that are triggering the action twice.

[kg77]

It appears that someone else has already experienced the same problem, so this isn't just me: Marker Dialogue Box automatically opening whenever I Add Marker 

I first noticed that when I hit my keyboard shortcut for "Add Marker," it would add a marker to the timeline, and then automatically open up the dialogue box for that marker. Every time I add a marker, I have to close this dialoge box before I can continue editing.

Additionally, I noticed that when using my keyboard shortcuts for "Go to Previous Marker" or "Go to Next Marker," the playhead would jump two markers intead of just one. It appears that whenever I hit one of these keyboard shortcuts, it's registering as if it's happening twice.

I am using Premiere Pro 25.1 on a Windows 10 computer. Below is a GIF screen recording of the issue.

[kg77]

Oddly enough, this bug doesn't appear to apply to every marker-related keyboard shortcut. I have different shortcuts for adding different marker colors—some work correctly without bringing up the dialogue box, and some don't. I'm finding that green and yellow are glitchy, but red and white are not.

[Warren Heaton]

Sounds like pressing the M key on your keyboard is registering as M bring pressed twice rafter than once.

 Do to have another keyboard that to can try as part of the troubleshooting process?

[kg77]

I actually have custom keyboard shortcuts, so it's not my M key. But in the above GIF, there are multiple different shortcuts that are messed up, each using different keys.

Add Marker = *
Go to Previous Marker = Page Up

Go to Next Marker = Page Down

All of these acted as though they were pressed twice, not once. So I don't believe my keyboard is what's at fault. (Especially since I found another Adobe user who was experiencing the same thing.)

This bug only started happening after I upgraded from 24.4.1 to 25.1.

[Warren Heaton]

I'm not able to reproduce it with the default shortcuts with Premiere Pro 2024 or 2025 under macOS or Windows.  Placing markers, opening Edit Marker, and going to the next or previous marker work as expected.

Two of the systems are Mac based, one is an HP zBook Studio.

[kg77]

What version of Windows are you running? I'm on Windows 10.

[Stan Jones]

@kg77,

This is odd. Thanks for the screen recording and good description.

In the other thread you linked, I tested with Win 10 PR 25.0.0 using only the "M" shortcut. I could not replicate. I am waiting to finish a project before updating to 25.1.

If you add using the menu command, do you get the same result?

Stan

[kg77]

When I used the "Add Marker" button in the project monitor, it worked just fine. So it seems to specifically be an issue with the keyboard shortcuts.

[Stan Jones]

@kg77,

If you switch from your custom shortcuts to the Adobe Premier Pro Default shortcuts do you see the problem?

Stan

[kg77]

I just switched to default keyboard shortcuts, and they work fine. So it appears that it's specifically the custom shortcuts that are triggering the action twice.

[Stan Jones]

@kg77,

> it's specifically the custom shortcuts that are triggering the action twice.

Sometime back, one of the updates resulted in issues with the shortcuts. Custom setups required being recreated. If you did not do that after the recent install, I would give that a try. Start with the default and add a couple of the problem ones and save that new custom set. If they work, I'd redo all your custom shortcuts.

Stan

[jamieclarke]

Hi @kg77 - Do you see this issue if you reset your preferences?  

[kg77]

I just switched to default keyboard shortcuts, and they work fine. So it appears that it's specifically the custom shortcuts that are triggering the action twice.

[kg77]

@Stan Jones @jamieclarke So, I'm not 100% sure what I did, but the shortcuts are working fine now. I switched to default keyboard shortcuts to see what would happen, and those worked (as I said somewhere on this thread), but then just now after a few days I switched back to my custom shortcuts and they're working fine. So... problem solved? haha Thanks for your help, I'll let you know if there are any changes.

[Stan Jones]

@kg77,

Thanks for reporting back. Yes, let us know if this happens again.

Stan

[kg77 · Accepted solution]

I just created a new document, and the keyboard shortcuts started acting up again. I tried switching to default, and default shortcuts worked. I switched back to my custom shortcuts preset, and it still didn't work. I'm remaking my keyboard shortcuts now, and the new set I'm making seems to work fine so far.