Skip to main content
Participating Frequently
June 5, 2023
Answered

Close Premiere Pro native panels using extendscript

  • June 5, 2023
  • 1 reply
  • 880 views

Is it possible to close a Premiere Pro panel, such as the History panel or the Markers panel, using extendscript code running in a CEP extension? 

If this is not possible, is it possible from the CPP SDK?

 

Thanks

This topic has been closed for replies.
Correct answer Bruce Bullis

Yes, with the Marker panel open, ExtendScript-based marker manipulation suffers significant performance issues; thumbnails aren't free. 🙂

So, in my example above, you could 1. save the initial project with workspace, 2. open a different project containing a known (Markers panel-free) workspace, 3. fiddle with markers, then 4. re-open the initial project, and 5. close the different project. 

One much less complicated approach: Your panel could also pop a confirmation dialog (hopefully, containing a 'never remind me again' checkbox) that says something like "performance will suffer if you do this with the Markers panel open; continue?"

1 reply

Bruce Bullis
Community Manager
Community Manager
June 5, 2023

No PPro API allows for controlling the display of individual panels.  

closest available work-around = panels can control whether PPro opens the workspace contained within an opening project, so you could 1. Save the current project (which will include the current workspace), 2. Force ON the "change to the workspace contained in this project" pref, then 3. Open a project containing  a saved workspace. Bonus points for 4. Setting the previously active project active again, and/or 5. Offering to restore the saved state from the step 1 project.

 

Stipulated: not an optimal solution. 🙂

 

 

what's the actual workflow you're trying to support?

Participating Frequently
June 6, 2023

Actually I need this functionality in order to overcome an unwanted behavior in PPRO. If you add many markers to a certain track while the Markers panel is open, the UI freezes and sometimes the whole application can crash. I've reached the conclusion that closing the Markers panel before this operation imrpoves performance a lot and avoids the possible crash. That's why I want to close the panel during the operation and reopen it after the operation.

Any other advise? Maybe the PPRO team can comment on this unwanted behavior? Maybe I'm doing something wrong? I tried both adding markers in bulk or one by one and still I get the same behavior.

Bruce Bullis
Community Manager
Bruce BullisCommunity ManagerCorrect answer
Community Manager
June 6, 2023

Yes, with the Marker panel open, ExtendScript-based marker manipulation suffers significant performance issues; thumbnails aren't free. 🙂

So, in my example above, you could 1. save the initial project with workspace, 2. open a different project containing a known (Markers panel-free) workspace, 3. fiddle with markers, then 4. re-open the initial project, and 5. close the different project. 

One much less complicated approach: Your panel could also pop a confirmation dialog (hopefully, containing a 'never remind me again' checkbox) that says something like "performance will suffer if you do this with the Markers panel open; continue?"