#11255: Insensible "libx264" encoding default
-------------------------------------+-------------------------------------
Reporter: Jeremy | Owner: (none)
Hopkinson |
Type: enhancement | Status: new
Priority: normal | Component: avcodec
Version: git-master | Resolution:
Keywords: libx264 | Blocked By:
Blocking: | Reproduced by developer: 0
Analyzed by developer: 0 |
-------------------------------------+-------------------------------------
Comment (by Balling):
profile:v option does not always work and sometimes does not overwrite
profile. For example in this example it fails: #9573
>Profile high444 predictive is only forced by qp 0, it cannot be forced by
-profile:v high444, also crf 0 does not force high444 profile and thus is
not lossless. Maybe the cause is deprecation of high 444 itself in ITU
spec in favour of predictive.
Indeed, ffmpeg -i https://trac.ffmpeg.org/raw-
attachment/ticket/9573/test.mkv -c:v libx264 -preset veryfast -profile:v
high444 high10profile.mp4
produces high10 5.1 profile even though I am trying to force high444.
Also profile is incorrectly written when Nvidia encoder is in use, which
is insane. https://trac.ffmpeg.org/ticket/6476#comment:12
>And I guess it's very likely just your playback device doesn't support
10bpc.
ALMOST NOTHING supports hi10p of H.264. That is not really an argument. (I
know Mediatek added it in 2022 and I think Apple M2, M3, M4 added it).
--
Ticket URL: <https://trac.ffmpeg.org/ticket/11255#comment:2>
FFmpeg <https://ffmpeg.org>
FFmpeg issue tracker
_______________________________________________
FFmpeg-trac mailing list
FFmpeg-trac@avcodec.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-trac
To unsubscribe, visit link above, or email
ffmpeg-trac-requ...@ffmpeg.org with subject "unsubscribe".
