P: Frame substitution attempt aborting error - .MXF Files

[Anthony LV]

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!

[WesHowellPPro]

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.  

[kennyy69162399]

Hello,

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

Thank you for your help

[Flix_799]

Hello,

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

Mxf - drops, errors

Timeline - not responsive, freezing

[R Neil Haugen]

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

Neil

[WesHowellPPro]

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

[Christiaan1]

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.

[Christiaan1]

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.

[mantomatt]

Same here with MXF files from Canon C300mkiii. 

The error messages seems to pop up frequently, and our biggest issue is that it slows Premiere down. 

We've tried isolating the problem by editing files from our local drive, instead of the server. Project Files on local computer, instead of Google Drive. Importing files through Media Browser instead of Finder. 

The common denominator here is Premiere Pro. It has occasionally had issues in the past, but not on this scale. 

We are using a combination of Mac Studios, M1 and M2, along with iMac i7's. The i7 allowed me to switch renderer, which did reduce the number of errors, but also slowed editing down massively. 

Transcoding is not a cost-effective solution, as this requires both our time and extra drive space. One of the biggest benefits of using Premiere Pro from 2010 onwards, was the native file format editing, and it would be ashame for this to be lost. 

We require a fix to this problem ASAP!

[Christiaan1]

Has this been read by the developers?

[Christiaan1]

Would be great to see this fixed in the next update. 

[Joao Lopes Brazil]

There is only one sollution until this moment!!! Go back to Premiere 23! The Premiere 24 dos not work at all!

I use a Macbookpro M2 and work with C70 MXF 4K files. From the moment i made the upgrade my life turned into hell!

Error retrieving frames messages popping up and performance lost! So i decided to go back into versions and the problem was gone! Adobe must pay attention and test upgrades before release them to us users! 

[Sumeet Kumar Choubey]

Hi everyone, 

We're sorry about the poor experience. We're currently investigating this issue. Could you please confirm if this is happening specifically with the project files created in the previous version of Premiere Pro, or is it happening with new projects as well? Also, if possible, please share a download link for the sample media with which you are experiencing this issue.

Thanks,

Sumeet

[mantomatt]

Yes, still happening in brand new project files created in Premiere 24 version. 

[juhaniv94094739]

Same here with Mac M1 and MXF-files shooted with Sony.

First substituting, then retrieving, but test exporting seem to be ok.

Must be sure about this issue, because of cust omer projects.

Thanks for clearing this.

BR

Juhani

[juhaniv94094739]

Here is one screenshot about those issues.

[jamieclarke]

Hi @Anthony LV  - Do you have any plugins installed?  If you do can you try holding down the shift key while opening Premiere and clearing the cache.   If you are able, can you try using Premiere Pro Beta 24.5 and see if that helps your problem.

[Christiaan1]

Updating to the newest NVIDIA studio drivers made the files viewable in Premiere Pro, but the speed of showing the files is super duper slow. Normal playback is not possible. You have to wait for 10 seconds to see one frame. But playback is not possible.

[Christiaan1]

Here some info for the developers: 

24.4.1 Errors. Sony MXF files.

Here three screenshots:
Error codes.
PRogram monitor.
File specs.
Playback from super fast QNAP media NAS. No problems in 2024.3

Can see the file now in the program monitor (after waiting more than 10 seconds when moving the timelineindicator. But playback is not possible.

   

[jamieclarke]

Hi @Christiaan1  - Would it be possible for you to send a video with this happening?  Thank you for your help in reporting, we are working to identify and fix the issue.

[Averdahl]

I have had the very same issue with MXF footage from a Sony X70, 1080p50/10-bit/4:2:2 in both 24.4 and now in 24.4.1. Same error messages, playback is really bad, etc, etc.

But then i created a new project and imported the footage there and got the same result. All media is located on an internal NVMe drive. Resetting prefs and deleting media cache, etc did not help. So i continued and imported footage from another internal NVMe drive and footage with the same specs from the same camera worked for some reason. So i moved the project that did not work to another NVMe drive and opened it and bingo, it worked. Then i moved it back to the original NVMe drive again after trimming the drive and bingo, it worked now as well.

All drives are NVMe drives. I had no issues in Pr 24.3.

In my case there was something on the first drive that offended the MXF-importer in 24.4/24.4.1 since opening the project, or importing the files in Pr 24.3 works as expected. I can now open the project in Pr 24.4.1 without issues, so it was nothing wrong with the project itself.

One of the oddest issues i have seen...

[Justin Opinion]

I have also been having this problem for some time - maybe since two updates ago. Now, with the latest update 24.4.1 the MXF files are completely black, as if there is no support for them at all. Adobe is literally killing my ability to work and meet deadlines. Might be time to jump off this sinking ship.

[Terry37641153sxh2]

The issue I get with MXF files is PP quits unexpectely, no warning or error - program just closes. When I reboot I get the option of recovering session. I edited the same camera footage 2 weeks ago without issues. It auto updated to 24.4.1 yesterday and now this issue. 

Solution is to save every 5 seconds so when it crashes you only lose 5 seconds of work! Second solution is to activate my free Resolve license which came with my camera. Have been too stubborn to jump ship since I've been on PP for 20yrs. This issue is the final straw! 

[Averdahl]

The issue I get with MXF files is PP quits unexpectely, no warning or error - program just closes. When I reboot I get the option of recovering session. I edited the same camera footage 2 weeks ago without issues. It auto updated to 24.4.1 yesterday and now this issue. 

By @Terry37641153sxh2 

Yes, i got the very same problem yesterday. I am back on 24.3 yet again...

[Christiaan1]

Besides that, footage that I use the Warp stabilizer on, can start to lose color detail like it is less colors or something.
Gradients start to become banding with warp stabiliser i think.

Does this also have to do with this bug?

[Christiaan1]

Sure. Done. I have sent two video files.