Christian.Z wrote
For me it's working fine. Some people were reporting stability bugs, but most of them were solved by the regular preferences/Cache trashing, Or by optimizing their systems and workflows.
What are the specs of your system? Are you using a different software? or an older version of PP?
If you are using a different software, you can try PP for 30 days.
If you are using an older version I suggest the following:
1- Do not update if you have pending projects. Finish your important projects before updating.
2- When you update it, try it daily for 2-4 weeks, report any issues you might have, and If you did not feel comfortable, you can roll back to the older version.
Let me know.
I hoped that I implied that I was a full-time post pro in my Subject, so I wasn't looking for advice for amateurs. This is my 50th year as a full-time editor. I was an early convert to Avid, and did the switches to FCP and then PP CS 5.5 as they emerged as the better NLEs for people who didn't want to pay the ransom on an outrageously priced Avid dongle. So, I'm no babe in the woods as to jumping on the newest build without covering my butt. That's why I'm still using Ae and Pr CC 2018, as I've found them mostly reliable, except for the constant loss of Dynamically Linked clips from Ae in Pr.
That's a minor nuisance, although constant. I've done a lot of re-rendering and relinking in Pr. It's gotten to where I use the Replace with After Effects Composition in Pr, do my voodoo in Ae, render it, and replace the DLed clip in Pr to avoid constant re-rendering in Pr.
Christian, my system is as bold and bad as can be had on a cheesegrater MacPro 5,1, 128GB RAM, Titan X GPU, ATTO RAID5, 10.13.6 - which IINM, is the most powerful OSX hardware available if you want to maximize Pr's implementation of CUDA, and GPU in general.
The one thing I've noticed that will cause instability in this and prior versions of Pr is when I have a variety of codecs in my source media, especially crap codecs like AVCHD - highly compressed Long-GOP. Those seem to cause prefs corruption, and I have a routine for saving a clean set that puts me back in business when that happens:
Alias to enclosing folder on Desktop, with a fresh, virgin set of prefs in a zip file in that folder. Trash the bad prefs, unzip the good ones, and relaunch. Double-click the Project file while Pr is launching, and I'm back to where I was in about a minute.
Most of the projects I do with quality codecs from Sony, Panasonic, RED, Canon, Atomos, etc. have been very stable, with which I've had fewer crashes and prefs corruption.
If you all don't know about this free Pr Project Downgrader, you should. I may save your impetuous butts some day.
Premiere Project Downgrader - Free prproj Version Convert
IMO, Adobe should offer a script or utility that does this, instead of making us rely on the generosity of another user.
Thanks for the input from everybody!
Cheers,
Jim