[FFmpeg-trac] #9351(undetermined:open): bug in several windows builds when reencoding h.264 to h.265 with GPU

[FFmpeg]

#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):

 I tried extra frames all the way up to 15 and it still fails. Also, I have
 tried this on two different machines with two different GPUs and it
 consistently fails on both. So I guess it is possible both GPUs can't
 handle it. Has anyone else tried this with the uploaded MKV with the same
 ffmpeg commands? (FWIW, I did change -hwaccel to cuda)

 Also, I tried -bf0 and got:
 Codec AVOption bf (set maximum number of B-frames between non-B-frames)
 specified for input file #0 (z:\temp\test_H_264_AAC_1080p.mkv) is not a
 decoding option.
 Completely unfamiliar with -bf0.
 If I disable the GPU options, it definitely works. Hopefully this isn't a
 permanent workaround though as I do a tremendous amount of x.265 encoding.
 I could always stay with older versions of FFMPEG also as a workaround
 since this bug only appears in all newer versions.

 Replying to [comment:23 Balling]:
 > Real workaround is -bf 0. Sigh, just like was in #9130. [Or of course
 just do not use -
 > hwaccel_output_format cuda.]
 >
 > ffmpeg-2021-05-30-git-51f1194eda-full_build also has this problem, since
 it also has this a0949d0bcb0eee2f3fffcf9a4810c0295d14c0dc that lead to
 #9130.
 >
 > Still, it is strange that -extra_hw_frames 5 does not work for you.
 Maybe you GPU cannot do it?
-- 
Ticket URL: <https://trac.ffmpeg.org/ticket/9351#comment:24>
FFmpeg <https://ffmpeg.org>
FFmpeg issue tracker