[FFmpeg-trac] #7511(undetermined:new): FFmpeg Windows version with QSV hwaccel fails over TERMINAL

[FFmpeg]

#7511: FFmpeg Windows version with QSV hwaccel fails over TERMINAL
-------------------------------------+-------------------------------------
             Reporter:  msiders      |                    Owner:
                 Type:  defect       |                   Status:  new
             Priority:  normal       |                Component:
              Version:  git-master   |  undetermined
             Keywords:               |               Resolution:
             Blocking:               |               Blocked By:
Analyzed by developer:  0            |  Reproduced by developer:  0
-------------------------------------+-------------------------------------

Comment (by msiders):

 Hi,

 I found specific information in offical documentation from Intel:
 https://jp.xlsoft.com/documents/intel/media/2014/Intel_Media_Developers_Guide_0.pdf

 In section "4.18.1 Muti-GPU and “headless” configurations" indicates:


 {{{
 Applications wishing to leverage the Intel Media SDK’s hardware
 acceleration library
 when a discrete card is the primary device, or on devices without a
 monitor attached –
 such as “Session 0” modes, are required to initialize the Intel Media SDK
 to utilize the
 DirectX11 infrastructure, as well as provide its own memory allocation
 routines that
 manage DirectX 11 surfaces.
 }}}

 So, the solution seems to include a new parameter when initializing the
 QSV context to select D3D11 when calling to MFXInit().

 What you think?

--
Ticket URL: <https://trac.ffmpeg.org/ticket/7511#comment:4>
FFmpeg <https://ffmpeg.org>
FFmpeg issue tracker