- January 13, 2021 at 11:58 pm
Since Dec 29th, my Compressor (ver. 4.4.8) has failed every attempted render. The error is always about the same.
Failed: Error: RenderFrameAt returned: 4 for absolute frame: xxxxxx
Failed: Error: RenderFrameAt returned: 3 for absolute frame: xxxxx
I’ve tried many times and get the save error message. Now when I go back into FCPX my picture will appear in the FCPX playback monitor when I scrub or play it but then it goes black, Now the entire video is black. Sound but no picture. These 2 videos in question here (the one’s I’ve been trying to render since Dec 29th), one is a single clip (107mins) and the other is a single Compound clip. I loaded in a 3rd project (3 Compound clips) and it appears to be fine. With this one I have done no additional editing since Dec 29th.
Pay attention. I restart FCPX. the first video plays fine when I scrub through. But when I play right before the frame number given in the error message my picture goes black and from that point on one I have NO PICTURE anywhere in the video. It’s all black. No picture but still I have sound. Same thing happens in the other video in question too. All since Dec 29th! Any plug-ins I may have gotten around that time have not been used in these videos.
What the hell is going no here????
Help. Advice. Suggestions.
- January 14, 2021 at 12:49 am
Trash your cache files, and trash your preferences.
At that point in time, where it goes black, what happens if you match frame?
- January 29, 2021 at 9:00 pm
I can no longer Share or have Compressor render any of my new and older FCPX files. I always get this frame error message. Most of the time that frame number is just at a black frame in the video. Like at the end of a fade to black. The last Share I tried it crashed at frame 0.
My cache file is in the Library and I can’t find it. And how do I delete my Preferences?
Until this get fixed, I’m out of a job!
Thanks for any feedback.
- February 3, 2021 at 10:03 pm
We’ll need some information to make sense of your issues.
– What are your system specs (machine, OS, RAM, external hardware / drives, etc.)?
– What version of Final Cut are you running?
– Where do your Libraries and media live, on external drives or on your boot disk?
The degradation in usability suggests you may have some file system corruption, and should run Disk Utility on your drive(s) as a precautionary measure.
Cached files are deleted through the app (File -> Delete Generate Clip Files…)
– Do NOT go digging through the Library package! It’s a database and if you move / delete things in there through the Finder, you’re asking for problems.
- February 4, 2021 at 12:59 am
System: iMac, Mojave 10.14.6, 32GB RAM, 2 9TB external RAIDs, 5 other external storage drives.
Libraries and media for this film are all on same external RAID.
This problem was solved by running a Share of the Project from frame 1 to several frames after the error frame number as Part 1. I then ran Share from the last frame from Part 1 to the end of the Project and Part 2. Made a new Project and dropped in Part 1 and 2 and Shared that out with no problems. Go figure.
- April 6, 2021 at 3:37 am
What we did was run First Aid on the Mac OS drive in the Disk Utility app.
This solved multiple problems, but most likely a corrupt hard drive that Mojave started. Before this fix, we couldn’t run any program without the OS being so slow (with just one App open) on 16GB Ram and an upgraded GPU.
Log in to reply.