Skip to main content
V
Vanja23926808h7qj
Participant
October 13, 2024

P: Premiere Pro 25 bug with "undo" and "redo" Set Property

  • October 13, 2024
  • 返信数 36.
  • 4834 ビュー

I have a problem with undo and redo commands since I've updated to Premiere Pro 25.00. Whenever I use CMD+Z to undo a step at first nothing happens. But when I use it a second time it does undo as it should. So I always have to double-hit CMD+Z whenever I have to undo a step.

 

The second problem is that the "redo" command doesn't work. It's also greyed in the "Edit" menu. I realized that when I hit CMD+Z once (and it doesn't work) the "redo" isn't grayed and it's available. But when I hit CMD+Z a second time to undo a step because the first time nothing happened the "redo" becomes grayed.

 

So basically every time I have to undo a step I must hit the "undo" command twice and I can never redo a step because of that bug. Does anyone have an idea how to fix this? 

    返信数 36

    前の返信を表示
    A
    abhijithasokan
    Participant
    November 6, 2024

    I have the same issue too. It's messing up my workflow.

      Y
      YvesSmelt
      Participant
      November 5, 2024

      Damn, I just realised I have the exact same problem @Vanja23926808h7qj, did you manage to resolve this somehow?


        Kevin-Monahan
        Community Manager
        Kevin-MonahanCommunity Manager
        Community Manager
        October 28, 2024

        Hello @Vanja23926808h7qj,

        Thanks for the message and welcome to the forum. The team might need more information from you to help you with the bug. See, How do I write a bug report? I appreciate you trying Ann's suggested troubleshooting step. I apologize that it didn't work. Here are a few other steps that might help resolve these problems:

        • Reinstall Premiere Pro: If the issue persists, try uninstalling and then reinstalling Premiere Pro. This can sometimes resolve deeper issues that a simple reset won't fix.
        • Check Keyboard Shortcuts: Verify that the keyboard shortcuts for undo (CMD+Z) and redo (CMD+Shift+Z) are correctly set in the Premiere Pro keyboard shortcuts menu. Sometimes, custom shortcuts can interfere with default commands.
        • Clear Media Cache: Press Shift at launch and clear the media cache using the Reset Options dialog box. Corrupted cache files can sometimes cause unexpected behavior.
        • Contact Adobe Support: If none of the above steps work, it might be best to contact Adobe Support for further assistance. The chat pod is on the lower right. After connecting with an agent, ask for the "video queue." They can provide more specific troubleshooting steps based on your setup.


        I hope these suggestions help you get back to editing smoothly! If you need more detailed instructions on any of these steps, feel free to ask. 😊

         

        I hope we can help you soon. Sorry for the hassle.

         

        Thanks,
        Kevin

        Kevin Monahan - Sr. Community & Engagement Strategist – Pro Video and Audio
        V
        Vanja23926808h7qj作成者
        Participant
        October 28, 2024

        I already tried to fully reset the preferences and it didn't solve the problem. But thanks for the suggestion. 

        Ann Bens
        Community Expert
        Ann BensCommunity Expert
        Community Expert
        October 28, 2024

        Try resetting preferences.

          T
          Tom_edit
          Inspiring
          October 13, 2024

          As of the latest beta build (25.1.0.045), cutting on the timeline causes a "Set Property" (I don't even know what that is..?) to also fire, which not only floods the history but also causes a tonne of lag if you're someone like me that uses a macro that effectively binds "Move Cursor To Playhead" to a mouse button.

           

          This "Set Property" seems to not fire until both the Left & Right mouse buttons are released, so if you are holding the playhead and moving it around for example and spamming 'S' (I have set to "Add Edit"), this behaviour will not occur until the mouse button is released.  Funnily enough, after you have done a cut on the timeline and the "Set Property" has also happened, using "Undo" to return before the cut point will also end up firing a "Set Property" after a short delay.

           

          In the event that the user is using "Move Cursor to Playhead" and they cut on the timeline, the resulting "lag" while premiere tried to catch up to the "Set Property" effectively locks up the user as they are unable to interact with anything until the flood of properties get set.

           

          I'm on Windows 11, I installed the v25.0 beta and the behaviour is not present. (nor is it in the public release of 25.0 now that that is available)

            T
            Tom_edit
            Inspiring
            October 14, 2024

            still happening in beta build 52

            契約条件Accessibility statement
            Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices