[FFmpeg-trac] #6492(undetermined:new): Intel QSV: "No device available for encoder" message is given

[FFmpeg]

#6492: Intel QSV: "No device available for encoder" message is given
-------------------------------------+-------------------------------------
             Reporter:  alexpigment  |                    Owner:
                 Type:  defect       |                   Status:  new
             Priority:  important    |                Component:
              Version:  unspecified  |  undetermined
             Keywords:  qsv, quick   |               Resolution:
  sync, intel, h264_qsv              |               Blocked By:
             Blocking:               |  Reproduced by developer:  0
Analyzed by developer:  0            |
-------------------------------------+-------------------------------------

Comment (by alexpigment):

 When I specify either -init_hw_device qsv:hw or qsv:sw , I get the
 following message:

 {{{
 [AVHWDeviceContext @ 025d8b00] Error initializing an MFX session: -3.
 Device creation failed: -1313558101.
 Failed to set value 'qsv:hw' for option 'init_hw_device': Unknown error
 occurred

 Error parsing global options: Unknown error occurred
 }}}

 For what it's worth, this is on Windows on a system with both Nvidia and
 Intel cards enabled (a monitor is hooked into each to allow testing of
 NVENC and QSV simultaneously).

 Curiously, I tested on two systems with *only* Intel graphics, and
 specifying -init_hw_device qsv:hw processed without error. Specifying
 -init_hw_device qsv:sw would produce the same "Error initializing an MFX
 session" error.

 I did some benchmarks and it seems that the speed is roughly equivalent
 between specifying "-init_hw_device qsv:hw" and not specifying anything.

 --------------------

 So if I reevaluate the problem, here are my findings:

 1) "No device available for encoder (device typo qsv for codec h264_qsv)"
 message is being specified for any system (that I've tested, at least)
 since 2017-06-15.

 2) Specifying -init_hw_device qsv:hw will make the message/warning above
 go away for systems with only Intel graphics (and seemingly will produce
 identical videos).

 3) Specifying -init_hw_device qsv:hw will produce the following terminal
 error on systems with both Nvidia and Intel graphics:

 {{{
 [AVHWDeviceContext @ 025d8b00] Error initializing an MFX session: -3.
 Device creation failed: -1313558101.
 Failed to set value 'qsv:hw' for option 'init_hw_device': Unknown error
 occurred

 Error parsing global options: Unknown error occurred
 }}}

 4) Specifying -init_hw_device qsv:sw will produce the following terminal
 error on any system tested:

 {{{
 [AVHWDeviceContext @ 025d8b00] Error initializing an MFX session: -3.
 Device creation failed: -1313558101.
 Failed to set value 'qsv:sw' for option 'init_hw_device': Unknown error
 occurred

 Error parsing global options: Unknown error occurred
 }}}

 5) Specifying either "-init_hw_device qsv:hw" or "-init_sw_device qsv:sw"
 on any build prior to 2017-06-15 will produce the following unrecognized
 option error:

 {{{
 Unrecognized option 'init_hw_device'.
 Error splitting the argument list: Option not found
 }}}

 ----------------------

 I guess I'm not entirely sure what the point of the change was on
 2017-06-15.

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