This issue would crop up all the time on my edit due to time-stretching, so I’ve become almost hypersensitive to it 😉
Yes, that’s basically the issue, and it’s one I’ve encountered before, which is why I’m kicking myself hard this morning. Read below for the full explanation if you want to get into the weeds.
The full explanation:
For some reason, the subtitle workshop software I use to adjust the captions only matches my premiere timeline when the premiere timeline is set to flat 24 instead of 23.976, even though subtitle workshop is set to 23.976. Therefore, I have to change my premiere timeline temporarily to flat 24 in order to check captions. After I’m done, I switch my premiere timeline back to 23.976.
When I did this a long time ago for V1, I noticed that it messed with the in/out points of any shots that were time-stretched. I’ve since replaced all of the time-stretched shots in the timeline with Prores 444 renders from After Effects (it also does better frame-blending and frame-interpolation), save one. I missed the one shot of the crew looking around inside the base.
The other safeguard I put in place was to duplicate the project file and use the duplicate project make caption changes, instead of switching my main premiere sequence settings back and forth. This is what I did for V2. The safeguard only works, however, if you remember to do it! I simply forgot this time around, and did the same thing I did back for V1, and unfortunately, the one shot I had not pre-rendered got shifted by 1 frame.
Finally, my last mistake was checking each edit point before making the caption changes, instead of after. It should have been the very last thing I did before render. I do find it easier to catch errors this way, as I don’t always see flash-frames just by watching the film (others here have faster eyes than me). I hope that makes sense. Let me know if you have any questions!
Nev, thanks again so much for pointing this out before it went out to many more people! I really really appreciate the sharp eyes. I’m so sorry to anyone who used their bandwidth and time to download a file with a bad frame in it. I try to catch these things before they go out, but sometimes I miss things.
Bottom line:
I have fixed the error, rechecked every single edit point, and am now rendering again. I’ve taken down all of files with the error. I may decide to upload as encodes finish instead of all at once, but the full set should be finished uploading late Sunday night.