Frame Substitution Recursion Attempt Aborting After Multiple Attempts On File ๐Ÿ˜ก

Community Beginner ,
Jan 05, 2022 Jan 05, 2022

Copy link to clipboard

Copied

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:

 

Screen Shot 2022-01-05 at 9.21.36 PM.pngScreen Shot 2022-01-05 at 9.21.17 PM.png

 

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

 

TOPICS
Editing , Error or problem

Views

2.9K

Likes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Beginner ,
Jun 12, 2022 Jun 12, 2022

Copy link to clipboard

Copied

YUPPPPP! That's what we are all doing - LIVE TESTING A FREAKING BETA VERSION - while THEY get paid for it!!! What do we get? Lost money and clients, while they get paid. Do they offer us a discount or anything of the sort... NOPE! Thanks again Adobe, appreciate it!

Likes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
LEGEND ,
Jun 13, 2022 Jun 13, 2022

Copy link to clipboard

Copied

Try re-importing some troublesome clips via the media browser, but this time use Ingest and the ProRes422 ingest preset. (NB: the first clip will go faster if you have the media encoder already open.)

As you work with the transcoded, ingested footage, does the error still appear?

 

It would be great if all codecs on all systems behaved themselves no matter what. It sucks to have to transcode on ingest. But if it works......

Likes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Beginner ,
Jun 13, 2022 Jun 13, 2022

Copy link to clipboard

Copied

Thank you for the reply but transcoding footage is not the answer I'm looking for.  I'm aware that Premiere handles ProRes just fine.  

 

Transcoding footage adds time to workflows on both ingest and finishing.  In some cases, this is not ideal, particularly with clients who ask for same-day shoot and edit turnarounds, etc.  

 

 I understand processing slowdowns will happen due to dealing with temporal compression, etc.   But my real hope for a Premiere fix is to work with camera original Canon MXF footage without errors -- like I can do in other software packages.   

Likes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
LEGEND ,
Jun 13, 2022 Jun 13, 2022

Copy link to clipboard

Copied

So it seems you have options if this isn't fixed by the time your next client deadline looms. And while your arguments are lucid and reasonable, they won't get the attention of the developers here. You need to post your thoughts on this at Premiere Pro User Voice

Likes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Explorer ,
Jun 14, 2022 Jun 14, 2022

Copy link to clipboard

Copied

SAME Issue.  I can cut to the quick... EVERYTHING IS SAME.  7 years of multiple cameras recording multiple events every week for 7 school years.  Same cameras, same workflow, same Premiere procedure- over and over - every week.  NEVER, NOT EVER have I encountered this error UNTIL THIS UPDATE.  Now, when camera starts new file, I have to for some reason clip the 1st 3 frames of all subsequent files in timeline.  The only change is Premiere version.  Tell developers to UNDO whatever they did.  If this is to be the new norm, Premiere is UNUSABLE as I cannot make seamless video any longer ( I have a 3 frame black gap).  Very much  awaiting a coherent response that does NOT involve analyzing hardware.

Likes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Expert ,
Jun 14, 2022 Jun 14, 2022

Copy link to clipboard

Copied

why not revert to the previous version which was working?  Premiere allows you to have multiple version installed on your system...  

Likes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Explorer ,
Jun 14, 2022 Jun 14, 2022

Copy link to clipboard

Copied

LOL  agreed.  I suppone one could make the argument by that logic we'd all still be on verion 1.0 of all software!  I'd like to point out this HUGE bug wasn't in the update documentation, so I had no way of knowing it existed until I actually did some work.  At this point I may revert, but seems to defeat the purpose of a cloud- based application that updates itself.

Likes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Expert ,
Jun 14, 2022 Jun 14, 2022

Copy link to clipboard

Copied

you can turn off automatic updates....  Having worked with NLE's starting with AVID media composer very early on, that's always been the smartest way to work.  

Likes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Explorer ,
Jun 14, 2022 Jun 14, 2022

Copy link to clipboard

Copied

