Inspiring

Answered

Warning, error, frame substitution???

113 replies
88242 views
Translate

Why did I get this?

Participating Frequently

I switched the "video rendering and playback" to Mercury Playback Engine software only, like someone mentioned, and it worked!! YAY

H

hamood25206530oq8u

Participant

Save the project

Close Adobe Premiere
Rename the file that is giving this error
Launch Adobe Premiere again
It will say file not found (Because we renamed it)
Click on locate and then browse the renamed File
Hopefully it will work, it has worked for me 3 to 4 times

Translate

M

MunchyBugs

Known Participant

The year is 2023. Adobe is still unable to fix this problem. It is still here. The Avid people at my studio are looking smarter and smarter. And I'm looking dumber and dumber for not switching to Resolve years ago. Getting tired of waiting to fixes to dumb problems.

Translate

madelope

Participating Frequently

Ensure footage is all set to "constant frame rate". All your footage can be 25f/s but some footage can have a variable frame rate if it was recorded on a different device/encoded separately/provided by a third party.

Translate

P

PowerhouseVideos

Participant

I have just had the same issues in the latest version - 23. The "fix" is to turn off CUDA but to be honest this is not a real solution is it. I now have to turn off to use the project file and remember to turn back when rendering - which I do often. We pay a lot of money for the product so expect it to work and not create problems for the end user.

Translate

Y

yvesmagat

Known Participant

😞pfff... I was thinking in eventualy updating to the latest version, hoping this problem would not exist any more... Well, I will stick to the more stable 14.0-2020 version. I'm just wondering why I'm paying 30 $ a month...

Translate

P

PowerhouseVideos

Participant

Yes dont bother - it still exists. Its screwed up my project files as it insists on updating them on the 23 version.

Translate

L

LV_2

Participant

Premiere Pro 22.5 same problem, receiving black frames even after rendering. the clips are fine, this startet to occure suddenly on random clips (I guess with the last update?) after working with this material for half a year over several Premiere versions. No solution seems to make any sense. The bug is in the program, not on the user side (slow HDD, VFR, Blackmagic, PC/MAC... all the different setups have the same problem). sad! 😞

Translate

D

dakula74

Known Participant

same 22.6

Translate

Peru Bob

Community Expert

same 22.6

By @dakula74

22.6.2?

Translate

madelope

Participating Frequently

I know this is an old thread but adding this here as I didn't see it so far.

Same issue, after doing some digging, here's what I found:

Actual issue: footage has variable frame rate (the codec does not matter), you can confirm this by viewing properties of the clip in PP (it will say variable OR constant frame rate). Adobe does NOT (at least NO LONGER) reads footage exported with variable frame rates. Footage received was from a documentary project working with historial footage with a lower frame rate, therefore the editor rendered using "variable frame rate", hence my issue.

