Hi Hendrik, On Tue, 3 Dec 2024 at 17:47, Devin Heitmueller <[email protected]> wrote: > > On Tue, Dec 3, 2024 at 9:57 AM Hendrik Leppkes <[email protected]> wrote: > > The real question is, why are you using cuviddec instead of nvdec? > > side data would already pass through natively with nvdec, and other > > hwaccel-based decoders.
I think it's a good question and I will try to benchmark performance and latency of the nvdec against cuvid for my use case. Are you sure that side data would be natively supported with nvdec? Reading the source code, the only function I saw is ff_decode_frame_props(), which will make the side data not properly sync for my use case. > > I suspect there could be benefits if your workload involves alot of > decoding and the GPU only has a single nvdec unit on it. Even if it's > less efficient to do it with CUDA, getting a graphics card with lots > of CUDA units could very well be cheaper than a card with multiple > nvdec fixed units on it (each of which might only be able to do 10-15 > decodes depending on codec/resolution/framerate). > > Devin > > -- > Devin Heitmueller, Senior Software Engineer > LTN Global Communications > o: +1 (301) 363-1001 > w: https://ltnglobal.com e: [email protected] > _______________________________________________ > ffmpeg-devel mailing list > [email protected] > https://ffmpeg.org/mailman/listinfo/ffmpeg-devel > > To unsubscribe, visit link above, or email > [email protected] with subject "unsubscribe". _______________________________________________ ffmpeg-devel mailing list [email protected] https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email [email protected] with subject "unsubscribe".
