> so if i want to write a driver for h/w based h264 video decoder then it
> should contain all the calls as a s/w decoder which is part of gstreamer.
I haven't looked at the h264 encoder in gstreamer; but for a lot of
modules; gstreamer provides a wrapper around an external library
(jasper, ffmpeg).
The GStreamer buffers are prepared and passed to the library, the result
is put back in GStreamer buffers.
A hardware encoder would probably be the same.
And as for all the calls; you'd only need to expose the parameters that
your hardware encoder knows/uses.
--
greetz, marc
UFOs are for real: the Air Force doesn't exist.
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