Bug Issue: Premiere Pro 22.1.2 working with .mxf XAVC-I files
I've worked with these files fine in Premiere v15.4.1 and did not have this issue but since updating earlier this month to v22.1.2 I've had several issues with Premiere errors while editing and random crashes without warning or pinwheel of death.
Most common error is "Unable to access resource "SErrorXlND@2x'(type svg)" Attached screen shot below. Once this error occurs I almost always have to completely restart Premiere.
It also has made it nearly impossible to export a finished project from both Premiere and Media Encoder. When doing so it will hang up at some point in the export and create an Accelerated Renderer Error - Unable to produce frame.
The only way I'm able to export is by changing the render settings from GPU to mercury playback engine software only. That work around works for now but isn't great.
The issue is difficult to replicate. I've provided my computer specifications below.
Mac Pro 2019
3.2 GHz 16 Core Xeon W
128 GB Ram
AMD Radeon Pro Vega II 32 gb
We have determined the underlying cause of this issue and we're working on a fix for it. I don't have a date when it will be fixed but when I do, I will share it here.
Ian Servin commented
Encountered this issue as well, both on an M1 based MBP and my M1 based Studio. On one hand, i can't believe they've taken so long to address this critical bug after identifying the root cause, on the other hand, Adobe.
Hope it gets fixed soon, luckily our team runs both Windows and Mac machines so we can work around it but wow...
neo musica commented
Yes, This problem is SO BAD. I get this random black frames with Sony XAVC file (mxf). Our news show have so much problem with this. We are about to move to final cut pro or Avid.
Adobe, fix this bug!
Robert Cherouny commented
This is INSANE! I'm having exactly the same problem. 4 month old MacBook Pro M1 ProMax, 32G Ram (28 GB allotted to Premiere Pro and never run other programs while editing to be safe anyway), 2 TB internal SSD drive. All media on 4 TB Sandisk Extreme Pro USB C SSD drive (not even close to 1/4 full). Almost Nothing else on the machine. 4K MXF footage shot on Sony FX-9 is totally unplayable and uneditable once tossed into a timeline and then totally slow to even retrieve media for preview in preview window. Error Retrieving Frame messages everywhere on timeline playback. Usually edit 4K in 1920x1080 timeline and set 4k footage to frame size to allow punching in. Same problem whether or not footage is set to frame size or left at full 4k raster. Tried all kinds of fixes - turning off GPU acceleration, changing playback resolution (tried full, and 1/2), etc...Running on PP 22.5 and watching for every update. My late 2014 MBP worked way better than this trainwreck!!! Adobe, please help!!!
I think the solution is to move to Avid. Adobe doesn't really care about their professional customers. That's pretty clear.
crista rock commented
What is the update on this? I have 7 episodes of a tv show that are next to impossible to edit because of this bug with mxf files. No one at adobe is helping.
Does Fergus even work at Adobe anymore? WTF with the radio silence?
Thom Cookes commented
Sorry Fergus, just to clarify - is the underlying cause you have identified to do with Intel Xeon processors ? I'm getting this issue on both an Intel (Xeon) iMac Pro and an M1 Max MacBook Pro ... thanks, cheers
crista rock commented
Also happening to me! This is a big issue and it need to be fixed ASAP! The new update didn’t fix the problem. I have a 3.3 GHz 12-Core Intel Xeon W and cant edit with MXF files.
Jaron Henrie-McCrea commented
Is there an update on this? I just bought a new M1 Max Mac Studio with 10-core CPU, 32-core GPU, 16-core Neural Engine with 64gb unified memory and when editing 1920x1080 50Mbps long gop .mxf files from an SDD connected via Thunderbolt 4 in Premiere 22.4.0 build 57 I can't even scrub the footage without it becoming choppy. My eight year old iMac never had this problem. I'm forced to make ProRes proxies to have normal playback which is insane. Footage scrubs fine in FCP 10.6.3. so it's definitely Premiere.
Tim Koster commented
So the underlying cause was found around April 20th and 6 weeks later there still isn't a solution?
Got a new laptop last week after working 6 years on the old one and never having issues. Also used the latest software. But now with a silicon based model I can't edit more than 2 minutes before it notifies me of 'errors retrieving frames'.
Guess i have to film on a lower codec until this gets fixed.
I'm working on a macbook M1 Pro 16gyg
Doug Sand commented
Is there any update or workaround or even some advice?! You all should be making this a priority.
Jason Siriwardene commented
Taking too long
Jason Siriwardene commented
Pls FIX IT!
Piotr Kwasnik commented
SAME HERE!!! It's ridiculous! (Same errors with FX6 footage) Especially with the XAVC-L (XAVC-I) seems more stable.
Its impossible to edit some projects, this NEEDS A FIX ASAP!
Brendan McNamara commented
Any updates to this?! Absolutely ridiculous! How in the **** can you clowns at Adobe release a version as buggy as this! Adobe deserves to lose all of it's customers because this has just gone too far! Can't even do basic edits these days with this POS software.
Calle Johansson commented
Can't believe they haven't fixed this issue yet. It's almost impossible to work in Premiere at the moment.
Any ETA on a fix? This is a real project killer!
Edit 7 commented
Cool. Figure that out in a beta next time and don't release it as a "working", "updated" version with no option for paying pros to revert their project to an earlier, semi-stable build. What a trash amateur's app.
Just cut in Da Vinci. Or at this rate iMovie....
Todd Monnin commented
I am having the frame substitution error with MXF files in 22.3. It has become a real problem with multiple scenes on the timeline turning black with the first frame black video.
John Hartman commented
Yes. It's been happening all day.