Hello Gwenole, As I can see the current implementation of qsv-accelerated components already allows to use external MXF session created by main application. Please look the AVQSVContext structure into \libavcodec\qsv.h, example of its allocation into the \doc\examples\qsvdec.c and how AVCodecContext::hwaccel_context uses into the libavcodec\qsvenc.c::ff_qsv_enc_init()
Only when external session not specified the qsv engine forced to search appropriate device by itself and open an internal session. Tuesday, July 14, 2015, 12:26:41 AM, you wrote: GB> Note it would also be interesting to provide a means to import a GB> VADisplay from the user through an additional function. e.g. in view GB> to interop VA decode to MSDK encode and/or video processing. GB> Regards, -- Best regards, Ivan mailto:ivan.us...@nablet.com _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