Fix: no need to re-encode. You can convert the footage to use a "constant frame rate" setting using softwares like Handbrake, I used a free trial of EaseFab video converter (here's a link: https://www.easefab.com/video-converter/). If using Easefab, here's a tutorial: https://www.easefab.com/resource/transcode-variable-frame-rate-to-constant-frame-rate.html#2 - it's ONLY FOUR SIMPLE STEPS.

I simply used the SAME codec of the source footage, but set the frame rate to 29.975. Adobe now reads it properly.

They should probably make a patch to automatically convert or just simply read footage with variable frame rates.

Translate

Y

yvesmagat

Known Participant

Hi Madelope,

Thanks for the info. Since I downgraded to the 2020 version I didn't have any problem. I'm afraid to upgrade again... Using your solution, don't you get a loss of quality ?

Bye.

Translate

madelope

Participating Frequently

No, I did not see a loss in resolution.

Translate

S

Senem5FCE

Participant

Why is this problem marked as solved? It isn't really. There are a bunch of work-arounds none of which shows consistency. And no real reason to why this happens. It literally hits your out of the blue and you're completely[edited by moderator] stuck.

It cost me two days (!) going through all the fixes and none of it worked. I moved the project to different mashines, but to no avail. Tried to re-enocde but ME would crash because auf "missing frames".

My "solution" was to import the project to PP 2018 via xml.

This is absolutely unexaptable.

Translate

H

Hunter5CFE

Participant

It's because your footage has an inconsistent bitrate. Look at some of the solutions here on the forum.

Translate

Peru Bob

Community Expert

Variable Frame Rate is sometimes an issue, not variable bit rate.

Translate

L

Lunavision

Participant

Sadly it still doesn't work for me. I have the same problem and it appeared completly out of the blue, since I just opened a project on which I was already working the day before.

In my settings for video rendering and playback it was already set to Mercury Playback Engine Software only. Has anyone other suggestions? I would be very grateful!

Translate

C

CloudDisaster

Known Participant

Something that seemed to work for our team--moving the Media Cache and database off Networked Storage (read and write speeds exceeding 500MB/s) to internal SSDs (similar speeds) and in our online suites to internal NVMes (1500MB/s).

Although we're still left with some problematic files from time to time, this has dramatically cut down our frame substitutions. Also purging the media cache as soon as problems arise. It's just not worth struggling through it with manual offline/relink procedures. It's honestly faster to just purge the cache and grab a coffee while it rebuilds. YMMV depending on the complexity and size of your projects.

Hope that helps you!

Translate

C

CloudDisaster

Known Participant

...also, pending Windows updates (if this applies to you). Our systems run like hot garbage if there are updates pending. Our updates are managed via group policy, and most times the updates won't properly install. At times, our systems seem to be caught in some half-installed limbo and Premiere becomes entirely unpredictable. We routinely have to ask IT to force updates through, and afterward Premiere functions *closer* to what you'd expect. Not perfect--but certainly less wonky.

Translate

H

Hunter5CFE

Participant

This is going to sound dumb, but the easiest solution is copy and pasting the video file in your folder and then importing that pasted file. It works for me everytime, but then again we could be having different issues that cause the same problems.

Translate

C

CloudDisaster

Known Participant

As in duplicate the file and (re)import the duplicate? This works for you consistently?

Sadly many of our source files run 100 to 300 GB, so we don't have a lot of space to be duping files...

Translate

crabspanner

Known Participant

This does sometimes work but it's an abusrd thing to be doing. Copying hundreds of gigs is impractical and it's just as likely to be broken again the next time you open it.

What storage are you using? Network or local drives? If we use drives it tends to be ok but as we have a super fast and super expensive video network, this is also impractical.

Translate

W

workshopguy

Participant

I had the same problem wiht a project I hadn't touched since this past summer. All my edited clips were black, sound was good but all had the frame substitution exception. My Ace IT department rolled my Premier back to the version before the September update and that solved the problem.

Translate

J

Jason5E19

Participant

After a few phone chats with support I was able to pry some information out of them. I couldn't get them to repeat the phrase "this is a known issue" only that the next beta addresses it. Except it doesn't--I test it and lasted an hour.

The problem, as they discussed, is the .mov container. If you use it, you can get frame subs. MP4 and MXF do not have this issue. If you have an MOV in a project with MXFs and MP4s, that can actually cause the MXFs and MP4s to throw frame subs. It's down the existence of MOVs in your project.

I didn't bother testing this because all the files we receive are ProRes, and we're not about to transcode everything just to work on it--the volume it far too high. Perhaps there are members here who can shift their entire workflows to accomdate Adobe's bugs, so I thought I'd share.

BONUS: unrelated tidbit of knowledge that is shared exactly nowhere--if you have closed captions where there is no captioning within the first 2 seconds of the caption file itself, there is a chance Adobe will simply ignore the caption when attempting to embed it. The "solution" provided was to export the caption and then bring them back in again. (all this does is snug the captions up to the begining of the file as far as I can tell). I simply chop the beginning off and that works and saves a pointless in and out roundtrip.

Translate

crabspanner

Known Participant

This is rediculous. I have just tested the Beta and it's exactly the same, in fact the very first project I opened was screwed. We use an almost entirel; ProRes Mov workflow but have seen the same issue with MXF media.

I honeslty don't think anyone is looking into this issue despite it rendering the software entirely useless.

Translate

Rishaar

Participant

This "fix" doesn't work.
This has been going on for a year now, why cant we just disable this feature in preferences????

Translate

C

CloudDisaster

Known Participant

We're nearly at a complete standstill. Media goes offline every 5 minutes. Making it offline and then relinking will sometimes buy you another 5 minutes.

Software rendering does not fix it.

Runnning all pending windows updates didn't fix it.

Blowing away all preferences and plug-in caches doesn't fix it.

Sychronizing all computer and server time(s) doesn't fix it.

New projects don't fix it.

Upgrading to 14.4 didn't fix it.

Rolling Quadro P4000 drivers forward, then backward, then backward about 6 times didn't fix it.

Reinstalling Premiere didn't fix it.

Blowing away all caches--all of them--fixed it. For about 6 minutes. Because I suspect that's how long it took to create a bunch of corrupt caches again.

This ia an absolute show-stopper in a PRODUCTION, as if the project the file resides in is open and in use by another user (you know--the thing that makes PRODUCTIONS useful?) you need to contact them (pray they're at their desk) and get them to either make the clip offline and relink it, or relinquish control so you can do it. Every. Five. Minutes.

We're not rocking some wack-ass social media app codec here--bog standard XDCAM, DNxHD and ProRes. Broadcast formats that have been ironed out for eons. There should be no surprises here.

Have sat on hold with Adobe for 2 40 minute sessions now, and when it eventually forces me to leave a call back number, it never beeps, and then just give me dead air...into which I give my name and number (can't hurt, right?), and then never hear back.

Really, really, really, really not digging on Adobe right now. Not at all. Not even a little bit. Like, I'm angry turning on my computer in the morning knowing this is the mess I have to face with deadlines looming.

Our chief technology officer this morning: "Remind me why you don't use Resolve instead? I can't seem to find as many people screaming about show-stopping issues like these in that camp..."

Translate

Dylan Garton

Participating Frequently

Most users would swap new features for some stability that's for sure. I think the Premiere team need a new leader.

I'm not sure how long Adobe can go on like this, they'll lose customers, especially people who aren't tied to other CC apps.

Translate

Show more replies

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.