Post
by Mister Hatt » Sun Jan 23, 2011 5:46 pm
It's related to frame indices actually. Disabling b-frames is a terrible idea and you shouldn't do it. Some modes of b-pyramid do things differently to how you'd expect however. "--b-pyramid strict" will most likely fix this. The MP4 muxers that most people use seem to put the MOOV atom at the end, this could also be the problem, try using MKV instead. The last option is that you are for some reason using open GOPs and the first GOP when fed into a sequential decoder is getting hurfed over as it lacks an index. This does surprise me as Google use x264 and ffmpeg internally anyway, and IIRC libavcodec doesn't have this decoding problem. Posting the MediaInfo container dump and SEI headers for your video (x264 options chunk from MediaInfo as well as the 'codec information') should allow someone to tell you which.