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)

[mariar39182158]

Been getting the same issue with PP 2020

[M&E Films]

I've been able to resolve the problem relating to an error at frame 0 when adding clips to timeline. I'm not sure if this has been mentioned, but I'm getting the error no matter where the footage is located on any drive. For me, it seems to have issue with proxy folders. If I remove the proxy folder from where the clips are, can import them and dragged to the timeline without the error. Then, I can move the proxy folder back to the clips folder, toggle proxies, and everything works like normal! Try it! Hope this helps

[AlexProkopenko]

I updated my built-in video card driver and this error disappeared. Previously, this error appeared for no reason. Try it, it might work in your case, good luck!

[eprentice01]

I was having both the Missing Frame 0 error and others.  RED Error Triangles everywhere!  All I did to resolve all the errors was uncheck the "Enable Hardware Accelerated Decoder"(requires restart)."  You get to the setting by EDIT>PREFERENCES>MEDIA

I have Premier 2020 - ASUS Zenbook  with I9 8th gen with GEFORCE GTX.  

I hope this works for everyone. 

[riaz_83]

This worked fine for me.....

[levelupyourgame]

Just wanted to say I've been getting this issue when using Speed/Duration to accelerate parts of my videos.

Fixed it by going to File->Project Settings->General

And then under General->Video Rendering and Playback:

Change the Renderer to "Mercury Playback Engine Software Only"

Which SUCKS, because I have a GTX 1080 and shouldn't have to sacrifice performance for something that is clearly a bug on Adobe/Nvidia's end.

[Neofilm]

This isn't working for me, now when i try to play it is playing a few seconds then stops. Adobe SUCKS

[calebparris]

EASY SOLUTION

I didn't understand the "Solved" comment, but here's what worked for me:

Click the little red exclamation point icon in the bottom right (where it's telling you there's an error), and it will bring up a window with all of the errors. Then click "Clear All".

If that doesn't work, delete the bad clip, go find that source clip on your computer and move it to a different folder, then add it back into the timeline from that folder. When the errors pop up, clear them again, and it should work.

[shahnoza1982]

I've just resave the project to other file and no any issue like this.

[olivercrocker]

I just had this same issue and it took me about a half hour of trouble shooting before I finally closed and reopened premiere. Oddly enough, this simple action completely fixed whatever issue I was having. It's possible that I got the error because I reorganized a few files I was working with into a folder while I was editing, but this wasn't entirely the case because one of the video clips that was having the issue was newly imported from my desktop. Also, premiere will normally pop up with a "Media Offline" screen in the playback and prompt you to locate the lost clips when this is the case. Instead it came up with a black screen in the playback and no audio aside from a scratching sound at the end of the clip. Very strange, I've never had this happen while working in premiere before. I suppose the takeaway is to just quit and reopen premiere when this happens, and avoid moving files while you're in the middle of editing. Hope this helps someone. 

[tnote43]

I am currently having the same issue. I am a young content creator and trying to use PP for editing, this started to happen about 3 weeks ago. I thought updating my graphics card would work but today the same message pops up. I don't know what else to do.

[CDSOUZA]

Hi! I am having this error too, tried changing the project setting to Software only, but  I am still facing the error

[crabspanner]

I can't believe we're still dealing with this. Our entire facility is stuck on 2018 because of thise. We have extremely fast 10gbe storage and cannot use either 2019 or 2020 due to constant errors retrieving frames.

For the love of god please add a tick box to disable this awful mess of a feature!

[richardrock]

I agree. Turn off CUDA is the answer? WOW! I went out of my way to make sure I have CUDA. How about fix the software Adobe!!!

[jillf51680068]

Hi! had the same problem, though mine was shot using phone. I was able to solve this by downloading handbrake and uploading the files there. That would work.

[Kevin-Monahan]

Hey Jill,

Couldn't the files be imported into Media Encoder? Did you attempt to create a proxy file? Let me know.

Thanks,
Kevin

[thxapproved2]

