Skip to main content
Known Participant
February 27, 2024

P: Frame substitution attempt aborting error - .MXF Files Fixed in version 25

  • February 27, 2024
  • 110 replies
  • 47868 views

UPDATE 10-14-24:  

MXF file frame substitution errors has been fixed in version 25 of Premiere Pro 

 

---------------------------------------------------------------------------------------------------------------------------------------------------------------------

I've seen a number of posts about this, and am now running into the problem myself. Although there are a few differences I'd like to share that I'm hoping may shed more light on what appears to be a longstanding issue.

 

Specs: M3 Max Macbook Pro (64GB RAM), Sonoma 14.3.1, Premiere Pro 24.1.0

 

The .MXF files were shot XAVC-I from the Sony FX6 shot on a V90 card. I copied the entire memory card structure to my internal drive, and imported the clips using the media browser. The clips are 59.94 fps and 23.976 fps on a 23.976 timeline.

 

As I perform regular editing tasks (slowing 59.94 clips to 40%, adding clips to timeline, scrolling through), I get these error messages.

 

BUT, here's the kicker: I'm not actually seeing dropped frames yet. For one of the clips I received the error on, I decided to go to the source window and scroll through frame by frame. I didn't see any black frames, but scrolling through did create 9 new error messages at different frames.

 

Aside from the error popups being annoying, this is a project that many people are depending on. If these dropped frames actually do end up showing, I'll be in a bad spot. It seems as though with every new project, I have to factor in at least a day to deal with errors or bugs in Premiere. I shouldn't have to be constantly fighting with the tools that allow me to do my job. Moreover, the C70 and FX6 both shoot in .MXF and are fixtures of video production. Frankly, I'm taken aback that there hasn't been more meaningful support from Adobe on this.

 

I'm currently creating ProRes Proxies to see if that may solve the issue, but I'm concerned that this will only solve the problem in editing, and the error (dropped frames) may show up once exported.

 

Does anyone have thoughts on why this may be happening? Is it time to switch to Resolve like everyone seems to be saying, or could this be a workflow issue on my end?

 

Many thanks!

110 replies

Inspiring
March 20, 2024

I have the same problem as posted here. You can read my reply. When you need Sony FX6 Footage just let me know.
Maybe the footage is not the problem. I also have the frame substitusion message with other file formats.
Has never been a problem. I think it is since the last update.

Inspiring
March 20, 2024

Same here with footage from Sony FX6 Camera.
One layer of video is fine.
When I layer the same clip over it, the trouble begins.
Many frams substitution messages. Laggy response. 
I have a monster PC and a very very fast NAS. Never been the problem.

When I can be of any assistence by sending footage, let me know.
Best regards, Christiaan.

steves2019
Participant
March 12, 2024

After updating to Premiere 24.2.1 from 23.6.4 there is now a delay of approximately 2-3 seconds after hitting the play button when working in the timeline.  Also, there is the "error retrieving frame" alert popping up from time to time.

 

Important to note is I am able to playback and edit the exact same footage in version 23.6.4 with no issues at all.

 

The issue seems to be unique to footage coming off the Sony Z280.

Footage properties:

Image Size: 1920 x 1080
Frame Rate: 29.97

AVC Long GOP High 4:2:2 Profile 10-bit Unconstrained Coding
Bitstream Format: Sony
Class 35

 

Again, no issues with this footage in Premiere v23.6.4

 

Just adding to my last post that footage from the Sony FS5 is behaving the same way.  HD 29.97 mxf format , class 35.  Footage from Nikon Z50 is fine, as is footage from the Blackmagic Pocket 4k.

 

System specs:

Windows 10

AMD Ryzen 9 3900X 12-Core

63.9 GB of RAM

Nvidia RTX 2080

 

Any assistance would be greatly appreciated.

 

 

 

 

 

jamieclarke
Community Manager
Community Manager
May 16, 2024

Hi Steves,  If you are able, can you install the Beta 24.5 and see if that helps your problem?

WesHowellPPro
Adobe Employee
Adobe Employee
March 6, 2024

