Le lauantaina 1. kesäkuuta 2024, 0.06.55 EEST averne a écrit : > As for your second question, I probably should've given some > context about this decision. Initially I thought about writing a > vaapi driver, but for a number of reasons I decided against it.
VA-API would be difficult anyway as it is tied to Linux DRM. My question remains though: why isn't this implemented with the NVDEC API? FFmpeg already support NVDEC natively with the same set of codecs as this patchset, and presumably with all the necessary codec state tracking. This would also address Timo's concerns by moving the driver into a library, and shield FFmpeg from hypothetical L4T ABI breaks. -- 雷米‧德尼-库尔蒙 http://www.remlab.net/ _______________________________________________ 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".
