Today DirectX 12 provides APIs to support GPU acceleration for several video applications such as Video Decoding, Video Processing and Motion estimation as detailed in Direct3D 12 Video Overview<\/a>.<\/span>\u00a0<\/span><\/p>\n We are\u00a0happy to announce that D3D12 has added a new Video Encode feature to the existing video API families, with a new set of interfaces that allow developers to perform video encoding using GPU accelerated video engines.<\/span>\u00a0<\/span><\/p>\n This feature provides a new way for apps to implement video encoding consistently with the\u00a0DirectX\u00a012 principles and style.<\/span>\u00a0<\/span><\/p>\n In terms of data flow, the API takes each video frame represented by ID3D12Resource<\/a> textures and compresses them into an ID3D12Resource<\/a> buffer, that contains the slice headers and\u00a0payload of each encoded frame. Currently only DXGI_FORMAT_NV12<\/a> and DXGI_FORMAT_P010<\/a> are\u00a0available depending on driver support, so input content may need to be color converted and\u00a0down sampled\u00a0previously by the API user.<\/span>\u00a0<\/span><\/p>\n The available codecs today are H264 and HEVC\u00a0and specific support for each codec and their encoding tools\u00a0must\u00a0be queried\u00a0using\u00a0ID3D12VideoDevice::CheckFeatureSupport<\/a> as\u00a0there are\u00a0driver support\u00a0requirements.<\/span><\/p>\n The responsibility for handling the rest of the bitstream codec headers (i.e.\u00a0SEI\/VUI\/VPS\/SPS\/PPS) is completely delegated to the user, who will generate and pack them into the final bitstream along with the compressed bitstream obtained from the GPU operation for each frame.<\/span>\u00a0<\/span><\/p>\n Following\u00a0DirectX\u00a012 principles and style<\/a>, reference frames are managed\u00a0explicitly,\u00a0and their memory is completely tracked by the API user. This allows for clear usage of array of textures or texture arrays to store the DPB having explicit memory budgeting\/management\u00a0control and\u00a0enables\u00a0the API user to have full control\u00a0of\u00a0the DPB size and the reference picture selection strategies. Other aspects of reference picture management such as I\/P\/B picture type selection and B-frame group-of-pictures reordering are also in control in the user, who will track the display ordering and reference frame dependencies topology and submit GPU operations in encode order with the desired picture type.<\/span>\u00a0<\/span><\/p>\n A considerable number of configurable parameters are exposed by this API for the user to tweak different aspects of the encoding process and make them fit best for their scenarios such as: custom slices partitioning scheme, active (i.e. CBR, VBR, QBVR) and passive (Absolute\/Delta custom QP maps) rate control configuration modes, custom codec encoding tools usage, custom codec block and transform sizes, motion vector precision limit, explicit usage of intra-refresh sessions, dynamic reconfiguration of video stream resolution\/rate control\/slices partitioning and more.<\/span>\u00a0<\/span><\/p>\n This API also reports\u00a0encode\u00a0statistics and can be used along with SetPredication <\/a><\/span>and Timestamp<\/a><\/span>\u00a0D3D12 Features.<\/span>\u00a0<\/span><\/p>\n The API usage is similar to other existing Video DirectX 12 features and the high-level steps are:<\/span>\u00a0<\/span><\/p>\n The detailed API interfaces and structures definition can be found here<\/a>.<\/span><\/p>\n For finding more design details and detailed documentation for the API, please refer to this document<\/a>.<\/span><\/p>\n The Video Encode API\u00a0<\/span>is\u00a0<\/span>included as part of\u00a0<\/span>Windows\u00a0<\/span>11\u00a0<\/span>and\u00a0<\/span>can\u00a0<\/span>also be<\/span>\u00a0found in\u00a0<\/span>the<\/span> DirectX 12 Agility SDK <\/a>(<\/span>version<\/span>\u00a01.700.10-preview<\/a> or newer)<\/span>.<\/span><\/p>\n P<\/span>lease see below the list of hardware platforms that currently have support for Video Encode<\/span> for both H264 and HEVC codecs<\/span> and the<\/span>ir<\/span> minimum driver version requirements<\/span>.<\/span><\/span>\u00a0<\/span><\/p>\n Introduction Today DirectX 12 provides APIs to support GPU acceleration for several video applications such as Video Decoding, Video Processing and Motion estimation as detailed in Direct3D 12 Video Overview.\u00a0 We are\u00a0happy to announce that D3D12 has added a new Video Encode feature to the existing video API families, with a new set of interfaces […]<\/p>\n","protected":false},"author":70024,"featured_media":12651,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[1],"tags":[],"class_list":["post-5459","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-directx"],"acf":[],"blog_post_summary":" Introduction Today DirectX 12 provides APIs to support GPU acceleration for several video applications such as Video Decoding, Video Processing and Motion estimation as detailed in Direct3D 12 Video Overview.\u00a0 We are\u00a0happy to announce that D3D12 has added a new Video Encode feature to the existing video API families, with a new set of interfaces […]<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/directx\/wp-json\/wp\/v2\/posts\/5459","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/devblogs.microsoft.com\/directx\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/devblogs.microsoft.com\/directx\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/directx\/wp-json\/wp\/v2\/users\/70024"}],"replies":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/directx\/wp-json\/wp\/v2\/comments?post=5459"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/directx\/wp-json\/wp\/v2\/posts\/5459\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/directx\/wp-json\/wp\/v2\/media\/12651"}],"wp:attachment":[{"href":"https:\/\/devblogs.microsoft.com\/directx\/wp-json\/wp\/v2\/media?parent=5459"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/directx\/wp-json\/wp\/v2\/categories?post=5459"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/directx\/wp-json\/wp\/v2\/tags?post=5459"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}Video Encode API Remarks<\/span>\u00a0<\/span><\/h3>\n
Video Encode API documentation resources<\/span>\u00a0<\/span><\/h3>\n
\n
\n
Video Encode API supported platforms<\/span>\u00a0<\/span><\/h3>\n
\n\n
\n Vendor<\/td>\n Supported platforms<\/td>\n Minimum video driver version<\/td>\n<\/tr>\n \n AMD<\/td>\n \n \n
In development \u2013 ETA Q2 \u20182022<\/td>\n<\/tr>\n \n Intel<\/td>\n \n \n
v30.0.100.9955<\/td>\n<\/tr>\n \n NVIDIA<\/td>\n \n \n
v471.41<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n","protected":false},"excerpt":{"rendered":"