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!

[Semmanuel]

Same problem with MXF 

[gilsoo]

Yeah same problem here. Crashing every other minute with the same error. Rolling back to 24.1 as 24.3 cannot read 24.4.1 files. Come on Adobe.

[Kevin-Monahan]

Are you still having this problem, @juhaniv94094739? Let the team know.

Thanks,
Kevin

[juhaniv94094739]

Hi

I have it, I think, because i learn to use conversion programs to avoid this problem.

Only negative point is, that it needs more hassle.

and 4-channel sound brings more it.

regards

juhani

[Anaëlle R]

Hello,
I have the same problem and it's really annoying...
The 2023 version of premiere worked very well. But since 2024, I have exactly the same problem as described here, and there are many of us.
Playback is no longer fluid, and there's this problem with MXFs and the image retrieval error at timecode level. This was a problem I didn't have with previous versions of premiere. And I've been shooting for 4 years with a Canon C70 and in Long Gop, 4K UHD, without encountering any problems.
We pay a lot of money for the Adobe suite and it's really not right that so many of us have this problem and that nothing is done on your side to fix it.
I have a good computer and have never needed a proxy. Proxying is time-consuming and requires space on the hard disk, and I bought a powerful computer so that I wouldn't automatically have to go through this, so it's not a feasible solution.
Thanks for your help.

[Edit23]

Good luck with that, I talked to Adobe 2 years ago and the issue still continues with me to this day.  Even with a brand new computer, and through multiple updates.

It always happens on my MXF files shot with my Sony FS5 and it happens all day, every day.  Probably 50-60 times.

I hate to be Debbie Downer, but it's so frustrating.  Davinci Resolve is looking better and better every day...

[inkaontheway]

Hy Carlos, I have the same problem with Premiere Pro 2024. I already cut half of the 20 minute film but now there are appearing more and more errors, especially with 4K files. I would like to change the whole projekt in an older, more stable version (there I never had the problem) but  if I want to open it, it says that it is not possible. Do you have an idea what I can do?

[Carlos Ziade]

@inkaontheway 

can you share with us the errors you are receiving?

did you try to reset the preferences?

you can also try this method to downgrade your project

but backup everything before trying this:

Manually Editing the Project File

This method involves manually editing the project file, which can be risky and is generally not recommended for those unfamiliar with XML editing.

1. Save a Copy: Make a backup of your project file.
2. Open the Project File: Open the .prproj file in a text editor (like Notepad++ or Sublime Text).
3. Change Version Number:
   • Look for the line that starts with <Project ObjectID="16" Version="...">.
   • Change the version number to an earlier version (this requires knowledge of specific version numbers for different Premiere Pro releases).
4. Save and Test: Save the edited project file and attempt to open it in the older version of Premiere Pro.

   5. Recompress the Project File

   1. Recompress Using 7-Zip or WinRAR:
      • Right-click on the edited XML file.
      • Select 7-Zip > Add to archive....
      • Choose gzip as the archive format and ensure the file extension is .prproj.
      • Save the file.

   6. Test the Project File

   1. Open in Older Version of Premiere Pro:
      • Open Premiere Pro with the version you want to test.
      • Try opening the edited and recompressed .prproj file.

   Summary

   Here are the key points:

   1. Backup Your Original File: Always start by creating a backup.
   2. Decompress the File: Use tools like 7-Zip or WinRAR to decompress the .prproj file.
   3. Edit the XML: Change the version number in a text editor.
   4. Recompress the File: Recompress the file back to .prproj using gzip compression.
   5. Test: Open the file in the older version of Premiere Pro to ensure compatibility.

   This process involves manually handling gzip compression, making the necessary XML edits, and then recompressing the file, which allows you to potentially downgrade your Premiere Pro project file to an earlier version.

Note: This method can be unreliable and may lead to project corruption or loss of features, so proceed with caution and always keep a backup.

[Dinar G.]

Поставил себе эту бетаверсию и проблема с работой формата mxf ушла

[telecam2]

@jamieclarke FYI, I am still seeing "Frame Substitution Recursion" error pop up here and there but they seem to be non-lethal, playback continues and works fine.

[Matteo32734852irua]

Yes same problem here, the MXF files (they come from a SONY FS5) are no longer working with Premiere 24.4.1.

The Program window is just black when I try to play a timeline with some of them.

Switching back to 24.3 it works as always.

[Radim37046208zysv]

That's terrible. I read about this problem two weeks ago and still it isn't solved. I can't work with MXF files in new Premiere Pro. It shows me random errors about "retrieving frame". I'm already exhausted. I have to constantly trim shots and often that doesn't even help or this error appears on another shot. Yet I have small project. Yes, it is in 4K, but only about a few shots in 20s timeline. Please, do with it something! And yes I tried beta version and I have the same problem...

