Exporting For The Web

andythefilmer

andythefilmer

Veteran
I am sure this is covered many times, but I have a dilemma. I just finished a 7 1/2 minute mini-documentary and I want to upload it to Vimeo. I have the free account, so of course the upload limit is 500MB. For whatever reason, I cannot get the file size under 1.3 GB without it looking like crap in the .mov format. I tried .avi and it was 21 MB but there was so much artifacting, and I set it to be the best quality. Same with the MP4 format. My backup plan was to upload to YouTube since it can accept up to 2 GB and then download off 'my videos' as a MP4, but for whatever reason, YouTube cut off the video for the first 5 seconds, but not the audio. Is there a way I can get the file size to an acceptable limit under 500MB with good quality still? I want it on both because Vimeo is my professional resume but YouTube has some of my other videos that aren't very professional. Thanks.
 
Hi Andy, export as H.264 - size: 720x405, frame rate=current, key frames every 240, data rate of 1200kbps, audio= AAC 44.1khz, 128kbps.

file will be about 80MB.

If you want HD resolution, you are going to need to compromise the data rate to get a decent file size.


jason
 
Hey all... I don't dare make a new thread on this subject but I am not happy with my exports either.

I have used a PC and made some very nice footage with mp4 h.264 at variable 10-14mbs...

I try the same thing with FCP and get unsatifactory results. My blacks are all pixelated, the quality is non-hd looking and I am just not impressed. I am using mp4 h.264, 10,000kbs, keyframe 60....

Any suggestions? Ive seen the suggestion for this link, but thats old stuff... http://www.kenstone.net/fcp_homepage/youtube_compressor_gary.html

PC clean footage: http://vimeo.com/6620323 pass:tut2009

FCP footage: http://vimeo.com/7804140
 
Are you exporting directly from FCP via 'export using QT conversion"? If so, try exporting your movie to a master file first, using your current settings in fcp, THEN using QT pro (ver 7 and below only, I hear) export to H264.
It will preserve colors that way. You could also use Compressor to do the same.

Make sure it's on 2-PASS, not single pass.

Hope this helps.
 
Uprez to HD

Uprez to HD

AwakenedFilms said:
Hi Andy, export as H.264 - size: 720x405, frame rate=current, key frames every 240, data rate of 1200kbps, audio= AAC 44.1khz, 128kbps.

file will be about 80MB.

If you want HD resolution, you are going to need to compromise the data rate to get a decent file size.

jason
Click to expand...

So you're recommending these setting with DVX100b DV footage? I'll give it a try to day
and post the results on Vimeo. I too am not satisfied with my export quality.

One more thought - I've heard people talk about up-rezing their DV footage to HD and
then exporting using the h.264 codec to Vimeo. Does this improve the quality? If so, what
software are people using to do this. I'm editing with Premiere Pro CS3

Thanks.

Peter
 
Tim Joy said:
Are you exporting directly from FCP via 'export using QT conversion"? If so, try exporting your movie to a master file first, using your current settings in fcp, THEN using QT pro (ver 7 and below only, I hear) export to H264.
It will preserve colors that way. You could also use Compressor to do the same.

Make sure it's on 2-PASS, not single pass.

Hope this helps.
Click to expand...

Ill give it a try... I have heard compressing with other programs is better then FCP... all that money spent and claimed power - they cant get a good export function? boo
 
SO gay... compressor makes much better low bandwidth video!

Anyone want to share a good setup for 1280x720 mp4 .264 ? (Vimeo)
 
MadHMC150 said:
Ill give it a try... I have heard compressing with other programs is better then FCP... all that money spent and claimed power - they cant get a good export function? boo
Click to expand...

FCP is currently 10 year-old-code. It's still 32bit. And is completely dependent on QuickTime 7 which dates back to the early 90s! Think about that in computer life terms!! The program code is simply not multi-core friendly.

It's hit its natural speed limit. A brand new 64bit FCP & QuickTime, built from scratch is happening now. The stripped down QT X we can use already on SL, but only for consumer level features.

Programing a complicated software application takes a long ass time. Not to mention that the OS & computer hardware are still in a 64bit transition. Apple ( and Adobe Photoshop ) have to re-create or translate ALL of their older Carbon based apps to Cocoa programing code. The reason is that Carbon is limited to 32bit. 64bit requires Cocoa. That includes FCS & even iTunes. That's an enourmous task at hand just for one application. Multiply that to all the programs Apple develops...

Even compressor is still 32bit. But Apple has created a workaround by implementing virtual clusters for multicore systems. I can testify first hand, the advantage is worlds above what FCP can do which doesn't have virtual cluster's built into the software. Compressor's ONLY purpose is to transcode & batch render format to format. Naturally it SHOULD do better then FCP. It doesn't have to think about editing.

My Leatherman has a decent screwdriver on it, but it's no match for a proper drill. My drill doesn't have to think about cutting, filing, scissoring, or fitting into my front pocket. My drill has a huge battery and rotates in two directions... really really well. It wont' fit in my pocket though. :~)

Rendering a 5 min clip into h.264 web streaming video takes what seems like merely seconds when using virtual clusters and a Mac Pro.
 
Last edited:
You must log in or register to reply here.
Back
Top