Re- set up the gtk-doc system. I'd managed to mutilate it a while back, but now it's fixed. I'll put a copy of the ...
Original commit message from CVS:
Re- set up the gtk-doc system. I'd managed to mutilate it a while back,
but now it's fixed. I'll put a copy of the HTML output somewhere on the
website tonight.
In order to actually generate the docs, you'll have to install all the
DocBook tools, as well as gtk-doc from GNOME cvs. (see
http://developer.gnome.org/arch/doc/tools.html)
Notes (I'll codify these some day):
- Don't believe the Gnome page, always edit the SOURCES when documenting a
given function, never the tmpl file.
- I'll be re-arranging things a lot, but gtk-doc is smart enough to merge
any changes to the tmpl file. However, gtk-doc's merge and CVS's diff are
two entirely separate animals. We should probably have a virtual mutex on
the entire docs/gst/ directory, over and above what CVS does.
- I'm going to try to end up with a book set (docbook terms), where
docs/gst/ is only one book. There'd be another called docs/manual/, and
another docs/plugins/, etc. If you have any comments as to how these
should be done, gstreamer-devel is the place.
2000-02-01 09:16:43 +00:00
|
|
|
<!-- ##### SECTION Title ##### -->
|
|
|
|
GstPad
|
|
|
|
|
|
|
|
<!-- ##### SECTION Short_Description ##### -->
|
2000-03-27 19:53:43 +00:00
|
|
|
The connection between Elements
|
Re- set up the gtk-doc system. I'd managed to mutilate it a while back, but now it's fixed. I'll put a copy of the ...
Original commit message from CVS:
Re- set up the gtk-doc system. I'd managed to mutilate it a while back,
but now it's fixed. I'll put a copy of the HTML output somewhere on the
website tonight.
In order to actually generate the docs, you'll have to install all the
DocBook tools, as well as gtk-doc from GNOME cvs. (see
http://developer.gnome.org/arch/doc/tools.html)
Notes (I'll codify these some day):
- Don't believe the Gnome page, always edit the SOURCES when documenting a
given function, never the tmpl file.
- I'll be re-arranging things a lot, but gtk-doc is smart enough to merge
any changes to the tmpl file. However, gtk-doc's merge and CVS's diff are
two entirely separate animals. We should probably have a virtual mutex on
the entire docs/gst/ directory, over and above what CVS does.
- I'm going to try to end up with a book set (docbook terms), where
docs/gst/ is only one book. There'd be another called docs/manual/, and
another docs/plugins/, etc. If you have any comments as to how these
should be done, gstreamer-devel is the place.
2000-02-01 09:16:43 +00:00
|
|
|
|
|
|
|
<!-- ##### SECTION Long_Description ##### -->
|
|
|
|
<para>
|
2001-04-19 22:25:04 +00:00
|
|
|
#GstElement are connected to each other via "pads", which are extremely light-weight generic
|
|
|
|
connections. After two pad are retrieved from an element with gst_element_get_pad(), the pads
|
|
|
|
can be connected with gst_pad_connect().
|
|
|
|
</para>
|
|
|
|
<para>
|
|
|
|
PedTemplates are use to describe the runtime behaviour of an element and what pads it
|
|
|
|
will have during its lifetime. Pads are typically created from a padtemplate with
|
|
|
|
GST_PADTEMPLATE_NEW() or with the factory macro GST_PADTEMPLATE_FACTORY().
|
|
|
|
</para>
|
|
|
|
<para>
|
|
|
|
Pad and PadTemplates have #GstCaps attached to it to describe the media type they
|
|
|
|
are capable of dealing with. gst_pad_get_caps() and gst_pad_set_caps() are used to
|
|
|
|
manipulate the caps of the pads. gst_padtemplate_get_caps() is used to get the
|
|
|
|
caps of a padtemplate. It's not possible to modify the caps of a padtemplate after
|
|
|
|
creation. The following code example shows the code to create a pad from a padtemplate.
|
|
|
|
<programlisting>
|
|
|
|
GST_PADTEMPLATE_FACTORY (my_factory,
|
|
|
|
"sink", /* the name of the pad */
|
|
|
|
GST_PAD_SINK, /* the direction of the pad */
|
|
|
|
GST_PAD_ALWAYS, /* when this pad will be present */
|
|
|
|
GST_CAPS_NEW ( /* the capabilities of the padtemplate */
|
|
|
|
"my_caps",
|
|
|
|
"audio/raw",
|
|
|
|
"format", GST_PROPS_STRING ("int"),
|
|
|
|
"channels", GST_PROPS_INT_RANGE (1, 6)
|
|
|
|
)
|
|
|
|
)
|
Re- set up the gtk-doc system. I'd managed to mutilate it a while back, but now it's fixed. I'll put a copy of the ...
Original commit message from CVS:
Re- set up the gtk-doc system. I'd managed to mutilate it a while back,
but now it's fixed. I'll put a copy of the HTML output somewhere on the
website tonight.
In order to actually generate the docs, you'll have to install all the
DocBook tools, as well as gtk-doc from GNOME cvs. (see
http://developer.gnome.org/arch/doc/tools.html)
Notes (I'll codify these some day):
- Don't believe the Gnome page, always edit the SOURCES when documenting a
given function, never the tmpl file.
- I'll be re-arranging things a lot, but gtk-doc is smart enough to merge
any changes to the tmpl file. However, gtk-doc's merge and CVS's diff are
two entirely separate animals. We should probably have a virtual mutex on
the entire docs/gst/ directory, over and above what CVS does.
- I'm going to try to end up with a book set (docbook terms), where
docs/gst/ is only one book. There'd be another called docs/manual/, and
another docs/plugins/, etc. If you have any comments as to how these
should be done, gstreamer-devel is the place.
2000-02-01 09:16:43 +00:00
|
|
|
|
2001-04-19 22:25:04 +00:00
|
|
|
void
|
|
|
|
my_method (void)
|
|
|
|
{
|
|
|
|
GstPad *pad;
|
|
|
|
|
|
|
|
pad = gst_pad_new_from_template (GST_PADTEMPLATE_GET (my_factory), "sink");
|
|
|
|
...
|
|
|
|
}
|
|
|
|
</programlisting>
|
|
|
|
Pads created from a padtemplate cannot set capabilities that are incompatible with
|
|
|
|
the padtemplates capabilities.
|
|
|
|
</para>
|
|
|
|
<para>
|
|
|
|
Pads without padtemplates can be created with gst_pad_new() which takes a direction and
|
|
|
|
a name as an argument.
|
|
|
|
</para>
|
|
|
|
<para>
|
|
|
|
gst_pad_get_parent() will retrieve the GstElement that owns the pad.
|
|
|
|
</para>
|
|
|
|
<para>
|
|
|
|
GstElements creating a pad will typicilally use the various gst_pad_set_*_function() calls
|
|
|
|
to register callbacks for various events on the pads.
|
|
|
|
</para>
|
|
|
|
<para>
|
|
|
|
GstElements will use gst_pad_push() and gst_pad_pull() to push out or pull a buffer in. The
|
|
|
|
gst_pad_pullregion() function can be used to request for a buffer with a specific offset (in
|
|
|
|
time or in bytes).
|
Re- set up the gtk-doc system. I'd managed to mutilate it a while back, but now it's fixed. I'll put a copy of the ...
Original commit message from CVS:
Re- set up the gtk-doc system. I'd managed to mutilate it a while back,
but now it's fixed. I'll put a copy of the HTML output somewhere on the
website tonight.
In order to actually generate the docs, you'll have to install all the
DocBook tools, as well as gtk-doc from GNOME cvs. (see
http://developer.gnome.org/arch/doc/tools.html)
Notes (I'll codify these some day):
- Don't believe the Gnome page, always edit the SOURCES when documenting a
given function, never the tmpl file.
- I'll be re-arranging things a lot, but gtk-doc is smart enough to merge
any changes to the tmpl file. However, gtk-doc's merge and CVS's diff are
two entirely separate animals. We should probably have a virtual mutex on
the entire docs/gst/ directory, over and above what CVS does.
- I'm going to try to end up with a book set (docbook terms), where
docs/gst/ is only one book. There'd be another called docs/manual/, and
another docs/plugins/, etc. If you have any comments as to how these
should be done, gstreamer-devel is the place.
2000-02-01 09:16:43 +00:00
|
|
|
</para>
|
|
|
|
|
|
|
|
<!-- ##### SECTION See_Also ##### -->
|
|
|
|
<para>
|
2001-04-19 22:25:04 +00:00
|
|
|
#GstCaps, #GstElement
|
Re- set up the gtk-doc system. I'd managed to mutilate it a while back, but now it's fixed. I'll put a copy of the ...
Original commit message from CVS:
Re- set up the gtk-doc system. I'd managed to mutilate it a while back,
but now it's fixed. I'll put a copy of the HTML output somewhere on the
website tonight.
In order to actually generate the docs, you'll have to install all the
DocBook tools, as well as gtk-doc from GNOME cvs. (see
http://developer.gnome.org/arch/doc/tools.html)
Notes (I'll codify these some day):
- Don't believe the Gnome page, always edit the SOURCES when documenting a
given function, never the tmpl file.
- I'll be re-arranging things a lot, but gtk-doc is smart enough to merge
any changes to the tmpl file. However, gtk-doc's merge and CVS's diff are
two entirely separate animals. We should probably have a virtual mutex on
the entire docs/gst/ directory, over and above what CVS does.
- I'm going to try to end up with a book set (docbook terms), where
docs/gst/ is only one book. There'd be another called docs/manual/, and
another docs/plugins/, etc. If you have any comments as to how these
should be done, gstreamer-devel is the place.
2000-02-01 09:16:43 +00:00
|
|
|
</para>
|
|
|
|
|
2001-01-19 22:15:21 +00:00
|
|
|
<!-- ##### MACRO GST_PAD_NAME ##### -->
|
|
|
|
<para>
|
|
|
|
Get the name of the pad.
|
|
|
|
</para>
|
|
|
|
|
|
|
|
@pad: the pad to query
|
|
|
|
|
|
|
|
|
|
|
|
<!-- ##### MACRO GST_PAD_ELEMENT_PRIVATE ##### -->
|
|
|
|
<para>
|
|
|
|
Get the private data set by the element that owns the pad.
|
|
|
|
</para>
|
|
|
|
|
|
|
|
@pad: the pad to query
|
|
|
|
|
|
|
|
|
|
|
|
<!-- ##### MACRO GST_PAD_PARENT ##### -->
|
|
|
|
<para>
|
|
|
|
Get the parent element of this pad.
|
|
|
|
</para>
|
|
|
|
|
|
|
|
@pad: the pad to query
|
|
|
|
|
|
|
|
|
|
|
|
<!-- ##### MACRO GST_PAD_PADTEMPLATE ##### -->
|
|
|
|
<para>
|
|
|
|
Get the padtemplate that was used to create this pad. NULL if no padtemplate
|
|
|
|
was used.
|
|
|
|
</para>
|
|
|
|
|
|
|
|
@pad: the pad to query
|
|
|
|
|
|
|
|
|
|
|
|
<!-- ##### MACRO GST_PAD_REALIZE ##### -->
|
|
|
|
<para>
|
|
|
|
Return the real pad of this pad.
|
|
|
|
</para>
|
|
|
|
|
|
|
|
@pad: the pad to query
|
|
|
|
|
|
|
|
|
|
|
|
<!-- ##### MACRO GST_PAD_DIRECTION ##### -->
|
|
|
|
<para>
|
|
|
|
Get the pad direction.
|
|
|
|
</para>
|
|
|
|
|
|
|
|
@pad: the pad to query
|
|
|
|
|
|
|
|
|
|
|
|
<!-- ##### MACRO GST_PAD_CAPS ##### -->
|
|
|
|
<para>
|
|
|
|
Get the capabilities of a pad.
|
|
|
|
</para>
|
|
|
|
|
|
|
|
@pad: the pad to query
|
|
|
|
|
|
|
|
|
|
|
|
<!-- ##### MACRO GST_PAD_PEER ##### -->
|
|
|
|
<para>
|
|
|
|
Get the peerpad of this pad.
|
|
|
|
</para>
|
|
|
|
|
|
|
|
@pad: the pad to query
|
|
|
|
|
|
|
|
|
2000-03-27 19:53:43 +00:00
|
|
|
<!-- ##### MACRO GST_PAD_CONNECTED ##### -->
|
Re- set up the gtk-doc system. I'd managed to mutilate it a while back, but now it's fixed. I'll put a copy of the ...
Original commit message from CVS:
Re- set up the gtk-doc system. I'd managed to mutilate it a while back,
but now it's fixed. I'll put a copy of the HTML output somewhere on the
website tonight.
In order to actually generate the docs, you'll have to install all the
DocBook tools, as well as gtk-doc from GNOME cvs. (see
http://developer.gnome.org/arch/doc/tools.html)
Notes (I'll codify these some day):
- Don't believe the Gnome page, always edit the SOURCES when documenting a
given function, never the tmpl file.
- I'll be re-arranging things a lot, but gtk-doc is smart enough to merge
any changes to the tmpl file. However, gtk-doc's merge and CVS's diff are
two entirely separate animals. We should probably have a virtual mutex on
the entire docs/gst/ directory, over and above what CVS does.
- I'm going to try to end up with a book set (docbook terms), where
docs/gst/ is only one book. There'd be another called docs/manual/, and
another docs/plugins/, etc. If you have any comments as to how these
should be done, gstreamer-devel is the place.
2000-02-01 09:16:43 +00:00
|
|
|
<para>
|
2001-01-06 22:05:15 +00:00
|
|
|
Is this pad connected.
|
2000-03-27 19:53:43 +00:00
|
|
|
</para>
|
|
|
|
|
|
|
|
@pad: the pad to check
|
Re- set up the gtk-doc system. I'd managed to mutilate it a while back, but now it's fixed. I'll put a copy of the ...
Original commit message from CVS:
Re- set up the gtk-doc system. I'd managed to mutilate it a while back,
but now it's fixed. I'll put a copy of the HTML output somewhere on the
website tonight.
In order to actually generate the docs, you'll have to install all the
DocBook tools, as well as gtk-doc from GNOME cvs. (see
http://developer.gnome.org/arch/doc/tools.html)
Notes (I'll codify these some day):
- Don't believe the Gnome page, always edit the SOURCES when documenting a
given function, never the tmpl file.
- I'll be re-arranging things a lot, but gtk-doc is smart enough to merge
any changes to the tmpl file. However, gtk-doc's merge and CVS's diff are
two entirely separate animals. We should probably have a virtual mutex on
the entire docs/gst/ directory, over and above what CVS does.
- I'm going to try to end up with a book set (docbook terms), where
docs/gst/ is only one book. There'd be another called docs/manual/, and
another docs/plugins/, etc. If you have any comments as to how these
should be done, gstreamer-devel is the place.
2000-02-01 09:16:43 +00:00
|
|
|
|
2000-03-27 19:53:43 +00:00
|
|
|
|
|
|
|
<!-- ##### MACRO GST_PAD_CAN_PULL ##### -->
|
|
|
|
<para>
|
2001-01-06 22:05:15 +00:00
|
|
|
Can this pad be used to pull a buffer.
|
Re- set up the gtk-doc system. I'd managed to mutilate it a while back, but now it's fixed. I'll put a copy of the ...
Original commit message from CVS:
Re- set up the gtk-doc system. I'd managed to mutilate it a while back,
but now it's fixed. I'll put a copy of the HTML output somewhere on the
website tonight.
In order to actually generate the docs, you'll have to install all the
DocBook tools, as well as gtk-doc from GNOME cvs. (see
http://developer.gnome.org/arch/doc/tools.html)
Notes (I'll codify these some day):
- Don't believe the Gnome page, always edit the SOURCES when documenting a
given function, never the tmpl file.
- I'll be re-arranging things a lot, but gtk-doc is smart enough to merge
any changes to the tmpl file. However, gtk-doc's merge and CVS's diff are
two entirely separate animals. We should probably have a virtual mutex on
the entire docs/gst/ directory, over and above what CVS does.
- I'm going to try to end up with a book set (docbook terms), where
docs/gst/ is only one book. There'd be another called docs/manual/, and
another docs/plugins/, etc. If you have any comments as to how these
should be done, gstreamer-devel is the place.
2000-02-01 09:16:43 +00:00
|
|
|
</para>
|
|
|
|
|
2000-03-27 19:53:43 +00:00
|
|
|
@pad: the pad to check
|
Re- set up the gtk-doc system. I'd managed to mutilate it a while back, but now it's fixed. I'll put a copy of the ...
Original commit message from CVS:
Re- set up the gtk-doc system. I'd managed to mutilate it a while back,
but now it's fixed. I'll put a copy of the HTML output somewhere on the
website tonight.
In order to actually generate the docs, you'll have to install all the
DocBook tools, as well as gtk-doc from GNOME cvs. (see
http://developer.gnome.org/arch/doc/tools.html)
Notes (I'll codify these some day):
- Don't believe the Gnome page, always edit the SOURCES when documenting a
given function, never the tmpl file.
- I'll be re-arranging things a lot, but gtk-doc is smart enough to merge
any changes to the tmpl file. However, gtk-doc's merge and CVS's diff are
two entirely separate animals. We should probably have a virtual mutex on
the entire docs/gst/ directory, over and above what CVS does.
- I'm going to try to end up with a book set (docbook terms), where
docs/gst/ is only one book. There'd be another called docs/manual/, and
another docs/plugins/, etc. If you have any comments as to how these
should be done, gstreamer-devel is the place.
2000-02-01 09:16:43 +00:00
|
|
|
|
|
|
|
|
2000-03-27 19:53:43 +00:00
|
|
|
<!-- ##### STRUCT GstPad ##### -->
|
Re- set up the gtk-doc system. I'd managed to mutilate it a while back, but now it's fixed. I'll put a copy of the ...
Original commit message from CVS:
Re- set up the gtk-doc system. I'd managed to mutilate it a while back,
but now it's fixed. I'll put a copy of the HTML output somewhere on the
website tonight.
In order to actually generate the docs, you'll have to install all the
DocBook tools, as well as gtk-doc from GNOME cvs. (see
http://developer.gnome.org/arch/doc/tools.html)
Notes (I'll codify these some day):
- Don't believe the Gnome page, always edit the SOURCES when documenting a
given function, never the tmpl file.
- I'll be re-arranging things a lot, but gtk-doc is smart enough to merge
any changes to the tmpl file. However, gtk-doc's merge and CVS's diff are
two entirely separate animals. We should probably have a virtual mutex on
the entire docs/gst/ directory, over and above what CVS does.
- I'm going to try to end up with a book set (docbook terms), where
docs/gst/ is only one book. There'd be another called docs/manual/, and
another docs/plugins/, etc. If you have any comments as to how these
should be done, gstreamer-devel is the place.
2000-02-01 09:16:43 +00:00
|
|
|
<para>
|
|
|
|
|
|
|
|
</para>
|
|
|
|
|
|
|
|
|
|
|
|
<!-- ##### USER_FUNCTION GstPadChainFunction ##### -->
|
|
|
|
<para>
|
2000-09-13 19:04:55 +00:00
|
|
|
The function that will be called when chaining buffers.
|
Re- set up the gtk-doc system. I'd managed to mutilate it a while back, but now it's fixed. I'll put a copy of the ...
Original commit message from CVS:
Re- set up the gtk-doc system. I'd managed to mutilate it a while back,
but now it's fixed. I'll put a copy of the HTML output somewhere on the
website tonight.
In order to actually generate the docs, you'll have to install all the
DocBook tools, as well as gtk-doc from GNOME cvs. (see
http://developer.gnome.org/arch/doc/tools.html)
Notes (I'll codify these some day):
- Don't believe the Gnome page, always edit the SOURCES when documenting a
given function, never the tmpl file.
- I'll be re-arranging things a lot, but gtk-doc is smart enough to merge
any changes to the tmpl file. However, gtk-doc's merge and CVS's diff are
two entirely separate animals. We should probably have a virtual mutex on
the entire docs/gst/ directory, over and above what CVS does.
- I'm going to try to end up with a book set (docbook terms), where
docs/gst/ is only one book. There'd be another called docs/manual/, and
another docs/plugins/, etc. If you have any comments as to how these
should be done, gstreamer-devel is the place.
2000-02-01 09:16:43 +00:00
|
|
|
</para>
|
|
|
|
|
2000-09-13 19:04:55 +00:00
|
|
|
@pad: the pad that performed the chain
|
|
|
|
@buf: the buffer that is chained
|
Re- set up the gtk-doc system. I'd managed to mutilate it a while back, but now it's fixed. I'll put a copy of the ...
Original commit message from CVS:
Re- set up the gtk-doc system. I'd managed to mutilate it a while back,
but now it's fixed. I'll put a copy of the HTML output somewhere on the
website tonight.
In order to actually generate the docs, you'll have to install all the
DocBook tools, as well as gtk-doc from GNOME cvs. (see
http://developer.gnome.org/arch/doc/tools.html)
Notes (I'll codify these some day):
- Don't believe the Gnome page, always edit the SOURCES when documenting a
given function, never the tmpl file.
- I'll be re-arranging things a lot, but gtk-doc is smart enough to merge
any changes to the tmpl file. However, gtk-doc's merge and CVS's diff are
two entirely separate animals. We should probably have a virtual mutex on
the entire docs/gst/ directory, over and above what CVS does.
- I'm going to try to end up with a book set (docbook terms), where
docs/gst/ is only one book. There'd be another called docs/manual/, and
another docs/plugins/, etc. If you have any comments as to how these
should be done, gstreamer-devel is the place.
2000-02-01 09:16:43 +00:00
|
|
|
|
|
|
|
|
2000-12-28 21:42:23 +00:00
|
|
|
<!-- ##### USER_FUNCTION GstPadGetFunction ##### -->
|
2000-03-27 19:53:43 +00:00
|
|
|
<para>
|
2000-12-28 21:42:23 +00:00
|
|
|
The function that will be called when pulling a buffer.
|
2000-03-27 19:53:43 +00:00
|
|
|
</para>
|
|
|
|
|
2000-12-28 21:42:23 +00:00
|
|
|
@pad: the pad to get a buffer from
|
2001-01-06 22:05:15 +00:00
|
|
|
@Returns: a #GstBuffer
|
2000-03-27 19:53:43 +00:00
|
|
|
|
|
|
|
|
2000-12-28 21:42:23 +00:00
|
|
|
<!-- ##### USER_FUNCTION GstPadGetRegionFunction ##### -->
|
2000-11-07 21:24:12 +00:00
|
|
|
<para>
|
|
|
|
The function that will be called when pulling a region buffer.
|
2001-02-22 23:18:51 +00:00
|
|
|
You can specify which buffer to get using an offset/length pair or
|
|
|
|
a start/stop timecode pair.
|
2000-11-07 21:24:12 +00:00
|
|
|
</para>
|
|
|
|
|
2000-12-28 21:42:23 +00:00
|
|
|
@pad: the pad to get a buffer from
|
2001-02-22 23:18:51 +00:00
|
|
|
@type: the type of region to get (time or offset based)
|
2000-12-28 21:42:23 +00:00
|
|
|
@offset: the offset of the region to get
|
2001-02-22 23:18:51 +00:00
|
|
|
@len: the length of the region to get
|
2001-01-06 22:05:15 +00:00
|
|
|
@Returns: a #GstBuffer
|
2001-03-07 21:52:56 +00:00
|
|
|
<!-- # Unused Parameters # -->
|
|
|
|
@size: the size of the region to get
|
2000-12-28 21:42:23 +00:00
|
|
|
|
|
|
|
|
2001-04-12 18:11:19 +00:00
|
|
|
<!-- ##### USER_FUNCTION GstPadNewCapsFunction ##### -->
|
|
|
|
<para>
|
2001-04-17 21:14:55 +00:00
|
|
|
The function that will be called when the caps of the pad has
|
|
|
|
changed.
|
|
|
|
</para>
|
|
|
|
|
|
|
|
@pad: The pad that has its caps changed
|
|
|
|
@caps: the new caps of the pad
|
|
|
|
|
2001-04-12 18:11:19 +00:00
|
|
|
|
2001-04-17 21:14:55 +00:00
|
|
|
<!-- ##### USER_FUNCTION GstPadBufferPoolFunction ##### -->
|
|
|
|
<para>
|
|
|
|
The function that will be called when a bufferpool is requested
|
|
|
|
from this pad.
|
2001-04-12 18:11:19 +00:00
|
|
|
</para>
|
|
|
|
|
2001-04-17 21:14:55 +00:00
|
|
|
@pad: the pad with the bufferpool
|
|
|
|
@Returns: the GstBufferPool associated with this pad.
|
2001-04-12 18:11:19 +00:00
|
|
|
|
|
|
|
|
2001-03-21 21:43:56 +00:00
|
|
|
<!-- ##### ENUM GstPadNegotiateReturn ##### -->
|
|
|
|
<para>
|
|
|
|
The possible results from padnegotiation.
|
|
|
|
</para>
|
|
|
|
|
|
|
|
@GST_PAD_NEGOTIATE_FAIL: The pads could not agree about the media type.
|
|
|
|
@GST_PAD_NEGOTIATE_AGREE: The pads agreed about the media type.
|
|
|
|
@GST_PAD_NEGOTIATE_TRY: The pad did not agree and suggests another media type.
|
|
|
|
|
|
|
|
<!-- ##### USER_FUNCTION GstPadNegotiateFunction ##### -->
|
|
|
|
<para>
|
|
|
|
The function that will be called when negotiating.
|
|
|
|
</para>
|
|
|
|
|
|
|
|
@pad: The pad that is being negotiated
|
|
|
|
@caps: The current caps that are being negotiated
|
2001-04-17 21:14:55 +00:00
|
|
|
@data: A generic gpointer that can be used to store user_data
|
2001-03-21 21:43:56 +00:00
|
|
|
@Returns: The result of the negotiation process
|
|
|
|
|
|
|
|
|
2001-02-22 23:18:51 +00:00
|
|
|
<!-- ##### ENUM GstRegionType ##### -->
|
|
|
|
<para>
|
|
|
|
the region types for #gst_pad_pullregion.
|
|
|
|
</para>
|
|
|
|
|
2001-07-07 10:55:58 +00:00
|
|
|
@GST_REGION_VOID:
|
2001-02-22 23:18:51 +00:00
|
|
|
@GST_REGION_OFFSET_LEN: an offet/length pair
|
|
|
|
@GST_REGION_TIME_LEN: a time start/length pair
|
|
|
|
|
2000-12-28 21:42:23 +00:00
|
|
|
<!-- ##### USER_FUNCTION GstPadPullRegionFunction ##### -->
|
|
|
|
<para>
|
|
|
|
The function that will be called when pulling a region buffer.
|
2001-02-22 23:18:51 +00:00
|
|
|
You can specify which buffer to get using an offset/length pair or
|
|
|
|
a start/stop timecode pair.
|
2000-12-28 21:42:23 +00:00
|
|
|
</para>
|
|
|
|
|
2001-02-22 23:18:51 +00:00
|
|
|
@pad: the pad to get a buffer from
|
|
|
|
@type: the type of region to get (time or offset based)
|
|
|
|
@offset: the offset of the region to get
|
|
|
|
@len: the length of the region to get
|
|
|
|
@Returns: a #GstBuffer
|
|
|
|
</para>
|
Re- set up the gtk-doc system. I'd managed to mutilate it a while back, but now it's fixed. I'll put a copy of the ...
Original commit message from CVS:
Re- set up the gtk-doc system. I'd managed to mutilate it a while back,
but now it's fixed. I'll put a copy of the HTML output somewhere on the
website tonight.
In order to actually generate the docs, you'll have to install all the
DocBook tools, as well as gtk-doc from GNOME cvs. (see
http://developer.gnome.org/arch/doc/tools.html)
Notes (I'll codify these some day):
- Don't believe the Gnome page, always edit the SOURCES when documenting a
given function, never the tmpl file.
- I'll be re-arranging things a lot, but gtk-doc is smart enough to merge
any changes to the tmpl file. However, gtk-doc's merge and CVS's diff are
two entirely separate animals. We should probably have a virtual mutex on
the entire docs/gst/ directory, over and above what CVS does.
- I'm going to try to end up with a book set (docbook terms), where
docs/gst/ is only one book. There'd be another called docs/manual/, and
another docs/plugins/, etc. If you have any comments as to how these
should be done, gstreamer-devel is the place.
2000-02-01 09:16:43 +00:00
|
|
|
|
|
|
|
|
|
|
|
<!-- ##### ENUM GstPadDirection ##### -->
|
|
|
|
<para>
|
2001-01-06 22:05:15 +00:00
|
|
|
The direction this pad is.
|
2000-12-28 21:42:23 +00:00
|
|
|
</para>
|
|
|
|
|
|
|
|
@GST_PAD_UNKNOWN: direction is unknown
|
|
|
|
@GST_PAD_SRC: this is a source pad
|
|
|
|
@GST_PAD_SINK: this is a sink pad
|
Re- set up the gtk-doc system. I'd managed to mutilate it a while back, but now it's fixed. I'll put a copy of the ...
Original commit message from CVS:
Re- set up the gtk-doc system. I'd managed to mutilate it a while back,
but now it's fixed. I'll put a copy of the HTML output somewhere on the
website tonight.
In order to actually generate the docs, you'll have to install all the
DocBook tools, as well as gtk-doc from GNOME cvs. (see
http://developer.gnome.org/arch/doc/tools.html)
Notes (I'll codify these some day):
- Don't believe the Gnome page, always edit the SOURCES when documenting a
given function, never the tmpl file.
- I'll be re-arranging things a lot, but gtk-doc is smart enough to merge
any changes to the tmpl file. However, gtk-doc's merge and CVS's diff are
two entirely separate animals. We should probably have a virtual mutex on
the entire docs/gst/ directory, over and above what CVS does.
- I'm going to try to end up with a book set (docbook terms), where
docs/gst/ is only one book. There'd be another called docs/manual/, and
another docs/plugins/, etc. If you have any comments as to how these
should be done, gstreamer-devel is the place.
2000-02-01 09:16:43 +00:00
|
|
|
|
2000-12-28 21:42:23 +00:00
|
|
|
<!-- ##### ENUM GstPadFlags ##### -->
|
|
|
|
<para>
|
2001-01-06 22:05:15 +00:00
|
|
|
Flags for the pad.
|
Re- set up the gtk-doc system. I'd managed to mutilate it a while back, but now it's fixed. I'll put a copy of the ...
Original commit message from CVS:
Re- set up the gtk-doc system. I'd managed to mutilate it a while back,
but now it's fixed. I'll put a copy of the HTML output somewhere on the
website tonight.
In order to actually generate the docs, you'll have to install all the
DocBook tools, as well as gtk-doc from GNOME cvs. (see
http://developer.gnome.org/arch/doc/tools.html)
Notes (I'll codify these some day):
- Don't believe the Gnome page, always edit the SOURCES when documenting a
given function, never the tmpl file.
- I'll be re-arranging things a lot, but gtk-doc is smart enough to merge
any changes to the tmpl file. However, gtk-doc's merge and CVS's diff are
two entirely separate animals. We should probably have a virtual mutex on
the entire docs/gst/ directory, over and above what CVS does.
- I'm going to try to end up with a book set (docbook terms), where
docs/gst/ is only one book. There'd be another called docs/manual/, and
another docs/plugins/, etc. If you have any comments as to how these
should be done, gstreamer-devel is the place.
2000-02-01 09:16:43 +00:00
|
|
|
</para>
|
|
|
|
|
2000-12-28 21:42:23 +00:00
|
|
|
@GST_PAD_DISABLED: the pad is disabled
|
|
|
|
@GST_PAD_EOS: the pad is in end of stream state
|
|
|
|
@GST_PAD_FLAG_LAST: subclasses can use this number to enumerate their flags
|
Re- set up the gtk-doc system. I'd managed to mutilate it a while back, but now it's fixed. I'll put a copy of the ...
Original commit message from CVS:
Re- set up the gtk-doc system. I'd managed to mutilate it a while back,
but now it's fixed. I'll put a copy of the HTML output somewhere on the
website tonight.
In order to actually generate the docs, you'll have to install all the
DocBook tools, as well as gtk-doc from GNOME cvs. (see
http://developer.gnome.org/arch/doc/tools.html)
Notes (I'll codify these some day):
- Don't believe the Gnome page, always edit the SOURCES when documenting a
given function, never the tmpl file.
- I'll be re-arranging things a lot, but gtk-doc is smart enough to merge
any changes to the tmpl file. However, gtk-doc's merge and CVS's diff are
two entirely separate animals. We should probably have a virtual mutex on
the entire docs/gst/ directory, over and above what CVS does.
- I'm going to try to end up with a book set (docbook terms), where
docs/gst/ is only one book. There'd be another called docs/manual/, and
another docs/plugins/, etc. If you have any comments as to how these
should be done, gstreamer-devel is the place.
2000-02-01 09:16:43 +00:00
|
|
|
|
|
|
|
<!-- ##### FUNCTION gst_pad_new ##### -->
|
|
|
|
<para>
|
|
|
|
|
|
|
|
</para>
|
|
|
|
|
|
|
|
@name:
|
|
|
|
@direction:
|
|
|
|
@Returns:
|
|
|
|
|
|
|
|
|
2000-11-07 21:24:12 +00:00
|
|
|
<!-- ##### MACRO gst_pad_destroy ##### -->
|
Re- set up the gtk-doc system. I'd managed to mutilate it a while back, but now it's fixed. I'll put a copy of the ...
Original commit message from CVS:
Re- set up the gtk-doc system. I'd managed to mutilate it a while back,
but now it's fixed. I'll put a copy of the HTML output somewhere on the
website tonight.
In order to actually generate the docs, you'll have to install all the
DocBook tools, as well as gtk-doc from GNOME cvs. (see
http://developer.gnome.org/arch/doc/tools.html)
Notes (I'll codify these some day):
- Don't believe the Gnome page, always edit the SOURCES when documenting a
given function, never the tmpl file.
- I'll be re-arranging things a lot, but gtk-doc is smart enough to merge
any changes to the tmpl file. However, gtk-doc's merge and CVS's diff are
two entirely separate animals. We should probably have a virtual mutex on
the entire docs/gst/ directory, over and above what CVS does.
- I'm going to try to end up with a book set (docbook terms), where
docs/gst/ is only one book. There'd be another called docs/manual/, and
another docs/plugins/, etc. If you have any comments as to how these
should be done, gstreamer-devel is the place.
2000-02-01 09:16:43 +00:00
|
|
|
<para>
|
2001-01-06 22:05:15 +00:00
|
|
|
Destroy the pad.
|
2000-12-28 21:42:23 +00:00
|
|
|
</para>
|
|
|
|
|
|
|
|
@pad: the pad to destroy
|
|
|
|
|
|
|
|
|
|
|
|
<!-- ##### FUNCTION gst_pad_new_from_template ##### -->
|
|
|
|
<para>
|
Re- set up the gtk-doc system. I'd managed to mutilate it a while back, but now it's fixed. I'll put a copy of the ...
Original commit message from CVS:
Re- set up the gtk-doc system. I'd managed to mutilate it a while back,
but now it's fixed. I'll put a copy of the HTML output somewhere on the
website tonight.
In order to actually generate the docs, you'll have to install all the
DocBook tools, as well as gtk-doc from GNOME cvs. (see
http://developer.gnome.org/arch/doc/tools.html)
Notes (I'll codify these some day):
- Don't believe the Gnome page, always edit the SOURCES when documenting a
given function, never the tmpl file.
- I'll be re-arranging things a lot, but gtk-doc is smart enough to merge
any changes to the tmpl file. However, gtk-doc's merge and CVS's diff are
two entirely separate animals. We should probably have a virtual mutex on
the entire docs/gst/ directory, over and above what CVS does.
- I'm going to try to end up with a book set (docbook terms), where
docs/gst/ is only one book. There'd be another called docs/manual/, and
another docs/plugins/, etc. If you have any comments as to how these
should be done, gstreamer-devel is the place.
2000-02-01 09:16:43 +00:00
|
|
|
|
|
|
|
</para>
|
|
|
|
|
2001-01-19 22:15:21 +00:00
|
|
|
@templ:
|
2000-12-28 21:42:23 +00:00
|
|
|
@name:
|
|
|
|
@Returns:
|
2001-01-19 22:15:21 +00:00
|
|
|
<!-- # Unused Parameters # -->
|
|
|
|
@temp:
|
Re- set up the gtk-doc system. I'd managed to mutilate it a while back, but now it's fixed. I'll put a copy of the ...
Original commit message from CVS:
Re- set up the gtk-doc system. I'd managed to mutilate it a while back,
but now it's fixed. I'll put a copy of the HTML output somewhere on the
website tonight.
In order to actually generate the docs, you'll have to install all the
DocBook tools, as well as gtk-doc from GNOME cvs. (see
http://developer.gnome.org/arch/doc/tools.html)
Notes (I'll codify these some day):
- Don't believe the Gnome page, always edit the SOURCES when documenting a
given function, never the tmpl file.
- I'll be re-arranging things a lot, but gtk-doc is smart enough to merge
any changes to the tmpl file. However, gtk-doc's merge and CVS's diff are
two entirely separate animals. We should probably have a virtual mutex on
the entire docs/gst/ directory, over and above what CVS does.
- I'm going to try to end up with a book set (docbook terms), where
docs/gst/ is only one book. There'd be another called docs/manual/, and
another docs/plugins/, etc. If you have any comments as to how these
should be done, gstreamer-devel is the place.
2000-02-01 09:16:43 +00:00
|
|
|
|
|
|
|
|
|
|
|
<!-- ##### FUNCTION gst_pad_get_direction ##### -->
|
|
|
|
<para>
|
|
|
|
|
|
|
|
</para>
|
|
|
|
|
|
|
|
@pad:
|
|
|
|
@Returns:
|
|
|
|
|
|
|
|
|
|
|
|
<!-- ##### FUNCTION gst_pad_set_chain_function ##### -->
|
|
|
|
<para>
|
|
|
|
|
|
|
|
</para>
|
|
|
|
|
|
|
|
@pad:
|
|
|
|
@chain:
|
|
|
|
|
|
|
|
|
2000-12-28 21:42:23 +00:00
|
|
|
<!-- ##### FUNCTION gst_pad_set_get_function ##### -->
|
|
|
|
<para>
|
|
|
|
|
|
|
|
</para>
|
|
|
|
|
|
|
|
@pad:
|
|
|
|
@get:
|
|
|
|
|
|
|
|
|
|
|
|
<!-- ##### FUNCTION gst_pad_set_getregion_function ##### -->
|
|
|
|
<para>
|
|
|
|
|
|
|
|
</para>
|
|
|
|
|
|
|
|
@pad:
|
|
|
|
@getregion:
|
|
|
|
|
|
|
|
|
2001-03-21 21:43:56 +00:00
|
|
|
<!-- ##### FUNCTION gst_pad_set_negotiate_function ##### -->
|
2000-12-28 21:42:23 +00:00
|
|
|
<para>
|
|
|
|
|
|
|
|
</para>
|
|
|
|
|
|
|
|
@pad:
|
2001-03-21 21:43:56 +00:00
|
|
|
@nego:
|
2000-12-28 21:42:23 +00:00
|
|
|
|
|
|
|
|
2001-04-12 18:11:19 +00:00
|
|
|
<!-- ##### FUNCTION gst_pad_set_newcaps_function ##### -->
|
|
|
|
<para>
|
|
|
|
|
|
|
|
</para>
|
|
|
|
|
|
|
|
@pad:
|
|
|
|
@newcaps:
|
|
|
|
|
|
|
|
|
2001-04-17 21:14:55 +00:00
|
|
|
<!-- ##### FUNCTION gst_pad_set_bufferpool_function ##### -->
|
|
|
|
<para>
|
|
|
|
|
|
|
|
</para>
|
|
|
|
|
|
|
|
@pad:
|
|
|
|
@bufpool:
|
|
|
|
|
|
|
|
|
2001-03-21 21:43:56 +00:00
|
|
|
<!-- ##### FUNCTION gst_pad_set_caps ##### -->
|
Re- set up the gtk-doc system. I'd managed to mutilate it a while back, but now it's fixed. I'll put a copy of the ...
Original commit message from CVS:
Re- set up the gtk-doc system. I'd managed to mutilate it a while back,
but now it's fixed. I'll put a copy of the HTML output somewhere on the
website tonight.
In order to actually generate the docs, you'll have to install all the
DocBook tools, as well as gtk-doc from GNOME cvs. (see
http://developer.gnome.org/arch/doc/tools.html)
Notes (I'll codify these some day):
- Don't believe the Gnome page, always edit the SOURCES when documenting a
given function, never the tmpl file.
- I'll be re-arranging things a lot, but gtk-doc is smart enough to merge
any changes to the tmpl file. However, gtk-doc's merge and CVS's diff are
two entirely separate animals. We should probably have a virtual mutex on
the entire docs/gst/ directory, over and above what CVS does.
- I'm going to try to end up with a book set (docbook terms), where
docs/gst/ is only one book. There'd be another called docs/manual/, and
another docs/plugins/, etc. If you have any comments as to how these
should be done, gstreamer-devel is the place.
2000-02-01 09:16:43 +00:00
|
|
|
<para>
|
|
|
|
|
|
|
|
</para>
|
|
|
|
|
|
|
|
@pad:
|
2001-03-21 21:43:56 +00:00
|
|
|
@caps:
|
2000-12-28 21:42:23 +00:00
|
|
|
@Returns:
|
Re- set up the gtk-doc system. I'd managed to mutilate it a while back, but now it's fixed. I'll put a copy of the ...
Original commit message from CVS:
Re- set up the gtk-doc system. I'd managed to mutilate it a while back,
but now it's fixed. I'll put a copy of the HTML output somewhere on the
website tonight.
In order to actually generate the docs, you'll have to install all the
DocBook tools, as well as gtk-doc from GNOME cvs. (see
http://developer.gnome.org/arch/doc/tools.html)
Notes (I'll codify these some day):
- Don't believe the Gnome page, always edit the SOURCES when documenting a
given function, never the tmpl file.
- I'll be re-arranging things a lot, but gtk-doc is smart enough to merge
any changes to the tmpl file. However, gtk-doc's merge and CVS's diff are
two entirely separate animals. We should probably have a virtual mutex on
the entire docs/gst/ directory, over and above what CVS does.
- I'm going to try to end up with a book set (docbook terms), where
docs/gst/ is only one book. There'd be another called docs/manual/, and
another docs/plugins/, etc. If you have any comments as to how these
should be done, gstreamer-devel is the place.
2000-02-01 09:16:43 +00:00
|
|
|
|
|
|
|
|
2001-03-21 21:43:56 +00:00
|
|
|
<!-- ##### FUNCTION gst_pad_get_caps ##### -->
|
2000-12-31 17:02:47 +00:00
|
|
|
<para>
|
|
|
|
|
|
|
|
</para>
|
|
|
|
|
|
|
|
@pad:
|
|
|
|
@Returns:
|
|
|
|
|
|
|
|
|
|
|
|
<!-- ##### FUNCTION gst_pad_check_compatibility ##### -->
|
|
|
|
<para>
|
|
|
|
|
|
|
|
</para>
|
|
|
|
|
|
|
|
@srcpad:
|
|
|
|
@sinkpad:
|
|
|
|
@Returns:
|
|
|
|
|
|
|
|
|
2000-03-27 19:53:43 +00:00
|
|
|
<!-- ##### FUNCTION gst_pad_set_name ##### -->
|
Re- set up the gtk-doc system. I'd managed to mutilate it a while back, but now it's fixed. I'll put a copy of the ...
Original commit message from CVS:
Re- set up the gtk-doc system. I'd managed to mutilate it a while back,
but now it's fixed. I'll put a copy of the HTML output somewhere on the
website tonight.
In order to actually generate the docs, you'll have to install all the
DocBook tools, as well as gtk-doc from GNOME cvs. (see
http://developer.gnome.org/arch/doc/tools.html)
Notes (I'll codify these some day):
- Don't believe the Gnome page, always edit the SOURCES when documenting a
given function, never the tmpl file.
- I'll be re-arranging things a lot, but gtk-doc is smart enough to merge
any changes to the tmpl file. However, gtk-doc's merge and CVS's diff are
two entirely separate animals. We should probably have a virtual mutex on
the entire docs/gst/ directory, over and above what CVS does.
- I'm going to try to end up with a book set (docbook terms), where
docs/gst/ is only one book. There'd be another called docs/manual/, and
another docs/plugins/, etc. If you have any comments as to how these
should be done, gstreamer-devel is the place.
2000-02-01 09:16:43 +00:00
|
|
|
<para>
|
|
|
|
|
|
|
|
</para>
|
|
|
|
|
|
|
|
@pad:
|
2000-03-27 19:53:43 +00:00
|
|
|
@name:
|
Re- set up the gtk-doc system. I'd managed to mutilate it a while back, but now it's fixed. I'll put a copy of the ...
Original commit message from CVS:
Re- set up the gtk-doc system. I'd managed to mutilate it a while back,
but now it's fixed. I'll put a copy of the HTML output somewhere on the
website tonight.
In order to actually generate the docs, you'll have to install all the
DocBook tools, as well as gtk-doc from GNOME cvs. (see
http://developer.gnome.org/arch/doc/tools.html)
Notes (I'll codify these some day):
- Don't believe the Gnome page, always edit the SOURCES when documenting a
given function, never the tmpl file.
- I'll be re-arranging things a lot, but gtk-doc is smart enough to merge
any changes to the tmpl file. However, gtk-doc's merge and CVS's diff are
two entirely separate animals. We should probably have a virtual mutex on
the entire docs/gst/ directory, over and above what CVS does.
- I'm going to try to end up with a book set (docbook terms), where
docs/gst/ is only one book. There'd be another called docs/manual/, and
another docs/plugins/, etc. If you have any comments as to how these
should be done, gstreamer-devel is the place.
2000-02-01 09:16:43 +00:00
|
|
|
|
|
|
|
|
2000-03-27 19:53:43 +00:00
|
|
|
<!-- ##### FUNCTION gst_pad_get_name ##### -->
|
Re- set up the gtk-doc system. I'd managed to mutilate it a while back, but now it's fixed. I'll put a copy of the ...
Original commit message from CVS:
Re- set up the gtk-doc system. I'd managed to mutilate it a while back,
but now it's fixed. I'll put a copy of the HTML output somewhere on the
website tonight.
In order to actually generate the docs, you'll have to install all the
DocBook tools, as well as gtk-doc from GNOME cvs. (see
http://developer.gnome.org/arch/doc/tools.html)
Notes (I'll codify these some day):
- Don't believe the Gnome page, always edit the SOURCES when documenting a
given function, never the tmpl file.
- I'll be re-arranging things a lot, but gtk-doc is smart enough to merge
any changes to the tmpl file. However, gtk-doc's merge and CVS's diff are
two entirely separate animals. We should probably have a virtual mutex on
the entire docs/gst/ directory, over and above what CVS does.
- I'm going to try to end up with a book set (docbook terms), where
docs/gst/ is only one book. There'd be another called docs/manual/, and
another docs/plugins/, etc. If you have any comments as to how these
should be done, gstreamer-devel is the place.
2000-02-01 09:16:43 +00:00
|
|
|
<para>
|
|
|
|
|
|
|
|
</para>
|
|
|
|
|
|
|
|
@pad:
|
|
|
|
@Returns:
|
|
|
|
|
|
|
|
|
2001-01-19 22:15:21 +00:00
|
|
|
<!-- ##### FUNCTION gst_pad_set_element_private ##### -->
|
|
|
|
<para>
|
|
|
|
|
|
|
|
</para>
|
|
|
|
|
|
|
|
@pad:
|
|
|
|
@priv:
|
|
|
|
|
|
|
|
|
|
|
|
<!-- ##### FUNCTION gst_pad_get_element_private ##### -->
|
|
|
|
<para>
|
|
|
|
|
|
|
|
</para>
|
|
|
|
|
|
|
|
@pad:
|
|
|
|
@Returns:
|
|
|
|
|
|
|
|
|
Re- set up the gtk-doc system. I'd managed to mutilate it a while back, but now it's fixed. I'll put a copy of the ...
Original commit message from CVS:
Re- set up the gtk-doc system. I'd managed to mutilate it a while back,
but now it's fixed. I'll put a copy of the HTML output somewhere on the
website tonight.
In order to actually generate the docs, you'll have to install all the
DocBook tools, as well as gtk-doc from GNOME cvs. (see
http://developer.gnome.org/arch/doc/tools.html)
Notes (I'll codify these some day):
- Don't believe the Gnome page, always edit the SOURCES when documenting a
given function, never the tmpl file.
- I'll be re-arranging things a lot, but gtk-doc is smart enough to merge
any changes to the tmpl file. However, gtk-doc's merge and CVS's diff are
two entirely separate animals. We should probably have a virtual mutex on
the entire docs/gst/ directory, over and above what CVS does.
- I'm going to try to end up with a book set (docbook terms), where
docs/gst/ is only one book. There'd be another called docs/manual/, and
another docs/plugins/, etc. If you have any comments as to how these
should be done, gstreamer-devel is the place.
2000-02-01 09:16:43 +00:00
|
|
|
<!-- ##### FUNCTION gst_pad_set_parent ##### -->
|
|
|
|
<para>
|
|
|
|
|
|
|
|
</para>
|
|
|
|
|
|
|
|
@pad:
|
|
|
|
@parent:
|
|
|
|
|
|
|
|
|
2000-12-28 21:42:23 +00:00
|
|
|
<!-- ##### FUNCTION gst_pad_get_parent ##### -->
|
Re- set up the gtk-doc system. I'd managed to mutilate it a while back, but now it's fixed. I'll put a copy of the ...
Original commit message from CVS:
Re- set up the gtk-doc system. I'd managed to mutilate it a while back,
but now it's fixed. I'll put a copy of the HTML output somewhere on the
website tonight.
In order to actually generate the docs, you'll have to install all the
DocBook tools, as well as gtk-doc from GNOME cvs. (see
http://developer.gnome.org/arch/doc/tools.html)
Notes (I'll codify these some day):
- Don't believe the Gnome page, always edit the SOURCES when documenting a
given function, never the tmpl file.
- I'll be re-arranging things a lot, but gtk-doc is smart enough to merge
any changes to the tmpl file. However, gtk-doc's merge and CVS's diff are
two entirely separate animals. We should probably have a virtual mutex on
the entire docs/gst/ directory, over and above what CVS does.
- I'm going to try to end up with a book set (docbook terms), where
docs/gst/ is only one book. There'd be another called docs/manual/, and
another docs/plugins/, etc. If you have any comments as to how these
should be done, gstreamer-devel is the place.
2000-02-01 09:16:43 +00:00
|
|
|
<para>
|
|
|
|
|
|
|
|
</para>
|
|
|
|
|
|
|
|
@pad:
|
2000-12-28 21:42:23 +00:00
|
|
|
@Returns:
|
Re- set up the gtk-doc system. I'd managed to mutilate it a while back, but now it's fixed. I'll put a copy of the ...
Original commit message from CVS:
Re- set up the gtk-doc system. I'd managed to mutilate it a while back,
but now it's fixed. I'll put a copy of the HTML output somewhere on the
website tonight.
In order to actually generate the docs, you'll have to install all the
DocBook tools, as well as gtk-doc from GNOME cvs. (see
http://developer.gnome.org/arch/doc/tools.html)
Notes (I'll codify these some day):
- Don't believe the Gnome page, always edit the SOURCES when documenting a
given function, never the tmpl file.
- I'll be re-arranging things a lot, but gtk-doc is smart enough to merge
any changes to the tmpl file. However, gtk-doc's merge and CVS's diff are
two entirely separate animals. We should probably have a virtual mutex on
the entire docs/gst/ directory, over and above what CVS does.
- I'm going to try to end up with a book set (docbook terms), where
docs/gst/ is only one book. There'd be another called docs/manual/, and
another docs/plugins/, etc. If you have any comments as to how these
should be done, gstreamer-devel is the place.
2000-02-01 09:16:43 +00:00
|
|
|
|
|
|
|
|
2001-05-27 14:33:30 +00:00
|
|
|
<!-- ##### FUNCTION gst_pad_get_sched ##### -->
|
|
|
|
<para>
|
|
|
|
|
|
|
|
</para>
|
|
|
|
|
|
|
|
@pad:
|
|
|
|
@Returns:
|
|
|
|
|
|
|
|
|
|
|
|
<!-- ##### FUNCTION gst_pad_set_sched ##### -->
|
|
|
|
<para>
|
|
|
|
|
|
|
|
</para>
|
|
|
|
|
|
|
|
@pad:
|
|
|
|
@sched:
|
|
|
|
|
|
|
|
|
2001-03-21 21:43:56 +00:00
|
|
|
<!-- ##### FUNCTION gst_pad_get_real_parent ##### -->
|
|
|
|
<para>
|
|
|
|
|
|
|
|
</para>
|
|
|
|
|
|
|
|
@pad:
|
|
|
|
@Returns:
|
|
|
|
|
|
|
|
|
2001-01-21 23:20:46 +00:00
|
|
|
<!-- ##### FUNCTION gst_pad_add_ghost_pad ##### -->
|
Re- set up the gtk-doc system. I'd managed to mutilate it a while back, but now it's fixed. I'll put a copy of the ...
Original commit message from CVS:
Re- set up the gtk-doc system. I'd managed to mutilate it a while back,
but now it's fixed. I'll put a copy of the HTML output somewhere on the
website tonight.
In order to actually generate the docs, you'll have to install all the
DocBook tools, as well as gtk-doc from GNOME cvs. (see
http://developer.gnome.org/arch/doc/tools.html)
Notes (I'll codify these some day):
- Don't believe the Gnome page, always edit the SOURCES when documenting a
given function, never the tmpl file.
- I'll be re-arranging things a lot, but gtk-doc is smart enough to merge
any changes to the tmpl file. However, gtk-doc's merge and CVS's diff are
two entirely separate animals. We should probably have a virtual mutex on
the entire docs/gst/ directory, over and above what CVS does.
- I'm going to try to end up with a book set (docbook terms), where
docs/gst/ is only one book. There'd be another called docs/manual/, and
another docs/plugins/, etc. If you have any comments as to how these
should be done, gstreamer-devel is the place.
2000-02-01 09:16:43 +00:00
|
|
|
<para>
|
|
|
|
|
|
|
|
</para>
|
|
|
|
|
|
|
|
@pad:
|
2001-01-21 23:20:46 +00:00
|
|
|
@ghostpad:
|
Re- set up the gtk-doc system. I'd managed to mutilate it a while back, but now it's fixed. I'll put a copy of the ...
Original commit message from CVS:
Re- set up the gtk-doc system. I'd managed to mutilate it a while back,
but now it's fixed. I'll put a copy of the HTML output somewhere on the
website tonight.
In order to actually generate the docs, you'll have to install all the
DocBook tools, as well as gtk-doc from GNOME cvs. (see
http://developer.gnome.org/arch/doc/tools.html)
Notes (I'll codify these some day):
- Don't believe the Gnome page, always edit the SOURCES when documenting a
given function, never the tmpl file.
- I'll be re-arranging things a lot, but gtk-doc is smart enough to merge
any changes to the tmpl file. However, gtk-doc's merge and CVS's diff are
two entirely separate animals. We should probably have a virtual mutex on
the entire docs/gst/ directory, over and above what CVS does.
- I'm going to try to end up with a book set (docbook terms), where
docs/gst/ is only one book. There'd be another called docs/manual/, and
another docs/plugins/, etc. If you have any comments as to how these
should be done, gstreamer-devel is the place.
2000-02-01 09:16:43 +00:00
|
|
|
|
|
|
|
|
2001-01-21 23:20:46 +00:00
|
|
|
<!-- ##### FUNCTION gst_pad_remove_ghost_pad ##### -->
|
Re- set up the gtk-doc system. I'd managed to mutilate it a while back, but now it's fixed. I'll put a copy of the ...
Original commit message from CVS:
Re- set up the gtk-doc system. I'd managed to mutilate it a while back,
but now it's fixed. I'll put a copy of the HTML output somewhere on the
website tonight.
In order to actually generate the docs, you'll have to install all the
DocBook tools, as well as gtk-doc from GNOME cvs. (see
http://developer.gnome.org/arch/doc/tools.html)
Notes (I'll codify these some day):
- Don't believe the Gnome page, always edit the SOURCES when documenting a
given function, never the tmpl file.
- I'll be re-arranging things a lot, but gtk-doc is smart enough to merge
any changes to the tmpl file. However, gtk-doc's merge and CVS's diff are
two entirely separate animals. We should probably have a virtual mutex on
the entire docs/gst/ directory, over and above what CVS does.
- I'm going to try to end up with a book set (docbook terms), where
docs/gst/ is only one book. There'd be another called docs/manual/, and
another docs/plugins/, etc. If you have any comments as to how these
should be done, gstreamer-devel is the place.
2000-02-01 09:16:43 +00:00
|
|
|
<para>
|
|
|
|
|
|
|
|
</para>
|
|
|
|
|
|
|
|
@pad:
|
2001-01-21 23:20:46 +00:00
|
|
|
@ghostpad:
|
Re- set up the gtk-doc system. I'd managed to mutilate it a while back, but now it's fixed. I'll put a copy of the ...
Original commit message from CVS:
Re- set up the gtk-doc system. I'd managed to mutilate it a while back,
but now it's fixed. I'll put a copy of the HTML output somewhere on the
website tonight.
In order to actually generate the docs, you'll have to install all the
DocBook tools, as well as gtk-doc from GNOME cvs. (see
http://developer.gnome.org/arch/doc/tools.html)
Notes (I'll codify these some day):
- Don't believe the Gnome page, always edit the SOURCES when documenting a
given function, never the tmpl file.
- I'll be re-arranging things a lot, but gtk-doc is smart enough to merge
any changes to the tmpl file. However, gtk-doc's merge and CVS's diff are
two entirely separate animals. We should probably have a virtual mutex on
the entire docs/gst/ directory, over and above what CVS does.
- I'm going to try to end up with a book set (docbook terms), where
docs/gst/ is only one book. There'd be another called docs/manual/, and
another docs/plugins/, etc. If you have any comments as to how these
should be done, gstreamer-devel is the place.
2000-02-01 09:16:43 +00:00
|
|
|
|
|
|
|
|
2001-01-21 23:20:46 +00:00
|
|
|
<!-- ##### FUNCTION gst_pad_get_ghost_pad_list ##### -->
|
Re- set up the gtk-doc system. I'd managed to mutilate it a while back, but now it's fixed. I'll put a copy of the ...
Original commit message from CVS:
Re- set up the gtk-doc system. I'd managed to mutilate it a while back,
but now it's fixed. I'll put a copy of the HTML output somewhere on the
website tonight.
In order to actually generate the docs, you'll have to install all the
DocBook tools, as well as gtk-doc from GNOME cvs. (see
http://developer.gnome.org/arch/doc/tools.html)
Notes (I'll codify these some day):
- Don't believe the Gnome page, always edit the SOURCES when documenting a
given function, never the tmpl file.
- I'll be re-arranging things a lot, but gtk-doc is smart enough to merge
any changes to the tmpl file. However, gtk-doc's merge and CVS's diff are
two entirely separate animals. We should probably have a virtual mutex on
the entire docs/gst/ directory, over and above what CVS does.
- I'm going to try to end up with a book set (docbook terms), where
docs/gst/ is only one book. There'd be another called docs/manual/, and
another docs/plugins/, etc. If you have any comments as to how these
should be done, gstreamer-devel is the place.
2000-02-01 09:16:43 +00:00
|
|
|
<para>
|
|
|
|
|
|
|
|
</para>
|
|
|
|
|
|
|
|
@pad:
|
|
|
|
@Returns:
|
|
|
|
|
|
|
|
|
|
|
|
<!-- ##### FUNCTION gst_pad_get_peer ##### -->
|
|
|
|
<para>
|
|
|
|
|
|
|
|
</para>
|
|
|
|
|
|
|
|
@pad:
|
|
|
|
@Returns:
|
|
|
|
|
|
|
|
|
|
|
|
<!-- ##### FUNCTION gst_pad_connect ##### -->
|
|
|
|
<para>
|
|
|
|
|
|
|
|
</para>
|
|
|
|
|
|
|
|
@srcpad:
|
|
|
|
@sinkpad:
|
2001-03-21 21:43:56 +00:00
|
|
|
@Returns:
|
Re- set up the gtk-doc system. I'd managed to mutilate it a while back, but now it's fixed. I'll put a copy of the ...
Original commit message from CVS:
Re- set up the gtk-doc system. I'd managed to mutilate it a while back,
but now it's fixed. I'll put a copy of the HTML output somewhere on the
website tonight.
In order to actually generate the docs, you'll have to install all the
DocBook tools, as well as gtk-doc from GNOME cvs. (see
http://developer.gnome.org/arch/doc/tools.html)
Notes (I'll codify these some day):
- Don't believe the Gnome page, always edit the SOURCES when documenting a
given function, never the tmpl file.
- I'll be re-arranging things a lot, but gtk-doc is smart enough to merge
any changes to the tmpl file. However, gtk-doc's merge and CVS's diff are
two entirely separate animals. We should probably have a virtual mutex on
the entire docs/gst/ directory, over and above what CVS does.
- I'm going to try to end up with a book set (docbook terms), where
docs/gst/ is only one book. There'd be another called docs/manual/, and
another docs/plugins/, etc. If you have any comments as to how these
should be done, gstreamer-devel is the place.
2000-02-01 09:16:43 +00:00
|
|
|
|
|
|
|
|
2000-09-13 19:04:55 +00:00
|
|
|
<!-- ##### FUNCTION gst_pad_disconnect ##### -->
|
|
|
|
<para>
|
|
|
|
|
|
|
|
</para>
|
|
|
|
|
|
|
|
@srcpad:
|
|
|
|
@sinkpad:
|
|
|
|
|
|
|
|
|
Re- set up the gtk-doc system. I'd managed to mutilate it a while back, but now it's fixed. I'll put a copy of the ...
Original commit message from CVS:
Re- set up the gtk-doc system. I'd managed to mutilate it a while back,
but now it's fixed. I'll put a copy of the HTML output somewhere on the
website tonight.
In order to actually generate the docs, you'll have to install all the
DocBook tools, as well as gtk-doc from GNOME cvs. (see
http://developer.gnome.org/arch/doc/tools.html)
Notes (I'll codify these some day):
- Don't believe the Gnome page, always edit the SOURCES when documenting a
given function, never the tmpl file.
- I'll be re-arranging things a lot, but gtk-doc is smart enough to merge
any changes to the tmpl file. However, gtk-doc's merge and CVS's diff are
two entirely separate animals. We should probably have a virtual mutex on
the entire docs/gst/ directory, over and above what CVS does.
- I'm going to try to end up with a book set (docbook terms), where
docs/gst/ is only one book. There'd be another called docs/manual/, and
another docs/plugins/, etc. If you have any comments as to how these
should be done, gstreamer-devel is the place.
2000-02-01 09:16:43 +00:00
|
|
|
<!-- ##### FUNCTION gst_pad_push ##### -->
|
|
|
|
<para>
|
|
|
|
|
|
|
|
</para>
|
|
|
|
|
|
|
|
@pad:
|
2001-02-22 23:18:51 +00:00
|
|
|
@buf:
|
|
|
|
<!-- # Unused Parameters # -->
|
Re- set up the gtk-doc system. I'd managed to mutilate it a while back, but now it's fixed. I'll put a copy of the ...
Original commit message from CVS:
Re- set up the gtk-doc system. I'd managed to mutilate it a while back,
but now it's fixed. I'll put a copy of the HTML output somewhere on the
website tonight.
In order to actually generate the docs, you'll have to install all the
DocBook tools, as well as gtk-doc from GNOME cvs. (see
http://developer.gnome.org/arch/doc/tools.html)
Notes (I'll codify these some day):
- Don't believe the Gnome page, always edit the SOURCES when documenting a
given function, never the tmpl file.
- I'll be re-arranging things a lot, but gtk-doc is smart enough to merge
any changes to the tmpl file. However, gtk-doc's merge and CVS's diff are
two entirely separate animals. We should probably have a virtual mutex on
the entire docs/gst/ directory, over and above what CVS does.
- I'm going to try to end up with a book set (docbook terms), where
docs/gst/ is only one book. There'd be another called docs/manual/, and
another docs/plugins/, etc. If you have any comments as to how these
should be done, gstreamer-devel is the place.
2000-02-01 09:16:43 +00:00
|
|
|
@buffer:
|
|
|
|
|
|
|
|
|
|
|
|
<!-- ##### FUNCTION gst_pad_pull ##### -->
|
|
|
|
<para>
|
|
|
|
|
|
|
|
</para>
|
|
|
|
|
|
|
|
@pad:
|
|
|
|
@Returns:
|
|
|
|
|
|
|
|
|
2001-02-21 23:01:36 +00:00
|
|
|
<!-- ##### FUNCTION gst_pad_pullregion ##### -->
|
2000-11-07 21:24:12 +00:00
|
|
|
<para>
|
|
|
|
|
|
|
|
</para>
|
|
|
|
|
|
|
|
@pad:
|
2001-02-21 23:01:36 +00:00
|
|
|
@type:
|
2000-11-07 21:24:12 +00:00
|
|
|
@offset:
|
2001-02-21 23:01:36 +00:00
|
|
|
@len:
|
2000-11-07 21:24:12 +00:00
|
|
|
@Returns:
|
2001-02-21 23:01:36 +00:00
|
|
|
<!-- # Unused Parameters # -->
|
2000-12-28 21:42:23 +00:00
|
|
|
@size:
|
2000-09-13 19:04:55 +00:00
|
|
|
|
|
|
|
|
2001-04-17 21:14:55 +00:00
|
|
|
<!-- ##### FUNCTION gst_pad_get_bufferpool ##### -->
|
|
|
|
<para>
|
|
|
|
|
|
|
|
</para>
|
|
|
|
|
|
|
|
@pad:
|
|
|
|
@Returns:
|
|
|
|
|
|
|
|
|
2000-10-22 16:30:25 +00:00
|
|
|
<!-- ##### FUNCTION gst_pad_load_and_connect ##### -->
|
|
|
|
<para>
|
|
|
|
|
|
|
|
</para>
|
|
|
|
|
2001-01-29 00:06:02 +00:00
|
|
|
@self:
|
2000-10-22 16:30:25 +00:00
|
|
|
@parent:
|
2001-01-29 00:06:02 +00:00
|
|
|
<!-- # Unused Parameters # -->
|
2000-10-22 16:30:25 +00:00
|
|
|
@element:
|
|
|
|
@elements:
|
|
|
|
|
|
|
|
|
2001-03-21 21:43:56 +00:00
|
|
|
<!-- ##### FUNCTION gst_pad_negotiate_proxy ##### -->
|
|
|
|
<para>
|
|
|
|
|
|
|
|
</para>
|
|
|
|
|
|
|
|
@srcpad:
|
|
|
|
@destpad:
|
|
|
|
@caps:
|
|
|
|
@Returns:
|
|
|
|
<!-- # Unused Parameters # -->
|
2001-04-12 18:11:19 +00:00
|
|
|
@counter:
|
2001-03-21 21:43:56 +00:00
|
|
|
@count:
|
|
|
|
|
|
|
|
|
|
|
|
<!-- ##### FUNCTION gst_pad_renegotiate ##### -->
|
|
|
|
<para>
|
|
|
|
|
|
|
|
</para>
|
|
|
|
|
|
|
|
@pad:
|
|
|
|
@Returns:
|
|
|
|
|
|
|
|
|
|
|
|
<!-- ##### FUNCTION gst_pad_get_padtemplate ##### -->
|
|
|
|
<para>
|
|
|
|
|
|
|
|
</para>
|
|
|
|
|
|
|
|
@pad:
|
|
|
|
@Returns:
|
|
|
|
|
|
|
|
|
|
|
|
<!-- ##### FUNCTION gst_pad_get_padtemplate_caps ##### -->
|
|
|
|
<para>
|
|
|
|
|
|
|
|
</para>
|
|
|
|
|
|
|
|
@pad:
|
|
|
|
@Returns:
|
|
|
|
|
|
|
|
|
2001-01-19 22:15:21 +00:00
|
|
|
<!-- ##### STRUCT GstRealPad ##### -->
|
|
|
|
<para>
|
|
|
|
|
|
|
|
</para>
|
|
|
|
|
|
|
|
@pad:
|
|
|
|
@caps:
|
|
|
|
@direction:
|
|
|
|
@threadstate:
|
|
|
|
@peer:
|
|
|
|
@bufpen:
|
2001-02-21 23:01:36 +00:00
|
|
|
@regiontype:
|
|
|
|
@offset:
|
|
|
|
@len:
|
2001-05-27 14:33:30 +00:00
|
|
|
@sched:
|
2001-01-19 22:15:21 +00:00
|
|
|
@chainfunc:
|
2001-10-17 10:21:27 +00:00
|
|
|
@chainhandler:
|
2001-01-19 22:15:21 +00:00
|
|
|
@getfunc:
|
2001-10-17 10:21:27 +00:00
|
|
|
@gethandler:
|
|
|
|
@eventfunc:
|
|
|
|
@eventhandler:
|
2001-01-19 22:15:21 +00:00
|
|
|
@getregionfunc:
|
|
|
|
@pullregionfunc:
|
2001-03-21 21:43:56 +00:00
|
|
|
@negotiatefunc:
|
2001-04-12 18:11:19 +00:00
|
|
|
@newcapsfunc:
|
2001-04-17 21:14:55 +00:00
|
|
|
@bufferpoolfunc:
|
2001-01-21 23:20:46 +00:00
|
|
|
@ghostpads:
|
2001-01-19 22:15:21 +00:00
|
|
|
|
2001-05-27 14:33:30 +00:00
|
|
|
<!-- ##### MACRO GST_RPAD_LEN ##### -->
|
|
|
|
<para>
|
|
|
|
Get the length of the region that is being pulled.
|
|
|
|
</para>
|
|
|
|
|
|
|
|
@pad: the real pad to query.
|
|
|
|
|
|
|
|
|
|
|
|
<!-- ##### MACRO GST_RPAD_OFFSET ##### -->
|
|
|
|
<para>
|
|
|
|
Get the offset of the region that is being pulled.
|
|
|
|
</para>
|
|
|
|
|
|
|
|
@pad: the real pad to query.
|
|
|
|
|
|
|
|
|
|
|
|
<!-- ##### MACRO GST_RPAD_SCHED ##### -->
|
|
|
|
<para>
|
|
|
|
|
|
|
|
</para>
|
|
|
|
|
|
|
|
@pad:
|
|
|
|
|
|
|
|
|
|
|
|
<!-- ##### MACRO GST_RPAD_REGIONTYPE ##### -->
|
|
|
|
<para>
|
|
|
|
Get the type of the region that is being pulled.
|
|
|
|
</para>
|
|
|
|
|
|
|
|
@pad: the real pad to query.
|
|
|
|
|
|
|
|
|
2001-01-19 22:15:21 +00:00
|
|
|
<!-- ##### MACRO GST_RPAD_DIRECTION ##### -->
|
|
|
|
<para>
|
|
|
|
Get the direction of the real pad.
|
|
|
|
</para>
|
|
|
|
|
|
|
|
@pad: the realpad to query.
|
|
|
|
|
|
|
|
|
|
|
|
<!-- ##### MACRO GST_RPAD_CAPS ##### -->
|
|
|
|
<para>
|
|
|
|
Get the caps of the real pad.
|
|
|
|
</para>
|
|
|
|
|
|
|
|
@pad: the real pad to query.
|
|
|
|
|
|
|
|
|
|
|
|
<!-- ##### MACRO GST_RPAD_PEER ##### -->
|
|
|
|
<para>
|
|
|
|
Get the peer element of the real pad.
|
|
|
|
</para>
|
|
|
|
|
|
|
|
@pad: the real pad to query.
|
|
|
|
|
|
|
|
|
|
|
|
<!-- ##### MACRO GST_RPAD_BUFPEN ##### -->
|
|
|
|
<para>
|
|
|
|
Get the bufpen of the real pad.
|
|
|
|
</para>
|
|
|
|
|
|
|
|
@pad: the real pad to query.
|
|
|
|
|
|
|
|
|
|
|
|
<!-- ##### MACRO GST_RPAD_CHAINFUNC ##### -->
|
|
|
|
<para>
|
|
|
|
Get the chain function of the real pad.
|
|
|
|
</para>
|
|
|
|
|
|
|
|
@pad: the real pad to query.
|
|
|
|
|
|
|
|
|
|
|
|
<!-- ##### MACRO GST_RPAD_GETFUNC ##### -->
|
|
|
|
<para>
|
|
|
|
Get get getfunction of the real pad.
|
|
|
|
</para>
|
|
|
|
|
|
|
|
@pad: the real pad to query.
|
|
|
|
|
|
|
|
|
|
|
|
<!-- ##### MACRO GST_RPAD_GETREGIONFUNC ##### -->
|
|
|
|
<para>
|
|
|
|
Get the getregion function of the real pad.
|
|
|
|
</para>
|
|
|
|
|
|
|
|
@pad: the real pad to query.
|
|
|
|
|
|
|
|
|
|
|
|
<!-- ##### MACRO GST_RPAD_PULLREGIONFUNC ##### -->
|
|
|
|
<para>
|
|
|
|
Get the pullregion function of the real pad.
|
|
|
|
</para>
|
|
|
|
|
|
|
|
@pad: the real pad to query.
|
|
|
|
|
|
|
|
|
2001-03-21 21:43:56 +00:00
|
|
|
<!-- ##### MACRO GST_RPAD_NEGOTIATEFUNC ##### -->
|
|
|
|
<para>
|
2001-04-19 22:25:04 +00:00
|
|
|
Get the negotiate function from the real pad.
|
2001-03-21 21:43:56 +00:00
|
|
|
</para>
|
|
|
|
|
2001-04-19 22:25:04 +00:00
|
|
|
@pad: the real pad to query.
|
2001-03-21 21:43:56 +00:00
|
|
|
|
|
|
|
|
2001-04-12 18:11:19 +00:00
|
|
|
<!-- ##### MACRO GST_RPAD_NEWCAPSFUNC ##### -->
|
|
|
|
<para>
|
2001-04-19 22:25:04 +00:00
|
|
|
Get the newcaps function from the real pad.
|
2001-04-12 18:11:19 +00:00
|
|
|
</para>
|
|
|
|
|
2001-04-19 22:25:04 +00:00
|
|
|
@pad: the real pad to query.
|
2001-04-12 18:11:19 +00:00
|
|
|
|
|
|
|
|
2001-04-17 21:14:55 +00:00
|
|
|
<!-- ##### MACRO GST_RPAD_BUFFERPOOLFUNC ##### -->
|
|
|
|
<para>
|
2001-04-19 22:25:04 +00:00
|
|
|
Get the bufferpoolfunction from the real pad.
|
2001-04-17 21:14:55 +00:00
|
|
|
</para>
|
|
|
|
|
2001-04-19 22:25:04 +00:00
|
|
|
@pad: the real pad to query.
|
2001-04-17 21:14:55 +00:00
|
|
|
|
|
|
|
|
2001-01-19 22:15:21 +00:00
|
|
|
<!-- ##### MACRO GST_GPAD_REALPAD ##### -->
|
|
|
|
<para>
|
|
|
|
Get the real pad of this ghost pad.
|
|
|
|
</para>
|
|
|
|
|
|
|
|
@pad: the real pad to query.
|
|
|
|
|
|
|
|
|
|
|
|
<!-- ##### STRUCT GstGhostPad ##### -->
|
|
|
|
<para>
|
|
|
|
|
|
|
|
</para>
|
|
|
|
|
|
|
|
@pad:
|
|
|
|
@realpad:
|
|
|
|
|
2001-01-21 23:20:46 +00:00
|
|
|
<!-- ##### FUNCTION gst_ghost_pad_new ##### -->
|
|
|
|
<para>
|
|
|
|
|
|
|
|
</para>
|
|
|
|
|
|
|
|
@name:
|
|
|
|
@pad:
|
|
|
|
@Returns:
|
|
|
|
|
|
|
|
|
2000-12-28 21:42:23 +00:00
|
|
|
<!-- ##### ENUM GstPadPresence ##### -->
|
|
|
|
<para>
|
2001-01-06 22:05:15 +00:00
|
|
|
Indicates when this pad will become available.
|
2000-12-28 21:42:23 +00:00
|
|
|
</para>
|
|
|
|
|
|
|
|
@GST_PAD_ALWAYS: the pad is always available
|
|
|
|
@GST_PAD_SOMETIMES: the pad will become available depending on the media stream
|
2001-04-19 22:25:04 +00:00
|
|
|
@GST_PAD_REQUEST: th pad is only available on request with
|
|
|
|
gst_element_request_pad_by_name() or gst_element_request_compatible_pad().
|
2000-12-28 21:42:23 +00:00
|
|
|
|
|
|
|
<!-- ##### STRUCT GstPadTemplate ##### -->
|
|
|
|
<para>
|
|
|
|
|
|
|
|
</para>
|
|
|
|
|
|
|
|
@object:
|
|
|
|
@name_template:
|
|
|
|
@direction:
|
|
|
|
@presence:
|
|
|
|
@caps:
|
|
|
|
|
2001-03-21 21:43:56 +00:00
|
|
|
<!-- ##### MACRO GST_PADTEMPLATE_CAPS ##### -->
|
|
|
|
<para>
|
2001-04-19 22:25:04 +00:00
|
|
|
Get a handle to the padtemplate #GstCaps
|
2001-03-21 21:43:56 +00:00
|
|
|
</para>
|
|
|
|
|
2001-04-19 22:25:04 +00:00
|
|
|
@templ: the template to query
|
2001-03-21 21:43:56 +00:00
|
|
|
|
|
|
|
|
|
|
|
<!-- ##### MACRO GST_PADTEMPLATE_DIRECTION ##### -->
|
|
|
|
<para>
|
2001-04-19 22:25:04 +00:00
|
|
|
Get the direction of the padtemplate.
|
2001-03-21 21:43:56 +00:00
|
|
|
</para>
|
|
|
|
|
2001-04-19 22:25:04 +00:00
|
|
|
@templ: the template to query
|
2001-03-21 21:43:56 +00:00
|
|
|
|
|
|
|
|
|
|
|
<!-- ##### MACRO GST_PADTEMPLATE_NAME_TEMPLATE ##### -->
|
|
|
|
<para>
|
2001-04-19 22:25:04 +00:00
|
|
|
Get the nametemplate of the padtemplate.
|
2001-03-21 21:43:56 +00:00
|
|
|
</para>
|
|
|
|
|
2001-04-19 22:25:04 +00:00
|
|
|
@templ: the template to query
|
2001-03-21 21:43:56 +00:00
|
|
|
|
|
|
|
|
|
|
|
<!-- ##### MACRO GST_PADTEMPLATE_PRESENCE ##### -->
|
|
|
|
<para>
|
2001-04-19 22:25:04 +00:00
|
|
|
Get the presence of the padtemplate.
|
2001-03-21 21:43:56 +00:00
|
|
|
</para>
|
|
|
|
|
2001-04-19 22:25:04 +00:00
|
|
|
@templ: the template to query
|
2001-03-21 21:43:56 +00:00
|
|
|
|
|
|
|
|
2001-04-17 21:14:55 +00:00
|
|
|
<!-- ##### MACRO GST_PADTEMPLATE_NEW ##### -->
|
|
|
|
<para>
|
2001-04-19 22:25:04 +00:00
|
|
|
Create a new padtemplate.
|
2001-04-17 21:14:55 +00:00
|
|
|
</para>
|
|
|
|
|
2001-04-19 22:25:04 +00:00
|
|
|
@padname: the nametemplate for the pads that will be created with this template
|
|
|
|
@dir: the direction of the pads.
|
|
|
|
@pres: the presence of the pads.
|
|
|
|
@a...: the capabilities of this padtemplate usually created with GST_CAPS_NEW()
|
2001-04-17 21:14:55 +00:00
|
|
|
|
|
|
|
|
|
|
|
<!-- ##### MACRO GST_PADTEMPLATE_FACTORY ##### -->
|
|
|
|
<para>
|
2001-04-19 22:25:04 +00:00
|
|
|
Create a factory for a padtemplate. This can be used if you only want one instance
|
|
|
|
of the padtemplate. Use GST_PADTEMPLATE_GET() to get the unique padtemplate.
|
2001-04-17 21:14:55 +00:00
|
|
|
</para>
|
|
|
|
|
2001-04-19 22:25:04 +00:00
|
|
|
@name: th name of the factory
|
|
|
|
@padname: the nametemplate of the pads
|
|
|
|
@dir: the direction of the pads.
|
|
|
|
@pres: the presence of the pads.
|
|
|
|
@a...: the capabilities of this padtemplate, usually created with GST_CAPS_NEW()
|
2001-04-17 21:14:55 +00:00
|
|
|
|
|
|
|
|
|
|
|
<!-- ##### MACRO GST_PADTEMPLATE_GET ##### -->
|
|
|
|
<para>
|
2001-04-19 22:25:04 +00:00
|
|
|
Get the padtemplate of the factory created with GST_PADTEMPLATE_FACTORY()
|
2001-04-17 21:14:55 +00:00
|
|
|
</para>
|
|
|
|
|
2001-04-19 22:25:04 +00:00
|
|
|
@fact: the factory name to get the padtemplate from.
|
2001-04-17 21:14:55 +00:00
|
|
|
|
|
|
|
|
2000-12-28 21:42:23 +00:00
|
|
|
<!-- ##### FUNCTION gst_padtemplate_new ##### -->
|
|
|
|
<para>
|
|
|
|
|
|
|
|
</para>
|
|
|
|
|
|
|
|
@name_template:
|
|
|
|
@direction:
|
|
|
|
@presence:
|
|
|
|
@caps:
|
2001-04-14 18:56:37 +00:00
|
|
|
@Varargs:
|
2000-12-28 21:42:23 +00:00
|
|
|
@Returns:
|
|
|
|
|
|
|
|
|
|
|
|
<!-- ##### FUNCTION gst_padtemplate_load_thyself ##### -->
|
|
|
|
<para>
|
|
|
|
|
|
|
|
</para>
|
|
|
|
|
|
|
|
@parent:
|
|
|
|
@Returns:
|
|
|
|
|
|
|
|
|
|
|
|
<!-- ##### FUNCTION gst_padtemplate_save_thyself ##### -->
|
2000-12-13 19:29:35 +00:00
|
|
|
<para>
|
|
|
|
|
|
|
|
</para>
|
|
|
|
|
2001-01-19 22:15:21 +00:00
|
|
|
@templ:
|
2000-12-28 21:42:23 +00:00
|
|
|
@parent:
|
|
|
|
@Returns:
|
|
|
|
|
|
|
|
|
2001-03-21 21:43:56 +00:00
|
|
|
<!-- ##### FUNCTION gst_padtemplate_get_caps ##### -->
|
|
|
|
<para>
|
|
|
|
|
|
|
|
</para>
|
|
|
|
|
|
|
|
@templ:
|
|
|
|
@Returns:
|
|
|
|
|
|
|
|
|
|
|
|
<!-- ##### FUNCTION gst_padtemplate_get_caps_by_name ##### -->
|
|
|
|
<para>
|
|
|
|
|
|
|
|
</para>
|
|
|
|
|
|
|
|
@templ:
|
|
|
|
@name:
|
|
|
|
@Returns:
|
|
|
|
|
|
|
|
|