[FFmpeg-trac] #9898(undetermined:reopened): Different result using FFmpeg 5.1 and 5.0.1 with -color_trc log / log_sqrt
FFmpeg
trac at avcodec.org
Wed Aug 31 15:04:16 EEST 2022
#9898: Different result using FFmpeg 5.1 and 5.0.1 with -color_trc log / log_sqrt
-------------------------------------+-------------------------------------
Reporter: gabriele_ls | Owner: (none)
Type: defect | Status: reopened
Priority: normal | Component:
| undetermined
Version: unspecified | Resolution:
Keywords: | Blocked By:
Blocking: | Reproduced by developer: 0
Analyzed by developer: 0 |
-------------------------------------+-------------------------------------
Comment (by Balling):
> The result you achieve with FFmpeg 5.0.1 differs from that you achieve
with the FFmpeg git head
Because of e645a1ddb90a863e129108aad9aa7e2d417f3615, your original file is
full range. This was just a bug in ffmpeg, see #9576 (full range of a file
was being recognized as limited in some cases). Compare your original file
with ffplay before and after that commit:
ffplay.exe CAM1_20220823_2907.MP4
This can also make it obvious:
ffmpeg -i CAM1_20220823_2907.MP4 -map 0:0 -map 0:1 -c:a aac -ab 320k -c:v
libx264 -crf 15 -s 960x540 -vf scale=in_range=tv:out_range=pc -pix_fmt
yuv422p10le -profile:v high422 -preset fast -g 1 -color_trc log_sqrt
-color_range jpeg output1.mp4
--
Ticket URL: <https://trac.ffmpeg.org/ticket/9898#comment:17>
FFmpeg <https://ffmpeg.org>
FFmpeg issue tracker
More information about the FFmpeg-trac
mailing list