Thanks Neil - I'll see if I can track that down. Investigating...

R Neil Haugen
Legend
March 6, 2024

Wes, you've probably noted that this has popped up on the Facebook pro editors forum also.

 

Neil

Everyone's mileage always varies ...
Known Participant
March 6, 2024

Hello,

same here, Windows 11, Premiere 24.2.1. (Build 2)

Mxf - drops, errors

Timeline - not responsive, freezing

Participant
March 6, 2024

Hello,

 

Same here, MXF import to Premiere will appear message "Error retrieving frame from the file".

 

Thank you for your help

 

 

WesHowellPPro
Adobe Employee
Adobe Employee
March 4, 2024

Hi Anthony,

Sorry you are experiencing some issues here.
I work on the Pr engineering team. Would you mind sharing a sample file or two with me?  If you'd like to send me a PM, I'm happy to chat further.  

Cinema Físico
Known Participant
February 28, 2024

I have just bought a brand new Macbook M2 Pro 12 CORE 19 CORE GPU 16 ram mac os Sonoma 14.3.1. Instaled Premire Pro Version 24.2.1 (Build 2). I am editing project with Canon C70 MXF avci, 4096x2160, 23,976 fps, in a 1920x1080 sequence.

 

I have been working for 8 hours and I received 20 alerts saying " Error retrieving frame" and 1 alert saying "Frame subsistitution recursion attempt aborting aftre multiples attemps on file". And also sometimes the palyback gets slow. I am only using 2 videos tracks, one sound track, no .jpge, no .png, no motion. I am just begining my edit. So I am just cut, delete, copy paste clips, adjust some clips scales and position, 1 lumetri with a input lut, no speed change, no 3rd part plugins, full playback mode, one external monitor, my footage is in a external ssd in a thunderbolt 4 port.

 

Before buy this new macbook, I work in the last intel Imac with Premiere 23 and never get this alerts. And the playback was bit better than with this brand new macbook.

 

What is going on? Is it a bug? Am I doing anything wrong? What should I do to get a better perfomance?

 

Thank you.

 

 

Fernando AlvesEditor
Adobe Employee
February 29, 2024

@Cinema Físico Thanks for reporting this issue, can you please try your project with latest beta build of PremierePro and check if it is working fine for you or not? 

 

Regards,

Khyati Gupta 

Juerg5CF2
Known Participant
February 27, 2024

Hi all

 

I have done plenty of projects in the last 12 months with Canon C70 and R5C MXF long GOP footage (2160p, 25 fps, 4:2:2, 10 bit) without having seen a single error message popping up in Premiere Pro on my Windows 11 PC. 

 

Today, a customer of mine asked me to continue working on a bigger project, where we started filming in July 2022. When I imported the Canon C70 and R5C long GOP clips (> 200 clips) from back then, everything seemed fine first. But as soon as I started to put e.g. a lumetri on it, recursion and many retrieveing frame error messages started to pile up!

 

After having tried many suggestions offered in this forum and elsewhere, I spent hours with Adobe support on remote desktop with no solution. They advised me to transcode with handbrake, I tested it and yes, it works, but I can only choose one audio track out of my 4 and there will be a quality loss and another huge data pile. 

 

I tried the proxy workflow with a couple of files and so far and fingers crossed, I have not gotten a single error message!

Funny thing is, even when I toggle the proxy off and work on the original file, I do not seem to get an error message.

 

Does anybody know what is going on here? This is really weird.

I was using exactly the same format on both of my cams back then and these days, yet newer clips work perfect and the older do not.

 

Thanks for any help,  much appreciated, also because I am on a tight schedule.

Juerg

 

AMD Ryzen 9 5900X

NVIDIA GeForce RTX 3090 V 546.01

128 GB Ram

Windows 11, 10.0.22631

 

Inspiring
February 27, 2024

These are official file formats of cameras sold for professional use, and thus Premiere *should* be supporting them and not throwing up these error messages.

 

It's gotten worse with the latest 24.2.1 version.