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

What makes the Beta version 25 different from Premiere 24.4 update you mentioned? Or the Beta version 24.6?

That's in the Public Beta, which you can install alongside the 'shipping' versions at all times. Now that the beta is 25.x, as noted, you can't open a project in that and then the shipping.

So create a new project and test your media there. They've got amazing new color managment tools also, including the ability to set a wide gamut timeline with a different monitor gamut and output gamut. Just wow.

Hi @Anthony LV  @rranney  @telecam2 @Christiaan1 @juhaniv94094739 @Juerg5CF2 and anyone else experiencing frame recursion errors. - 

We just released an update in beta that is a potential fix for these frame recursion errors.  Can you try downloading 25.0.0 build 29 or later and see if that helps your issue?   

Version 25 is part of our next major release so it is not backwards compatible to 24, but it would be good to know if this version helps your issue.  

You can find Premiere Pro version 25 beta in the creative cloud desktop app in the sidebar under beta apps.  Thank You!

And that's a freaking pain. Yea.

I know we need to have a quick workaround occasionally but this issue has been happening for months now and it needs to be addressed and fixed by Adobe. I've been a customer since the beginning... yes.. that long.  I've never seen Adobe ignore a serious issue like this one.   I too had a long tech support call... they gave me the handbrake advice.  I never thought that I would begin thinking of using another editing platform but this is taking too long.  All of our cameras are Canon C series.  We have switched to ALL-I and those files are editing fine but we have tons of in-house stock in Long-GOP that's almost impossible to edit fluidly. 

That's something you are quite correct on, that's past Handbrake. And ShutterEncoder handles multichannel audio better, at least for some things.

Some of the colorists I know do a fair amount of "finishing" work, and they've got one or two other apps that are good for specific professional needs. You gotta know the tools ... 

Yes, as you already stated before. I can send you samples if you need to have experience with using Handbrake to keep free run timecode intact along with four tracks of LPCM mono channels. 

As I noted, ShutterEncoder has both ProRes and DNx ... all variants of those ... as well as a ton of other codecs of varying types. But again, you the user set the quality of the output of either one.

I've seen multiple generation tests of Handbrake outputs that are quite good through 3-4 generations. Using an overlay set to Difference.

You can also produce a file that breaks the second generation.

Just because ffmpeg is capable of delivering professional results does not mean that Handbrake, with its subset of options, is. As evidenced by the point made about being incapable of dealing with mutlichannel audio tracks within the MXF container.

But if your primary experience with video footage consists of H.264/5 MP4 files with a single stereo track, I can see why this wouldn't enter one's mind as a concern.

A couple observations.

First, it's a total pain that the MXF files don't all work with Premiere, and they have to get that sorted. Period.

Second ... as to using Handbrake, that's a front-end for ffmpeg, and is able to provide all the quality anyone needs within the codecs it writes to. If you set the compression to "placebo" and pump up the levels and encoding 'base', you get basically All-I out of it. Or close enough that 2-3 generations won't kill you unless you're doing CGI plates, really.

So it's in the settings chosen that determines the image Q out of Handbrake. Not that Handbrake is an inferior or "prosumer" option.

Personally I would have recommended ShutterEncoder as that can transcode to either DNx or ProRes codecs also. This is also a front-end for ffmpeg.