docs/faq/: Some minor FAQ updates that won't change the fact that our FAQ is badly structured, full of information ha...

Original commit message from CVS:
* docs/faq/developing.xml:
* docs/faq/faq.xml:
* docs/faq/troubleshooting.xml:
* docs/faq/using.xml:
Some minor FAQ updates that won't change the fact that
our FAQ is badly structured, full of information hardly
anyone new to GStreamer needs to know and lacking lots
of information people constantly ask for.

ChangeLog

@@ -1,3 +1,14 @@
+2006-05-19  Tim-Philipp Müller  <tim at centricular dot net>
+
+	* docs/faq/developing.xml:
+	* docs/faq/faq.xml:
+	* docs/faq/troubleshooting.xml:
+	* docs/faq/using.xml:
+	  Some minor FAQ updates that won't change the fact that
+	  our FAQ is badly structured, full of information hardly
+	  anyone new to GStreamer needs to know and lacking lots
+	  of information people constantly ask for.
+	  
 2006-05-19  Jan Schmidt  <thaytan@mad.scientist.com>
 
 	* gst/gstpad.c: (gst_pad_set_caps):

docs/faq/developing.xml

@@ -76,33 +76,12 @@ before any installed copies.
 
       <answer>
         <para>
-It's a good idea to use GConf to use default ways of outputting audio and
+For GNOME applications it's a good idea to use GConf to find the default ways
-video.  Since GStreamer's GConf keys can be more than
+of outputting audio and video.  You can do this by using the 'gconfaudiosink'
-just one element, but a whole pipeline, it would be a good idea
+and 'gconfvideosink' elements for audio and video output. They will take
-to use the gstgconf library.  It provides functions to parse the GConf key
+care of everything GConf-related for you and automatically use the outputs
-to a usable pipeline.
+that the user configured.
         </para>
-        <para>
-To link against gstgconf, use pkg-config to query the gstreamer-libs-&GST_MAJORMINOR;.pc file
-for link flags, and add -lgstgconf to the link flags.
-This fragment of configure.ac shows how to use pkg-config to get the LIBS:
-        </para>
-<programlisting>
-dnl check for GStreamer helper libs
-PKG_CHECK_MODULES(GST_HELPLIBS, gstreamer-libs-&GST_MAJORMINOR; >= $GSTREAMER_REQ,,exit)
-AC_SUBST(GST_HELPLIBS_LIBS)
-AC_SUBST(GST_HELPLIBS_CFLAGS)
-</programlisting>
-        <para>
-This fragment of a Makefile.am file shows how to make your application link
-to it:
-        </para>
-<programlisting>
-bin_PROGRAMS = application
-
-application_LDADD = $(GST_LIBS) $(GST_HELPLIBS_LIBS) -lgstgconf
-application_CFLAGS = $(GST_CFLAGS) $(GST_HELPLIBS_CFLAGS)
-</programlisting>
       </answer>
     </qandaentry>
 
@@ -137,8 +116,6 @@ Our main arena for coordination and discussion is IRC, not email.
 Join us in <ulink url="irc://irc.freenode.net/#gstreamer">#gstreamer on irc.freenode.net</ulink>
 For larger picture questions or getting more input from more persons,
 a mail to gstreamer-devel is never a bad idea.
-However, we do archive our IRC discussions, which you may find in the 
-gstreamer-daily mailing list archives.
         </para>
       </answer>
     </qandaentry>
@@ -216,6 +193,13 @@ As for the code itself, the
 Where possible, we try to adhere to the spirit of GObject and use similar
 coding idioms.
         </para>
+        <para>
+Patches should be made against CVS or the latest release and should be
+in 'unified context' format (use diff -u -p). They should be attached to
+a bug report (or feature request) in
+<ulink url="http://bugzilla.gnome.org">bugzilla</ulink> rather than
+sent to the mailing list.
+        </para>
       </answer>
     </qandaentry>
   </qandaset>

docs/faq/faq.xml

@@ -33,8 +33,14 @@
         deep-down-and-dirty compilation issues.
       </para>
     </abstract>
-    
+
     <revhistory>
+      <revision>
+        <revnumber>0.2.1</revnumber>
+        <date>2006-05-19</date>
+        <revremark>Some updates for GStreamer-0.10</revremark>
+      </revision>
+
       <revision>
         <revnumber>0.2.0</revnumber>
         <date>2006-03-16</date>
@@ -53,7 +59,6 @@
         <revremark>Initial conversion from FAQ database.</revremark>
       </revision>
     </revhistory>
-
   </articleinfo>
 
   &START;

docs/faq/troubleshooting.xml

@@ -2,33 +2,6 @@
   <title id="title-troubleshooting">Troubleshooting GStreamer</title>
   <qandaset defaultlabel="qanda">
 
-    <qandaentry>
-      <question id="troubleshooting-undefined-behaviour">
-        <label>
-My GStreamer-based application crashes on startup with errors about unfound
-schedulers on the command-line.
-        </label>
-        <para>
-I get undefined behaviour as soon as anyGStreamer element is being initialized.
-        </para>
-      </question>
-
-      <answer>
-        <para>
-If the application is using GStreamer-0.8 it might be that your registry is missing, or is outdated (i.e. not updated after
-a recent upgrade). Fix this by running gst-register yourself:
-          <programlisting>
-gst-register
-          </programlisting>
-In the worst case, you might have to run it both as user and as root.
-        </para>
-        <para>
-Note that package managers are suggested to run this automatically during the
-post-installation. Our RPMs and Debian packages do just that.
-        </para>
-      </answer>
-    </qandaentry>
-
     <qandaentry>
       <question id="troubleshooting-missing-plug-in">
         <para>
@@ -183,14 +156,14 @@ On my system there is no gst-register command.
 
       <answer>
         <para>
-GStreamer version 0.9 and higher does not need this anymore. The registry will
+GStreamer version 0.10 does not need this anymore. The registry will
-be rebuild automatically. If you suspect the registry is broken, just delete the
+be rebuilt automatically. If you suspect the registry is broken, just delete the
 <filename>registry.*.xml</filename> files under <filename>$HOME/.gstreamer-0.X/</filename>
 and run
 <programlisting>
   gst-inspect
 </programlisting>
-to rebuild the registry. You might need to do this as root again for the system-wide registry.
+to rebuild the registry.
         </para>
       </answer>
     </qandaentry>

docs/faq/using.xml

@@ -58,9 +58,10 @@ A (non-complete) list of output plug-ins for audio is
 <itemizedlist>
 <listitem><para>osssink for OSS output</para></listitem>
 <listitem><para>esdsink for ESound output</para></listitem>
-<listitem><para>artsdsink for aRTs output</para></listitem>
+<listitem><para>artsdsink for aRTs output (not ported to 0.10 yet)</para></listitem>
 <listitem><para>alsasink for ALSA output</para></listitem>
-<listitem><para>jacksink for JACK output</para></listitem>
+<listitem><para>alsaspdifsink for ALSA S/PDIF output</para></listitem>
+<listitem><para>jacksink for JACK output (not available yet)</para></listitem>
 </itemizedlist>
 First of all, run gst-inspect on the output plug-in you want to use to
 make sure you have it installed.  For example, if you use OSS, run
@@ -72,7 +73,7 @@ and see if that prints out a bunch of properties for the plug-in.
         <para>
 Then try to play the sine tone by running
 <programlisting>
-$ gst-launch audiotestsrc ! osssink
+$ gst-launch audiotestsrc ! audioconvert ! audioresample ! 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.