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!

[Christiaan1]

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

[jackalope500]

Hi Ishan,

Thanks. I will try the beta version. I've also been reluctant to try resetting my preferences (such a hassle to get them all set up again), but I did that this morning, and the errors started coming again after a while... not as many but they were there again. I believe it has something to do wtih the original 4K files and the proxies.

I'm not sure about sharing sample source files as this is commissioned work for a client, but let me try the beta version first.

In the meantime, here is one of the source files that is constantly bringing up errors in one project:

A051C013_231026WT_CANON.MXF
Type: MXF
File Size: 10,77 GB
Image Size: 3840 x 2160
Frame Rate: 25,00
Source Audio Format: 48000 Hz - 24-bit - 4 Channels
Project Audio Format: 48000 Hz - 32 bit floating point - 4 Channels
Total Duration: 00:10:05:07
Pixel Aspect Ratio: 1,0
Alpha: None
Color Space: Rec. 709
Color Space Override: Off
Input LUT: None

MXF File details:
Wrapper type: MXF OP1a (type: SingleItem SinglePackage MultiTrack Stream Internal)
File generated by: CANON, XA50 (1.00)
H.264/MPEG-4 AVC Long GOP High Profile 4:2:0 Unconstrained Coding

[Ishan Y]

Let us know how it goes! Thanks for sharing the media properties. If you find a media file you can share, please upload it to any file-sharing platform and send the link through a private message. I'm curious to know if you also see the error message when the MXF file is saved in your internal storage. I understand that working from your internal storage is not practical for you, but this info can help us better understand the problem. 

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

[Khyati Gupta]

@fernando alves Sorry for delay in reply. Thanks for checking beta version 24.4 release of ours will have changes that were present in beta version. Glitch issue which you are reporting we will try it at our side and fix it.

Thanks for reporting.

[Yash Nene]

Hi @fernando alves

I've faced playback issues while working with Canon C70 footage as well, and it can be extremely irritating.

Working with proxies seemed to solve my issue. I created proxies using Premiere Pro (creating proxy jobs within Premiere) and toggled the proxies on while editing.

I think having an edit friendly codec (Something like ProRes 422 LT, or ProRes Proxy) reduced the stress on Premiere and ensured a smoother playback.

While glitching footage is not acceptable, and I understand that in the later stages of the edit one may want to see the crisp RAW footage even while editing, proxy footage worked just fine during assembly. After reaching the first cut if I wanted to review the edit with the RAW footage I rendered the sequence to review.

Hope this is of some help.

Cheers,

Yash

[juhaniv94094739]

Using .mxf -files result black frames in Mac.

No answers how or when this issue is over. First bug reports are really old.

Do we need to buy new cameras?

[jamieclarke]

Hi Juhani I'm sorry you're having these problems, you definitely should not need to buy a new camera.   What type of camera are you using?  Are these files straight from the camera or are they transcoded from an app?  Would you be able to upload one of these files to us so that we can investigate further?  Thank you for your patience.

[juhaniv94094739]

Here are clip and alerts. 

Most of MXF-clips  there is several black frames. Those clips are useless.

Camera is Sony PXW-Z90.

Problem is that this issue occurred after the last Premiere-version, so it is a bug, not my problem. Many others have the same issue.

My work is blocked now and I really want to buy a new camera. It is cheaper than this problem.

BR

Juhani

[jamieclarke]

I see the errors you are getting and understand how frustrating that is.  Are you using markers in your workflow?  Are your MXF files long gop?  Do you mind posting a screengrab of the properties from one of your problem clips.

[juhaniv94094739]

No, I dont use markers.

Clip total lenghts are 15 sec ... 2 minutes about. Using mostly only 5 to 10 seconds.

Maybe I dont understand exactly the properties, but here is one screnshot.

BR

Juhani

[jamieclarke]

Thanks for the screenshot of your timeline, that is very helpful.  If you right click on that MXF file and select "Properties" That is what I was looking for.  Would you be willing to upload that file for me so that I can take a closer look?  If you could put it in dropbox or google drive or any other service that lets you share files and send the link that would be super helpful.  Thank you for taking the time to get this problem fixed.

[juhaniv94094739]

Hi Thanks.

Here is the screenshot.

I will send the file with WeTransfer, I use for work. But what is the email?

[jamieclarke]

Amazing!  Thank you so much you can use jamiec@adobe.com

[juhaniv94094739]

Thanks.

The clip takes 25 minutes to upload.

It is coming.

BR

Juhani

[jamieclarke]

Thank You Juhani! Clip received, I will let you know what I find.

[juhaniv94094739]

Hi
Thanks
Br
Juhani

Mod note: Personal info removed.

[juhaniv94094739]

Hi

Anything found?

BR

Juhani

[jamieclarke]

We are still investigating.  Do you use the import panel to bring in footage or do you double click in the project to import it?

[juhaniv94094739]

Hi
I import to panel by ”grab and move”.

Terveisin

[jamieclarke]

Hi Juhani,  Hope you are well.  We just released Premiere Pro 24.4.  Can you update and let us know if you still are having problems?