[jamieclarke]

Hi @Radim37046208zysv - Sorry about these errors you are gettin, I understand that this is frustrating.  We are currently tracking and working on a fix for these.  Are you using markers?  Also, Can you confirm what version of Premiere you are using.

[Christiaan1]

POSSIBLE SOLUTION
I had errors in 24.4.1. Frame substitution error and Black video showing.
When I started Premiere Pro while HOLDING SHIFT (and resetting plugin cache) the error was gone and clips play normal.
I hope this will help many people.

Though a little strange that this was not known to the developers and support.

[Kevin-Monahan]

Hello Community,

The bug is being worked on by the team, so I updated the status.

Thanks,
Kevin

[Kevin-Monahan]

Hello @Christiaan1,

Thanks for the question.

Has this been read by the developers?

Yes, and it is being worked on

Thanks,
Kevin

[mustbebelize]

While the recent update of Premiere Pro to 24.4.1 has a lot of cool features, it's also caused a lot of frustration for a lot of people including myself.  The application was not working and causing my computer to crash.  I have a performance computer running Windows 11 Pro with the latest Intel CPU, Nvidia's Geforce RTX 4070 and 64GB RAM.  It was always smooth sailling until the update.  But here's what I discovered and what Adobe wasn't saying.

I have always uploaded footage from my Canons and Sonys in native format and just imported into my project with no problems.  I never paid attention to the app preferences for the uploaded videos.  I have several type of video applications including Real, VLC and Windows Microsoft video apps.  

Apparently, the simple fix was to just set the videos to open with Premiere Pro.  So you right-click on the video file and set it to open to Premiere Pro.  Then if you had just updated from previous version, you'll need to clear the media cache.  It then regenerates the cache after reopening your project.

And presto, the app is working again.  I'm really intrigued though, that the Premiere software engineers did not discover this issue in their testing.  And if they knew, why did they not advise of the solution?  Their problem shooting tool advised to update hardware drivers etc.  But none of that worked.

It's simply to set your video file preference within your project folders on your harddrive to open with Premiere Pro 24.4.1.

Hope that helps.

[mustbebelize]

I worked with the new version 24.4.1 for 2 days before I decided to report the fix that I mention above.  But I swear as soon as I posted the above, Premiere Pro 24.4.1 crashed and keeps on crashing!!!  It's insane at this point.

[jamieclarke]

Hi @Anaëlle R - What version of Premiere are you using?  Are you getting these issues in a clean project or an upgraded one?  Are you using markers?  We have identified an issue with Long Gop MXF files when using markers and are working on a fix.

[jamieclarke]

Hi @juhaniv94094739 - Checking back in on your issue, are you still having problems?

[juhaniv94094739]

Hi
I am working now only with .mp4 converted mxf- materials.
No time to try possible problems.
I try again with mxf when some fix has been found.
Regards
Juhani



Terveisin

*Inssimainos OyJuhani Viitanen*
+358 40 588 9260
juhani.o.viitanen@gmail.com

[Kevin-Monahan]

Hi Community,

I updated the bug's status since the product team is investigating this issue.

Thanks,
Kevin

[mr_short]

I've been having this same issue on my iMac while footage will play perfectly fine on my MacbookPro. The footage shows up as black frames. The differences are:

iMac 2019 running Sonoma 14.5 with Permier Pro 24.4.1 - NOT working

MacBook Pro 2021 running Sonoma 14.2.1 with Premier Pro 24.3.0 - WORKING

The footage is XML files from a Sony FX6. So it appeared to me that either Sonoma 14.5 or PrPro 24.4.1 are the issue. I re-installed PrPro 24.3 to see if that would fix the issue and it did. I can now see my footage.

So THE PROBLEM IS Premier Pro 24.4.1

[mr_short]

Update: After only an hour or two of editing after re-installing Premier Pro, the issue is back with version 24.3. Interesting that it takes time for the black frames to start appearing. Any suggestions welcome!

I am on a iMac 3.6 GHz 8-Core Intel i9, w/ Radeon Pro Vega 48 8Gb Graphics and 64 Gb of memory, running Sonoma 14.5 (23F79). Trying to edit Sony FX6 .MXF files.

[chungcheongnamdh13787606]

동일한 증상입니다. mp4파일 사용의 경우 문제가 없는데, mxf 사용하면 바로 다운되어 버립니다. 너무 심하네요. 편집이 불가합니다. 2000년대 초반에 프리미어 프로 사용할때 생각이 나네요.