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

[Anthony LV]

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!

[R Neil Haugen]

There are many changes between the 24.x builds and the 25.x public beta. Including massive changes in color management, adding many options we've never had before. And other things.

[gian.delgadoaspiazu]

Hi @jamieclarke 

I've been testing version 25, and everything seems to be working just fine for me.

Thank you!

[IslandFox]

Adobe clearly does not care at all. I have been having this issue forever and the only option is to downgrade. I regret not switching to davinci sooner.

[jamieclarke]

@IslandFox - Please see the pinned post.  We have made some updates in the current beta version of Premiere Pro 

[AntonK_1984]

Hi Jamie,

Thank you for your help! it does look like Beta is working much better. 

We still experience minor artifacts in the Control Monitor playback (resolved with cache clean-up); however, those do not get transferred to the final render. 

Could you give us approx. timeline when do you guys expect to release version 25? Thank you.

[StMarduk]

I see 24.6 is out. Can anyone confirm if this resolves the MXF issues? I'm in the middle of a project so I won't be able to upgrade yet. 

[jamieclarke]

HI @StMarduk - We have made some updates in the beta version 25 for customers experiencing frame recurssion errors.  So far the potential fix has looked promising.  If you experience these errors in a project it would be helpful to install the beta and test if you still get them.  Please let us know thank you for your help.

[Television Photog]

@StMarduk 24.6 had the same crashing issue for me when I tried it once. Didn't have time to explore it further, so back to 23.x I went for the night.

[bennief3451038]

Has anyone had success with the 25.0 beta? I tried it out and it ran extremely slow on my computer. Ended up getting frustrated and downgrading to version 23. 

Final Cut Pro is looking very appealing right now.... 

[Christiaan1]

Updated: 
Possible solution... oh no... still glitches in export.
Try Clearing Cache in the preferences. It can help for playback .
But in my export there are glitches again.
Sony MXF Long 4k
Prem 24.6.1

[jamieclarke]

Hi @bennief3451038 - Confirming that you are not seeing frame recursion errors?  What are your computer specs?  What build are you working on, you can check in the about Adobe.

[AnthonyAS]

Bonjour, j'ai un projet avec des fichiers "AVC Long GOP High 4:2:2 Profile 10-bit Unconstrained Coding", et Premiere Pro se ferme subitement, sans arrêt. J'ai essayé d'anciennes versions de Premiere, idem. J'ai supprimé le cache. Idem. J'ai fait un diagnostic. Rien n'est remarqué sur mon système. Premiere pro se ferme sans laisser de message d'erreur. C'est la première fois que j'ai cette difficulté. 

Que se passe t-il ? 

[jamieclarke]

HI @AnthonyAS - Can you give us some more information. What are your PC specs? What version of Premiere do you have installed?  Do you have any third party plugins installed?

[AnthonyAS]

Thank you for your assistance. I don’t have any third-party plugins installed. I was using the latest version of Premiere Pro (24.6), but it kept crashing. I've since reverted to version 24.4.1 (build 2), which seems to be more stable. It did crash twice within the first 15 seconds of opening, but it's been running without issues for the last 15 minutes. Here are my system specs:

• Processor: AMD Ryzen 9 3900X 12-Core Processor 3.79 GHz
• Installed RAM: 64.0 GB
• Operating System: Windows 10, 64-bit

[AnthonyAS]

it just crashs again....

[jamieclarke]

Hi @AnthonyAS - We are investigating an issue with crashing in certain instances.

 Can you try troubleshooting one thing for me.  There is a file in the Premiere Pro folder labeled ImageRenderer.dll You can find it in C:\Program Files\Adobe\Adobe Premiere Pro 2024 Can you try deleting that file and then update to Premiere Pro 24.6 and let us know if you are still getting crashes.  

[AnthonyAS]

Done. When i opened Premiere pro last version (24.6.0 (build 86)), no crash for now, but 2 error messages ' error retrieving frame 2814 at time 00 52 00 12 from the file E:/....CANON.MXF, substituting grame 2813'  ' error retrieving frame 2818 at time 00 52 00 16 from the file E:/....CANON.MXF, substituting grame 2817,  

[AnthonyAS]

and it crashed again...

[jamieclarke]

HI @AnthonyAS - 

We just released an update in beta that is a potential fix for these frame recursion errors.  Can you try downloading 25.0.0 and see if that helps your issue?   

Version 25 is part of our next major release so it is not backwards compatible to 24, but it would be good to know if this version helps your issue.  Thank You! 

[AnthonyAS]

I'm currently testing the beta version. So far, no error messages or crashes. I'll keep you updated. Thanks for your help Jamie !

[jamieclarke]

Thank you for your help troubleshooting and hanging in there, I know how frustrating that is.  Please keep us updated.

[reboussier]

Bonjour
J’ ai le même problème avec des fichiers 4k mxf 422 10 bits
Une fermeture violent de première pro
Ma seule solution actuellement a été de transformer ces fichiers en pm4 h264
Et je n ‘ai plus de pb
C’est la premiere fois que j’ ai de l’ instabilité sur premiere
Ce logiciel se dégrade , trop de mises à jour non validés

Envoyé de mon iPad

[jamieclarke]

HI @reboussier - Please see pinned post, and let us know if that helps your issue.

[AnthonyAS]

En effet, c'est assez frustrant ces bugs. Pour l'instant, l'installation de la beta semble corriger tout ça. Pas de crash ni de messages d'erreur depuis 1 heure. 

[freds1960]

I downloaded the v25 beta and mxf files do play now. However, had timeline all files, upgrade to AE25 Beta as well, relink graphics one by one (others on path did not relink automatically) and the color correction on some files is now off, enough that the keys (using ultra key) are also off. 
all mxf files were shot with Sony FS6 or FS7. I have dozens of projects with footage from these cameras so hope you can fix this soon. These are not outdated or obscure cameras. Tha ks