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 >
In case you missed it, Compressor has been updated.
Several people have asked about workarounds for encoding 1080p to Apple devices – particularly Apple TV.
This update provides that 1080p capability as a preset.
BTW, Software Updates was "silent: about the availability of these updates (performance improvements for Motion and FCX as well), but a trip to the App Store located them for download.
Good luck.
Russ
Just tried the new YouTube/Vimeo presets. Export failed with QT error code -108.
Try again using single pass. But I'm not in good hope that this update lets me use this program instead of Handbrake and MPEG streamclip. :-(
Single pass worked but the file size is 4 times bigger than with MPEG streamclip with not much better quality.
cigame all works here no problems.
Well, I had a somewhat different result. Had no problem encoding an XDCAM 1080p clip in Compressor, using the new video sharing VBR preset and did the same encode in Streamclip. As expected STreamclip was faster its h.264 file. However the STreamclip file was 3X the size of Compressor's.
Russ
I tried the MyCometG3 x264 plug-in and it seems to encoded faster.
Personally, I use x264 over Quicktimes h.264. Better encoding quality, faster encoding and better control over settings's.
Been using it for years.
BTW, I don't understand why the YouTube (for Vimeo too) settings has the Framer Reordering selected. YouTube in it encoding directions instructs to have this setting off.
Upload to Youtube and Vimeo from Compressor works.
Must have to do with file size. Selecting only a minute works. The whole movie is 15 min. Tried again with error -108.
Try another video and see what happens. It could be the video.
Tried with two different exported from FCP X as pro res
Try a video that don't come from FCPX.
Thanks! Works perfect. Now Compressor behaves like Handbrake. Small files. Good Quality. And what is best, no failed exports after hours of encoding without information what went wrong.
Glad it's working for you.
In the course of testing a longer (13 minute) Pro Res clip to see if I could duplicate your issues, discovered that the update had broken distributed processing. Trying to get it to work only caused Compressor to get stubborn and refused to compress submitted jobs of any sort. Re-set background processing, quit, and repaired an impressively long list of permissions and I was back in business.
So like you, found that Compressor would encode a reasonably long Pro Res clip with the1080p video-sharing preset. I'd say the h.264 quality is no better/no worse than it's always been (IMO, just fair, but acceptable) and it's certainly no faster than before.
Definitely good to have presets that people were asking for.
Russ
And I probably ought to try working with x.264, as David suggested.
But I found that the processor load with x264 is much higher than on using h264. Almost 1600% on my macpro.
Also the file size is a little bigger with x264.
So I will stick to MPEG Streamclip (only 400% cpu load) and h264 presets for now.
You want the encoding to use all of the processing power that your computer can deliver. You can cut the processing to a useable number if you wish. I find the file size about the same... You can also use x264 in Streamclip.
http://realworldvideocompression.com/rwvc/2010/5/7/using-x264-plugin-in-compress or.html
4.0.3 Update
