Participating Frequently

Answered

'Frame substitution recursion attempt aborting after multiple attempts on file'

Forum|Forum|4 years ago
March 3, 2021
16 replies
86350 views

Hi everyone,

I've got a problem that I think others have had, I'm trying to use MXF video files in a project I'm working on, the quality of the video is the main priority (Audio has been recorded separately so there's no audio on the MXF video files). I've already tried using MP4 but the quality has reduced significantly so that's a no-go. After importing the MXF files, the error sign lights up, and 'Frame substitution recursion attempt aborting after multiple attempts on file' is the issue every time. I've imported it under different Video rendering and playback options but no luck there. Each time I've tried importing the MXF files, the number of errors alternates, sometimes there are loads, other times there are less. Does anyone know what to do to fix it?

Correct answer hamood25206530oq8u

Save the project

Close Adobe Premiere
Rename the file that is giving this error
Launch Adobe Premiere again
It will say file not found (Because we renamed it)
Click on locate and then browse the renamed File
Hopefully it will work, it has worked for me 3 to 4 times

Show previous replies

S

samuelboneham

Participant

Here is a shoot resolution for those using the C70 or Canon - shoot your files with the following settings for no drop frame issues - Long GOP seems to be the issue potentially or Clog2...

If you have already shot and have drop frame issues create Quicktime proxies and work from those - won't be any issues. Then when you export make sure you close down Premiere, then re-open and begin export process. Keep an eye out for drop frames on the export and cross your fingers.

Camera settings:

XF-AVC YCC422 10 Bit

3840X2160 Intra-Frame

250mbps

Colour profiles tested so far are:

C1:BT. 709 Wide DR

Clog3

Yet to test Clog2

ALIASLABS

Participating Frequently

this is where all of my problems started with in the first place are these dam n MXF files that you're talking about? I generally only work with Sony but I got a different project from someone who works with CANNON and their MX files are creating these frames substitution problems, so frustrated I will never work with these files again after this project, I'm on the same boat with you on this one. If you figure out a solution, please let me know. Thank you.

Kevin-Monahan

Community Manager

Hi AL,

Sorry. I saw your other post too. Sorry for the pain.

I see now what footage you may be working with. Looks like it's from Canon C300. Is it: 4K 10-bit YCbCr 4:2:2 at 410 Mbps? Is this your computer?

If so, you may wish to make proxies. Another problem might be with your project, but I can help you in the other thread.

Thanks,
Kevin

Kevin Monahan - Sr. Community & Engagement Strategist – Pro Video and Audio

ALIASLABS

Participating Frequently

yes, it was CANNON files. I'll keep proxies in mind for this if it happens again fingers crossed it won't, but I may consider bumping back to the previous version. Going forward. It's just that I've been on a huge project with multiple edits and the auto update definitely threw me off. I think I need to turn that auto update off. Lol.

jj88708322

Participant

So I just encountered the same issue recently in April of 2022. Some specifics about my case. I was using footage from four cameras, of two different types. Two sony a7's and two panasonic lumix's. Here's what worked for me. I updated to the newest version of Premiere, also updated my drivers. But the main thing I did was this

Offline all the media

Delete imports

Re-import

Link Media

For some reason the simplest method worked out for me when all others have not. I know this may be one of the first things you guys tried, but if not seriously consider it. Would have saved me many hours of fustration.

jj88708322

Participant

Nevermind It just happened again 😞

B

benwinter

Inspiring

Keep reverting to older versions of Premiere until the issue goes away. 2021 (v15) worked for me. Or, do what I did, and switch to Resolve, and kiss all your problems goodbye forever.

F

fddeutsch

Participating Frequently

Getting beyond frustrated with this error since updating to Premiere 2022 last week...

I am currently trying to edit a wedding film and this error pops up just about every 30 seconds and my clips turn black.

My clips just become black in the timeline and or don't play back at all in the program monitor after this error pops up.

My clips playback fine in the source window and no files are corrupt.. but in the timeline / program monitor they don't play. Very confusing.

The clips are from a Canon c70 (.mxf files). Shot in 4k 60fps and interpreted to 23.976

My sequence settings are very standard. 4k 23.976fps.

I also have .braw files in the project too but it's only happening to my .mxf files.

I've seen a couple other threads about this issue and have tried the other 'solutions' but none of them seem to be working. Im a week late now on this project with no end in site because of this..

What I am working with:

Any help would be greatly appreciated. Im on the verge of totally restarting this project in Final Cut but that is my last resort..

M

Milo25185114gfl1

Participant

Having the same exact issue... extrememly frustrating. After reading through this thread it seems like my best options are:

1. download an older version of PP - anyone know which version this issue started on? should i go all the way back to 15.0?

2. shoot in mp4 instead of mxf - i really like the mxf codec and would prefer not to switch, but i suppose this would be an easy fix?

thanks!

Kevin-Monahan

Community Manager

I have the same issue with MXF files from the Sony FX6.

Adobe has known about the issue since April and still hasn't fixed it.

To be absolutely clear what is going on here: Following the 2022 update, Premiere is straight-up incompatible with one of the most popular video containers found natively in lots of professional production cameras, and Adobe seems unable or unwilling to undo what they did to break it.

I tried raising the issue but Kevin Monahan responded by trying to blame my hardware (I'm on a brand new 2019 Mac Pro, claiming Xeon processors can't handle H.264—which is completely irrelevant to these MXF files) and then locked the thread.

After more than a decade with Premiere, this was the final straw for me. I'm switching to Resolve and cancelling my CC subscription.

I'm editing my latest project in Resolve and it's an absolute joy. It's clearly 100x better optimized, the UI is snappier, instant playback, I don't need to render proxies. To all who are hesitant, the learning curve is friendly and adaptation from Premiere is easy. I can't believe this is what I was missing out on. Adobe has completely dropped the ball and it's time to leave. Enough waiting around for Adobe to stop polishing the turd. Ciao Adobe.

Hey ben,

claiming Xeon processors can't handle H.264

I probably said Xeon processors do not support Quick Sync; they don't. However, H.264 GPU acceleration should be supported by your Mac's GPU. I find it odd that most people experiencing this bug have the same 2019 Mac Pros.

—which is completely irrelevant to these MXF files)

.MXF is a container; the XAVC format uses H.264, so that's the connection I was making.

and then locked the thread.

Not sure what happened there. Sorry for any misunderstanding. I'm advocating for a fix and hope the issue will be addressed soon.

Ciao Adobe.

Wishing you luck in your future projects.

Take Care,
Kevin

Kevin Monahan - Sr. Community & Engagement Strategist – Pro Video and Audio

Jeff Bugbee

Community Expert

Looks like your video files are on an external drive. Can you place them on a local drive instead? I've seen users get the recursive error before and it was because the external drive was too slow.

M

mackinnoncreativeAuthor

Participating Frequently

Yes, they are on my external drives. Ideally, I would do that, but the footage adds up to about 12 hours, and it's 325Gb so that's a no-go. Maybe I could have done one folder at a time but that seems to be making more effort than just leaving it on my external hard drive.