Announcement

Collapse
No announcement yet.

Mesa 24.1 Enables AV1 LTR Encode Support For RDNA3 GPUs With VCN4

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Mesa 24.1 Enables AV1 LTR Encode Support For RDNA3 GPUs With VCN4

    Phoronix: Mesa 24.1 Enables AV1 LTR Encode Support For RDNA3 GPUs With VCN4

    Building upon the existing AV1 encode support for RDNA3 GPUs within the Mesa RadeonSI Gallium3D driver, AV1 Long-Term Reference "LTR" support is now enabled within Mesa 24.1...


  • #2
    Trying to encode any input with dimensions not aligned to 64 width x 16 height px will result in additional black padding at bottom/right in the resulting encoded...

    Any sensible person would avoid using AMD hardware for AV1 encoding.

    Comment


    • #3
      Originally posted by edxposed View Post
      https://gitlab.freedesktop.org/mesa/...5#note_1954937
      Any sensible person would avoid using AMD hardware for AV1 encoding.
      It’s actually normal for video data sizes to be rounded up to a multiple of 64 pixels (or whatever the block size is). The file header tells the player the exact size to display in pixels…

      You can presumably set the video dimensions correctly after compression. 1080 isn’t a multiple of 64, so someone would notice….

      Comment


      • #4
        Originally posted by edxposed View Post
        https://gitlab.freedesktop.org/mesa/...5#note_1954937
        Any sensible person would avoid using AMD hardware for AV1 encoding.
        fair, there is a (not yet merged) copium patch for FFmpeg that can make it usable
        Describe the bug It seems that when using the AMF_VIDEO_ENCODER_AV1_ALIGNMENT_MODE set to AMF_VIDEO_ENCODER_AV1_ALIGNMENT_MODE_NO_RESTRICTIONS, the video is extended by adding rows/columns of black...
        Last edited by davidbepo; 29 February 2024, 02:46 PM.

        Comment


        • #5
          Im personally waiting for vulkan video encoding. Nvidia already supports this. I have to switch to my decade older nvidia gpu to develop with vulkan video.

          Comment


          • #6
            Originally posted by OneTimeShot View Post

            It’s actually normal for video data sizes to be rounded up to a multiple of 64 pixels (or whatever the block size is). The file header tells the player the exact size to display in pixels…

            You can presumably set the video dimensions correctly after compression. 1080 isn’t a multiple of 64, so someone would notice….
            Sure that is a typical limitation of block based quantitation like JPEG that has 8x8 but the user should never have to deal with it because the encoder typically does the padding and the decoder cuts the padding away.

            In this case the decoder doesn't cut it away if I understand it correct? But even then there is something strange since AV1 can have 128x128 down to 4x4 block sizes. 64x16 is only one possible T-partition: https://en.wikipedia.org/wiki/AV1#/m...rtitioning.svg

            If that is the limit for height and width something is seriously wrong.

            Comment


            • #7
              Does anybody know if this also works for recent APUs with RDNA 3 e.g. Radeon 780M? Thanks

              Comment

              Working...
              X