P: Frame substitution attempt aborting error - .MXF Files

[Anthony LV]

UPDATE 8-30-24:  

We have released an update in beta that is a potential fix for these frame recursion errors.  

Please download 25 beta and see if that helps your issue?   

You can find Premiere Pro version 25 beta in the creative cloud desktop app in the sidebar under beta apps.  Thank You!

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

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!

[Copy and Paste5CFB]

I experience same issue. Luckily I havent deleted the previous version yet. The same project file seems struggle in 24.2.1 with no solution to how to stop the error popping up  while in 23.6 I found not even a red line over my sequence.

[jackalope500]

Hi again,

Now it's a couple months since my initial post, and I've just been using the Beta versions of Premiere and Media Encoder without the above-described error problems. They are great.

The biggest drag (besides all the time spent trying to figure this out in the beginning) is that I deleted all my preferences as one solution early on - which helped only temporarily - but it's a bit of a drag re-doing those again, including my own keyboard shortcuts.

BUT - I strongly recommend just using the Beta version, anyone else who is experiencing this problem!

[cyrilc74]

Thanks, this simple fix of "right-click on the MXF video file and set it to open to Premiere Pro" works for me and my friend. (Canon 70 XF-AVC Footage on windows)

[Anaëlle R]

Hello @jamieclarke  !

I'm on windows 10, and with Premiere Pro 24.3

I'm experimenting the issu with clean projet, and without markers..

[Timoooo]

I tried all the solutions but nothing works, still got the error message and black screens in the clips - using no external plugins and footage is from a sony fx6

[Sam23768955c1ez]

After June release of Premiere Pro 24.4.1, errors were encountered when opening project files that were successfully saved and closed in April, 2024 and before. The raw files referenced in the project were recorded using a Canon XA50 (MXF format).  The event messages were of two forms. First, "Frame substitution recursion attempt aborting after multiple attemps on the file ...(raw MXF file)."  Second. "Error retrieving frame xxxx at time xx from the file ...(raw MXF file)."  The would repeat numbers of times.

[Sam23768955c1ez]

After June release of Premiere Pro 24.4.1, errors were encountered when opening project files that were successfully saved and closed in April, 2024, and before.  The raw files referenced in the project were recorded using a Canon XA50 (MXF format).  The event messages were of two forms.  The first form was as follows: "Frame substitution recursion attempt aborting after multiple attemps on the file ... (the raw MXF file name)."  The second form was as follows: "Error retrieving frame XXXX at time XX from the file ... (the raw MXF file name)."  This error message would repeat multiple times for different frame numbers.  Also, no video was shown in the project window.

[RobShultz]

It is suggested not to update Premiere while working on a project because of unexpected errors.

[FibiBerlin]

Yes, I have the same problems with old projects. I open them and get these errors all the time. With material that was never a problem before. That's pretty annoying. It is also really very annoying that Adobe is now always releasing versions that are not really well tested. And even more annoying that they react so slowly to the problems.

[Chrisanthi Pel]

any update on this one? I have the exact same problem. I was able to work with mxf files before with no issue. after the latest update, I can't work at all! 

[Sumeet Kumar Choubey]

Hi Sam23768955c1ez,

We're sorry about the poor experience. We're currently working on this issue. We will keep you posted as we get more details. Thanks for your patience.

Sumeet

[Peru Bob]

Yes, I have the same problems with old projects. I open them and get these errors all the time.

By @FibiBerlin

Create a new project and import the old one into it.

[Timoooo]

I created the project 3 days ago and stil get the error message

[Semmanuel]

don"t work for me 

[inkaontheway]

Is clearing the plugin cache the same as clearing the media cache? How can I clear my plugin cache? I cant find anything about it.

[pedrop45338571]

@Christiaan1 thanks for the solution, it worked!

[jamieclarke]

Hi @inkaontheway - If you hold down SHIFT while opening premiere you can choose which caches to clear.

[jamieclarke]

Hi @Timoooo - We released 24.5 can you try updating and let us know if you are still having issues.  You should be able to download within 24 hours.

[stevec99374408]

I have the same issue with Sony MXF files

[gian.delgadoaspiazu]

Apparently version 24.5 still don't fix the issues that it has when working with MXF files that came from a Sony Camera. I don't know if other cameras are affected.

Had to revert again to version 24.0 that works perfect for me.

Mod note: The title was changed slightly.

[jamieclarke]

Hi @gian.delgadoaspiazu - What MXF issues are you experiencing with 24.5?  What are your system specs?  Do you have any plugins installed?  Are you using markers? Have you tried holding down shift while opening Premiere and resetting your caches?

[ewannicholson]

Jamie,

I've followed your responses on this and other threads regarding recent MXF problems in Premiere. Holding shift while launching and disabling didn't help. Removing all 3rd party apps didn't help. The new version 24.5 does not help. The only stable solution that provides usable performance for me is to roll back to 24.2.1. I find 24.3 is stable but very slow. 24.4 onwards is a disaster. I'm using mxf files from R5C and C70 and editing on PC.

[jamieclarke]

Hi @Anaëlle R - We just released 24.5 can you try updating and let us know if you are still having issues?

[jamieclarke]

Hi @ewannicholson - Are you getting crashes or frame errors?  Just to confirm when you updated to 24.5 you cleared your media cache?

[defaultqlagna8dyi5e]

I too am getting this issue with R5C MXF files on premiere on PC. Rolled back my version to 24.3 and deleted Media cache but it seems to come back after some time. Was 24.5 just released? Does this have a fix for the issue?