Warning, error, frame substitution???

Any news on this for a fix?

I'm get these errors, still get them with Mercury GPU turned off.

I'm not scaling the footage, just 2 x 1080 ProRes LT files, simply making cut away shots. have had to re-start Premier about 5 times today already!

OS Name Microsoft Windows 10 Pro

Version 10.0.17763 Build 17763

Processor Intel(R) Core(TM) i7-6700K CPU @ 4.00GHz, 4001 Mhz, 4 Core(s), 8 Logical Processor(s)

Installed Physical Memory (RAM) 64.0 GB

Dual Nvidia 1070 GFX cards

PP Version 13.1.1. build 9

All OS and GFX drivers on the latest versions!

I get this error, strange thing is the location shown does not exist! D: drive is my media drive, I've searched everywhere but nothing!

POSSIBLE FIX!  I was having the same problem. I had Adobe have their way with my computer and they didnt fix anything. I am usually working with different resolutions higher than 4k so I usually click "Scale to Frame Size". I turned that off and just scaled manually and the issue went away. Hope this helps for somebody. 

Hit this problem big time yesterday. Just finished a project, went to export the master file, and I started getting that error. When I checked the export frames were in the wrong order at the points the error message said. I found that if I kept trying to export eventually it would work.

I then needed to shorten the final file, so I took my good export back in Premiere, chopped the end off and exported. The export would still fail. That's a single ProRes(HQ) file as the source and ProRes(HQ) export, so hardly very taxing for Premiere.

I have now spent the last 24 hours trying to get to the bottom of things. What I have discovered is that this largely happens with ProRes(HQ) files and exports. This doesn't seem to happen with ProRes. Ticking 'Use Maximum Render Quality' on export makes it fail a lot more often.

Premiere 13.1.2

OS: OSX 10.14.5 (Mojave)

I'm having the same problem even for a simple sequence; one clip and one audio track. I've had so many and different problems since "upgrading" from CS6 to CC. I totally wish Adobe would divert their development team from making new features to just making the current capability bugfree and stable. For professionals, a stable system is much more important than some new 'feature' or gadget!!!

I'm getting exactly the same thing. Normally I'm editing fine for the first 2 hours then suddenly get relentless warnings about "frame substitution" - it's annoying but I can still edit.... until some of my clips start displaying as just blackness in the canvas.... as which point have to quit the program and go to a last saved version. VERY ANNOYING! PLEASE SORT ADOBE!!!!

I'm having the same exact issue. The video will be fine if I don't attempt to make any edits to it. The second I try to use the program for what it is suppose to be used for, editing, I start to lose frames until I lose all frames and I just have a blank video.

I had this problem. Also have a whizz bang new build.... I have found that sequences don't like blank spaces - which I have for 20 years used as black. Now I use 'black video' instead.

Also, with the dreaded error - 'frame recursion' - my project was crashing (although it was a few years old and being opened in the new update). Here's what I did to fix it....

Create a new project

Select 'mercury playback software only' in the project settings

Import the old project (I selected only the sequences that I needed)

Create a new sequence

Drag the old sequence into the new sequence **make sure you have the sequence button selected that allows for all tracks - not just a merged sequence

I have this problem as well...with PROXY FILES!!! It starts about 30 to 60 minutes into editing and then I have to restart or Premiere will just crash.  Once I restart I can edit again for a time until it starts happening again. I know there is no issue with the files because...well, they were made by the ingester inside of Premiere!  That and they don't have a problem until Premiere gets warmed up. Pathetic. On a high end HP Z series workstation that is connected to a NAS via Fiber...we have another workstation connected to this NAS that does not have this issue with the same media "pool" (though it has other issues that are much worse). Thinking about getting back into Resolve.

This is causing so much trouble in my post facility. Can this new feature be disabled? It clearly doesn't work properly and needs fixing.

Clips will randomly show this error while editing, making it impossible to work and export a master. The exact same files may have worked properly 10 minutes earlier, or be fixed by re-opening the project, using a different computer or just sometimes switching between Metal and OpenCL. There is no consistency to the errors or workarounds, we just have to keep re-opening projects until it stops. I'm rolling back to an older version until this is rectified.

Errors are detected at random on:

ProRes 422HQ

ProRes 4444

DNxHD 185x MXF

Photoshop files

We have 6 Macs all suffering from the same problem.

4x MacPro Trash cans - all 64GB - High Sierra 10.13.6

1x iMac 5k - High Sierra 10.13.6

1x MacPro 2010 - Nvidia TitanV - High Sierra 10.13.6

Now, this is on a project that is still on the same, pretty new, SSD drive. I'm not about to move this to my m.2 because it's a huge project. I've had warning/crashes with other projects, so it's not just this project. But, this issue is something new. I haven't really needed to render the timeline for a while and when I did I just got a compiling error simply trying to render the timeline. I switched from CUDA to Software only and I was able to render the timeline for a bit, however, I didn't continue because doing this required the entire timeline to be rendered and I really didn't want to. I WANT TO USE CUDA! That's why I have this $1,400 2080 Ti video card!

: