hello all,
How a hardware based H.264 video decoder driver can be integrate in to gstreamer framework? so that a player developed with gstreamer api can access this driver. anything similar like avstream + directshow architecture in windows. Regards, userone ------------------------------------------------------------------------------ This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev _______________________________________________ gstreamer-devel mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/gstreamer-devel |
Hi,
If the driver implements one of the known APIs such as VAAPI or VDPAU then it should be easy to get it integrated in existing infrastructures. Otherwise you will have to create a decoder element around that driver and integrate it nicely into GStreamer pipelines. Best regards, Julien Moutte, FLUENDO S.A. On Mon, Dec 21, 2009 at 1:07 PM, user1 linux <[hidden email]> wrote: hello all, ------------------------------------------------------------------------------ This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev _______________________________________________ gstreamer-devel mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/gstreamer-devel |
In reply to this post by user1 linux
> How a hardware based H.264 video decoder driver can be integrate in to
> gstreamer framework? so that a player developed with gstreamer api can > access this driver. anything similar like avstream + directshow architecture > in windows. simply put: Create an element with the caps as in a software encoder; rip out the library call and replace it by copying the buffer to your hardware driver after you've done your buffer alignment if required by your hardware; the resulting encoded data is handled the same and sent out. I don't see a real difference between a hardware and software encoder; they both end up making a call to somewhere else (hardware or software library). -- greetz, marc This is clearly another case of too many mad scientists, and not enough hunchbacks. crichton 2.6.26 #1 PREEMPT Tue Jul 29 21:17:59 CDT 2008 GNU/Linux ------------------------------------------------------------------------------ This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev _______________________________________________ gstreamer-devel mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/gstreamer-devel signature.asc (196 bytes) Download Attachment |
Free forum by Nabble | Edit this page |