Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Apple Final Cut Pro X FCPX 10.5.4 no longer will share a master file and Compressor 4.5.4 fails too

  • FCPX 10.5.4 no longer will share a master file and Compressor 4.5.4 fails too

    Posted by Anne Davis on May 24, 2023 at 11:04 pm

    I’m using FCPX 10.5.4 for several years on a documentary I’m finally ready to output. Suddenly Share Master File (which I’ve been using all along doesn’t work) and when I try to output via Compressor 4.5.4 I’m getting fails and error messages like RenderFrameAt returned: 4 for absolute frame 88928. (This has also come back for a totally different frame). I go back into the timeline, the video in that area is not displaying and when I try to relink to the original media that doesn’t resolve the issue. The project is only one hour long so I’m concerned that it’s possibly a hardware issue vs. a corrupted file. Anyone else experience this issue?

    Ben Balser replied 6 months, 2 weeks ago 4 Members · 4 Replies
  • 4 Replies
  • Ben Balser

    May 25, 2023 at 11:34 am

    First, turn off background rendering.

    Then delete all render files for that library.

    Then I’d delete FCP’s preference files.

    See if these three (in this order) help.

  • Mads Nybo jørgensen

    May 26, 2023 at 1:08 pm

    Hey Anne,

    Nothing more awful than when a year of hard work won’t play ball on delivery.

    Absolutely follow Ben’s advice.

    If that does not fix the problem, I would add:
    Investigate if the source file is corrupted, by playing it outside of FCPX?
    If in need of delivering soon, split your Library up into smaller Libraries and render out your project in chunks.
    Where it crashes, disable the media and render out as black frames.
    Re-import “chunks” into new Library and insert missing media. Then render out a full length master.

    Obviously if Media is corrupted, you will hopefully have a back-up drive that you can restore it from.
    Also worth checking whether the editing media drive is “dying”, and replace with another drive to do the work from.


  • Doug Metz

    May 26, 2023 at 6:51 pm

    Hi Anne,

    When you try to share a master for this project, how does it fail, and how far does it let you go into the process of exporting? Any error messages? The more detail here the better.

    Do you have the same issue exporting a master file from every project / library, or is it just this specific one?

  • Ben Balser

    May 29, 2023 at 9:14 pm

    “RenderFrameAt returned: 4 for absolute frame 88928”

    This indicates that in your timeline on frame 88928 there’s an issue. Many times this is due to a corrupt render file. No problem, delete them, FCP will create a new one on its own. But if it’s a corrupt frame in the original media (very rare) then we have a major problem.

    In FCPX Settings > General > Time Display, set it to Frames, then find that frame in your timeline. Does it playback OK? My guess is it will. But I’d place a marker there, too, so you can remember where the problem is. Delete render files, export again.

    Now, IF you get an error message, is it the same frame, or a different frame, or an error not relating to corrupted frames?

We use anonymous cookies to give you the best experience we can.
Our Privacy policy | GDPR Policy