You can make a difference in the Apple Support Community!

When you sign up with your Apple Account, you can provide valuable feedback to other community members by upvoting helpful replies and User Tips.

Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

Error: RequestCVPixelBufferForFrame returned: 3 for absolute frame: 136803

Hi there, I recently updated iMovie and am getting this message when trying to export a file: Error: RequestCVPixelBufferForFrame returned: 3 for absolute frame: 136803


It has happened a couple times now. Any suggestions for how to correct it?


MacBook Pro 15″, macOS 12.0

Posted on Nov 8, 2021 10:49 AM

Reply
Question marked as Top-ranking reply

Posted on Nov 8, 2021 1:19 PM

The error means that there is some kind of corruption at frame No. 136803. The correction is to expand your time line full out and scroll to frame No. 136803 and vicinity and cut out the corrupt frame.


To locate frame No. 136803 in seconds on the timeline divide 136803 by the frame rate of the project. So, if it is a 30 fps project, divide 136803 by 30 = 4560 seconds or 76 minutes. Then use the time/frame counter above the timeline to scroll to the 76th minute. Scroll around in the area of the 76th minute, looking for black frames, white flashes, artifacts, and any other evidence of corruption. Cut out any that you find. You might want to create a duplicate of your project and work with the duplicate so as to preserve your original.


-- Rich

10 replies
Question marked as Top-ranking reply

Nov 8, 2021 1:19 PM in response to Goodieco

The error means that there is some kind of corruption at frame No. 136803. The correction is to expand your time line full out and scroll to frame No. 136803 and vicinity and cut out the corrupt frame.


To locate frame No. 136803 in seconds on the timeline divide 136803 by the frame rate of the project. So, if it is a 30 fps project, divide 136803 by 30 = 4560 seconds or 76 minutes. Then use the time/frame counter above the timeline to scroll to the 76th minute. Scroll around in the area of the 76th minute, looking for black frames, white flashes, artifacts, and any other evidence of corruption. Cut out any that you find. You might want to create a duplicate of your project and work with the duplicate so as to preserve your original.


-- Rich

Nov 8, 2021 1:57 PM in response to Rich839

Another thing you can try, since it is so easy to do, is to delete preferences and see if that fixes the buffer problem. To delete preferences, open iMovie while holding down the Option and Command keys and select to delete preferences in the box that appears. iMovie will open in a new library. Reopen your old library to get back to your projects.  Deleting preferences is a safe procedure that will not cause data loss or disruption to your project.


-- Rich

Dec 16, 2021 11:46 AM in response to Rich839

That explanation doesn't make sense to me. I can scrub or play in the iMovie app just fine. Somehow iMovie will skip, blank, or otherwise deal with the single corrupted input frame (and in fact, I don't see anything wrong with any frame when I'm just going from frame to frame in the app itself), and play the entire edited movie for me with no trouble. It is therefore possible. But when I export to a file, the entire export stops upon encountering one corrupted frame in the input. Not even a dialog box that says "corrupt frame encountered, skip Y/N". So I have to try to find that one frame given an absolute frame number (hey, guess what, the iMovie interface only tells me seconds, not frame numbers, so more fiddling), finally excise the region I think has the bad frame, start another 10 minute export, until it finds the next bad frame (turns out there were 4, widely scattered in my hour-long set of clips). If a single bad frame can derail the whole process, then that's all the more reason for the software's logic to account for this possibility and give the user at least an option of automatically excising the minimum amount that will let it continue starting at the next uncorrupted frame.

Dec 16, 2021 12:02 PM in response to lgritz

I agree that the current procedure for dealing with corrupt frames on export is awkward. A yes or no option to skip the frame and proceed would be nice. That would be something that Apple would need to address. We on this forum are consumers like yourself. We have no input into Apple's software designs or decisions.


You can contact Apple directly at this link:


https://www.apple.com/feedback/imovie.html


-- Rich

Error: RequestCVPixelBufferForFrame returned: 3 for absolute frame: 136803

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.