Good, Clean Compression for HD Streaming at DVinfo.net

Finn Yarbrough · September 18th, 2012, 07:53 PM

There is a major disparity between the videos that I upload to the internet (Vimeo) and many of the others that I see there. My videos, by contrast, seem plagued by noise and motion artifacts:

I am using FCP6 Compressor, and following the Vimeo guidelines:

H.264
VBR set to "Best"
.mov
24p
Plus, project originally transcoded via Media Manager and edited in ProRes 422.

For examples of how much better videos can look on Vimeo, look no farther than any video on the "Staff Picks" channel. My question: is my problem just that I am shooting with a Letus attached to a 3x1/3" 4:2:0 camera? Or is there a better compressor out there that others are using?

Nate Haustein · September 18th, 2012, 08:04 PM

1) Does the video look this way if you export a full quality ProRes 422 file and watch it on your computer?

2) The video does look weird. It should be better than that.

3) You compression settings above are missing one critical component - bit rate. For 720p, make sure you're running at least 5000 kbps. I use 10,000 kbps for 1080p.

4) An easy way to make a video that looks great is to use the "iPad" preset in FCP, Quicktime or Compressor. It encodes a 720p .m4v file (that works fine on Vimeo) with a 5000 kbps bit rate and 128 kbps audio. If you want to do 1080p, try the "Mac" or "AppleTV" presets.

Finn Yarbrough · September 21st, 2012, 06:27 PM

Thanks for the advice. 5,000 Kb/s actually yields an inferior result to the VBR compression that I am using now (because the max VBR travels higher than 5k, I think). I think that it must have something to do with the organic noise and lack of contract in the original. Somebody in a post-house up here told me that both of those things can be confusing to compressors.

Unless...anybody else has a compression secret?

Sareesh Sudhakaran · September 25th, 2012, 08:33 AM

Have you tried CBR? Not all encoders incorporate VBR very well.

Also, I would never recommend an H.264 to Prores to H.234 workflow. I have always been better off with editing native.

John-Michael Trojan · September 28th, 2012, 09:05 AM

Having ripped the video down and opened in QT, I noticed the frame rate is now 30fps. I know Vimeo has its own re-compression pass after content is uploaded to the site, so not sure if that is where the frame rate change is happening. It looks as if duplicate frames are being inserted before a compression pass, adding to the jerky motion.

Besides looking into the frame rate itself - try increasing the number of keyframes rather than using auto. I like to use every 4 or 5 frames depending on the source frame rate (i.e. 5 for 30fps, 4 for 23.98fps).

September 18th, 2012, 07:53 PM	#1
Finn Yarbrough Regular Crew Join Date: Nov 2010 Location: Ferrisburgh, VT Posts: 179	Good, Clean Compression for HD Streaming There is a major disparity between the videos that I upload to the internet (Vimeo) and many of the others that I see there. My videos, by contrast, seem plagued by noise and motion artifacts: The Ministry of the Stove on Vimeo I am using FCP6 Compressor, and following the Vimeo guidelines: H.264 VBR set to "Best" .mov 24p Plus, project originally transcoded via Media Manager and edited in ProRes 422. For examples of how much better videos can look on Vimeo, look no farther than any video on the "Staff Picks" channel. My question: is my problem just that I am shooting with a Letus attached to a 3x1/3" 4:2:0 camera? Or is there a better compressor out there that others are using?

September 18th, 2012, 08:04 PM	#2
Nate Haustein Trustee Join Date: May 2007 Location: Minneapolis, MN Posts: 1,313	Re: Good, Clean Compression for HD Streaming 1) Does the video look this way if you export a full quality ProRes 422 file and watch it on your computer? 2) The video does look weird. It should be better than that. 3) You compression settings above are missing one critical component - bit rate. For 720p, make sure you're running at least 5000 kbps. I use 10,000 kbps for 1080p. 4) An easy way to make a video that looks great is to use the "iPad" preset in FCP, Quicktime or Compressor. It encodes a 720p .m4v file (that works fine on Vimeo) with a 5000 kbps bit rate and 128 kbps audio. If you want to do 1080p, try the "Mac" or "AppleTV" presets. __________________ Nate Haustein PXW-FX9 / FCPX www.flightcreativemedia.com

September 21st, 2012, 06:27 PM	#3
Finn Yarbrough Regular Crew Join Date: Nov 2010 Location: Ferrisburgh, VT Posts: 179	Re: Good, Clean Compression for HD Streaming Thanks for the advice. 5,000 Kb/s actually yields an inferior result to the VBR compression that I am using now (because the max VBR travels higher than 5k, I think). I think that it must have something to do with the organic noise and lack of contract in the original. Somebody in a post-house up here told me that both of those things can be confusing to compressors. Unless...anybody else has a compression secret?

September 25th, 2012, 08:33 AM	#4
Sareesh Sudhakaran Trustee Join Date: Jan 2008 Location: Mumbai, India Posts: 1,385	Re: Good, Clean Compression for HD Streaming Have you tried CBR? Not all encoders incorporate VBR very well. Also, I would never recommend an H.264 to Prores to H.234 workflow. I have always been better off with editing native. __________________ Get the Free Comprehensive Guide to Rigging ANY Camera - one guide to rig them all - DSLRs to the Arri Alexa.

September 28th, 2012, 09:05 AM	#5
John-Michael Trojan Tourist Join Date: Aug 2011 Location: Philadelphia, PA Posts: 2	Re: Good, Clean Compression for HD Streaming Having ripped the video down and opened in QT, I noticed the frame rate is now 30fps. I know Vimeo has its own re-compression pass after content is uploaded to the site, so not sure if that is where the frame rate change is happening. It looks as if duplicate frames are being inserted before a compression pass, adding to the jerky motion. Besides looking into the frame rate itself - try increasing the number of keyframes rather than using auto. I like to use every 4 or 5 frames depending on the source frame rate (i.e. 5 for 30fps, 4 for 23.98fps).