Showing posts with label bad sync. Show all posts
Showing posts with label bad sync. Show all posts

Sunday, August 22, 2010

Getting the Most from YouTube Help When Your Video Fails


How to get specific help when a video goes bad.

The first thing you may want to do is look at (and possibly share) a MediaInfo report on the file you uploaded. 

The MediaInfo utility is free, open source and, once installed can offer a concise but detailed technical overview of your uploaded video.  It can also provide details about other types of media files, such as your source video, digital photos, audio recordings, and other multimedia files you might have used in your work.  

MediaInfo reports can reveal useful, detailed information when applied to source video, and reveal conflicts between source video and what you rendered and uploaded.  


Such conflicts are often at the center of many technical issues with YouTube videos.  


You can find the downloadable installer (and the source code) for MediaInfo at http://mediainfo.sourceforge.net/  It does need to be installed, but it's a small utility and takes little space or time to install.

MediaInfo Capture
This is what the text-only view looks like for a MediaInfo report.

If you think one of the source videos or other media files are involved with the problems you're having, you may want to offer details about those files too. If you're fairly experienced with editing and rendering, the report may give you clues to the problem all by itself. But if you're fairly new to video, or just not technically-minded, others are likely to be able to offer far more pointed advice if you share this information up front. 

Vague questions generate vague answers, and sometimes lead to burn-out from those trying to be helpful.

Be sure to cut and paste the text-only version of the report.  The Text format is selectable from the View tab of the report.  

Others formats make the reports hard to read, or may not cut & paste at all.  The image shown (click it to see a larger, full-size, readable version) and the text below both show what a typical MediaInfo report should look like.  

If yours looks like it is repeating lines or is otherwise hugely redundant, check under the Debug tab to see that Advanced is not checked and that Debug-0 is checked:

General
Complete name : D:\YourVid\Awesome\ThisMovieShouldBeWorking.mp4
Format : MPEG-4
Format profile : Base Media / Version 2
Codec ID : mp42
File size : 97.2 MiB
Duration : 1mn 20s
Overall bit rate : 10.2 Mbps
Encoded date : UTC 2010-07-28 07:11:38
Tagged date : UTC 2010-07-28 07:11:38

Video
ID : 2
Format : AVC
Format/Info : Advanced Video Codec
Format profile : Baseline@L4.0
Format settings, CABAC : No
Format settings, ReFrames : 2 frames
Muxing mode : Container profile=Baseline@0.0
Codec ID : avc1
Codec ID/Info : Advanced Video Coding
Duration : 1mn 20s
Bit rate mode : Variable
Bit rate : 9 978 Kbps
Width : 1 280 pixels
Height : 720 pixels
Display aspect ratio : 16/9
Frame rate mode : Constant
Frame rate : 119.880 fps
Original frame rate : 59.940 fps
Resolution : 24 bits
Colorimetry : 4:2:0
Scan type : Interlaced
Bits/(Pixel*Frame) : 0.090
Stream size : 95.3 MiB (98%)
Language : English
Encoded date : UTC 2010-07-28 07:11:38
Tagged date : UTC 2010-07-28 07:11:38

Audio
ID : 1
Format : AAC
Format/Info : Advanced Audio Codec
Format version : Version 4
Format profile : LC
Format settings, SBR : No
Codec ID : 40
Duration : 1mn 20s
Bit rate mode : Constant
Bit rate : 192 Kbps
Channel(s) : 2 channels
Channel positions : L R
Sampling rate : 44.1 KHz
Resolution : 16 bits
Stream size : 1.83 MiB (2%)
Language : English
Encoded date : UTC 2010-07-28 07:11:38
Tagged date : UTC 2010-07-28 07:11:38


Depending on the container, codecs and other details it may looks somewhat different.  This particular report is for an HD (720p) MP4 video container, generated from Sony Vegas Pro 9.0.  But the overall structure of the report will usually contain three blocks of text:  General, Video and Audio.  

If your report is missing one, or has multiples, that in itself may suggest a problem.  YouTube has a nasty habit of expecting just one video stream and one audio stream, preferably of exactly the same running time.

Keep in mind that most of the people likely to respond to a question on the forum are users like yourself, and those who are actually trying to help are usually those with the least free time to spend back and forth pulling out the various details that are basic to making any kind of informed suggestions or identifying your problem as a emerging, widespread issue.  You'll find people are much more generous with their time if they see that you're already prepared and are willing to share enough details to make their efforts worthwhile and not just an exercise in frustration on both sides.

Tuesday, June 2, 2009

Is the HQ35 Mystery Solved?

[This post is under review: Expect revisions soon (or not). Specifically, I spotted some issues in my test video that have me questioning some assumptions I've made so far. More detail will be added, once I've sorted out just how significant the effect of these discoveries may be on the issue at hand, getting smooth, high frame rate playback under HQ35 encoding and the related issue of getting the HQ35 encoding at all.

At this point, getting HQ35 has become such a rarity that I've backed off on seeking an answer to a question that has almost become moot.]


Sadly it's going to be a little hard to tell since so far, uploading test videos comparable to the ones in the previous demo of this problem will not seem to render to HQ35. However, without the alternating squares in each pair of frames, there still seems to have been significant progress, in this video.



and in this one:



The first video was rendered in Sony Vegas Pro 8.0c. Full specs are provided in the description section of the video's YouTube page.

I need to confirm just how the second video was rendered. I suspect it was done in Final Cut Pro, probably as a Quicktime container using H.264 video and AAC audio.

The key either way is to boost the number of reference frames or (in Quicktime) keyframes. Onno (maker of the animation) says that he increased the keyframes to 1 keyframe per frame... in other words, each frame is also a keyframe. I hope he will see fit to share more detailed rendering specs and settings that I can download and implement. This was discussed in some detail in a recent thread in YouTube's recently renovated Help Center.

A render of my adapted test video, with the alternating blocks appears below the fold.



Be warned, though, that at least at the time this was uploaded, it only received the HQ18 encoding. I suspect this may be because, to defeat frame droppage in HQ35, videos have to meet a certain standard of "compressibility," so as to avoid presenting them at such a high bit rate that they become too difficult, time consuming, (and costly) to stream effectively, particularly for those of us with slower connections.

So here's the one with the bouncing boxes:



Enjoy! And please leave comments if you find that this information is not helping to eliminate stutter and lost frames in your HQ35 videos. This is a very new development and I'm far from confident that this is a definitive answer.