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!

[NitzMedia]

Hello! 

Would you mind screenshotting the media metadata and sequence settings dialogue box? What GPU are you using? I work for a company with dozens of editors and solved this issue by adjusting a couple of items on the sequence side. Proxies are always a plus and exporting through ME never hurts. 

[freds1960]

Thanks.
Not sure what you specifically mean by media meta data - but the
problematic files are MXF from Sony FS7, not sure of the data rate, but not
super high.

GPU is
[image: Screen Shot 2024-09-12 at 2.41.37 PM.png]

Mac Info is
[image: Screen Shot 2024-09-12 at 2.42.58 PM.png]

Here's the sequence settings:
[image: Screen Shot 2024-09-12 at 2.36.40 PM.png]

[freds1960]

sorry, replied via email and images didn't attach.  I'm having similar problems with mxf files, starting about 3-4 weeks ago.

GPU

 Mac

 sequence settings

 No longer getting substitution error message, but the mxf files hang, updating to a new still frame every couple of seconds.

[chrislognion]

 25.1.0 Beta (Build 11) has cleared up all issues with our C70 .mxf files on our studio PCs!  It's the best performance I've seen so far.

Chris

[AnthonyAS]

Hi, now i have all sorts of error messages. And the proxies files doesn't seem to activate... is it possible to have a stable version of premiere pro to work on please ?

[Radim37046208zysv]

Hi, please how does new beta version work with mxf.? Are there still errors and glitches? I'm going to edit a big project and I don't want to realize the problems while I'm working. Or should I convert all the mxfs to another format just to be sure? To which one? And which app for converting a huge numbers of files do you recommend?  

[Robert26002911p8fm]

The Beta is fine with .mxf files. I’ve edited two big projects on it with no problems. Plus it’s got some other goodies you’ll either love or hate.

Sent from my phone, but don’t be afraid to call me out on typos.

[Erin246010172zro]

I am using Beta 25.0.0 and 25.1 and can playback MXF files without getting error messages, however I still have clips with artefacts in the playback and export (clips that are fine in VLC). I don't believe the current beta has 100% resolved the issue with MXF files.

[jamieclarke]

Updating Status

[mayjain]

Hi @Erin246010172zro and everyone,

Apologies for the inconvenience caused by the glitches with MXF files.

We’ve implemented a fix for this issue in the latest beta versions of Premiere (build 25.4.16 and later), AME, and AE.  This fix is expected to be included in the next official update of Premiere Pro, AME, and AE.
Thank you all for your support and collaboration in investigating this issue.

While we don’t recommend using beta versions for production work, the beta installs separately from the release versions and can be used if you'd like to test the fix. Please let us know how things look on your end after testing the beta.

We sincerely appreciate your patience and continued support.

Thanks,
Mayjain

[David Goldschlag HF]

Good morning,

I just downloaded the Adobe Premiere Beta version to test if the .mxf issue has been fixed. I started immediately getting the errors that I also received on Premiere version 25.

I currently shoot with a Canon XA 40 in 29.97 1080 or 4K 60.

Premiere Pro v 24.1 is stable and does not give me these errors with the same exact files.

Can you respond to the below email:

David.Goldschlag@HF.org

Thank you,

David Goldschlag
Sr Video Production Specialist
Health First



#######################################################################

For more than 80 years, Health First has been committed to improving
the wellness and health of Brevard County. To learn how Health First
gives back to our community, visit HF.org.

This message is for the named person's use only. It may contain
private, proprietary, or legally privileged information. No
privilege is waived or lost by any mistransmission. If you receive
this message in error, please immediately delete it and all copies
of it from your system, destroy any hard copies of it and notify
the sender. You must not, directly or indirectly, use, disclose,
distribute, print, or copy any part of this message if you are not
the intended recipient. Health First reserves the right to monitor
all e-mail communications through its networks. Any views or opinions
expressed in this message are solely those of the individual sender,
except (1) where the message states such views or opinions are on
behalf of a particular entity; and (2) the sender is authorized by
the entity to give such views or opinions.

#######################################################################