+2005-11-23 Thomas Vander Stichele <thomas at apestaart dot org>
+
+ * docs/faq/using.xml:
+ * docs/libs/tmpl/gstcontrol.sgml:
+ * docs/manual/advanced-dparams.xml:
+ * docs/manual/appendix-checklist.xml:
+ * docs/manual/basics-elements.xml:
+ * docs/pwg/other-source.xml:
+ * docs/random/moving-plugins:
+ * gst/gstpad.c:
+ * tools/gst-launch.1.in:
+ remove mentions of sinesrc
+
2005-11-23 Michael Smith <msmith@fluendo.com>
* docs/gst/gstreamer-sections.txt:
<answer>
<para>
You can test this by trying to play a sine tone. For this, you need to
-link the sinesrc plug-in to an output plug-in that matches your hardware.
+link the audiotestsrc element to an output element that matches your hardware.
A (non-complete) list of output plug-ins for audio is
<itemizedlist>
<listitem><para>osssink for OSS output</para></listitem>
<para>
Then try to play the sine tone by running
<programlisting>
-$ gst-launch sinesrc ! osssink
+$ gst-launch audiotestsrc ! osssink
</programlisting>
and see if you hear something. Make sure your volume is turned up,
but also make sure it is not too loud and you are not wearing your headphones.
For a full example look at the <file>gst-plugins/gst/sine/demo-dparams.c</file>
</para>
<para>
-To add dparam support to a plugin look at <file>gst-plugins/gst/sine/gstsinesrc.c</file>
+To add dparam support to a plugin look at <file>gst-plugins/gst/audiotestsrc/gstaudiotestsrc.c</file>
or <file>gst-plugins/gst/volume/gstvolume.c</file>.
The key concept is to call GST_DPMAN_PREPROCESS() before processing data and to
wrap the data processing (chain or loop function) by GST_DPMAN_PROCESS().
<filename>"asynchronous"</filename> because parameter changes may happen in the middle of a buffer being processed.
</para>
<programlisting>
- GstElement *sinesrc;
+ GstElement *audiotestsrc;
GstDParamManager *dpman;
...
- sinesrc = gst_element_factory_make("sinesrc","sine-source");
+ audiotestsrc = gst_element_factory_make("audiotestsrc", NULL);
...
- dpman = gst_dpman_get_manager (sinesrc);
+ dpman = gst_dpman_get_manager (audiotestsrc);
gst_dpman_set_mode(dpman, "synchronous");
</programlisting>
<para>
<para>
<command>gst-launch</command> is a simple script-like commandline
application that can be used to test pipelines. For example, the
- command <command>gst-launch sinesrc ! alsasink</command> will run
+ command <command>gst-launch audiotestsrc ! alsasink</command> will run
a pipeline which generates a sine-wave audio stream and plays it
to your ALSA audio card. <command>gst-launch</command> also allows
the use of threads (using curly brackets, so <quote>{</quote>
gst_init (&argc, &argv);
/* get factory */
- factory = gst_element_factory_find ("sinesrc");
+ factory = gst_element_factory_find ("audiotestsrc");
if (!factory) {
- g_print ("You don't have the 'sinesrc' element installed, go get it!\n");
+ g_print ("You don't have the 'audiotestsrc' element installed!\n");
return -1;
}
source element. Things become slightly more complicated, but still
very simple, if we create artificial video or audio data sources,
such as a video test image source or an artificial audio source (e.g.
- <classname>sinesrc</classname> or <classname>silence</classname>).
+ <classname>audiotestsrc</classname>).
It will become more complicated if we want the element to be a
realtime capture source, such as a video4linux source (for reading
video frames from a TV card) or an ALSA source (for reading data
can either have hardware-timing, in which case we can rely on backends
to provide sync for us (in which case you probably want to provide a
clock), or we will have to emulate that internally (e.g. to acquire
- sync in artificial data elements such as <classname>sinesrc</classname>).
+ sync in artificial data elements such as
+ <classname>audiotestsrc</classname>).
Let's first look at the second option (software sync). The first option
(hardware sync + providing a clock) does not require any special code
with respect to timing, and the clocking section already explained how
- conform to the GStreamer coding style
- use a custom debug category
- use GST_(DEBUG/*)_OBJECT
+ - use dashes in object property names to separate words
+ - use correct value, name, nick for enums
- The compiled plug-in:
- should show up correct in gst-inspect output; no warnings, no unknown
*
* If you don't know what this is, you probably don't want to call it.
*
- * Returns: TRUE if the operation was successfull.
+ * Returns: TRUE if the operation was successful.
*
* MT safe.
*/
Generate a null stream and ignore it
.B
- gst\-launch sinesrc ! osssink
+ gst\-launch audiotestsrc ! osssink
.br
Generate a pure tone to test the audio output