Skip to main content
D
default2bitbh9ctgcd
Participant
March 28, 2023
Question

Premiere Pro V23.1 Source monitor Bug

  • March 28, 2023
  • 1 reply
  • 267 views

Hi All,

 

We have upgraded a large number of our Premiere Pro versions to V23.1. However, it has been raised a few times with us, that when you are playing something in the source monitor and try and click away, the application will not allow you to. To click anywhere else you have to stop the source monitor before continuing, adding uneccessary time to an edit. 
Additionally, when viewing media in the source monitor and switching to the audio clip mixer, as soon as you hit the spacebar to play the media, the clip mixer panel closes / reverts back to the source monitor. 
After testing and reproducing the error we wondered if anyone has experienced it, or if you know a way to resolve it? 
We have raised this on the public forum with no luck. We wondered if maybe it was resolved in the next update, or if there is something we can change to lessen the effect on the editors?

Thanks,

Emma

    This topic has been closed for replies.

    1 reply

    Kevin J. Monahan Jr.
    Kevin J. Monahan Jr.
    Legend
    April 10, 2024

    Hello @default2bitbh9ctgcd,

    Thanks for the message. It’s been a long time since you filed this bug, and I apologize for the lack of a response. Are you still having this issue? If so, the team will need more information from you to reproduce the bug. Can you provide the information required here? How do I write a bug report?

     

    I'll move your post to the Discussions board while we await your information.

     

    Thanks,


    Kevin

    Kevin Monahan - Sr. Community and Engagement Strategist – Adobe Pro Video and Audio
    D
    default2bitbh9ctgcdAuthor
    Participant
    April 10, 2024

    Hey Kevin,

     

    Thanks for the reply. Honestly it has been so long I forgot I posted this. It was an oficial bug, but has been resolved in a point release by Adobe. The newer versions (starting at 23.6) has this resolved. We resolved it for our teams when we rolled out the upgrade. 

    Terms & ConditionsAccessibility statement
    Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices