Your title here

[Mads Nybo jørgensen]

Hey Brian,

There is a whole list of issues that could be what is going wrong.

Not that you want to, but have you tried to render out the project in smaller chunks, to find the specific frames or videos that are creating the problem?

As Apple gives this advice:

If you see “Video rendering error: 10008” or “Error: RenderFrameAt returned: # for absolute frame: #####”

If you receive one of these alerts when trying to share your project, it means that the clip shown in the alert is unusable. The clip name and its timecode location are displayed in the alert so you can locate the unusable clip in your project.

To correct this, import the source clip again into Final Cut Pro. Before importing media into Final Cut Pro, always back up source media by creating a camera archive. By doing this, you’ll always have a fresh copy available to reimport if necessary.

If a backup or Final Cut Pro camera archive of the source media isn’t available, you may need to record the clip again. Before recording, check with the camera manufacturer for any firmware updates for your camera.

https://support.apple.com/en-gb/HT207791

If you haven’t already done it, maybe trash your preferences to see if that makes a change?

Finally, check your drives, and how full they are?
And, depending on whether they are HardDisk or SSD, maybe there is a bottleneck or something else that gets in the way.

I’m sure that there is smarter people around here with a better answer

Atb
Mads

support.apple.com

Import into Final Cut Pro for Mac from file-based cameras

In Final Cut Pro for Mac, import media from a file-based camcorder or device, or insert a device’s memory card into your Mac or a connected card reader.

[Ben Balser]

Corrupted media is rarely the cause for this erroneous error. Trash pref files (hold opt+cmd while launching) and render files (select the Library in the Browser, File > Delete All Generated…, select all render files). Those are the most common causes of it. FCP since v.1 has been notorious for render files corrupting and causing a lot of issues. And as mentioned, a full system drive can cause this. A system drive is full when less than about 15% of its total capacity is left as free space. The OS (UNIX or Windows) needs that space to write temporary working files that are totally hidden from us end users. If there’s not enough space to do so, it can create very odd issues. Many folks carry this over to secondary drives, though technically they don’t really matter as much, as they’re not used for this function.

When it actually is corrupted media, the frame number should be consistent, not random.