On 14.10.2019 18:56 Timo Rothenpieler wrote in http://ffmpeg.org/pipermail/ffmpeg-devel/2019-October/251611.html : > On 14.10.2019 17:43, Hendrik Leppkes wrote: > > Since some users seem to have blindly passed -refs to their > > commandline which now fails without really telling them why, any > > thoughts on moving the capability check error messages onto a high log > > level so that they are shown by default, since they are the source of > > a failure to encode? > > > > - Hendrik > > Maybe all errors in nvenc_check_capabilities should be warnings instead > of verbose even?
Warning: newbie user-submitted patch attached for your consideration. Attempting to use git send-email as requested. Reference Thread: "avcodec/nvenc: multiple reference frames support" http://ffmpeg.org/pipermail/ffmpeg-devel/2019-October/251611.html Context: https://trac.ffmpeg.org/ticket/8254 The option -refs works OK on newest models of nvidia graphics cards however fails with a slightly obscure (to a user) error message on common but lesser models of nvidia graphics cards (eg 1050Ti). The attached patch seeks to slightly modify relevant error messages and change error messages in nvenc_check_capabilities to be issued as warnings instead of verbose. Thank you for considering the patch. hydra3333 (1): Slightly update nvenc error messages and warnings libavcodec/nvenc.c | 40 +++++++++++++++++++++------------------- 1 file changed, 21 insertions(+), 19 deletions(-) -- 2.17.1 _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
