| Commit message (Collapse) | Author | Files | Lines |
|
Follow-up to 99ceb03a1cfcf35968cab589ea188a8c406cda52
|
|
These functions were composing the entire frame, not just the headers. Rename to more accurately describe them.
|
|
|
|
GPU decoding seems to be more picky when it comes to the maximum number of reference frames.
|
|
|
|
Makes for less code that we need to maintain.
|
|
|
|
Prevents bugs from occurring where the results of a function are
accidentally discarded
|
|
Enforces the type of the desired value in calling code.
|
|
Prevents a few unnecessary inclusions.
|
|
This commit aims to implement the NVDEC (Nvidia Decoder) functionality, with video frame decoding being handled by the FFmpeg library.
The process begins with Ioctl commands being sent to the NVDEC and VIC (Video Image Composer) emulated devices. These allocate the necessary GPU buffers for the frame data, along with providing information on the incoming video data. A Submit command then signals the GPU to process and decode the frame data.
To decode the frame, the respective codec's header must be manually composed from the information provided by NVDEC, then sent with the raw frame data to the ffmpeg library.
Currently, H264 and VP9 are supported, with VP9 having some minor artifacting issues related mainly to the reference frame composition in its uncompressed header.
Async GPU is not properly implemented at the moment.
Co-Authored-By: David <25727384+ogniK5377@users.noreply.github.com>
|