With these choices, ffprobe emitted Video: h264 (High) (avc1 / 0x31637661), yuv420pĪnd Twitter accepted my H.264 video. So, I followed this lovely resource and added the following command line flags to ffmpeg to explicitly set the profile High, level 4.0, and to set the pixel format to yuv420p: -profile:v high However, the video file(s) I tried all used the yuv444p pixel format, as shown by this line of output of ffprobe: Stream #0:0(und): Video: h264 (High 4:4:4 Predictive) (avc1 / 0x31637661), yuv444p, 1280x720, 271 kb/s, 30 fps, 30 tbr, 15360 tbn, 60 tbc (default) I was indeed using the “high” profile (see this for learning more about these profiles). “Only YUV 4:2:0 pixel format is supported”.I double-checked things like pixel aspect ratio etc, and then I found two rather rather specific boundary conditions: I then found which has a section “Video specifications and recommendations”. I found other people’s ramblings about this error message:īut those resources were not really helping. At the bottom it talks about constraints with respect to resolution, frame rate, aspect ratio - I got all that right. Yet, no matter what I tried, I got the following error message when trying to send the tweet: It’s not like I know nothing about H.264 and ffmpeg, and I chose what I thought were sane and common parameters (mainly ffmpeg defaults), also sane aspect ratio and resolution etc.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |