Want to highlight a helpful answer? Upvote!
Did someone help you, or did an answer or User Tip resolve your issue? Upvote by selecting the upvote arrow. Your feedback helps others! Learn more about when to upvote >
Did someone help you, or did an answer or User Tip resolve your issue? Upvote by selecting the upvote arrow. Your feedback helps others! Learn more about when to upvote >
I use Compressor to export video all the time, primarily to YouTube & Facebook format.
Podcast video episode - 27 minutes long, not even close to the longest one. Tried multiple times. It barely gets going and dies.
iMac Pro HD has 45 GB free. Running Monterey 12.7.1, 32GB RAM
Error image posted:
Does anyone know what this is and how to fix it?
Thank you,
Jason
[Re-Titled by Moderator]
iMac Pro (2017)
TrainerLarry, if you are still in need of settings, I can zip the Compressor.app/Contents/Resources/Settings/Prepare for HTTP Streaming/ directory and post a filemail link here. The settings files in the folder are dated 1/9/23 with Compressor.app at version 4.7.
Hi, Tom!
This error - ReuestCVPixelBufferForFrame returned... - is not, necessarily, caused by a full hard disk. I am getting this error every time I try to compress HTTP Live Stream files using H.264 (but not HEVC). My main drive has 1.5 TB free, my external drive has 4.4 TB free.
The actual file - which is ProRes 4444 - is 350 MB - so, plenty of room. What I've tried:
This is a relatively new problem - prior to February, this compression setting - which is Apple supplied - was bullet-proof.
I'm open to ideas.
Thanks!
Larry J.
Luis - I edited a 30-sec open separately, exported it from FC and then imported it as a completed file. I added this open to the beginning of the video podcast in the timeline. Then I exported to Compressor as YouTube/Facebook as I normally do. It dies before it even gets two minutes rendered so it has to be this file. But that is confusing because it isn't anything special - just three photos over VO.
Tom suggested re-editing it, which I will do now.
Tom - My iMac Pro HD jad 45 GB open at the start of this project. I am attempting to render this for the 5th time today, trying it in sections.
But - my HD says 1.5 GB!!!!
We have talked about this issue before; ALL of my media is stored on external drives. What in the name of Saturn's rings could be doing this? That seems like the culprit as to why it won't render. But all the files are somewhere other than the iMac Pro HD and I am exporting to an external drive as well!
Your drive is FULL - and even if it had 45GB it probably is too low - usually you want no less than 15-20% free on a system drive.
Whatever other issues might there be or not, a full system drive is a formula for disaster.
Make space NOW.
Please post an EtreCheck report https://etrecheck.com giving the application Full Disk Access in Privacy & Security System Settings. Copy the report and use the Add Text button to paste the result into reply box.
It sounds as if your system is too full to function properly. You have have 15 or 20% free space for the computer to be useable.
Can either of you explain how my hard drive went from 45 to 1.5 when all of the files are stored away from that drive? What is it that is filling up the hard drive simply because I am running compressor?
also, I subdivided the full project by cutting off the first three or four minutes of it and I am now rendering that whole back 4/5 of it in compressor and it appears to be working so that tells me there’s something wrong with the first part of it I just can’t figure out what because all of the files are clean they’re no glitches there is nothing that indicates they’re a bad files there and I don’t know how to figure that out .
The problem is most usually an issue with encoding a specific piece of media. Sometimes it’s the file itself or a render at that location if sending from FCP.
In this case we got sidetracked because of the full drive.
Additional information
I just ran Etrecheck and it found no major or minor problems, aside from three unsigned applications and three unread notifications.
Because I CAN encode H.264, but NOT encode H.264 when using HTTP Live Streaming, my guess is that something in this encoding preset got damaged in a recent upgrade. But I am unclear how to reset the Apple-native encoding presets.
Larry
Terry B:
Yay! I got the files and they work!! Clearly, my old settings were corrupt and reinstalling the program did not reinstall the settings.
(Also, just because I want to tell somebody, while Compressor was compressing these files using an M2 Max Mac Studio and SSD external drive, Compressor was reading data at 2.6 GB/second! Compressor has always been fast, but never THIS fast!
Thanks!
Larry
Usually this means a problem with the media. Are you using Send to Compressor to export a project from FCP? Or compressing a video file?
As Luis said this is often a media problem. Check the clip at the problem frame number. Maybe replace or re-edit it.
Probably system snapshots, cache files. Could be a lot of things. That’s why you need free space. Probably 45G is too little.
I am not sure what system snapshots are. Is there a way to clear them? And can I clear FCP cache?
You can clear them in the Disk Utility. Complete information on system from EtreCheck is really important to help users. There may be other software related issues.
Compressor Error - RequestCVPixelBufferForFrame
