Participating Frequently

Answered

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

Forum|Forum|4 years ago
March 3, 2021
16 replies
86305 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

New 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

New 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

New 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..

Kevin-Monahan

Community Manager

From the Premiere Pro Team:

"The issue that was originally causing this issue has been resolved. However, we do see some issues with playback errors like this that are machine specific. If you're still seeing this error (or something like it), please post a question about it, with specifics about your Premiere Pro version, OS, and media format, on the main support forum:

We're particularly interested to know if customers see this issue with LongGOP footage, Intraframe footage, or both.

LongGOP formats can be challenging to play back smoothly, particularly if you are using 10-bit 4:2:2, as this format is only hardware accelerated by Apple silicon Macs and 11th gen or later Intel Core processors that have Quick Sync enabled.

However, while we might expect to see dropped frames when playing back LongGOP formats on computers that don't support hardware acceleration, you should not see error messages, and it's this issue we'd like to get more information about."

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

Kevin-Monahan

Community Manager

Dec 16 2022

It's NOT been resolved.. I'm running on a iMac 2019, 3.7 Ghz 6core with128 Gb of RAM.. OS Ventura 13.0.1. This BUG is ruining a huge project no work arounds so far have solved this.. Why is it these kind of Software bugs fall on the shoulders of us to find the fix and why can't your company practice good ethics by reaching out to us via email etc. And explain the problems and FIX so we don't have yo search through a million different laymen answers? While on a 2 hour hold with Adobe? Errrr... If you have a simple answer Please step in.. Thank you!

AL,

Sorry for the frustration. Thanks for the info. It sounds like you are having trouble with this specific project. Regarding Ventura and updating your project to 23.1, the advice is to return to v.23.0 if possible.

Did copying and pasting clips into a new sequence solve your issue? Updating projects to new versions can sometimes corrupt sequences. I've seen that in Premiere Pro in some cases and with other NLEs, too over the years.

If you were getting the error indicated in the title, please let me know with specific details about your media (is it that 10-bit material?), and I can make suggestions.

About our support staff, I apologize for this strange behavior. Please feel free to PM me any case numbers, and I will take action.

Sorry again for the trouble.

Thanks,
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.