Rendering HD for Facebook using 'Pogressive D/L'

ShaneJ wrote on 3/5/2016, 1:44 PM
Hello. I've been searching the forum and have been unable to find anything regarding rendering HD video suitable for Facebook. I typically use Sony AVC/MCV codec for .mp4 and use the "Internet 1920x1080-30p" template as a base and then tweak the custom settings from there accordingly based on the source and other factors.

My main question is the "Enable progressive download" option. I typically uncheck that because I figure since the video is going to get processed again once uploaded to Facebook, the progressive option wouldn't make any difference other than creating unwanted artifacts after Facebook processing. I have been unable to research that assumption, so I would like to ask if anyone here would know and could let me know either way if that's correct or not? I have a half hour video I need to render and I calculated that I will need to set the bitrate to around 7,250 kbps to make it fit within the 1,700 MB file size upload limit. Wondering if progressive download should be enabled or not.

Additionally, I would love to see some tutorials of the best way to render an edited work from Vegas where the source files are 1080p MOV files with the H.264 MPEG-4 AVC codec (from my Canon Powershot SX-260). Also from iPhone 6 videos.

Any tips and suggestions would be greatly appreciated.

On another note, I really wish Sony would give us the option to "Upload to Facebook" in the File dropdown menu just like they have for YouTube. That is the first thing I look for whenever I upgrade to the newer version of Vegas Pro or update. I do not usually upload to YouTube, but mostly upload to Facebook to share videos with people on my friends list. An upload to Facebook option would be really helpful for me and save me a lot of time.


larry-peter wrote on 3/5/2016, 2:42 PM
AFAIK, the "progressive download" option simply moves the moov atom (which contains indexing and other info about the file) to the beginning of the file so it can be played before the entire file is downloaded. I haven't heard of any artifacts or visual differences introduced by doing this (perhaps others have better info on that).

Perhaps with the moov atom at the head of the file, processing of the file may be able to start before the upload is complete, which would mean your file may be visible on Facebook a bit sooner than otherwise.
musicvid10 wrote on 3/5/2016, 2:51 PM
Do your final render in Handbrake and check "Web Optimized."
Best way allaround.

It means Facebook's servers can process it without waiting for your whole upload in order to find the moov atom.

ShaneJ wrote on 3/5/2016, 3:01 PM
Thanks for the info, atom12.

Musicvid10, thanks also for your suggestion. The only problem I have with that is the videos will have been rendered twice, followed by the Facebook processing. That means the video has been compressed three times in total. I try to keep processing and renders down to an absolute minimum to prevent loss. This is why Sony needs to add a proper Facebook option to the rendering in Vegas.

Too keep as lossless as possible, do you recommend my first render from Vegas for the file to be further compressed/optimized in Handbreak be something like 20,000 kbps or more? The source files are variable from 18,000 to 20,000 kbps.
john_dennis wrote on 3/5/2016, 3:29 PM
"[I]The only problem I have with that is the videos will have been rendered twice, followed by the Facebook processing.[/I]"

Follow this workflow to frameserve directly from Vegas Pro to Handbrake or render from Vegas Pro to a lossless intermediate and use that as your input to Handbrake. In either case generation loss is not an issue.

My main system:
Motherboard: ASUS ProArt Z790-CREATOR WIFI
CPU: Intel Core i9-13900K - Core i9 13th Gen Raptor Lake 24-Core (8P+16E) P-core Base Frequency: 3.0 GHz E-core Base Frequency: 2.2 GHz LGA 1700 125W Intel UHD Graphics 770 Desktop Processor - BX8071513900K
GPU: Currently intel on-die video adapter
RAM: CORSAIR Vengeance 64GB (2 x 32GB) 288-Pin PC RAM DDR5 5600 (PC5 44800) Desktop Memory Model CMK64GX5M2B5600C40
Disk O/S & Programs: WD Black SN850 NVMe SSD WDS100T1X0E - SSD - 1 TB - PCIe 4.0 x4 (NVMe)
Disk Active Projects: 1TB & 2TB WD BLACK SN750 NVMe Internal PCI Express 3.0 x4 Solid State Drives
Disk Other: WD Ultrastar/Hitachi Hard Drives: WDBBUR0080BNC-WRSN, HGST HUH728080ALE600, 724040ALE640, HDS3020BLA642
Case: LIAN LI PC-90 Black Aluminum ATX Full Tower Case
CPU cooling: CORSAIR - iCUE H115i RGB PRO XT 280mm Radiator CPU Liquid Cooling System
Power supply: SeaSonic SS-750KM3 750W 80 PLUS GOLD Certified Full Modular Active PFC Power Supply
Drive Bay: Kingwin KF-256-BK 2.5" and 3.5" Trayless Hot Swap Rack with USB 3
Sound card: Realtek S1220A on motherboard. Recording done on another system.
Primary Monitor: ASUS ProArt 31.5" 1440p HDR10 Monitor PA328QV
O/S: Windows 10 Pro 10.0.19045 Build 19045
Camera: Sony RX10 Model IV

Magix Service Center

View Reliability History

Eagle Six wrote on 3/5/2016, 3:35 PM
Handbrake will encode to mp4. But it will accept a source from many codec and containers. You may want to render to an intermediate format providing near lossless, visually lossless or lossless, then feed that into Handbrake. Just a thought.

I don't use direct upload to YouTube, because YouTube can change the properties of the upload without notice. I would think other online services may do this as well. I always found the extra step less headache in the long run. Just the way I do it.

Best Regards......George

System Specs......
Corsair Obsidian Series 450D ATX Mid Tower
Asus X99-A II LGA 2011-v3, Intel X99 SATA 6 Gb/s USB 3.1/3.0 ATX Intel Motherboard
Intel Core i7-6800K 15M Broadwell-E, 6 core 3.4 GHz LGA 2011-v3 (overclocked 20%)
64GB Corsair Vengeance LPX DDR4 3200
Corsair Hydro Series H110i GTX 280mm Extreme Performance Liquid CPU Cooler
MSI Radeon R9 390 DirectX 12 8GB Video Card
Corsair RMx Series RM750X 740W 80 Plus Gold power pack
Samsung 970 EVO NVMe M.2 boot drive
Corsair Neutron XT 2.5 480GB SATA III SSD - video work drive
Western Digitial 1TB 7200 RPM SATA - video work drive
Western Digital Black 6TB 7200 RPM SATA 6Bb/s 128MB Cache 3.5 data drive

Bluray Disc burner drive
2x 1080p monitors
Microsoft Window 10 Pro
DaVinci Resolve Studio 16 pb2

musicvid10 wrote on 3/5/2016, 4:40 PM
It's not about loss, it's about time.
A lossless intermediate to Handbrake is Standard Operating Procedure in my corner of the business, and if there is ANY resizing or deinterlacing to be done, the results will be better than doing these things in Vegas, esp. at typical upload bitrates. This has been shown to be a consistent outcome many times on this forum.

If you are able to get the Frameserving script going to Handbrake or MeGUI, you will save even more time, with the same color accuracy as an uncompressed intermediate.
ShaneJ wrote on 3/7/2016, 12:19 AM
Thank you so much everybody. I tried out the methods that John suggested to me and it worked great. This is what I'll use going forward. Thank you everyone who responded for all of your help. It is greatly appreciated. Love this forum. :D