> Despite wm4 objections I am resubmitting this patch, because I can > find no other reasonable method for rejecting ffmpeg cuvid decoder > when it can't handle a given video stream. An unreasonable > alternative would be to duplicate the work that cuvid.c does > internally on my application side, and that would be of little benefit > to me and to ffmpeg -- I might as well use the nvenc APIs directly > then. I still see this patch as an improvement.
Cuvid should still return an error, just not on init, while some stream parameters are still unknown, but when decoding the first (couple) frame(s). If there is a case where it doesn't, I'd much rather fix that. _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
