Hi guys, after 6-8 hours of trial and error, i’m really losing my patience. I have 2 projects i’m working on, the settings are 1080p59.94fps on both. First one is mainly a slide show of images/ second is various clips. I export from MC a .h264/.mov file and select “same as source”. I then open this file in handbrake and encode a .mp4/ h264 file 1080p/59.94fps. After uploading to youtube, it is really laggy on Chrome and doesn’t even play on internet explorer (shows the YT static error screen). So I tried to upload the .mov file straight out of MC to Youtube and still the same exact issue. Any idea of what’s wrong? Some images were imported others linked into MC but I doubt this is my issue. I think using MC’s import may be my mistake but at this point i’d pay for a resolution or tech support.
I should add, the file size out of MC is 11.3gb and it's only a 3 minute video. After Hbrake encoding, it drops to 116mb but this is still large I believe.
Also I would like to add that other people's videos play fine on my pc without freezing. It's only my uploads that lag, so I know this is a pre-upload issue.
How does the encoded mp4 play straight from your computer drive (in Quicktime or VLC, for instance) before uploading it?
If it plays properly, the problem is unlikely to be related to the Avid/editorial stage but more likely an encoding/bandwidth issue. Perhaps try a lower bitrate?
Hi, thanks for the reply, yes it plays fine on my mac desktop and exported video quality is really nice in QT player. By lower bitrate are we talking from MComposer or HBbrake? (sorry i'm a musician not a video editor). In Hbrake it is at default bit rate of "constant RF 20" and around 10kbps
If the source file plays fine, then try one of the presets in Handbrake such as "Fast 1080p30" or "Vimeo YouTube HQ 1080p60", then, if the defaults don't work, change the quality from Constant Quality to Average Bitrate less than 9000.
Web encoding can be a lot of trial and error until you find the recipe that works for you, leveraging quality with file size.
In Handbrake, in the video tab, under extra options, type keyint=30
This forces the encoded file to have I-frames every 30 frames. This makes for much, much better scrolling and player response. I don’t know what the default setting is, but I have always found it way too low to work with.
Also, I tend to choose an average bit rate (10000 for 1920x1080 footage, which is as Vimeo specifies it), and set the encoder to Ultrafast and I tick the Fast Decode button, and de-select 2-pass. I haven’t done extensive quality comparison but it looks pretty great to me and it’s a huge timesaver.
Here's a YouTube article on upload requirements:
Normal 0 false false false EN-ZA X-NONE X-NONE /* Style Definitions */ table.MsoNormalTable {mso-style-name:"Table Normal"; mso-tstyle-rowband-size:0; mso-tstyle-colband-size:0; mso-style-noshow:yes; mso-style-priority:99; mso-style-parent:""; mso-padding-alt:0in 5.4pt 0in 5.4pt; mso-para-margin:0in; mso-para-margin-bottom:.0001pt; mso-pagination:widow-orphan; font-size:10.0pt; font-family:"Arial",sans-serif;}
https://support.google.com/youtube/answer/1722171?hl=en
Thanks for the reply, I am setting it up now. Would it benefit if I tick "2-pass encoding" box and "turbo first pass" box aswell?
Forgot to mention, I don't do 2-pass, just single pass.
Thanks alot I will try defaults then tweak with the settings if it doesnt work. in media compser do you have any idea why a 3 minute clip of pictures would end up being 13gb after exporting via "same as source"?
nonvohmusic:why a 3 minute clip of pictures would end up being 13gb after exporting via "same as source"?
That totally depends on the codec flavor your source footage is in. Sounds like you're in Uncompressed HD or something. What Same As Source does is copy the picture from the cut into a Quicktime container. The result will be a QT in the same codec flavor as the clips in your timeline. Unless there are multiple codecs/codec flavors in your timeline, then it will convert all to the hightest codec flavor in the timeline. That will also take longer.
So after encoding with handbrake, and trying various settings It has the same issues. The lag/skipping goes away once I downgrade to 480p but that doesnt do my video any good. Still not sure what the issue is. Are there other encoders people reccomend?
Downloaded compressor, going to give it a shot
still have the issue.
Just a final thought:
I wouldn't recommend custom exports from MC. Too slow, and you easily run into gamma issues caused by the QT engine used for Custom exports.
Alternatively, You could export Op1A MXF (via File-Export-AMA) as DNxHD115. That should be something like a 6.5GB file, which you can then upload to YouTube. YouTube will recompress no matter what you send them.
So the lagging issue you describe in the browser is actually a YouTube thing and has nothing to do with what you upload. My note about the I-frames came from me misunderstanding, thinking you had issues playing back the exported files at desktop level, before uploading to YouTube.
© Copyright 2011 Avid Technology, Inc. Terms of Use | Privacy Policy | Site Map | Find a Reseller