Known Participant

Released

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

387 replies
49058 views
Translate

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

G

ghuff

Inspiring

I spent hours with Adobe support on remote desktop with no solution. They advised me to transcode with handbrake, I tested it and yes, it works, but I can only choose one audio track out of my 4 and there will be a quality loss and another huge data pile.

There should be an all-points bulletin sent out to Adobe tech support staff to never ever EVER maket this recomendation, especially if they are not going to be savvy enough to tell the difference between MP4 files shot on some hybrid stills/video camera and the XF-AVC format from a professional cinema camera.

EditReady or even the free version of DaVinci Resolve would be better options for transcoding this footage, and it should only be into ProRes, otherwise you're starting to incur generation loss.

Just terrible advice to re-encode via Handbrake, and is very naively "prosumer" coming from Adobe.

Translate

yogendras31

Participant

Why is this coming ? This is so much frustrating. Hav tried many different types of menthods to overcome this but nothing is working. I was editing a film having almost 5 TB of data. Tried deleting Cache, Tried changing the renderer but since new mac update it doesn't allow anymore. Tried switching it to internal storage than a HDD. Any specific solution than going to and fro for many other solutions.

Translate

jamieclarke

Community Manager

Hi @yogendras31 - Can you give some more information on your computer specs? Also, What version of Premiere are you using? Do you have any plugins installed? Are you using an external monitor? Can you right click on one of your clips and select "Media File Properties" then post a screenshot. Thank you.

Translate

Н

Никита5E27

Participating Frequently

Hello, I have such a problem that Premiere pro version - 24.5.0 build 57, constantly crashes without errors when working with MXF containers, in any case, shot on sony pwx-z90. There is a computer next to it with the Premiere pro version of 23 years old and the program (premiere) works perfectly with the same files.

Translate

wildbill3867835

Participating Frequently

I'm getting lot's of warnings related to footage from my Canon XF605 .mxf files (see attached). They don't seem to be really affecting anything, but they are frequent and concerning. The other 4 cameras in the project are not reporting warnings.

Canon XF605 File Properties:

Type: MXF
File Size: 13.54 GB
Image Size: 1920 x 1080
Frame Rate: 23.976
Source Audio Format: 48000 Hz - 24-bit - 4 Channels
Project Audio Format: 48000 Hz - 32 bit floating point - 4 Channels
Total Duration: 00:41:00:12
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, XF605 (1.00)
AVC Long GOP High 4:2:2 Profile 10-bit Unconstrained Coding

Translate

wildbill3867835

Participating Frequently

Forgot to mention, running on Windows 11.

Translate

C

Christiaan1

Inspiring

Installing the latest beta today and cleaning cache did not prevent glitchens and frame substitution erros.

Back to 25.3 again...

Translate

rranney

Inspiring

I am still receiving these errors with the most recent beta (24.6 Build 74). I use Canon C70 .XMF files that are 4k 10bit 422 LongGop 150mbps. Here is a look at the media file properties of the footage I shoot for every project:

Translate

X

Xavier36342062hxms

Participant

Hello, my rushes are shot with a Canon camera in slow motion at 50 fps. I have several PCs with up-to-date premiere pro. They crash all the time with frame recovery errors even if I move the project to an internal drive. I empty the cache... Nothing helps. Apparently the only solution is to go back to the first version of 2024 ?

Translate

jamieclarke

Community Manager

Hi @Xavier36342062hxms - Can you please try the beta version 24.6, we have made some updates that have helped with your media. In the creative cloud desktop app under apps there is a section on the side labeled beta apps. This is where you can download Premiere Pro beta 24.6. Always remember to hold down shift after new installs and clear your media cache.

Translate

X

Xavier36342062hxms

Participant

It seems stable. But the reaction time when you start reading is long, it's not very smooth. We have the same style of problem when we make a project with rushes from different sources DJI + Canon + Sony... I already had a solution with the first version of 2024 but thanks for your help. That said, it's shocking that a company like Adobe releases a version that skips Canon rushes.

I'll end up taking a look at DaVinci if it continues...

Translate

U

UncleJessy

Participant

I'm still getting numerous frame retrieving and substitue errors for mxf files in the 24.6 beta. I did empty the cache before using.

Translate

ShadoworksWade

Participant

The issues are showing up on 3 different systems in the following builds:

Premiere 24.3.0 (Build 59) (Rolled back - still failing)
Premiere 24.4.1 (Build 2) (Rolled back - still failing)
Premiere 24.5.0 (Build 57) (Rolled back - still failing)

Issues:

Stuttering or frozen timeline playback
Corrupt Frames in preview or during rendered output
Corrupt frames in transition effects.
Constant “Red Flag” errors from Adobe when importing footage
Major lag or freezing in footage linking and re-linking within the bin.
Screenshots are included

All of the above issues only started happening following the last series of software updates.

Nvidia Drivers updated to most current for the Quadro RTX 4000 on Windows 11
Nvidia Drivers updated to most current for the RTX 2080 Super on Windows 11
Nvidia Drivers updated to most current for the RTX 3090 Laptop on Windows 11

Media Cache has been dumped.

It seems to only be impacting the following footage formats:

Camera Codec XF-AVC / Canon Log 3 / 3840x2160 YCC420 8 bit / SD Card
Camera Codec XF-AVC / Canon Log 3 / 1920x1080 YCC420 8 bit / SD Card
Apparently some of our Sony MXF shooters are having similar issues.

Camera C200 Latest Firmware 1.0.8.1.00

Converting the footage to a generic MP4 or 10-bit QuickTime format bypasses the issues… but that is a Band-Aid not a solution. This is not a rare or exotic format, and I cannot stress this enough, it was working without issue until the recent wave of updates.

.

Translate

D

danraica

Participant

Hi @ShadoworksWade @jamieclarke - I am having the exact same issues as described.

I am on M3 Pro, MacOS Sonoma. My files are stored on an external NVME SSD which has a tested and sustained speeds of R:2700MB/s and W:2850MB/s

I have manually deleted my cache and will await the issue to reoccur.

Has been happening during comparison view, and scrubbing timeline. Only working with XF-AVC footage - 2 C200 cameras with same settings. I do not get a sputtering playback or timeline issues at this stage.

Am awaiting confirmation of fix to be deployed @jamieclarke - or should I be confident to use beta? Given stable release isn't stable maybe those things don't matter with adobe products?

This is a pretty unacceptable problem to be dealing with with such a mature camera model and software...?

Translate

rranney

Inspiring

Translate

jamieclarke

Community Manager

Please post the media type you are working with. If you aren't sure you can right click on your media and select properties, then you can post the screenshot here.

Thank you for everyones help!

Translate

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.