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!

[juhaniv94094739]

Hi
Thanks
I do It.
Br
Juhani

Mod note: Please do not post personal info.

[juhaniv94094739]

Hi

Waiting new 24.4 version to appear inside the updates-list on my Adobe account...

Then we see the result.

BR

Juhani

[jamieclarke]

Hi Juhani,  If you are able I would recommend trying the beta version of Premiere Pro.

[jamieclarke]

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

[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.

[jamieclarke]

Hi @Master_chief  - If you are able, can you try using Premiere Pro Beta 24.5 and see if that helps your problem.

[jamieclarke]

HI Jackalope, If you are able, can you try using Premiere Pro Beta 24.5 and see if that helps your problem?

[juhaniv94094739]

Hi

Tried the beta-version.

First bug-warning about MXF just popped up.

So not working with mxf.

Now it seems to be more and more possible that to save the customer projects and customers, camera replacement is the only choice. By learning years to use Premiere,  changing it is not a solution.

[jamieclarke]

Hi Juhani,  Sorry you are still having trouble.  Would you be able to send me your project file so that I can take a look.  We are actively trying to fix this problem.  Thank you for your patience.

[juhaniv94094739]

Hi
When i used this beta- version first time, after a half an hour came first
bug-warning, but after that nothing else appeared, even the earlier
”replacing with black frame” warning is still missing.
So now It is maybe better to wait some days when i am working forward with
these projects, and look if this only warning was a ”shadow” from earlier.
So i let you know when i have some news to tell.
Br
Juhani

Mod note: Please do not post personal info.

[juhaniv94094739]

MXF-bug appeared again in Beta-version.

Now I go to video converter-method (App Store), so I think it can be a solution, which gives a little more work, but can solve this problem without changcing the camera equipment. Converters are quite high quality apps today.

BR

Juhani

[steves2019]

Tried Beta 24.5 and I get a lot of warnings about error retrieving frames and frame substituion attempts aborted.

[jamieclarke]

I'm sorry the beta version didn't work better for you, we will keep digging.  

What conversion app are you using?  Adobe Media Encoder can convert your footage for you as well.  I'm curious why you didn't use it?

[jamieclarke]

Are you using markers in your workflow by chance?

[juhaniv94094739]

Hi
Ok
I can try the App you recommend.
I did not want to use extra app because there is a problem with recording 4
channel voice.
Now this app i have tried converts It to 2- channel.
Maybe there is a possible to take the original Sony -recorded voice and add
It to converted video without problems.
All this is a little mess during work and the best way could be to have the
original mxf.
Br
Juhani

Mod note: Please do not post personal info.

[jamieclarke]

Yes I agree,  using the original MXF files is the correct solution to this problem, which is why we are making this a priority.

An easier way is to use the Proxy workflow.  Right click on media file > Proxy > Create Proxies >  Use settings: Frame Size Full, ProRes Quicktime Proxy. 

This will let you keep all of your audio channels and toggle between Original Media and Proxy Media.

[Kevin-Monahan]

Hello @steves2019,

I hope all is well with you. Can you provide the product team member with an answer to his question? We'll be here!

Thanks,
Kevin

[jamieclarke]

Hi @fernando alves  - I'm checking in on this issue.  Are you still having trouble or has the latest Premiere builds helped you?

[steves2019]

I tested a project with no markers and the same issues presented themselves.

Also, I'm currently communicating directly with Rach McIntire after speaking with Fergus Hammond about this and was told by Rach that he can recreate the error on both a Mac and PC and is working with the team now to nail down a solution.

[Kevin-Monahan]

Thank you @steves2019. I appreciate the added insight you gave the community. I am glad that you are in touch with engineering team members. Let me know if you need anything else as you work through this frustrating issue.

Take Care,

Kevin

[Kevin-Monahan]

Hello @fernando alves and @Yash Nene,

Is it possible to give feedback about how the format is working with Premiere Pro 24.5? Looking forward to hearing from you!

Take Care,

Kevin

[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...