These requirements mean you will likely have to compile everything for yourself (especially on Linux), but Shinchiro's windows () appear to be functional. The oldest usable commits are listed below. You will need to compile from git master for each of them. Right now, no release versions of any of the components contains the necessary code. In the short term, there will be rough edges, and only a narrow set of supported codecs (only H.264 and H.265 are standardised today, with AV1 still a work in progress), but in the future, it will hopefully be the most performant and capable way to do hardware decoding and processing. However, Vulkan video decoding has the potential to be a credible cross-vendor, cross-platform API that is well supported, and can work efficiently with Vulkan based filtering and post-processing. Right now, the actual functionality you gain access to is not terribly different from what you would get with existing video decoding APIs that ffmpeg and mpv already support. Why should I even care about Vulkan video decoding? This document attempts to lay out all the requirements and limitations, so you have a chance of successfully using the feature. Although the functionality is now all there, we still have a complex landscape in terms of what is supported on what hardware and with what drivers. On the 28th of May, we reached the significant milestone of finally merging all the required functionality into ffmpeg, libplacebo, and mpv to do end-to-end Vulkan video decoding and presentation. Vulkan Video Decoding: Usage Guide and FAQ
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |