[FFmpeg-trac] #6442(avcodec:new): libavcodec shouldn't advertise hardware specific codecs on systems without such hardware

FFmpeg trac at avcodec.org
Sun Jun 4 09:02:20 EEST 2017


#6442: libavcodec shouldn't advertise hardware specific codecs on systems without
such hardware
---------------------------------+---------------------------------------
             Reporter:  plater   |                     Type:  defect
               Status:  new      |                 Priority:  normal
            Component:  avcodec  |                  Version:  unspecified
             Keywords:           |               Blocked By:
             Blocking:           |  Reproduced by developer:  0
Analyzed by developer:  0        |
---------------------------------+---------------------------------------
 Summary of the bug: >= ffmpeg-3.3: browser won't play youtube video due to
 advertised h264_cuvid codec being present but not functional.
 How to reproduce:
 See https://bugzilla.suse.com/show_bug.cgi?id=1041794
 When using the official crippled avcodec in openSUSE the h264 codec is not
 present but the h264_cuvid decoder is advertised and the browser engine
 attempts to use this codec on no nvidia hardware. I have fixed this by
 disabling cuvid and cuda in the build. I can most probably enable cuda and
 just disable cuvid as a user with the crippled avcodec would most likely
 have the uncrippled version from Packman installed and I can confirm that
 when the normal h264 is available it is used and the youtube video works.
 There is also an anomaly that I can't explain which was also fixed when I
 disabled cuvid and cuda relating to gstreamer's libav see:
 https://bugzilla.suse.com/show_bug.cgi?id=1039163
 Unfortunately I can't reproduce that bug as I have intel graphics but I
 have two low end nvida cards which I will try at a later stage, when I
 have time to risk breaking my system.
 In that bug (1039163) the user has 4 different computers with nvidia
 graphics and gstreamer's libav timed out when attempting to read mpeg-1
 and 2 video, I'm not sure yet if the user has official nvidia drivers or
 the kernel's nouveau drivers in use.

--
Ticket URL: <https://trac.ffmpeg.org/ticket/6442>
FFmpeg <https://ffmpeg.org>
FFmpeg issue tracker


More information about the FFmpeg-trac mailing list