Skip to main content
ACV Comm Specialist
ACV Comm Specialist
Participating Frequently
September 18, 2020
Question

Frame Substitution Recursion Attempt

  • September 18, 2020
  • 7 replies
  • 7904 views

I have multiple projects that I use on a regular basis that contain common clips that get used over and over. Some of them are years old that get updated and exported again and again. Yesterday, I opened one of these projects and the Frame Substitution Recursion Attempt error window popped up on one of the video clips (the little red box in the corner — and the clip showed as a black box while the audio played fine). This is a clip I have been using for years, and Premiere never had a problem with it. The crazy thing is, the way I "fixed" it was to make a copy of the file, reimport it, and substitute it in the project. No conversion; no actual change to the clip was needed. Today, I ran into the same problem with a second project: two clips had issues. I made copies, reimported them, and went through the work of replacing them, etc. A pain. Afterward, I decided to downgrade to the most recent old version of Premiere in case there's a bug in the latest version. So, I downgraded from 14.4 to 14.3.2. I then opened up the project I had worked in today (I had saved the new, replaced project as a new file), and did not get the error. Yay ... I thought. I opened up a third project to see if it would error. It did not. Yay, again ... I thought. I started working in this third project and upon exporting, I receive the Frame Substitution Recursion Attempt in Media Encoder even though it didn't pop up while I was working. Again, these are clips I have used and exported many, many times in the past. What is going on?

    This topic has been closed for replies.

    7 replies

    vinnydego
    vinnydego
    New Participant
    November 21, 2020

    I'm having this exact same issue.  The clips I use over and over are Quicktime files with the animation codec selected so I could do an alph channel.  It's very frustrating.  No solutions from my end, just adding my complaint to the pile so Adobe addresses it.

    Kevin-Monahan
    Community Manager
    Kevin-MonahanCommunity Manager
    Community Manager
    November 21, 2020

    Try ProRes 4444+ instead. Does that work? 

    Kevin

    Kevin Monahan - Sr. Community & Engagement Strategist – Pro Video and Audio
    vinnydego
    vinnydego
    New Participant
    November 21, 2020

    That did work!  Thanks.  I'll respong again if something goes wrong but hopefully this is the last time i have to do that.

    O
    Odera5EEC
    New Participant
    October 25, 2020

    Same exact issue following for a solution. Im a anime youtube content creator and EVERY video I use these two clips title sequence and end sequence clips in every single one of my videos. However today I was unable ot at all and I need to get this video up cause I was already passed my deadline. 

    ACV Comm Specialist
    ACV Comm SpecialistAuthor
    Participating Frequently
    October 26, 2020

    Did you try the workaround I outlined in my first post? Even though we shouldn't have to do this, it does work (at least for me) and should be able to get you through this deadline. Make duplicates of the offending video clip files and either replace the footage in Premiere with the copies or import the copies and replace them in the sequences.

    O
    Odera5EEC
    New Participant
    October 29, 2020

    Unforunately no both making a copy and trying to import were not fruitful for m. I dont understand how this can still be a prevelant issue when so many people are experiencing it.

    S
    Studio 218
    New Participant
    October 1, 2020

    Same problem following for a solution. 

     

    ashrafaabduabdullah
    ashrafaabduabdullah
    Inspiring
    October 6, 2020

    Same here with the Frame Substitution Recursion with no fix, some said the graphic card may be the driver and change the file extension to m4v, change the render to software only, unfortunately, all suggestions haven't fixed the problem.

     

    it would be great if adobe responds with a bug fix or an update  

      M
      Markku16B8
      New Participant
      October 10, 2020

      Same problem. Old videos made using much older Premiere do not work anymore. I'm getting frustrated with this sh*t. Before migrating from Win7 to Win10 and having the codecs in Adobe package there were no problems. I want to have this system working, not wondering what else I need than Premiere and Windows (preferrablt Linux, but Adobe is not supporting Linux.)

      A
      Anonymous
      September 20, 2020

      Same issue with version 14.4. Did't occur before the update.

       

       

      C
      cootan01
      Participating Frequently
      September 24, 2020

      " So, I downgraded from 14.4 to 14.3.2. I then opened up the project I had worked in today (I had saved the new, replaced project as a new file), and did not get the error. "

      How do you do that? The problem arose immediately after I did the upgrade. Project I had been working on for a month, not a single problem. Hit upgrade and the error message pops up then proceeds to render it impossible to work as it repeats itself like bad pizza a hundred times a minute....

      Mark d 

        ACV Comm Specialist
        ACV Comm SpecialistAuthor
        Participating Frequently
        September 24, 2020

        I'm not sure which part you're asking about. The end of the situation is, no matter which version I use (downgraded step by step down to Version 13), I didn't stop getting the error, whether in Premiere or in Media Encoder when exporting. So, I've upgraded back up to 14.4 and will just have to fix each "problem file" as they present themselves. If Adobe fixes the problem, great, but I don't know how to do it myself. And no one here seems to know how to, either. At least the fix is fairly straight forward: make a copy of the clip file, import the copy, and replace the problem clip with the copy.

        B
        brusiephoto
        Participating Frequently
        September 18, 2020

        Same issue here. Random clips providing the same error. Also random graphic items (such as a Tiff I am doing a move on blacking out for 20 or 30 frames, no error. Project has been underway for a few weeks with no error prior to update.  Windows 10; GTX 980 graphics, i5 procesor, SSD for system, internal Raid 1 for assets

        B
        brusiephoto
        Participating Frequently
        September 18, 2020

        And, I reverted back to 14.3 and all is well. Bug in 14.4 or maybe my NVidia 980 is now obsolete?

        chrisw44157881
        chrisw44157881
        Inspiring
        September 18, 2020

        uncheck render at maximum bit depth. additionally try transcoding to prores or software render.

        ACV Comm Specialist
        ACV Comm SpecialistAuthor
        Participating Frequently
        September 18, 2020

        Render at Maxiumum was already unchecked. Exporting from within Premiere is working. This doesn't really solve the issue, though. I can't upgrade to the newest Premiere without having to "fix" every old project file, and I now have to wait while each file exports (typing up Premiere) instead of continuing to work on other projects while the exporting happens in the background in Media Encoder.

        M
        mainedan78
        New Participant
        September 18, 2020

        Similar issue. Tight deadline. Very frustrating. Following for help!!

          Terms & ConditionsAccessibility statement
          Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices