Known Participant

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

Forum|Forum|1 year ago
February 27, 2024
110 replies
47184 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!

Show previous replies

M

markh19434597

New Participant

I'm experiencing exactly the same problems running Premiere Pro 2024 - currently upgraded it to 24.4.1 in the hopes it would fix it, but it hasn't. I've shot a multi-camera shoot on Canon cameras all shooting MXF. Multiple dropped frames during import. The only way of playing the footage on the timeline without Premiere grinding to a halt is to make Proxie files. But then exporting the video takes 5 times longer and the video glitches and pulses on playback. Reverting back to a previous version of Premiere isn't doable without starting the whole project again from scratch, as I can't open this file in an older version. Which probably means I have to start the whole thing again, which is hugely frustrating as I'm 3 days into the edit. I don't understand how a new version plays these files worse than older versions of the programme. Especially as the newer version claims to have a 'faster timeline.' This current version is totally broken in it's present state.

C

Christiaan1

Inspiring

Sure. Done. I have sent two video files.

C

Christiaan1

Inspiring

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?

telecam2

Inspiring

Getting tons of "Frame Substitution Recursion Attempt..." errors, black video on many clips in bin on a project that was working fine and smoothly under previous versions. Media is mainly 4K UHD 29.97P Sony AVC-L codec from Sony FX6 and FX9 cameras. Reverting to previous version.

telecam2

Inspiring

Sorry, working under deadline, can't troubleshoot. Installed and tested latest update twice this weekend. Will keep using previous version for now.

F

Flix_799

Known Participant

Same with me

Averdahl

Community Expert

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

T

Terry37641153sxh2

New Participant

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!

J

Justin Opinion

Participating Frequently

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.

Averdahl

Community Expert

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

jamieclarke

Community Manager

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.

C

Christiaan1

Inspiring

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.

C

Christiaan1

Inspiring

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.

Show more replies

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.

Scanning file for viruses.

This file cannot be downloaded