Announcement

Collapse
No announcement yet.

Open-Source GStreamer VA-API Plug-In Support

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

  • #16
    Originally posted by deanjo View Post
    You can however, for personal use transcode the media to another format. From that point forward you may do what ever you wish with that transcoded media. The only thing that it is restricting you from doing is utilizing the original encoding for commercial purposes.
    Are you sure about that? I'm not a lawyer, but that seems like rather dubious logic. If you are utilizing the final encoding for commercial purposes, then doesn't that automatically imply that the original was also for commercial purposes? I don't think you can just insert a random "personal" step in there and get away with it.

    Comment


    • #17
      Originally posted by EarthMind View Post
      MPEG-7 is even more restricting: http://en.wikipedia.org/wiki/MPEG-7
      Mpeg7 is a metadata standard...

      Comment


      • #18
        Originally posted by V!NCENT View Post
        I do no longer care about MPEG. If any of you have also read about the latest licensing horrors about MPEG-LA you will not care about it either. Did you know that any MPEG video you create/shoot, regaredless oif converting it to OGG, will have your copyright be transferred to MPEG-LA? Read the manual of you consumer and pro camera's!

        Will now try to evade anything MPEG related wherever I can. Goodbye!
        Nonsense ... a manual isn't a license at least in most European countries if it isn't stated on a contract you sign when you buy the cam it is worthless.

        Even in the US I am not sure it holds anything (INAL) but you are not required to read the manual, you could as well open the cam, and throw the manual away as you already know how to operate it and use it.

        Comment


        • #19
          Originally posted by drago01 View Post
          Nonsense ... a manual isn't a license at least in most European countries if it isn't stated on a contract you sign when you buy the cam it is worthless.

          Even in the US I am not sure it holds anything (INAL) but you are not required to read the manual, you could as well open the cam, and throw the manual away as you already know how to operate it and use it.
          Of course the *only* intent is to get money and try as hard as they will to control and squeeze you. They don't care about, and can't stop, normal users, it's companies that these things are targeted towards. It's copyright and patent reform that is needed to stop these greedy malicious assholes.

          Originally posted by waucka View Post
          Personally, I will use my DSLR's HD video recording capabilities for whatever purpose I damn well please, and if the MPEG-LA wants me to pay them for the privilege of using my property to earn money, they can take their damn license fees from my cold, dead hands. Bastards.
          Yep, but they don't care about you, just big targets i.e. massive companies. Laws need to be changed to stop these vulture companies like MPEG-LA. Until then, abusing the system as you're suggesting may be the better route as it may help to de-legitimize laws like these, but I'm definitely no expert on the best course of action to fight back.

          Comment


          • #20
            Out of the box support when?

            To make this news a little more noob friendly, is there a good tutorial/example of how to get it to work?
            I need to ask some questions before I know this is good news:
            Does this work only with the proprietary catalyst driver?
            What hardware does it work on? HD3xxx+ 4xxx?
            Should it work by just installing Catalyst via Ubuntu 10.04's restricted drivers manager, or are there additional/different steps? (Download directly from amd/ati & follow cchtml, + install xvba package, any extra dependencies?
            Is there a .deb package anywhere, or does this the plugin have to be compiled & manually updated all the time?
            Finally, are mplayer, vlc, totem or other video players that I download from the stock ubuntu repos ready to use this?

            Basically how close are we to out of the box vaapi support with ubuntu 10.04 & an ATI 4670?

            Comment


            • #21
              gstreamer-vaapi 0.2.2

              Hi, gstreamer-vaapi 0.2.2 is now available at:
              http://www.splitted-desktop.com/~gbe...treamer-vaapi/

              Version 0.2.2 - 14.May.2010
              * Fix packaging dependencies
              * Fix a crash in the FFmpeg decoder on close
              * Fix OpenGL texture internal format (Clutter)
              * Fix foreign window size for embedding (Totem)

              Version 0.2.1 - 12.May.2010
              * Fix integration within the playbin2 pipeline
              * Fix vaapidecode to expose the HW supported caps only
              * Add GstXOverlay interface to vaapisink (Totem media player)

              Besides, Clutter now supports VA-API acceleration through GStreamer:
              http://bugzilla.openedhand.com/show_bug.cgi?id=2119

              Comment


              • #22
                A little help? Trying to compile to get gstreamer-vaapi working.

                I'm running 10.4. I need a patch to libavcodec (or a recent ffmpeg? not sure if ffmpeg has the neccessary headers) for vaapi headers. Anyone know where I can get this?

                Comment


                • #23
                  I just grabbed a tarball from here:

                  http://www.ffmpeg.org/download.html

                  And now got it working with Totem. Doesn't seem to do scaling yet though, as illustrated by the screenshot.



                  But anyway great work Gwenole. Now if only ATI/AMD did their part to get XvBA working with Evergreen.

                  Comment


                  • #24
                    Originally posted by monraaf View Post
                    And now got it working with Totem. Doesn't seem to do scaling yet though, as illustrated by the screenshot.
                    It does but the algorithm I use to compute the render size is probably broken. Normally, it scales to fit the window while preserving the aspect ratio. So, in any case, you should only have black bars either top/bottom or left/right.

                    Could you please report the outcome of:
                    $ GST_DEBUG=vaapisink:5 totem some args
                    ?

                    + the size of your Totem window + the size of the clip. Those should be available in the log, but just to make sure I retrieve the right data.

                    Comment


                    • #25
                      Sure. The log file is over here:

                      http://pastebin.com/28LRW8cT

                      The reported video size (1280x688) in the log is correct. The size of allocated to the video window from Totem is approximately 1680x856.
                      (whole Totem app is 1680x1002)

                      Comment


                      • #26
                        gstreamer-vaapi 0.2.3

                        Hi,

                        A new version is now available at:
                        http://www.splitted-desktop.com/~gbe...treamer-vaapi/

                        Version 0.2.3 - 16.May.2010
                        * Fix memory leak of encoded buffers
                        * Fix decoder caps to report codec aliases
                        * Fix VC-1 decoding through the playbin2 pipeline

                        Comment


                        • #27
                          Originally posted by monraaf View Post
                          Sure. The log file is over here:

                          http://pastebin.com/28LRW8cT

                          The reported video size (1280x688) in the log is correct. The size of allocated to the video window from Totem is approximately 1680x856.
                          (whole Totem app is 1680x1002)
                          Thanks, I have released a new version. There is no fix for your problem yet but extra debugging information that may be useful to me. I have an idea of the problem but I would like to confirm, so if you could have new dump, that could help. Thanks.

                          Comment


                          • #28
                            Originally posted by monraaf View Post
                            The reported video size (1280x688) in the log is correct. The size of allocated to the video window from Totem is approximately 1680x856.
                            (whole Totem app is 1680x1002)
                            I have uploaded a 0.2.4-pre1, it might help your case. At least, I am now using the same algorithms as in xvba-video/vdpau-video to detect foreign window size changes.

                            Comment


                            • #29
                              Nope also not working with 0.2.4-pre1. Just to be clear it's only upscaling that doesn't work here, downscaling does work.

                              Here's the log, same sizes as before:

                              http://pastebin.com/vg2rYjw5

                              Comment


                              • #30
                                Originally posted by monraaf View Post
                                Nope also not working with 0.2.4-pre1. Just to be clear it's only upscaling that doesn't work here, downscaling does work.
                                OK, thanks. This should be fixed in the newly uploaded 0.2.4-pre2.

                                Comment

                                Working...
                                X