Opened 17 months ago

Last modified 17 months ago

#11568 new defect

422.y4m encoded wrongly

Reported by: huhn Owned by:
Priority: normal Component: undetermined
Version: git-master Keywords: 422.y4m
Cc: Blocked By:
Blocking: Reproduced by developer: no
Analyzed by developer: no

Description (last modified by huhn)

Latest Auto-Build (2025-04-30 13:13) Latest ffmpeg-master-latest-win64-gpl-shared

ffmpeg.exe -i Untitled.bmp -vf scale=out_color_matrix=bt709:flags=lanczos -pix_fmt yuv422p 42224k.y4m

the 42224k.y4m works fine in video players and is 3840x2160 just like the bmp. file should be 16.588.800 bytes but is 16.588.858.

ffmpeg.exe -f rawvideo -pixel_format yuv422p -video_size 3840x2160 -i 42224k.y4m -c:v libx265 -x265-params crf=18 422.mkv
this is producing trash it is producing odd data at the left of right part and moves the chroma relative to the rest of the image. x264 was also tried same output.

edit: file is barely to big here you go: https://drive.google.com/file/d/1eLCFCJb4NKOf3CxTdYaYQDLGvaw7CEbJ/view?usp=sharing

Attachments (1)

422.mkv (301.3 KB ) - added by huhn 17 months ago.
corrupt output

Download all attachments as: .zip

Change History (3)

by huhn, 17 months ago

Attachment: 422.mkv added

corrupt output

comment:1 by huhn, 17 months ago

Description: modified (diff)

comment:2 by huhn, 17 months ago

x264.exe --crf 0 --output "42224k.mkv" "42224k.y4m"
this worked so something wrong with -f rawvideo -pixel_format yuv422p -video_size 3840x2160

ffmpeg needs defined size pixelformat and so on. x264 and video player can do that without any information.
are the 58 bytes meta data ffmpeg can't use them or are they just guessing and get lucky?

Note: See TracTickets for help on using tickets.