Error retrieving frame **** at time **

[hmdigiart.com]

I am trying to footage taken at a recent event that I shot with one camera, I imported it into premiere pro cc 2019 and then exported it only to get this error message every few seconds.

"Error retrieving frame **** at time **:**:**:** from the file"

The footage was shot on a C300 at 24 fps, in full HD, the sequence is 24 fps 1920x1080 which is a match./

it's only when I try to export it out that I start getting the error.

Please help.

Thanks

H&M

included is a screen capture (hope it helps)

[Sam016235468]

You are free to do whatever you want. I do my color correcting and then export them as H.264 CBR for further use. This works great and saves me an absolute fortune on storage, especially when upgrading my storage requires removing 16 4TB drives and replacing them with 8TB drives or larger. This is not only a Premiere.Media encoder issue, which is hoiw I ended up here. I hade the same issue on After effects. I haven't used Premiere because they seem morinterested in ruining the program instead of making it more user friendly. I have moved to that other one that you actually own and don't have to maekw forever payments on.

[JOHN MONDO]

Sam - if you're having this issue on AE perhaps it's the fact that you're using H264 as your editing format? Could there be a connection? I've never had this issue in AE. Like I said - it's fine if it works for you but it is NOT advice I would be giving to most editors. For a start, I individually colour correct shots and like most editors I do it on the edited material as to do it on the source would be crazy and involve hours of unnecessary work. I also make a living at this so if i have to spend money on storage that's a cost of doing business. Some of the projects I do the client has spent $AUD30K+ just on the shoots. I don't think they'd be too happy if I failed to archive the source material in what is already a compressed codec from the camera. 

BTW - I'm not advocating you transcode all your shots into ProRes or DNxHD (although I know some editors who do and swear by it) just the problematic ones that PP and ME are having issues with. You don't even have to archive them with the project. This problem popped up for me and I could not transcode this source material to H264 because all the material is shot in log. And even if I did it might not work because you're swapping Sony or Canon MXF for H264 which still involves decoding GOPs. Both ProRes and DNxHD are intraframe formats - ie they compress individual frames - they don't rely on previous or following frames for information. It's an important distinction.

[Sam016235468]

The problem I have had has only popped up a few times and it has always happened on footage I have had and used for many, many years, so it is not a codec issue.  This footage is footage that works, then after quitting and opening after effects again, it stops working and throws the error. These files also have worked fine in the other editor (that I'm not allowed to mention here.) that I do all my editing work in now.

On a side note, I wonder if they ever fix that problem with the double spaced file names not loading in After Effects for well over a decade.... I just checked and nope still there.

[JOHN MONDO]

I've been using AE since the early 2000's and have never seen this issue on AE. Error retrieving frame is normally a timing issue although it can be corrupt files. Anything that is encoded in DV/HDV mts or mpg is automatically suspect. I had an HDV recorder that encoded files that weren't recognised in any NLE and I was on Avid back then. The only solution was to transcode them in a program that didn't spit the dummy. 

[kyler67821026]

When you say the cable was the issue/there was a bad connection, do you mean the cable speed was the problem?

[kyler67821026]

I've been having this same issue too. After trying deleting cache, relinking, and basically everything else that people have suggested, what finally worked for me (per Video with Jens - https://videowithjens.com/premiere-pro-error-retrieving-frame/) is transcoding the MXF into another file format. So, to put it another way, this is entirely an issue with Premiere and there is no fix until Adobe decides to actually fix it. Having it still be an issue after four years is ridiculous, and it's especially frustrating given that so far, the transcoding I've tried of the MXFs significantly changes the look.

[alexm44078105]

Same issue as well. Seemed to arise in the last two weeks or so. I was wodnering if it was my DXNR files. Cause when I pull in H.264 I get no errors. But really that shouldn't be happening regardless. 

Then tried installing an old update and that did not fix it either. Seems like we need a new update Adobe. 

[SentinelAV]

It blows me away that people are still having problems despite this issue
being logged for almost half a decade.

--
Thomas Crotty

Creative Director

Sentinel AV

[JOHN MONDO]

It definitely shouldn't be changing the look. Are you using Media Encoder and either ProRes 422HQ or if you are on a PC DNxHD in 10 bit? Remember with DNxHD you have to match the target format to the source.

[Matt23348914u42z]

What solved my problem was disabling the 'Posterize Time' Effect, so I can only assume that every effect that changes frames will cause the issues. I would try to disable all effects first.

[PopHame]

A wee update to this - but please note that the BELOW SOLUTION DOES NOT APPLY TO EXPORT PROBLEMS arising from frame retreival errors, but to system bogging down with frame substitutions.

Was having the same-ish problem on a new install (and new machine) of Pr 24.2.1 (build 2) with 1080p25 HD422 .mxf files, initially on external GRAID HFS+ formatted 7200rpm drive mounted via MacDrive on PC (w11, fully updated at time of post). 

Wherever and whenever the play-head came to rest, either in Source or Programme Monitor/Timeline - not actually doing anything just sitting there - a slew of "error retrieving frame" alerts would pop up, starting after a minute or so referencing the clip in question, substituting adjacent frames, and then eventually substituting black video.

This was a new problem with a brand-new, well-spec'd, fast processor machine with 32gb ram, 16gb workstation GPU, different drives on different USB 3 ss10 ports. 

I had NO PROBLEMS DURING EXPORT, but viewing and working with footage got really clunky with duped frames, black video inserts etc. Problem would go away when media was rendered on the timeline (obviously not a cure for Source monitor media) - until any changes were applied, the the errors and clunkiness would return.

Restarts, deleting cache files, switching drives etc, made no difference.

I then spotted that 'playback resolution' was set to "1/2" (default on install apparently), which was not necessary given my setup. Switched to 'Full' and all the errors stopped.

I guess this may return if I find some way to max out my setup, perhaps with 8k video or hundreds animated video layers. Hopefully by this time ADOBE WILL FIX THIS!

Good luck out there - and happy knitting.

- x

 j

 w