[FFmpeg-trac] #9351(undetermined:open): bug in several windows builds when reencoding h.264 to h.265 with GPU
FFmpeg
trac at avcodec.org
Wed Aug 4 00:03:27 EEST 2021
#9351: bug in several windows builds when reencoding h.264 to h.265 with GPU
-------------------------------------+-------------------------------------
Reporter: John Dury | Owner: Timo R.
Type: defect | Status: open
Priority: normal | Component:
| undetermined
Version: unspecified | Resolution:
Keywords: ffmpeg gpu | Blocked By:
buffer |
Blocking: | Reproduced by developer: 0
Analyzed by developer: 0 |
-------------------------------------+-------------------------------------
Comment (by John Dury):
Thanks. I will try "-extra_sei 0" and wait for the 495 driver when it goes
GA. The driver I have installed is 471.41.
Replying to [comment:30 Timo R.]:
> The "Failed locking bitstream buffer: not enough buffer" thing seems to
be another fallout of a bug in the Nvidia-Driver regarding SEI data.
> Passing additional SEI data seemingly causes random memory corruption
and can cause all kinds of explosions when the input has any additional
SEI data (a53 subs, s12m timestamps, other user sei data, ...).
>
> Nvidia has acknowledged that bug and fixed it in Driver 495.
> There is no way for nvenc/CUDA to check the driver version, so there is
no sane way to conditionally disable that feature on older drivers.
>
> I added the "-extra_sei" option for that purpose. Setting it to 0 will
prevent it from writing any extra SEI data, avoding the issue.
> On 4.4 you will have to manually turn off s12m_tc and a53cc, since the
option to turn all of it off does not exist there.
--
Ticket URL: <https://trac.ffmpeg.org/ticket/9351#comment:31>
FFmpeg <https://ffmpeg.org>
FFmpeg issue tracker
More information about the FFmpeg-trac
mailing list