Changes between Version 6 and Version 7 of Hardware/VAAPI


Ignore:
Timestamp:
Apr 11, 2018, 9:20:20 AM (8 months ago)
Author:
mypopy
Comment:

Fix a typo

Legend:

Unmodified
Added
Removed
Modified
  • Hardware/VAAPI

    v6 v7  
    101101ffmpeg -init_hw_device vaapi=foo:/dev/dri/renderD128 -hwaccel vaapi -hwaccel_output_format vaapi -hwaccel_device foo -i input.mp4 -filter_hw_device foo -vf 'format=nv12|vaapi,hwupload' -c:v h264_vaapi output.mp4 
    102102}}} 
    103 This works because the decoder will output either `vaapi` surfaces (if the hwaccel is usable) or software frames (if it isn't).  In the first case, it matches the `vaapi` format and `hwupload` does nothing (it passes through hardware frames unchanged).  Im the second case, it matches the `nv12` format and converts whatever the input is to that, then uploads.  Performance will likely vary by a large amount depending which path is chosen, though. 
     103This works because the decoder will output either `vaapi` surfaces (if the hwaccel is usable) or software frames (if it isn't).  In the first case, it matches the `vaapi` format and `hwupload` does nothing (it passes through hardware frames unchanged).  In the second case, it matches the `nv12` format and converts whatever the input is to that, then uploads.  Performance will likely vary by a large amount depending which path is chosen, though. 
    104104 
    105105The supported encoders are: