Bug Premiere Pro 2020 crash when changing sequence settings

[CHCHK]

In the latest version I'm able to crash Premiere every time I make changes to a sequences setting - e.g. put in a new frame rate, change field order etc.

[josefski]

This is still happening as of July, 2021. Feels like we're getting put on the back burner here.

[MikeJM]

Also happening to me. With 2020 & 2021 (15.2.0)
Here's a video of what happens; not much to it but if it helps:
https://vimeo.com/573286181/136da07824

I can't create a crash report because I experience a freeze/hang - spinning beach ball / "not responding" - I have to force quit, and no crash pop-up appears.

I sampled the process when the app freezes and have attached that file here.

[jasons60157258]

Thanks for the process sample, Michael (and sorry for the delayed response). This is a known issue that we haven't been able to tackle yet, unfortunately. I've increased the priority and will ensure that the fix will be in the next release (I'll post here once the fix is available in the beta builds). My apologies for the inconvenience.

[jerzero]

Its still happening here July 29 2021. OP posted Nov. 03 2020

[MMazor]

Same, latest version Mac

[Edit_aufSchnitt]

August 2021.
Still happening.
latest build, win10.

Please, just take out the "Pro" of Premiere, at least be honest.

[creynolds42]

Yes this appalling oversight/bug/error is still there and remains unfixed. Every session I try it. Every time it crashes.

[Naiosama]

Switch from 16/9 sequence to a 9/16 causes frequent crash and it's not a recent problem.

[jerzero]

Aug 11 i was excited to update to latest version today knowing it will fix the issue but still having the same issue. wow this is craz

[WeAreMoose]

Yeah, pretty ridiculous. Clients want 9by16 outputs and expects us to work with professional software to realize this very simple request..but..nope.

[ConnorB95]

How is this still not fixed?

[mfeijo]

Sept 2021 - Still constantly crashing every time frame size is changed - MacPro 2013 - 12Cores - 64G RAM

[M5ED9]

How is it still not fixed?

There's FREE software out there that has no issues with whatever sequence settings I give it but God forbid the software I NEED to use every day actually work.

Ryzen 1950x - 64GB RAM - RTX2080

[jasons60157258]

Sorry for the delay, everyone, but this issue is fixed in the latest beta builds and will be in the forthcoming official 22.0 release. Thanks!

[creynolds42]

When will this 22.0 release go up. This bug is debilitating. As professional editors working across multiple platforms, duplicating a sequence and resizing it is something we may do tens of times a day. The fact that this error results in a catastrophic crash every time is utterly unbelievable. Adding nonsense like fast export icons and translation to subs is fun for your developers and looks great in a press release but meanwhile a basic usability error drags all us daily users down.

It’s astonishing that this has dragged on and all with you full knowledge. Is it unsurprising that so many of us are eyeing a jump to Resolve as soon as is practical?

Think on. Then maybe think about loyalty and support.

[daveysheps]

Just bumping this, because by the time it is (potentially) fixed in the 22 release, it means for the WHOLE of 21 this never worked and never got patched.

These days, nearly every commercial I do requires social cutdowns. So for a 30" TVC, there will be a 15", a 10" and maybe a 6" at 1x1, 9x16 and 4x5. It really is jokes this never got fixed

[Derrick_Spruill]

Yeah, this is being a huge pain even with the latest update, it's still not fixed.

[Pukka Films]

This is still not fixed. How can a professional product be charged for when lacking basic functionality? This is a SUBSCRIPTION product, with glaring errors and sloppy code regularly disruption professional use. I hope the Adobe team realise this loss of faith and goodwill will be the demise of being taken seriously at all in the editing profession,

[John McCormack]

Wow...so Adobe can acquire Frame.io for a cool $1 billion but not fix a known bug for almost a year? This is the type of lack of urgency that's infuriating to professional editors and cause for my wandering eye towards Resolve.

Today when I tried to change the timeline settings and it crashed out I though maybe this is just another typical Premiere crash, I'll reboot and it'll be fine. Now I find this thread and you haven't addressed this since November 2020 almost a year ago now?

I don't think the admin understands the word "priority". I'd love to be able to tell my client what we've been told:

"This is a known issue that we haven’t been able to tackle yet, unfortunately." We'd lose clients pretty quickly if that's what we came back to them with. Reminds me of the arrogant AVID days of them dragging their feet on issues and look at them now.

Even a suggestion of a workaround would be nice.

[John McCormack]

OK, so I've received and email from Dacia stating the exact same answer given today but just you know...in an email. How does this help?

I'm not familiar with "Beta builds". Are you suggesting I download this? If so, would you provide a link to do so or am I supposed to hunt it down?

Again, poor communication and just a regurgitation of a "solution" which serves no immediate help to the problem. Please someone correct me if I'm wrong or reading their email incorrectly but yes, I would still love a solution and not just condolences.

[M5ED9]

I absolutely adore the responses I'm seeing on this thread, you guys make me feel less alone in my despair.

I have 32 variable aspect ratio exports that I need to make in the next 24 hours so I can make rent this month and this problem still has not been fixed. Should I tell my clients and my landlord that Adobe is working "really hard" on it and I'll get them what they need as soon as that happens?

Imagine the kind of outcry we would see if builders would be forced to "license" a hammer for a monthly fee with the promise that it's the last hammer they'll ever need. Then imagine having issues with those hammers literally breaking when trying to put in square nails.

Imagine that after more than a year ACME would come back to said builders and offer them a still under testing "beta" hammer that "should" address the issue.

Imagine if that solution ends up not working and at the same time making the use of previous versions of the hammer/nails incompatible.

Would you trust a beta version of a hammer with your livelihood when the production version is so broken?

Now imagine that there are only 4 major hammer manufacturers in the world:
One is hardware locked to unfriendly overpriced hardware
One works fine but is not accepted as a hammer on most building sites as it's a combination hammer and crowbar
One is THE hammer if you plan to hammer like it's 1995 and have two assistants to line up the nails for you just right.
The last one is made by people who just don't seem to care how usable their software is as long as we pony up the monthly fee.

It looks like I'll have to finish my work in Resolve FREE but after I might make a short about these 4 hammer companies and cut it on Windows Movie Maker as at least I expect it to be unreliable.

Do any of you know a good attorney? Are there grounds for a class-action lawsuit for loss of revenue/ unnecessary stress upon the consumer?

(Probably not because of the EULA being written by far better lawyers than the coders seem to be)

[Elaine5EC8]

I've been battling with this bug all year long and I'm absolutely sick of it.

Sort it for us all before my next months payment. Or I stop subscribing and pirate the software.

[DaciaSaenz]

The bug is fixed in the latest release of Premiere Pro 22.0.

Apologies for the frustrating issue.

[Davith Hegaard]

well im running CC2021 this isue appears to have resurfaced 😞

[juacoc892077]

Having the same issue with Premiere 22.0.0.
Specifically when creating a 9:16 sequence.