[FFmpeg-trac] #6420(undetermined:new): hwaccel cuvid breaks B-Frames with h264_nvenc
FFmpeg
trac at avcodec.org
Fri May 26 19:41:07 EEST 2017
#6420: hwaccel cuvid breaks B-Frames with h264_nvenc
-------------------------------------+-------------------------------------
Reporter: ahakon | Owner:
Type: defect | Status: new
Priority: normal | Component:
Version: git-master | undetermined
Keywords: cuvid, | Resolution:
h264_cuvid, h264_nvenc | Blocked By:
Blocking: | Reproduced by developer: 0
Analyzed by developer: 0 |
-------------------------------------+-------------------------------------
Comment (by jgirot):
I was about to file a bug because I have encountered this same problem
(almost I'm using mpeg2_cuvid). This is a regression in ffmpeg. I was able
to do full hw-transcoding with ffmpeg v3.2.4, but not in latest git.
I performed a git-bisect and the first bad commit is:
af1761f7b5b1b72197dc40934953b775c2d951cc
This is the commandline I used for the git-bisect:
{{{
FFREPORT=file=$logfile.log:level=99 ./ffmpeg -report -v 9 -hwaccel cuvid
-c:v mpeg2_cuvid \
-i $INFILE -c:v h264_nvenc -rc-lookahead 24 -bf 3 \
$OUTFILE 2>&1 | tee $logfile.cli.log
}}}
With this I get an error about not having enough surfaces, but if I change
the cli, then I can get the error about not having an encoding device.
I don't know the ffmpeg source very well, but based on the comment from
the commit there was a change in how input files are initially probed. I
believe that changed how cuvid is initialized which leads to there being
no free surfaces.
I have attached the log from the suspect commit. I can provide other logs
from my git-bisect if requested.
--
Ticket URL: <https://trac.ffmpeg.org/ticket/6420#comment:4>
FFmpeg <https://ffmpeg.org>
FFmpeg issue tracker
More information about the FFmpeg-trac
mailing list