Calling all Premiere CC users! Premiere pro is quickly becoming unreliable and more unstable.

I've checked out this update but I'm still having terrible captioning problems and the lag is ungodly. I'm still using 2018 for the bulk of my work but when I get a CC 2020 Premiere file from clients an contractors I get filled with existential dread because I know YOUR product doesn't work anymore without huge hang-ups. It's just too unstable. In conclusion, I'm done and my company and I are switching to a better NLA editor after our projects slow down around Christmas/the new year. Don’t get me wrong I will be sad to see you go and I desperately want you to get back to when you had stable programs, but as echoed above, I'd like to get work done instead of needing to problem solve and waste time with Premier's ever-growing glitches. 

Hoping that Resolve works better for you than Premiere has. Although ... I spend a lot of my time with colorists mostly based in Resolve. I know of shops that never found a single 15.x version of R stable in their shop, so ... they went from the last 14.x version to maybe 16.1.

And others, like me, who were stable all along.

I've also seen the massive bug lists on LGG and other places for heavy R users. Because that app is also being designed to do more things on a wider array of computing gear than before, and so ... it is also hitting issues the developers simply can't predict before the thing ships.

These are complex apps, and things even interact with other apps in the background in ways that obvioulsly vary machine to machine. Just glad I'm not an engineer.

Many of my colorist acquaintances are saddened or disturbed by R becoming an equivalent to the Adobe suite. As ... well ... colorist needs just aren't top priority for fixes anymore. They're just part of a larger group, including a TON of quasi-pro users that BM is marketing to. Who probably already outnumber the pro colorist users significantly.

Things change. And not always in ways that I prefer.

But always remember ... these apps are just hammers. Tools. Fancy hammers, ok ... but ... just hammers.

Use what works to get your stuff out the door to the nice clients who pay your bills.

Neil

Pr does have a team of beta-testers, like any other app. No idea how big it is because it's kept under wraps. But it's there.

This app is it seems the NLE that is used across the widest array of gear and media out there. User-base figures are rather high compared to any other pro NLE. For example, FPCx is only usable on Mac's, with that very tightly controlled and tiny range of gear that Apple has produced in the last few years. Resolve and Avid also have far fewer users. Most of them on carefully built video-post processing rigs. (As you probably are.)

And for all it's sins, Pr is supposed to try to work with nearly any footage out there, which no one else really tries. At NAB last year there were a lot of Pr users who also use other apps talking about maybe Adobe should back off the "we work on anything on anything" pledge and limit both the hardware and the media that is guaranteed to work, and make sure it is stable on only that hardware and that media. Anything else, try ... but the user is on their own.

I don't know what to think of that ... it would mean more stability probably. Maybe it's worth a thought.

You're clearly an experienced user, and ... I understand the frustrations. I've been there also, with one version a couple years back that simply would not run on my machine until they were two updates into it. But I kept working in the previous one, of course. And ... voicing a bit of impatience now and then. Very regularly "now and then" ...

Most of the engineers are also editors either professionally or for the joy of it, and pretty dang good. And they do take pride in their work. From talking with them at NAB, they get as frustrated as anyone when they can't nail something down. There was one Mac-only bug a couple years back had a lot of users saying clearly the engineers had no idea of working with Macs.

Well ... actually ... while they all do work cross-platform, the engineers are mostly Mac-folks on their own gear. But they couldn't repro the problem on any Mac they had access to. When you can't repro, it's darn hard to figure out what the hay is going on.

Which of course does suggest that perhaps at some point in their cycle a larger beta group might be useful. At least, to us users, it seems so. But being as we don't have a clue how many, well ... that's just a wild guess.

Hope they get this sorted.

Neil