Error Retrieving frame

[Bryan Ramirez]

We're having a very hard time exporting an Episode for broadcast that has the exact same workflow, media, and setting has previous projects.

1. We keep getting errors about retrieving frames on various clips. 

2. We're working off of super macs that have max everything and we have never had issues before installing the update.

[Mike Dziennik]

Is the error on that particular file? Can you export if you remove that clip? If you can, try re-encoding it to another intra-frame codec like ProRes separately and relinking the clips to that file in your project.

[Clint Porter]

I am having this exact same problem exporting with Media Encoder. My TV episode mastering workflow hasn't changed lately. The problem has only begun after the 2022 update.

Same as you, iMac Pro with lots of power and RAM. I can export within Premiere just fine, but every Media Encoder export crashes on a random frame saying "error retreiving frame" from one of the source footage clips. The source footage is all MXFs from Sony FX1s. The mastering codec is ProRes 422. It happens on every program and with footage from different cameras, so it's not just one corrupted clip.

[Richard van den Boogaard]

Have you updated the GPU driver since updating to CC2022?

Try to delete the entire media cache.

If that does not work, consider creating a blank project in CC2022 and import the previous one.

If that does not work, please report back.

[Clint Porter]

Thanks Richard,

I did figure out a workaround today! First, with regard to the steps you recommended:

• Update GPU driver: this seems to be N/A for an iMac Pro/Mac OS setup. I'm on Big Sur with all point updates.
• Delete media cache: (I think I tried this a month or two ago and it didn't work?)
• Drag everything from old project into a new blank project: This has solved many other mysterious issues for me in the past, so this was one of the early things I tried. Didn't work.
• I also tried disabling Hardware rendering: didn't work

WORKAROUNDS DISCOVERED:

• Render using Premiere Pro instead of Media Encoder: This works reliably, but is impractical for my workflow and time constraints.
• Copy MXF footage to desktop on internal drive and relink files: This is the workaround I'm using for now, and it seems to work reliably. I tried it after coming across some tips online where people have had past issues with Premiere reading MXFs off of external disks. Typically I do most of this work on a 2TB Samsung T7 SSD connected directly to the Mac via USB 3 cable. It's a champ; very fast and stable. (I also have assorted necessary assets pulling from a second 6TB mirrored high-speed external drive.) If I use the MXF files on my desktop, Media Encoder no longer crashes. I'm still using lots of other assets on the T7 and also rendering to the T7. It's not a workaround that will work for all pro workflows since people need to be able to use external drives, but it will get me through until Adobe gets this sorted out.

[Clint Porter]

Update: working on the next new program, Media Encoder now failed for me on an MXF on my desktop. Premiere Export worked as always. Back to the drawing board.

[Clint Porter]

Richard, I have another program to export and I wanted to try deleting the media cache in case a cache corruption is somehow interrelated to my problem. Can you clarify, do you mean to simply press the "Delete" button on the Media Cache Files in Preferences, or do you mean something more involved?

[Richard van den Boogaard]

Personally, I am more keen on helping people solve their editing issues, not so much hard- or software issues.

Please check this: https://community.adobe.com/t5/premiere-pro-discussions/unofficial-premiere-pro-troubleshooting-guid...

[Peru Bob]

Richard,  Can you clarify, do you mean to simply press the "Delete" button on the Media Cache Files in Preferences, or do you mean something more involved?

By @Clint Porter

I'm not Richard, but see here:

https://community.adobe.com/t5/premiere-pro/faq-how-to-clear-your-media-cache-in-30-seconds-in-premi...