Skip to main content
hmdigiart.com
hmdigiart.com
Participating Frequently
April 16, 2019
Answered

Error retrieving frame **** at time **

  • April 16, 2019
  • 58 replies
  • 267126 views

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)

 

 

 

 

 

 

 

    Correct answer Jens Trimmer

    Here's an updated article with some troubleshooting steps to try if you are experiencing the error: https://videowithjens.com/premiere-pro-error-retrieving-frame/

     

    If you prefer watching a video, I've made that too: 

    58 replies

    Show previous replies
    Jens Trimmer
    Jens TrimmerCorrect answer
    Community Expert
    March 14, 2023

    Here's an updated article with some troubleshooting steps to try if you are experiencing the error: https://videowithjens.com/premiere-pro-error-retrieving-frame/

     

    If you prefer watching a video, I've made that too: 

      S
      Shannon5CF0
      New Participant
      June 2, 2024

      Folks, clearing the cache with the software reboot solved for me! Now I can use the correct renderer, not have to transcode, use my proxies for quickly editing my .mxf files, and render quickly and efficiently. 

      B
      By2492914424e2
      New Participant
      June 19, 2022

      Same problem here with Macbook Pro M1, 8GB, OS 12.3.1, Premiere version 22.4.0.
      Using MTS files and I've got around 100 videos that I need to put together.
      All source videos are on an external SSD drive. 
      Seems that there's issue with all of them, Premiere changes the first frame of every clip into a black frame. I've done the same process with previous versions of Premiere, but never had any problems. Any ideas?

      R
      Robert25217353bvxa
      Participating Frequently
      July 27, 2022

      Similar issue with 4K iPhone footage. Was told it might be because of H265 codec and variable frame rate that Apple uses. Was able to convert the footage to H264 using Handbrake which solved my problems.

      A
      Anthony5ECB
      Known Participant
      June 8, 2022

      I'm having this issue. Literally nothing that worked for others has worked for me. And it's not an MXF file, it's an MOV, a 10bit 4k MOV from the GH5. I've tried different proxy codecs, moved the file around from external drive to internal back to external, I've tried with and without GPU rendering, restarted my computer, updated everything, deleted the cache files in Premiere. I'm not using any FX or filters, no other file types on the lineline, just the clip. Once media encoder hits the 1:46:08 mark, it fails. Every single time. The source file is fine, no corruption to the image at any point in the file. Nothing odd happens at that point in the file. It plays back fine. I have NO IDEA why it keeps failing to create a proxy. 

      Media Not Found
      Media Not Found
      Participating Frequently
      June 8, 2022
      You may be doing this already but have you tried just pulling the source
      clip into media encoder directly and converting it to Prores? (Not using
      the built in proxy rendering). This is what I've had to do when working
      with problem mxf files.
      A
      Anthony5ECB
      Known Participant
      June 8, 2022

      Hey Media,

       

      I'd considered that, but thought there'd still be a high chance of failure since it would still be compressing it to prores and would have to go through the same error spot, even though it's not exactly the same codec.

       

      I just fixed it in a different way. What I've done is opened it in quicktime, go to one frame before the 1:46:08 mark, split the clip and saved out the first part. I then moved to a few frames after the error, split there and saved the 2nd part. Now I've loaded both clips in Premiere, dropped them in the timeline exactly where they occurred in the original clip and created proxies for them. And that worked. Unfortunately I'll loose a few frames but since this is an hour long clip that will be in a documentary containing segments from hundreds of other long clips, I can get by without a few frames.

      So yeah there must have been some real error at that point in the clip, but I didn't see it. Oh well. Good to know there's a way to split up a video file and be able to save it in its original format.

      macjanas
      macjanas
      New Participant
      May 1, 2022

      Macbook Pro M1 here, 16GB, updated OS (12.3.1), updated Premiere (22.3.1) and the issue is still here.
      Here's my flow:
      - I worked with proxies to cut, add effects etc. for a 5min video clip - external SSD drive connected
      - once done, I connected external HD + SD (over 2TB of 4K), opened the file and replaced proxies with "proper" 4K files
      Premiere started flooding me with error messages. I tried to move back - and re-create proxies, so they would be used only for export, but I can't even do proxies anymore as it keeps showing alerts. 
      I'm stuck, can't find a workaround since M1 doesn't even give the option to change settings to "Software only", switching folder idea doesn't work either. Any help guys? 

      Unicodia1
      Unicodia1
      Inspiring
      April 21, 2022

      Transition in a multi-cam edit was my culprit: I was confused when this happened to me because the output didn't seem to be effected.  When I looked at the timing of the substitution, I saw that it was around the time when I put a transition between an .mts file and .mxf file.  I just exported a short video of 3 minutes, and everything seems fine.  So far, I'm considering this an annoyance.  However, if it starts to mess with visible frames, I will probably try the proxy process that @excited_Genie16B8 recommended. I don't want to go there, but will if I have to.

      S
      SentinelAV
      Participating Frequently
      June 28, 2021

      At this point, it's pretty clear to me that Premiere Pro is abandonware. 

       

      Over the years, it's accumulated so many workflow-breaking bugs, failed to keep up with standard industry features, has in fact REMOVED features, and lacks so many elementary tools (like the ability to *reorder tracks*), that it's not simply not advisable to use this software for video editing.

       

      I've been receiving this bug on random projects since 2019, escalating to the level that the software is now totally unusable. This bug applies to .MP4 files, with playback set to software only. I can't scrub through the timeline for more than a few seconds successfully without an extremely long list of errors popping up. All the standard solutions such as clearing caches, transferring to other drives, resetting preferences, restarting etc fail to solve the problem, and tech support have nowhere to go if their engineers aren't fixing problems. 

       

      I've been using Premiere Pro mostly for the After Effects interop, but now I'm forced by sheer absence of functionality to move to Resolve, where I have stability, but lose the flexibility of working directly with AE. What a shame.  

      Oh but don't worry guys, they just added the revolutionary feature of  'Text Gradients' only 15 years after Vegas did!

      B
      bdscott74
      New Participant
      November 4, 2021

      I'm having this issue as well while using the latest version of Premiere (22.0.0) for the first time. Never had this issue before. Totally unusable.

      D
      defaulteiem1rhu3y45
      New Participant
      November 8, 2021

      Me too - just updated to newest Premiere and now everything has the error. Did you figure it out?

      B
      Brandon5E66
      New Participant
      March 21, 2021

      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
      Maja Wilhite-Hannisdal
      New Participant
      April 17, 2021

      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! 

      Media Not Found
      Media Not Found
      Participating Frequently
      April 20, 2021

      I have this issue with .mxf files from sony cameras every now and then. The last time the only reliable solution was  to rencode the .mxfs as prores or another format. I agree it's extremely frustrating an adobe needs to fix it. 

      JeremyAndrewDavis
      JeremyAndrewDavis
      Inspiring
      December 25, 2020

      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
        thxapproved2
        Inspiring
        January 8, 2021

        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..

        jpope@madstonefilms.biz
        jpope@madstonefilms.biz
        New Participant
        November 17, 2020

        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. 

        T
        Trevor_Asq
        Brainiac
        November 4, 2020

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

        thxapproved2
        thxapproved2
        Inspiring
        November 4, 2020

        @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

        Show more replies
        Terms & ConditionsAccessibility statement
        Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices