Pr (beta) 22.0.0 (build 144) crashed on load of a project created with curent version (15.4.1)
I join the error message
"encontered an error."
On Windows 10 pro 21H1
Video RTX 2080Ti
(All in French langage setup)
If I open a new project every thing worked fine.
I have same issue this morning. I found that if I don't click on the message I can continue to do somethings with the project file. I have to relink the sony camera files since they don't load. If I remove all my Sony A7S-3 files from the project file it will then open with no issues. Cannon footage loads fine, can't get it to work with Sony files.
windows 10 home
Ryzen 9 5950X
Able to work around it by importing everything into new project file, then opening old project file and copy sequence to new project file with "allow duplicate media during project import" in media settings disabled.
That's what I tried to do but I got same error the minute I imported the old project into the new project
SAME ERROR ON MAC MINI M1 using sony a7s3 footage
Having the same problems as all above.
Sick and tired of this, every update is a drama!
I am with a super tight schedule to finish a project and now this.
Feel your pain Yugo. I also had a deadline I missed this morning.
Forced to use this beta as v15 wasn't working on M1.
Premiere needs to be rebuilt from bottom up, constant dramas and so slow compared to othe NLEs. Pity as all other Adobe software works well
It´s an absurd and a total desrespect to their users.
I am running on the same specs as yours. Have invested a lot of money on upgrading my gear and now my workflow is even worse than before, forced to be on a beta version of Premiere so I won´t get glitchy images.
Feels like you gotta live on a cave to be on the same page as Premiere.
Any other solutions found yet also on a very tight schedule and can't make it work on 22.0
Mate, if you´re working with 2 monitors, move the error messages to a corner and just keep working normally as if they were not there, that´s how it will do for now. I am editing, saving, rendering etc. So far, so good.
Eventually, Adobe will take action to actually be a top software developer and will get their sh*t together.
Just remember to get a comfy chair while you wait for that.
Well I can't even see my files they are named as media missing ... I want to kill myself
Really thinking of moving to Davinvi since I'm already colorgradding in that program
dam that doesnt work for me, thought i maybe able to export xml and run to resolve
Hi, everyone. Sorry for the inconvenience, but this issue is now fixed (in tomorrow's beta build).
same problem/error my side
Process: Adobe Premiere Pro (Beta) 
Path: /Applications/Adobe Premiere Pro (Beta)/Adobe Premiere Pro (Beta).app/Contents/MacOS/Adobe Premiere Pro (Beta)
Version: 22.0 (22.0)
Code Type: ARM-64 (Native)
Parent Process: ??? 
Responsible: Adobe Premiere Pro (Beta) 
User ID: 501
Date/Time: 2021-09-21 07:08:43.239 +0200
OS Version: macOS 11.5.2 (20G95)
Report Version: 12
Anonymous UUID: BF5CA96D-6760-F634-DB3A-4C1143E906C5
Time Awake Since Boot: 880 seconds
System Integrity Protection: enabled
Crashed Thread: 53 Dispatch queue: com.apple.root.utility-qos
Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Exception Note: EXC_CORPSE_NOTIFY
also doesnt work with macOS 11.6 update
I updated my m1's IOS yesterday, should I bother downloading premiere beta´s update?
Im really worried this would make things worse, for I managed to work around with the app by ignoring the error messages
didnt work for me Yugo
M1 iOS 11.6 update and Premiere Beta 22 build 147
Yeah, still not working
Just made the update and its not fixed ...
Same issue happening here, with the same four errors. I don't have a dvaeng user on my machine either.
The 'dvaeng' user is from the build machine on which PPro was made; it'd be pretty surprising if you had a 'dvaeng' user on your system, as well.
DVA = Digital Video and Audio apps at Adobe, eng = Engineering.