Version 23.5 is appalling. So crashy!

[Greg @ Caprice]

Why am I even paying for a subscription??

I am having to install an older version just so I can complete projects!

I see Adobe want to release version 24.

My first question is: will it be sorted out before it's released or are the subscribers Adobe's R&D?

If so, maybe Adobe should be paying us!!

I'm over it so my next question is, as a PP user, which aligns better with PP, Davinci or Resolve?

It's simply time to change.

[Carlos Ziade]

you can always have your current working version and the updated.

best to finish ongoing projects on working versions and start fresh new

projects on new versions. Whatever software you will use, be it Final Cut,

Resolve or else, better follow this same methodology: never update when still

in the middle of ongoing projects and on tight deadlines.

[Greg @ Caprice]

That's the problem Carlos. I'm not updating during projects. 

It simply struggles with new projects.

As for running two versions; 

1- takes up more HD space

2- what's the point of updating if the update is to be treated with caution? Why am I paying for a subscription?

I would beleive it's Adobe's job to test updates before release but it feels like they're releasing them and dealing with the bugs as they come through from subscribers who honestly don't have the time to deal with so many bugs, nor should they.

Appreciate the reply though. 

Cheers. 

[R Neil Haugen]

If this problem was "just Adobe" ... well, you might have a point. But as someone who also uses Resolve and is on the Resolve forums and LGG every day ... the problems "over there" are rather similar. And I think trying to build incredibly complex apps to attempt to work on multiple operating systems and an amazing array of hardware has inherent problems.

It's especially notable that I've had many conversations with users with similar kit & media to mine ... yet I wasn't able to replicate their problems. That's very frustrating, actually. But fairly common. Two users with similar kit/media/workflows have wildly different responses from Premiere. Which is maddening.

The vast majority of the several million daily users of Premiere are getting along fine. Why you are getting hammered is something that "we" peers here can often help with. Though not always.

They instituted the public beta to get a wider array of hardware/media/workflows testing the upcoming builds than with a private beta. And the beta can always be run alongside the shipping versions. So some thousands of people have already been working with the 24.x builds. Including I've spent some time there too.

From experience, I never update a program with current major projects underway ... unless I can do so without 'touching' those projects. And you can do that with the CC system. You can't with say Resolve.

I've got all versions back to Pr2015 loaded on my backup (older) machine, 2018 on my 'new' machine. They take what, 3Gb each, on a 250GB drive? Not even notable. But it means my older projects can be worked in their original builds.

Resolve ... no. You can only have one version installed at any one time. So when you update there, all projects have to be updated to the new version. Not a big fan of that.

[Greg @ Caprice]

Thanks for the insightful reply, Neil.

I'll try running both and see how that works. 

I've currently resorted back to a previous version which I know I've had no issues with.

[R Neil Haugen]

This whole thing can be so frustrating at times. Hoping you can get better performance.