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, I noticed that all files I tried to upload 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)

mkv -c:v libx265 -preset medium -x265-params crf28 -pixfmt yuv420p -c:a copy 8bit. I was indeed using the “high” profile (see this for learning more about these profiles). Step 4: Start to Convert H264 x264 to HEVC x265. “Only YUV 4:2:0 pixel format is supported”.I double-checked things like pixel aspect ratio etc, and then I found two more rather rather specific criteria: I looked for further documentation and then found which has a section “Video specifications and recommendations”. I found other people’s ramblings about the above error message, but all these resources were not really offering a precise understanding: The error message linked to a rather unspecific help page showing constraints with respect to resolution, frame rate, aspect ratio - but the video I was trying to upload seemed to meet all those listed criteria. ffmpeg log says the input stream is bmp and I specified the target as h264 yuv420p. Color shift problem Ask Question Asked 11 months ago Modified 2 months ago Viewed 397 times 1 The ffmpeg command below is being used to capture the desktop and create a resulting mp4. Yet, no matter what I tried, I got the following error message when trying to send the tweet : Using ffmpeg gdigrab to capture desktop output to h264 yuv420p. I chose what I thought were sane and common parameters (mainly ffmpeg defaults), also sane aspect ratio and resolution and so on.

H264 yuv420p