I am finding this problem has been happening for quite some time?  This only began happening to me with the upgrade from 2018 to cc2020 (had to wait until I purchased a brand new machine to do so). Now, whenever I open up recently edited projects that use HDV (MPEG2 from a CF card camera-not tape capture) video I am receiving this error. I have NEVER had this with previous versions (well, 2018 and before). I've seen bogus "solutions," that recommend going to "Software Only" rendering. Well, then what's the point of having GPU accelleration? That's not a fix.  I have had mild success with deleting all the .MPGINDEX files and having cc2020 re-scan and rebuild them. But it does not always work.  I have tried changing video card drivers going all the way back until PPRO tells me my video driver is not compatible.

This is a brand new machine with an i9-10940x with 32GB of RAM and a RTX 2080Super running 456.38 Studio Driver.

The only files it seems to have problems with are the M2T files from my Sony HVR-Z7u CF-Card. It doesn't matter whether the project is 10-years old or shot last week. I am having issues on this computer as well as another one at work running the same PPRO version, but with an older CPU and GTX1080. So, it doesn't seem to be machine specific.

With problems such as this (which seem to have been going on forever) these forums really do feel like talking in the middle of the woods to no one. I am hoping this can get resolved.
If there is any more I can do to help or expedite fixing this issue, I would be happy to do so.

Thanks!

[Peder Jacobsson]

Hi, Downloaded 400 HDV tapes (took a while). Did not think it would be a problem since other HDV footage from the same camera works fine. This time, however, for saving time, tapes where downloaded with a download app called Lifeflix. Sadly, the downloaded material will not play back in premiere due to the ERM. I works well in quicktime and in FCP X, and doing any of solutions above will not work (not even creating proxies works) . Looks to me like it could be the codec is not supported in some way. What has happend and might it be solved ?

[Trevor_Asq]

I've been having this with v14.2 and XDCAM HD422 1080i 50Mb/s CBR clips - they play fine in v14.5

[thxapproved2]

@Peder Jacobsson @Trevor_Asq 

Both HDV and XDCAM HD422 are MPEG2 files.  For every file, Premiere creates a ".MPGINDEX" file. I have had luck, closing PPRO, deleting all the .MPGINDEX files associated with the footage, re-opening the project and having PPRO rescan and regenerate new .MPGINDEX files.  >95% of the time, this works.

-Todd

[jpope@madstonefilms.biz]

Has there been another work around or fix for this? I am exporting a drone video with heavy graphics. This terrible work around is going to take over 2hrs to export when it should only take 10 minutes. I am paying allot of money for this creative suite and I am really frustrated with the ongoing fails, crashes and lag of this program. It's getting considerably harder to get any project edited officiantly.  I am now on day two of trying to export a project when it should be wrapped up and I should be moving on to other projects. 

[JeremyAndrewDavis]

This is NOT solved! I never had this issue and then updated to the most recent CC and now EVERY project, no matter the media source, Canon, Sony, etc, gives me this error. I had always had Cuda enabled before and never had issues. Now with an update, all of my projects are giving me garbage errors and bogging down. FIX THIS ISSUE. Don't reply "Solved" when it isn't even really a workaround.

[thxapproved2]

It's not a good fix, but are these files MPEG-based?  If so, try deleting the "*.MPGINDEX" file that is generated (usually alongside the original media-if selected in "preferences"). By deleting these, the newer version of PPro re-scans and regenerates the MPGINDEX files. I have had decent luck with that semi-workaround. I don't have any clue as to whether this is being worked on..

[Brandon5E66]

Hello, 

I have the same Issue, Already tried averthgn that they Said but Still having some issues with the Sofware 

Honestly this is ridiculus and waiting my money already. Please advise and I HOPE YOU GUYS CAN FIX ALL THE ISSUES WITH THE sofware 

[Maja Wilhite-Hannisdal]

I'm having the same issues and am currently pulling my hair out over it! I'm turning bald!

I am not really looking for a fix solution from you all, I want Adobe to actually fix the problem in the software. It is not my job to find creative solutions around the problem. This effects my actual life! This is my actual job!