Skip to main content
Known Participant
February 27, 2024

P: Frame substitution attempt aborting error - .MXF Files Fixed in version 25

  • February 27, 2024
  • 110 replies
  • 47868 views

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!

110 replies

jamieclarke
Community Manager
Community Manager
May 16, 2024

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.

Participating Frequently
May 7, 2024

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
Community Manager
Community Manager
May 7, 2024

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.

Participating Frequently
April 26, 2024

Here is one screenshot about those issues.

Participating Frequently
April 26, 2024

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

 

Participant
April 26, 2024

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

Community Manager
April 25, 2024

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

Participant
April 24, 2024

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! 

Inspiring
April 16, 2024

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

Participating Frequently
April 5, 2024

Hi - I'm using 24.2.1 build 2 on a Mac Studio 2022 (M1), running Sonoma 14.4.1

Lately, I'm getting loads of error messages about "Error retrieving frame.....at time ...." See screenshot here.

The above came within minutes of opening up a project I last worked on a few months ago.

A new project this morning resulted in errors, too - not as many all at once like above, but they seemed to be provoked when I added a motion graphic --- and then even just touched the clip underneath. But even then, the errors would pop up on other clips I hadn't touched.

 

I film in 4K on a Canon, the files are MXF. When I import, I create proxies. I work off a fast SSD drive (Samsung 2TB). There is plenty of room open on the disk.

Until now, I have just clicked on "clear all" each time and it goes away for a few minutes ... but then comes back again ... slowing everything down (and not helping me reach my deadlines!)

This problem has happened before, and it went away again - I cannot remember if I did something to help it, but I think I did. Can someone please help!? 🙂 Let me know if you need more info.

Kartika Rawat
Community Manager
Community Manager
April 5, 2024

Hi there!

Sorry about the issue. We have a community thread that discusses a similar issue: https://adobe.ly/3TMZNBl

 

Let us know if that helps.

Thanks,

KR

 

 

Moved to disciussions

Participating Frequently
April 15, 2024

Hi KR,

Thanks for your reply. I've been trying out various things. The thread you list is now 5 years old. It does include an extra "updated" answer with many, many options to try.  I've been going through the first several.

- Reboot - does not help.

- Delete media cache. Helps for about 10 minutes, then the errors start coming agagin. I've also set the cache to my hard drive - it was always there.

- Move media to an internal drive. I've tried this now with one project. Just moved it before the weekend, so will try today. I travel a lot and edit on both a laptop and my MacStudio - much easier to work from portable SSD disks, as I have without problem for years. Plus I have several projects under edit at once. Do not want it to be the only solution that I must work only from the hard drive.

- Premiere is up to date, I use proxies...

- I was wondering a bit if the SSD disk I use is getting bad. So I've also transferred a project over to another SSD to try that.

- But if you can suggest anything else, I'll be grateful. It just happened again the other day where I needed to open a project I haven't opened in a few months, and within 10 minutes there were about 20 "Error retrieveing frame..." errors. !!

Best, Jack

Participant
April 2, 2024

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!