Just curious about a few things regarding your suggestion.

  1. what's the point of cloud app if I have to turn off the updates in fear?
  2. If I did turn it off, I would have installed the new update anyway (that's the point) only to find the same bug had I auto-updated? again what's the point?
  3. In many cases, Premiere converts "pproj" files upon opening which renders them inaccessible to older versions.  Again, I updated, did the work, found the heineous bug and now all the work I did would have to be redone AFTER I reinstall an older version.  again- what's the point?

See a theme yet????  Adobe has locked us into updating and clearly engineers have NO experience in video editing so these rudimentary workflow bugs would have exposed themselves LONG before public release.

C'mon... you understand this is totally rediculous!

Likes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Expert ,
Jun 14, 2022 Jun 14, 2022

Copy link to clipboard

Copied

Don't ssee how Adobe has locked you into immediately updating...  And the workflow bugs you talk about don't effect me or the majority of users.  Not to say that they shouldn't fix it...  

 

Premiere and other comparable programs are incredibly complex.  Back in the day of early Avids, they sold turnkey systems, controlling every piece of hardware and yet when there was an update, there were often problems and you learned not to update right away and to be ready to restore your system to its previous state if necessary.  And this was for a $50,000 system.    There is no way Adobe can test every possible permutation of equipment, os and also take in to account a myriad of other software that may be installed on the system and that may be interfering with some features of the software.   bwdik.    just have opinions from many years of experience...

Likes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Explorer ,
Jun 14, 2022 Jun 14, 2022

Copy link to clipboard

Copied

I've been encountering this issue since 2020 when I started working with the mxf files. It has gotten progressively worse throughout, so though it may be primarily in one version for one client, that's not everyone. Finding a work-around wasn't what I was looking for since that's only temporary and can change with the breeze. Ive been looking for the cause of the issue so hopefully Adobe can find a solution and didn't even realize I needed to submit customer feedback beyond here. 

Sadly this forum hasn't been any help for this issue since it persists no matter what has been suggested, when actually using the mxf files.

Likes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Expert ,
Jun 14, 2022 Jun 14, 2022

Copy link to clipboard

Copied

for what its worth, I've had issues with mxf files in the past and don't remember how I worked around them...   It seems that different camera manufacturers put different spins on their mxf files...  Sorry that this forum hasn't been of any help on this matter.  Forum participants are for the most part just users, not adobe employees and so if we're not experiencing the same problem, we're probably not gonna have an answer for you.  If you'd like to send me a problematic mxf file, happty to take a look at it on both the mac and pc with the latest version of premiere and see if I experience the same problem.   If you'd prefer to keep the communication private, just click on my user name at the head of my post to send me a direct message.  

 

Likes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Jul 09, 2022 Jul 09, 2022

Copy link to clipboard

Copied

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!

Likes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Expert ,
Jul 09, 2022 Jul 09, 2022

Copy link to clipboard

Copied

both mp4 and mxf are heavily compressed formats.  Smarter to shoot in (if possible) or transcode to an all i-frame format like the appropriate flavor of prores (if you're on a mac).  There's a downside to using prores on windows as other programs may not be able to work with prores (in particular DaVinci Resolve). Not sure what the best format is for windows...  I have found mxf files in particular to be problematic in some situations.  

Likes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Jul 09, 2022 Jul 09, 2022

Copy link to clipboard

Copied

yeah that's just not really an options for me, at least not with my current gear and workflow. i just need to shoot and edit quickly and i'm usually happy to trade compression for that. seems such a stupid issue consisering mxf is such a widely used codec.

 

just installed 15.0 so will see if the issue happens on this version.

Likes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Expert ,
Jul 09, 2022 Jul 09, 2022

Copy link to clipboard

Copied

what camera are you shooting with?  In the midst of a large documentary project with alot of 4K material shot with a sony camera as mxf.  There were serious issues in Premiere because of the color space the Sony shot in.   Reinterpreting the footage as rec709 solved alot of problems...   

Likes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Explorer ,
Jul 09, 2022 Jul 09, 2022

Copy link to clipboard

Copied

On the C70, MXF is the file type for XF-AVC and with the update you can shoot in that, MP4, or Cinema RAW Light. XF-AVC can be ALL-I, you just select Intra Frame instead of LONG GOP in the menu. Shooting settings really depends on what you're doing and your workflow, so I wouldn't simply say one specific setting is what you should use, but this guy has some good recommendations (https://www.youtube.com/watch?v=JpDMF3LrlaU https://www.youtube.com/watch?v=6XtwVleTZhs&t=386s ).

 

@Milo25185114gfl1 I still do a proxy work flow and deal with the issues when color/grading rendering but this can be horrible for some projects and not bad for others. If you're looking to shoot and edit quickly simply use two cards and let the camera create proxies in the 2nd card and get right to editing with the proxies, then only attach the files at the end and if needed toggle them on/off while working with them. 

Likes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Explorer ,
Jul 09, 2022 Jul 09, 2022

Copy link to clipboard

Copied

BOOM.... and just like that problem solved.  Clearly Adobe found the issue and fixed.

Likes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Contributor ,
Jul 09, 2022 Jul 09, 2022

Copy link to clipboard

Copied

Uhh, care to explain? What has been fixed? What version are you on?

Likes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Explorer ,
Jul 09, 2022 Jul 09, 2022

Copy link to clipboard

Copied

I know .. about to get my hopes up!

Likes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Explorer ,
Jul 11, 2022 Jul 11, 2022

Copy link to clipboard

Copied

Sure thing... I did nothing except EXACTLY what I did before - Let Adobe Cloud update my app.  New Version of Premiere no longer has issue of dropping 3 frames on subsequent camera files.  Just like that problem solved.

Which essentially beautifully illustrates my original point of letting Adobe auto-update and TRUSTING Adobe developement to test in order that we all can trust this process they've forced us into.

Likes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Explorer ,
Jul 11, 2022 Jul 11, 2022

Copy link to clipboard

Copied

So version 22.5?

Likes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Explorer ,
Jul 11, 2022 Jul 11, 2022

Copy link to clipboard

Copied

22.5.0 (build 62)

Likes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Aug 29, 2022 Aug 29, 2022

Copy link to clipboard

Copied

I have 22.5.0 (build 62), still have the same issue with .mxf files. Still not fixed. 

Likes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Expert ,
Aug 29, 2022 Aug 29, 2022

Copy link to clipboard

Copied

did you check the color space as I mentioned in an earlier post to this thread?  Also, try this (first duplicate the file in case there are any issues):  try replacing the .mxf extension with .mpg.   I think Ann Bens suggested this with an issue I was having with some mxf files...    I'm a great believer in workarounds... I know they're not always ideal, but the important thing is to get the job done...

Likes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines