Jeremy Abbott
My feedback
-
76 votes
An error occurred while saving the comment An error occurred while saving the comment 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 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 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.
-
107 votes
-
6 votes
-
537 votes
-
264 votes
Thanks for all the feedback so far.
It is one of many areas we are looking into.
-
496 votes
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.
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