Jeremy Abbott

My feedback

  1. 89 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    45 comments  ·  Premiere Pro » User experience/interface  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Jeremy Abbott commented  · 

    By the way Adobe has acknowledged this bug and that they're working on it. They started a thread about it here: https://community.adobe.com/t5/premiere-pro/faq-how-to-solve-issues-related-to-undocked-panels-in-premiere-pro-v14-5/td-p/11529321?page=1

    An error occurred while saving the comment
    Jeremy Abbott commented  · 

    Gary Barlow, when you tried my workaround, did you close the floating window on your second monitor first? Just using the reset command doesn't fix it unless it's been closed. I forgot that crucial step this morning and spent a few minutes pulling my hair out trying to figure out why it wasn't working at first.

    An error occurred while saving the comment
    Jeremy Abbott commented  · 

    Actually just found a full workaround at least in the main forums. It requires your custom window layout to be saved.

    Open a project, then close any undocked panels/windows. Then use windows > workspace > reset to saved layout, and everything should work as expected.

    An error occurred while saving the comment
    Jeremy Abbott commented  · 

    Yes, just came here to report the same bug. The weird thing was everything worked fine on the first project I worked on with the update, but then when I started a new project the panels functionality was broken.

    This includes using the ~ key for the fullscreen shorcut. There is a workaround for this at least. Select a panel in the main program window first, then hover over the other panel window and use ~ to make it fill the window. Pretty annoying though cause you have to constantly go click away to the main window then hover back to make it work again.

    Really hope this gets fixed ASAP, this bug completely destroys my workflow.

    Jeremy Abbott supported this idea  · 
  2. 109 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    9 comments  ·  Premiere Pro » User experience/interface  ·  Flag idea as inappropriate…  ·  Admin →
    Jeremy Abbott supported this idea  · 
  3. 6 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  Premiere Pro » Editing  ·  Flag idea as inappropriate…  ·  Admin →
    Jeremy Abbott supported this idea  · 
  4. 571 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    69 comments  ·  Premiere Pro » Editing  ·  Flag idea as inappropriate…  ·  Admin →
    Jeremy Abbott supported this idea  · 
  5. 309 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    69 comments  ·  Premiere Pro » General  ·  Flag idea as inappropriate…  ·  Admin →
    Jeremy Abbott supported this idea  · 
  6. 519 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    49 comments  ·  Premiere Pro » Performance  ·  Flag idea as inappropriate…  ·  Admin →
    Under Review  ·  Reg Santo Tomas responded

    As Wes noted, we are looking at many areas for optimization and have made strides in the last few releases already.

    We recognize there are still many areas to improve performance and we are investing in appropriate areas.

    Threads that are catch-alls are often non-actionable. Please keep giving us specific feedback on what workflows are slow for you.

    Technical solutions may not always be as obvious as some people may be suggesting as the application architecture is often very different than people’s conception.

    Short answer. Yes, we want to and will make it faster.

    Jeremy Abbott supported this idea  · 

Feedback and Knowledge Base