On 6/28/17, Dave Plater <davejpla...@gmail.com> wrote: > On 6/27/17, Wolfgang Bauer <e9325...@student.tuwien.ac.at> wrote: >> Am Donnerstag, 22. Juni 2017, 11:34:03 CEST schrieb Martin Herkt: >>> Is there any reason why FFmpeg is built with --disable-cuda and >>> --disable-cuvid? Neither requires NVIDIA SDK headers anymore—it’s loaded >>> at >>> runtime. I’d like to use those features. >> >> It causes problems for non-NVIDIA users. See the package changelog: >> * Wed May 31 2017 davejpla...@gmail.com >> - Disable cuda extensions to fix boo#1041794: >> ffmpeg 3.3 enablement of h264_cuvid causes browsers not to select >> webm >> >> And the bug report: https://bugzilla.opensuse.org/show_bug.cgi?id=1041794 >> >> Kind Regards, >> Wolfgang >> >> > I've enabled cuvid and nvidia and submitted to Factory but > unfortunately the 42.2 update version remains without it. The above > bug doesn't affect browsers if the full version of ffmpeg is installed > they only attempt to use the cuvid codec if there isn't an > alternative. The other bug concerning the full ffmpeg version which > only affected users with nvidia hardware was fixed in > gstreamer-plugins-libav. > Best regards > Dave > The full version of Tumbleweed ffmpeg will have cuvid and cuda when it is accepted. Dave
_______________________________________________ Packman mailing list Packman@links2linux.de http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
