Announcement

Collapse
No announcement yet.

AMD Advanced Media Acceleration "AMA" 1.0 SDK Released

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

  • AMD Advanced Media Acceleration "AMA" 1.0 SDK Released

    Phoronix: AMD Advanced Media Acceleration "AMA" 1.0 SDK Released

    AMD has published the Advanced Media Acceleration (AMA) v1.0 SDK as a software stack aimed for hardware video acceleration and capable of high density real-time transcoding. The AMD AMA SDK integrates with the likes of the open-source FFmpeg and GStreamer projects for fitting nicely in the Linux software ecosystem as well as sporting its own C-based API...

    Phoronix, Linux Hardware Reviews, Linux hardware benchmarks, Linux server benchmarks, Linux benchmarking, Desktop Linux, Linux performance, Open Source graphics, Linux How To, Ubuntu benchmarks, Ubuntu hardware, Phoronix Test Suite

  • #2
    There's commercial for some medicine for an eye disorder called AMD and it progresses into GA. What's up with that? This is the AMD Ask Me Anything, right?

    ----

    C based API? They should rewrite it in Rust.

    ----

    If the GPU was christened, was it also circumcised?

    I believe that covers everything that isn't on topic

    Comment


    • #3
      Am I understanding correctly that the MA35D has been out on the market for months and has gotten its first SDK version NOW?
      Were the clients supposed to have a specialised dev that could tap into them on the hardware level before???

      AMD...

      Comment


      • #4
        Originally posted by skeevy420 View Post
        C based API? They should rewrite it in Rust.
        GStreamer and ffmpeg are (predominantly) C. If you want to integrate with those & lots of other software out there, a C API is still the most sensible choice. That doesn't mean they can't implement in Rust.

        Comment


        • #5
          Originally posted by coder View Post
          GStreamer and ffmpeg are (predominantly) C. If you want to integrate with those & lots of other software out there, a C API is still the most sensible choice. That doesn't mean they can't implement in Rust.
          I was preemptively making fun of people who suggest "rewrite it in Rust" about practically everything that exists. Can't even make a glass of strawberry milk these days without them suggesting replacing strawberry milk mix with iron oxide powder.

          Comment


          • #6
            Originally posted by Mahboi View Post
            Am I understanding correctly that the MA35D has been out on the market for months and has gotten its first SDK version NOW?
            Were the clients supposed to have a specialised dev that could tap into them on the hardware level before???

            AMD...
            I don't think it has been, I was talking with one of my friends who has been trying to get a sample for months now, his contact wound up ghosting him. as far as I and he are concerned, it's not been released at all

            Comment


            • #7
              Given AMDs past - and poor - track record with supporting their hardware codes in ffmpeg (the AMD AMF stuff)...
              And as there's no message on the ffmpeg mailing lists regarding AMA...

              Means their "ffmpeg support" is one of these:
              1. Either there's going to be an AMD maintained fork
              2. It's developed in the dark under NDA and still has to be pushed to ffmpeg.

              I'm placing my bets on option 1. Which is bad as AMD is also bad at keeping it's software up to date. Oh well, let's wait and see what happens.

              Comment


              • #8
                Now this needs HDMI-in and Displayport-in to be a viable external video capture card to compete against Elgato products.

                Comment


                • #9
                  Originally posted by markg85 View Post
                  Given AMDs past - and poor - track record with supporting their hardware codes in ffmpeg (the AMD AMF stuff)...
                  And as there's no message on the ffmpeg mailing lists regarding AMA...

                  Means their "ffmpeg support" is one of these:
                  1. Either there's going to be an AMD maintained fork
                  2. It's developed in the dark under NDA and still has to be pushed to ffmpeg.

                  I'm placing my bets on option 1. Which is bad as AMD is also bad at keeping it's software up to date. Oh well, let's wait and see what happens.
                  this is ot "AMD" this is "Xilinx" which is even worse xD, look at the history of alveo, if anything AMD might actually be a benefit here of trying to get these upstreamed

                  Comment


                  • #10
                    Originally posted by Eirikr1848 View Post
                    Now this needs HDMI-in and Displayport-in to be a viable external video capture card to compete against Elgato products.
                    sir, I think you have the wrong market. these cards are for larger scale streaming solutions, typically you would have a seperate video injest solution. and as for if they were to make devices to compete with elgato products, I highly doubt they would want to use this api, they would probably use v4l2/libcamera, libva or uvc.

                    Comment

                    Working...
                    X