Thank you so much!

We will test this hopefully today, and verify the expected behavior with NSIGHT.

By the way, I'm new to ffmpeg, so... I don't know if you use your fork to test 
things first, before adding the changes to the main ffmpeg project? Or may we 
consider to compile and use your fork?

Thanks!

-----Original Message-----
From: ffmpeg-devel <ffmpeg-devel-boun...@ffmpeg.org> On Behalf Of Timo 
Rothenpieler
Sent: Tuesday, May 8, 2018 12:11 AM
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [PATCH] Added the possibility to pass an externally 
created CUDA context to libavutil/hwcontext.c/av_hwdevice_ctx_create() for 
decoding with NVDEC

Am 07.05.2018 um 19:37 schrieb Oscar Amoros Huguet:
> I was looking at the NVIDIA Video codec sdk samples 
> (https://developer.nvidia.com/nvidia-video-codec-sdk#Download), where you can 
> find the header NvDecoder.h next to cuviddec.h where CUVIDPROCPARAMS is 
> defined.
> 
> Anyway, I should have looked at ffmpeg code directly, to see what’s being 
> used, sorry for that.
> 
> Great then! Having the same cuda stream (either default or custom) for 
> everything is the safest and most efficient way to go (in this case).
> 
> Thanks, and let me know if I can help with anything.
> 

You can find the mentioned changes on my personal github:
https://github.com/BtbN/FFmpeg

The cuMemcpy is entirely gone, not just Async. And the CUstream can be set and 
will be passed on to cuvid/nvdec.

_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel

Reply via email to