mirror of
https://gitlab.freedesktop.org/mesa/mesa.git
synced 2025-12-30 18:40:13 +01:00
read-only mirror of https://gitlab.freedesktop.org/mesa/mesa
c8f644ec44
The Gallium pipe video "frame_num" variable is internally used as a counter of elapsed reference frames since the last IDR. The incoming frame_num field from VA picture parameters is not equivalent; the VA value may wrap to zero prematurely, as it is a 16-bit struct field with a documented max value of 2^(log2_max_frame_num_minus4 + 4)-1. This change improves "infinite GOP" single-client live streaming, where it is reasonable for the server to desire an endless series of P-frames without IDR. Without this change, it is difficult/impossible for an application to encode a P- or B-frame after the VA frame_num field wraps around to zero, depending on the backend encoder implementation. This change has no effect on existing applications that always signal an IDR frame and reset the VA frame_num to zero before it wraps around. For example, the FFmpeg vaapi encoder ignores the VA documentation and sends an un-wrapped VA frame_num, which results in identical computation of the internal frame_num (as long as each GOP is less than 65536 frames). Closes: https://gitlab.freedesktop.org/mesa/mesa/-/issues/5768 Reviewed-by: Thong Thai <thong.thai@amd.com> patch revision 3: correctly avoid incrementing frame_num when the encoded frame is not a reference, per h264 spec and ffmpeg behavior Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/14332> |
||
|---|---|---|
| .gitlab/issue_templates | ||
| .gitlab-ci | ||
| android | ||
| bin | ||
| build-support | ||
| docs | ||
| include | ||
| src | ||
| subprojects | ||
| .dir-locals.el | ||
| .editorconfig | ||
| .gitattributes | ||
| .gitignore | ||
| .gitlab-ci.yml | ||
| .mailmap | ||
| .travis.yml | ||
| CODEOWNERS | ||
| meson.build | ||
| meson_options.txt | ||
| README.rst | ||
| VERSION | ||
`Mesa <https://mesa3d.org>`_ - The 3D Graphics Library ====================================================== Source ------ This repository lives at https://gitlab.freedesktop.org/mesa/mesa. Other repositories are likely forks, and code found there is not supported. Build & install --------------- You can find more information in our documentation (`docs/install.rst <https://mesa3d.org/install.html>`_), but the recommended way is to use Meson (`docs/meson.rst <https://mesa3d.org/meson.html>`_): .. code-block:: sh $ mkdir build $ cd build $ meson .. $ sudo ninja install Support ------- Many Mesa devs hang on IRC; if you're not sure which channel is appropriate, you should ask your question on `OFTC's #dri-devel <irc://irc.oftc.net/dri-devel>`_, someone will redirect you if necessary. Remember that not everyone is in the same timezone as you, so it might take a while before someone qualified sees your question. To figure out who you're talking to, or which nick to ping for your question, check out `Who's Who on IRC <https://dri.freedesktop.org/wiki/WhosWho/>`_. The next best option is to ask your question in an email to the mailing lists: `mesa-dev\@lists.freedesktop.org <https://lists.freedesktop.org/mailman/listinfo/mesa-dev>`_ Bug reports ----------- If you think something isn't working properly, please file a bug report (`docs/bugs.rst <https://mesa3d.org/bugs.html>`_). Contributing ------------ Contributions are welcome, and step-by-step instructions can be found in our documentation (`docs/submittingpatches.rst <https://mesa3d.org/submittingpatches.html>`_). Note that Mesa uses gitlab for patches submission, review and discussions.