I'm a beginner at Premiere Pro, and I just updated it to v13.1.5. I've been working on this project for months, and now that I updated I keep getting these errors "Frame substitution recursion attempt aborting after multiple attempts on file" "Error retrieving frame" (see attached). It has affected about 90% of my footage making my file unusable. I was online with Adobe Support for 2 hours yesterday with no resolution. Does anyone have any ideas on if this can even be fixed? I tried replacing my footage with the orginal again and still no luck. I also attached my computer specs. Hopefully I'm explaining this correctly since I'm a beginner.
I have been asking for a preference to turn off this Frame Replacement bug/feature since it was released.
What version of Blackmagic Raw are you running?
I'm encountering the exact identical error, any updates or solutions yet? I'm editing in the latest version of Premiere Pro CC, and the footage is blackmagic raw
The only solutiion is to use a version of Premiere that was released before this Frame Substitution 'feature' was introduced. We have rolled back our entire post facility to 2018 as we found no workable solutions to this problem. You can spend hours replacing clips, copying files etc, but ultimately the issue is quite random and likely not related to your media unless you're working with very low end compressed or damaged formats. It's a shame that this still hasnn't been fixed after several updates.
You may have already found a solution by this time... I found a solution that fixed the frame substitution error on my system. I noticed on some footage that I had it was aquired in an .MOV container. Most didn't show a preview thumbnail in the windows explorer window. These were also the the same files that were giving me an error within Premiere Pro. The .MOV files would play fine in VLC but wouldn't play with quicktime or media player. I used VLC to convert the .MOV container into a .MP4-.h264 codec. I relinked the new files to the footage and the frame substitution error went away.
Hope this helps.
Updated to PP 2020 at the end of 2019 and I just ran into this same issue. I first found a suggestion to switch video rendering and playback to "Mercury Playback Engine software only" and unfortunately that did not work.
So, I found this suggestion, went over to cloudconvert, converted from .mov to .mp4 with the .264 codec, opened a new sequence, and dropped then converted file on and had no problems!
Thank you for the suggestion
Same message out of the blue for me. I updated to Premiere 14.0.2 and Media Encoder 14.0.2 on a base iMac Pro running Mojave 10.15.3
I'm not sure exactly what triggered it but I have a retainer client I work with every month so I keep the project with stock footage we collect over the years. I added new footage (Prores 4K DCI from my BMPCC 4K) along with some ProResHQ transcoded footage from a GH5 to my project and received the Frame substitution error...
I tried moving the clips to another drive, same issue so I tried exporting the previous sequence from last week which worked fine and received the same error...so just from trial and error I found that unchecking RENDER AT MAXIMUM DEPTH resolved the issue.
Hope that helps someone else out =D
I encountered this issue and read the previous input. I am a novice at best and so here is how I overcame the issue:
I did clean up the file by deleting 7-8 small .pngs that I did not need, but importantly (I think) when I re-created the image frame I wanted, rather than exporting as a .png, I changed it (to test) to a .jpg. I inserted teh .jpg and all worked fine. I reverted my saving style back to .png for future frame exports.
So - I do not feel the deletion of the 7-8 small images corrected it...maybe it was a corruptness in the frame export? Just glad it is fixed and I can move on.
BTW - thanks to all of you that share experiences/guidance - sure is beneficial
Found a fix 🙂 In Premiere Pro, go to sequence and select delete render files. Then select all of the videos necessary in your timeline and go to sequence and select render selection. I had this same exact problem as you have. Hope this helps 🙂
Thanks for sharing this tip! This worked for me too!
THANK YOU! I've been scratching my head about this problem for a while and this fix worked perfectly.
This worked for me. Thanks for the tip man.