P: Frame substitution attempt aborting error - .MXF Files Fixed in version 25
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!
AdChoices