Feature Request: Ensure an Adobe Premiere Pro update works without major failure

[Druidul]

I am an older video editor, I started in broadcasting and video editing in 2006. Never have I ever hated this piece of software like this before. I tried to learn other editing software but it is really hard at my age. Why can't you just make sure that the updates work? We are paying hard working money for this tool to work. Why do I have to tell my clients that I couldnt finish my job, becouse you are messing everything up, every update???? 

[edited by moderator] Your title was changed to reflect your actual issue and for search purposes.

[Media Editor]

If you are working on a project never update.

[Druidul]

True. But when there is a series and you take the last episode as a template and Premiere doesnt load it... and you have to make it from scratch.

[R Neil Haugen]

If you're doing episodic in the old stand-alone model, wow ... that's what Production mode was built for, and is a vastly better, more stable, more fluid, and more capable way to edit large projects.

Their documentation is probably the best docs they have ... I think because Jarle Leirpoll was lead author. 

Premiere Pro Productions Introduction

Using Productions in Premiere Pro

Adobe Long-form and Episodic Best Practices Guide 

Jarle’s blog expansion of the pdf Multicam section: Premiere Pro Multicam

For old style stand-alone workflows, migration works perhaps best if you ...

1) create a new project in the new version;

2) in that project, MediaBrowser panel, navigate to and right-click on the old version project file to select it;

3) in the dialog that pops up, select import assets.

That way you get a brand new project file correct for the new version, all the previous project assets loaded, and ... the old version project file is untouched and can be used if the new version build isn't working right for you.

And while I've certainly posted enough rants here myself ... some kinda epic ... if you tell us what ain't working, there's a fair chance someone here can get you going again.

[Kevin-Monahan]

Hi @Druidul,

I understand your frustration. I am both an editor and worik inside at Adobe. I'm also in my sixth decade on the planet, so I am sensitive to the needs of older editors, as I am one myself.

You may be surprised that not everyone has issues on updating. I think the reason is that many editiors have a routine that works for them when faced with an update. Mine is based on conservative approaches regarding my version of Premiere Pro, the project file I am working on, and the media that I am handling.

• If you are in the throes of a major project, avoid updating major projects to prevent project translation issues.
• Consider creating a Production. so that updating projects goes smoother since the projects are smaller than one large "granddaddy" project.
• If updating even a smaller project goes aswry, consider creating a new project and then import the contents of the previous project into it.
• Empy all media cache from the old project before beginning or updating any project for best results.
• Back up any workspaces, keyboard layouts, effects presets, etc., then reset preferences.
• You can reset preferences and delete all media cache by pressing Shift at launch to get the Reset Options dialog box. There are a number of troubleshooting options for you there.
• Make sure that your system is still meeting system requirements before updating. If not, update components to the "recommended" ones on the system requirements document.
• Go slow with the decision to update. Update the software only after a majority of other users have already made the move, so that you know the pitfalls. It is often not necessary to update the software unless a workflow bug or other issue is preventing you from moving the project forward. You might be able to wait for a more opportune time to update.
• Go slow also on the decision to update the OS. Again, wait unitl others have jumped into the new OS before you make that decision. When I find a good stable OS, I really don't like updating to a new OS unless forced. For example, I have not updated to macOS Sonoma yet on any of my personal Macs.
• These conservative policies around updating go against the grain of the subscription ideal, that is, updating to a new version of the software right away is what you are paying for. I say, "bite the bullet," and go with what works best now. You are the one that must protect that project file from becoming corrupt or non-functional. Doing anything whch may prevent the project from getting to the finish line should be avoided.
• These issues need to be considered for a smooth updating process, in my opinion. I learned many of these rules of thumb in Avid Boot Camp in the '90s. I continued them as an Apple employee and in teaching FCP. I brought these tips into the Premiere Pro realm and they work the same. The updating workflow I use has worked for me for a long while now.
• Why do you have to consider all these things with this application? It's because NLE apps are some of the most complicated pieces of software on the planet, containing millions of lines of code; many more than other "simpler" apps, so issues may crop up as a result.

I could probably add more tips, but these are the major things on my mind when updating. Plus, I am on a day off! 🙂 I hope the advice helps.

Thanks,
Kevin