svn commit: r41494 - projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/multimedia

Dru Lavigne dru at FreeBSD.org
Wed Apr 24 22:34:33 UTC 2013


Author: dru
Date: Wed Apr 24 22:34:32 2013
New Revision: 41494
URL: http://svnweb.freebsd.org/changeset/doc/41494

Log:
  White space fix only. Translators can ignore.
  
  Approved by: gjb (mentor)

Modified:
  projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/multimedia/chapter.xml

Modified: projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/multimedia/chapter.xml
==============================================================================
--- projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/multimedia/chapter.xml	Wed Apr 24 21:47:19 2013	(r41493)
+++ projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/multimedia/chapter.xml	Wed Apr 24 22:34:32 2013	(r41494)
@@ -25,17 +25,16 @@
       to enjoy high fidelity output from a &os; system.  This includes
       the ability to record and playback audio in the MPEG Audio Layer
       3 (<acronym>MP3</acronym>), Waveform Audio File
-     (<acronym>WAV</acronym>), Ogg Vorbis, and other
-      formats.  The &os; Ports Collection contains many
-      applications for editing recorded audio, adding sound
-      effects, and controlling attached MIDI devices.</para>
+      (<acronym>WAV</acronym>), Ogg Vorbis, and other formats.  The
+      &os; Ports Collection contains many applications for editing
+      recorded audio, adding sound effects, and controlling attached
+      MIDI devices.</para>
 
     <para>&os; also supports the playback of video files and DVDs.
       The &os; Ports Collection contains applications to encode,
       convert, and playback various video media.</para>
 
-    <para>This chapter describes how to configure
-      sound cards, video
+    <para>This chapter describes how to configure sound cards, video
       playback, TV tuner cards, and scanners on &os;.  It also
       describes some of the applications which are available for
       using these devices.</para>
@@ -44,8 +43,7 @@
 
     <itemizedlist>
       <listitem>
-	<para>Configure a sound card
-	  on os;.</para>
+	<para>Configure a sound card on os;.</para>
       </listitem>
 
       <listitem>
@@ -140,65 +138,56 @@
 	<secondary>configuration</secondary>
       </indexterm>
 
-      <para>In order to use the sound device,
-the proper
-	device driver must be loaded.  This may be accomplished in
-one of two ways.
-	The easiest way is to load a kernel module for the
-	sound card with &man.kldload.8;.  This example loads the
-driver
-	for a Creative &soundblaster; Live! sound card:</para>
+      <para>In order to use the sound device, the proper device driver
+	must be loaded.  This may be accomplished in one of two ways.
+	The easiest way is to load a kernel module for the sound card
+	with &man.kldload.8;.  This example loads the driver for a
+	Creative &soundblaster; Live! sound card:</para>
 
     <screen>&prompt.root; <userinput>kldload snd_emu10k1</userinput></screen>
 
     <para>To automate the loading of this driver at boot time, add the
-      driver to
-      <filename>/boot/loader.conf</filename>. The line for
+      driver to <filename>/boot/loader.conf</filename>. The line for
       this driver is:</para>
 
     <programlisting>snd_emu10k1_load="YES"</programlisting>
 
     <para>Other available sound modules are listed in
-      <filename>/boot/defaults/loader.conf</filename>.
-      When unsure which driver to use, load
-      the <filename>snd_driver</filename> module:</para>
+      <filename>/boot/defaults/loader.conf</filename>.  When unsure
+      which driver to use, load the <filename>snd_driver</filename>
+      module:</para>
 
     <screen>&prompt.root; <userinput>kldload snd_driver</userinput></screen>
 
     <para>This is a metadriver which loads all of the most common
-sound drivers
-      and can be used to speed up the search for the correct driver.
-It
-      is also possible to load all sound drivers by adding the
-metadriver to
+      sound drivers and can be used to speed up the search for the
+      correct driver.  It is also possible to load all sound drivers
+      by adding the metadriver to
       <filename>/boot/loader.conf</filename>.</para>
 
-    <para>To determine which driver was selected for the
-      sound card after loading the <filename>snd_driver</filename>
-      metadriver, type <command>cat /dev/sndstat</command>.</para>
-
-    <para>Users who prefer to statically
-      compile in support for the sound card in a custom kernel should
-refer to the instructions in the next
-      section.  For more information about
-      recompiling a kernel, refer to <xref
-      linkend="kernelconfig"/>.</para>
+    <para>To determine which driver was selected for the sound card
+      after loading the <filename>snd_driver</filename> metadriver,
+      type <command>cat /dev/sndstat</command>.</para>
+
+    <para>Users who prefer to statically compile in support for the
+      sound card in a custom kernel should refer to the instructions
+      in the next section.  For more information about recompiling a
+      kernel, refer to <xref linkend="kernelconfig"/>.</para>
 
   <sect3>
     <title>Configuring a Custom Kernel with Sound Support</title>
 
     <para>When using a custom kernel to provide sound support, make
-	sure that the audio framework driver
-exists in the custom kernel configuration file:</para>
+      sure that the audio framework driver exists in the custom kernel
+      configuration file:</para>
 
     <programlisting>device sound</programlisting>
 
-    <para>Next, add support for the sound card.
-      Therefore, you need to know which driver supports the card.
-      To
-	continue the example of the Creative &soundblaster; Live!
-	sound card from the previous section, use the following line
-	in the custom kernel configuration file:</para>
+    <para>Next, add support for the sound card.  Therefore, you need
+      to know which driver supports the card.  To continue the example
+      of the Creative &soundblaster; Live! sound card from the
+      previous section, use the following line in the custom kernel
+      configuration file:</para>
 
       <programlisting>device snd_emu10k1</programlisting>
 
@@ -208,10 +197,10 @@ exists in the custom kernel configuratio
 	found in <filename>/usr/src/sys/conf/NOTES</filename>.</para>
 
       <para>Non-PnP ISA sound cards may require the IRQ and I/O port
-	settings of the card to be added
-to <filename>/boot/device.hints</filename>.  During the
-	boot process, &man.loader.8; reads this file and passes
-	the settings to the kernel.  For example, an old Creative
+	settings of the card to be added to
+	<filename>/boot/device.hints</filename>.  During the boot
+	process, &man.loader.8; reads this file and passes the
+	settings to the kernel.  For example, an old Creative
 	&soundblaster; 16 ISA non-PnP card will use the
 	&man.snd.sbc.4; driver in conjunction with
 	<literal>snd_sb16</literal>.  For this card, the following
@@ -235,13 +224,13 @@ hint.sbc.0.flags="0x15"</programlisting>
 
       <para>The syntax used in
 	<filename>/boot/device.hints</filename> is described in
-	&man.sound.4; and the manual page
-	for the driver of the sound card.</para>
+	&man.sound.4; and the manual page for the driver of the sound
+	card.</para>
 
       <para>The settings shown above are the defaults.  In some
 	cases, the IRQ or other settings may need to be changed to
-	match the card.  Refer to &man.snd.sbc.4; for more
-	information about this card.</para>
+	match the card.  Refer to &man.snd.sbc.4; for more information
+	about this card.</para>
     </sect3>
   </sect2>
 
@@ -251,14 +240,14 @@ hint.sbc.0.flags="0x15"</programlisting>
     <para>After rebooting into the custom kernel, or after loading
       the required module, the sound card should appear in the system
       message buffer.  Run &man.dmesg.8; and look for a message
-like:</para>
+	like:</para>
 
     <screen>pcm0: <Intel ICH3 (82801CA)> port 0xdc80-0xdcbf,0xd800-0xd8ff irq 5 at device 31.5 on pci0
 pcm0: [GIANT-LOCKED]
 pcm0: <Cirrus Logic CS4205 AC97 Codec></screen>
 
-    <para>The status of the sound card may also be checked
-using this command:</para>
+    <para>The status of the sound card may also be checked using this
+      command:</para>
 
     <screen>&prompt.root; <userinput>cat /dev/sndstat</userinput>
 FreeBSD Audio Driver (newpcm)
@@ -272,35 +261,31 @@ kld snd_ich (1p/2r/0v channels duplex de
       device driver was chosen.  Common problems are listed in <xref
 	linkend="troubleshooting"/>.</para>
 
-    <para>If all goes well, the sound
-      card should now work in os;.  If the CD-ROM or DVD-ROM drive's
-audio-out pins are
-      properly connected to the sound card, one can insert an audio CD
-in the
+    <para>If all goes well, the sound card should now work in os;.  If
+      the CD-ROM or DVD-ROM drive's audio-out pins are properly
+      connected to the sound card, one can insert an audio CD in the
       drive and play it with &man.cdcontrol.1;:</para>
 
       <screen>&prompt.user; <userinput>cdcontrol -f /dev/acd0 play 1</userinput></screen>
 
     <para>Various applications, such as <filename
-	role="package">audio/workman</filename> provide a
-      friendlier interface.  The <filename
-role="package">audio/mpg123</filename> port can be installed to
-      listen to MP3 audio files.</para>
+	role="package">audio/workman</filename> provide a friendlier
+      interface.  The <filename role="package">audio/mpg123</filename>
+      port can be installed to listen to MP3 audio files.</para>
 
-    <para>Another quick way to test the card is to send data
-      to <filename>/dev/dsp</filename>:</para>
+    <para>Another quick way to test the card is to send data to
+      <filename>/dev/dsp</filename>:</para>
 
     <screen>&prompt.user; <userinput>cat <replaceable>filename</replaceable> > /dev/dsp</userinput></screen>
 
     <para>where
       <filename><replaceable>filename</replaceable></filename> can
-      be any file.  This command should produce some noise,
-      confirming that the sound card is actually working.</para>
+      be any file.  This command should produce some noise, confirming
+      that the sound card is actually working.</para>
 
     <note>
       <para>The <devicename>/dev/dsp*</devicename> device nodes will
-be
-	created automatically as needed.  When not in use, they
+	be created automatically as needed.  When not in use, they
 	do not exist and will not appear in the output of
 	&man.ls.1;.</para>
     </note>
@@ -351,9 +336,8 @@ be
 	      <entry><errorname>xxx: can't open
 		  /dev/dsp!</errorname></entry>
 	      <entry><para>Check with <command>fstat | grep
-		  dsp</command>
-		if another application is holding the device open.
-		Noteworthy troublemakers are
+		  dsp</command> if another application is holding the
+		device open.  Noteworthy troublemakers are
 		<application>esound</application> and
 		<application>KDE</application>'s sound
 		support.</para></entry>
@@ -365,9 +349,9 @@ be
       <para>Another issue is that modern graphics cards often come
 	with their own sound driver, for use with
 	<acronym>HDMI</acronym> and similar.  This sound device will
-	sometimes be enumerated before the sound card and the
-	sound card will subsequently not be used as the default
-	playback device.  To check if this is the case, run
+	sometimes be enumerated before the sound card and the sound
+	card will subsequently not be used as the default playback
+	device.  To check if this is the case, run
 	<application>dmesg</application> and look for
 	<literal>pcm</literal>.  The output looks something like
 	this:</para>
@@ -393,16 +377,15 @@ pcm7: <HDA Realtek ALC889 PCM #3 Digi
       <para>Here the graphics card (<literal>NVidia</literal>) has
 	been enumerated before the sound card (<literal>Realtek
 	ALC889</literal>).  To use the sound card as the default
-playback
-	device, change <varname>hw.snd.default_unit</varname> to the
-	unit that should be used for playback:</para>
+	playback device, change <varname>hw.snd.default_unit</varname>
+	to the unit that should be used for playback:</para>
 
       <screen>&prompt.root; <userinput>sysctl hw.snd.default_unit=<replaceable>n</replaceable></userinput></screen>
 
       <para>Here, <literal>n</literal> is the number of the sound
 	device to use.  In this example, it should be
-<literal>4</literal>. 
-	Make this change permanent by adding the following line to
+	<literal>4</literal>.  Make this change permanent by adding
+	the following line to
 	<filename>/etc/sysctl.conf</filename>:</para>
 
       <programlisting>hw.snd.default_unit=<replaceable>4</replaceable></programlisting>
@@ -422,12 +405,10 @@ playback
     <title>Utilizing Multiple Sound Sources</title>
 
     <para>It is often desirable to have multiple sources of sound that
-      are able to play simultaneously.  &os; uses
-<emphasis>Virtual Sound
-	Channels</emphasis>, which can be enabled using
-      &man.sysctl.8;.  Virtual channels allow one to
-      multiplex the sound card's playback by mixing sound in the
-      kernel.</para>
+      are able to play simultaneously.  &os; uses <emphasis>Virtual
+	Sound Channels</emphasis>, which can be enabled using
+      &man.sysctl.8;.  Virtual channels allow one to multiplex the
+      sound card's playback by mixing sound in the kernel.</para>
 
     <para>To set the number of virtual channels, three
       &man.sysctl.8; knobs are available:</para>
@@ -448,20 +429,19 @@ playback
       <devicename>pcm</devicename> module can be loaded independently
       of the hardware drivers, <varname>hw.snd.maxautovchans</varname>
       indicates how many virtual channels will be given to devices
-when they are attached. Refer to &man.pcm.4;
-      for more information.</para>
+      when they are attached. Refer to &man.pcm.4; for more
+      information.</para>
 
     <note>
-      <para>The number of virtual channels for a
-	device cannot be changed while it is in use.  First, close any
-programs using
+      <para>The number of virtual channels for a device cannot be
+	changed while it is in use.  First, close any programs using
 	the device, such as music players or sound daemons.</para>
     </note>
 
     <para>
       The correct <devicename>pcm</devicename> device will
-      automatically be allocated transparently to a program
-      that requests <filename>/dev/dsp0</filename>.</para>
+      automatically be allocated transparently to a program that
+      requests <filename>/dev/dsp0</filename>.</para>
   </sect2>
 
   <sect2>
@@ -479,19 +459,19 @@ programs using
 
     <para>The default values for the different mixer channels are
       hardcoded in the source code of the &man.pcm.4; driver.  There
-      are many different applications and daemons that allow
-      values to be set for the mixer that are remembered between
-      invocations, but this is not a clean solution.  It is possible
-      to set default mixer values at the driver level.  This
-      is accomplished by defining the appropriate values in
+      are many different applications and daemons that allow values to
+      be set for the mixer that are remembered between invocations,
+      but this is not a clean solution.  It is possible to set default
+      mixer values at the driver level.  This is accomplished by
+      defining the appropriate values in
       <filename>/boot/device.hints</filename>, as seen in this
-example:</para>
+      example:</para>
 
     <programlisting>hint.pcm.0.vol="50"</programlisting>
 
     <para>This will set the volume channel to a default value of
       <literal>50</literal> when the &man.pcm.4; module is
-loaded.</para>
+      loaded.</para>
   </sect2>
 </sect1>
 
@@ -536,16 +516,15 @@ loaded.</para>
 
       <para>The <filename role="package">audio/mpg123</filename> port
 	provides an alternative, command-line <acronym>MP3</acronym>
-player.</para>
+	player.</para>
 
       <para><application>mpg123</application> can be run by specifying
 	the sound device and the <acronym>MP3</acronym> file on the
-command line.
-	Assuming the audio device is
+	command line.  Assuming the audio device is
 	<devicename>/dev/dsp1.0</devicename> and the
 	<acronym>MP3</acronym> file is
-<replaceable>Foobar-GreatestHits.mp3</replaceable>,
-	enter the following to play the file:</para>
+	<replaceable>Foobar-GreatestHits.mp3</replaceable>, enter the
+	following to play the file:</para>
 
       <screen>&prompt.root; <userinput>mpg123 -a <devicename>/dev/dsp1.0</devicename> <replaceable>Foobar-GreatestHits.mp3</replaceable></userinput>
 High Performance MPEG 1.0/2.0/2.5 Audio Player for Layer 1, 2 and 3.
@@ -565,23 +544,20 @@ MPEG 1.0 layer III, 128 kbit/s, 44100 Hz
       <title>Ripping CD Audio Tracks</title>
 
       <para>Before encoding a CD or CD track to
-<acronym>MP3</acronym>, the audio data on
-	the CD must be ripped to the hard drive.  This is done by
-	copying the raw CD
+	<acronym>MP3</acronym>, the audio data on the CD must be
+	ripped to the hard drive.  This is done by copying the raw CD
 	Digital Audio (<acronym>CDDA</acronym>) data to
-<acronym>WAV</acronym>
-	files.</para>
+	<acronym>WAV</acronym> files.</para>
 
       <para>The <command>cdda2wav</command> tool, which is installed
-with
-	the <filename role="package">sysutils/cdrtools</filename>
+	with the <filename role="package">sysutils/cdrtools</filename>
 	suite, is used for ripping audio information from CDs and the
 	information associated with them.</para>
 
       <para>With the audio CD in the drive, the following command can
 	be issued as <username>root</username> to rip an entire CD
 	into individual (per track) <acronym>WAV</acronym>
-files:</para>
+	files:</para>
 
       <screen>&prompt.root; <userinput>cdda2wav -D <replaceable>0,1,0</replaceable> -B</userinput></screen>
 
@@ -590,10 +566,10 @@ files:</para>
 	which corresponds to the output of <command>cdrecord
 	  -scanbus</command>.</para>
 
-      <para><application>cdda2wav</application> will support
-	ATAPI (IDE) CDROM drives.  To rip from an IDE drive, specify
-	the device name in place of the SCSI unit numbers.  For
-	example, to rip track 7 from an IDE drive:</para>
+      <para><application>cdda2wav</application> will support ATAPI
+	(IDE) CDROM drives.  To rip from an IDE drive, specify the
+	device name in place of the SCSI unit numbers.  For example,
+	to rip track 7 from an IDE drive:</para>
 
       <screen>&prompt.root; <userinput>cdda2wav -D <replaceable>/dev/acd0</replaceable> -t 7</userinput></screen>
 
@@ -608,8 +584,8 @@ files:</para>
 
       <screen>&prompt.root; <userinput>cdda2wav -D <replaceable>0,1,0</replaceable> -t 1+7</userinput></screen>
 
-      <para>&man.dd.1; can also be used to extract audio
-	tracks on ATAPI drives, as described in <xref
+      <para>&man.dd.1; can also be used to extract audio tracks on
+	ATAPI drives, as described in <xref
 	  linkend="duplicating-audiocds"/>.</para>
 
     </sect2>
@@ -619,12 +595,11 @@ files:</para>
 
       <para>
 	<application>Lame</application> is a popular
-<acronym>MP3</acronym> encoder which can be installed from the
+	<acronym>MP3</acronym> encoder which can be installed from the
 	<filename role="package">audio/lame</filename> port.  Due to
 	licensing restrictions, a package is not available.</para>
 
-      <para>The following command will
-	convert the ripped
+      <para>The following command will convert the ripped
 	<acronym>WAV</acronym> files
 	<filename><replaceable>audio01.wav</replaceable></filename>
 	to
@@ -640,29 +615,26 @@ files:</para>
 <replaceable>audio01.wav audio01.mp3</replaceable></userinput></screen>
 
       <para>128 kbits is a standard <acronym>MP3</acronym>
-bitrate.  The 160 and 192 bitrates provide higher quality.  The higher
-	the bitrate, the larger the size of the resulting
-	<acronym>MP3</acronym>.
-	<option>-h</option> turns on the <quote>higher quality
-	but a little slower</quote> mode.  The options beginning with
-	<option>--t</option> indicate ID3 tags, which usually contain
-	song information, to be embedded within the
-<acronym>MP3</acronym> file.
-	Additional encoding options can be found in the
-	<application>lame</application> manual page.</para>
+	bitrate.  The 160 and 192 bitrates provide higher quality.
+	The higher the bitrate, the larger the size of the resulting
+	<acronym>MP3</acronym>.  <option>-h</option> turns on the
+	<quote>higher quality but a little slower</quote> mode.  The
+	options beginning with <option>--t</option> indicate ID3 tags,
+	which usually contain song information, to be embedded within
+	the <acronym>MP3</acronym> file.  Additional encoding options
+	can be found in the <application>lame</application> manual
+	page.</para>
     </sect2>
 
     <sect2 id="mp3-decoding">
       <title>Decoding MP3s</title>
 
       <para>In order to burn an audio CD from <acronym>MP3</acronym>s,
-they must first be
-	converted to a non-compressed <acronym>WAV</acronym> format.
-Both
+	they must first be converted to a non-compressed
+	<acronym>WAV</acronym> format.  Both
 	<application>XMMS</application> and
 	<application>mpg123</application> support the output of
-<acronym>MP3</acronym>
-	to an uncompressed file format.</para>
+	<acronym>MP3</acronym> to an uncompressed file format.</para>
 
       <para>Writing to Disk in <application>XMMS</application>:</para>
 
@@ -697,25 +669,22 @@ Both
 
 	<step>
 	  <para>Load the <acronym>MP3</acronym> file into
-<application>XMMS</application>
-	    as usual, with volume at 100% and EQ settings turned
-	    off.</para>
+	    <application>XMMS</application> as usual, with volume at
+	    100% and EQ settings turned off.</para>
 	</step>
 
 	<step>
 	  <para>Press <literal>Play</literal>.  The
 	    <application>XMMS</application> will appear as if it is
 	    playing the <acronym>MP3</acronym>, but no music will be
-heard.  It is
-	    actually playing the <acronym>MP3</acronym> to a
-file.</para>
+	    heard.  It is actually playing the <acronym>MP3</acronym>
+	    to a file.</para>
 	</step>
 
 	<step>
 	  <para>When finished, be sure to set the default Output
-Plugin back to what
-	    it was before in order to listen to
-<acronym>MP3</acronym>s again.</para>
+	    Plugin back to what it was before in order to listen to
+	    <acronym>MP3</acronym>s again.</para>
 	</step>
       </procedure>
 
@@ -731,27 +700,23 @@ Plugin back to what
       </procedure>
 
       <para><application>XMMS</application> writes a file in the
-<acronym>WAV</acronym>
-	format, while <application>mpg123</application> converts the
+	<acronym>WAV</acronym> format, while
+	<application>mpg123</application> converts the
 	<acronym>MP3</acronym> into raw PCM audio data.  Both of these
-formats can be
-	used with <application>cdrecord</application> to create audio
-	CDs, whereas &man.burncd.8; requires a raw Pulse-Code
-Modulation (<acronym>PCM</acronym>.  When using
+	formats can be used with <application>cdrecord</application>
+	to create audio CDs, whereas &man.burncd.8; requires a raw
+	Pulse-Code Modulation (<acronym>PCM</acronym>.  When using
 	<acronym>WAV</acronym> files, there will be a small tick
-sound at the
-	beginning of each track.  This sound is the header of the
-<acronym>WAV</acronym>
-	file.  One can remove the header with
-	<application>SoX</application>, which can be
+	sound at the beginning of each track.  This sound is the
+	header of the <acronym>WAV</acronym> file.  One can remove the
+	header with <application>SoX</application>, which can be
 	installed from the <filename
 	  role="package">audio/sox</filename> port or package:</para>
 
       <screen>&prompt.user; <userinput>sox -t wav -r 44100 -s -w -c 2 <replaceable>track.wav track.raw</replaceable></userinput></screen>
 
       <para>Refer to <xref linkend="creating-cds"/> for more
-information
-	on using a CD burner in &os;.</para>
+	information on using a CD burner in &os;.</para>
     </sect2>
   </sect1>
 
@@ -770,44 +735,39 @@ information
     <title>Video Playback</title>
 
     <para>Before configuring video playback, determine the model
-of the video
-      card and the chip it uses.  While
+      of the video card and the chip it uses.  While
       <application>&xorg;</application> supports a wide variety of
       video cards, fewer give good playback performance.  To obtain
       a list of extensions supported by the
-<application>&xorg;</application> server using the card, run
+      <application>&xorg;</application> server using the card, run
       &man.xdpyinfo.1; while <application>&xorg;</application> is
-running.</para>
+      running.</para>
 
     <para>It is a good idea to have a short MPEG test file for
-evaluating various players and
-      options.  Since some DVD applications look for DVD media in
-      <filename class="directory">/dev/dvd</filename> by default, or
-have this device
-      name hardcoded in them, it might be useful to make
+      evaluating various players and options.  Since some DVD
+      applications look for DVD media in <filename
+	class="directory">/dev/dvd</filename> by default, or have this
+      device name hardcoded in them, it might be useful to make
       symbolic links to the proper devices:</para>
 
     <screen>&prompt.root; <userinput>ln -sf /dev/acd0 /dev/dvd</userinput>
 &prompt.root; <userinput>ln -sf /dev/acd0 /dev/rdvd</userinput></screen>
 
-    <para>Due to the nature of &man.devfs.5;,
-      manually created links will not persist after a system reboot.
-      In order to create the symbolic links
-      automatically when the system boots, add the following
-      lines to <filename>/etc/devfs.conf</filename>:</para>
+    <para>Due to the nature of &man.devfs.5;, manually created links
+      will not persist after a system reboot.  In order to create the
+      symbolic links automatically when the system boots, add the
+      following lines to <filename>/etc/devfs.conf</filename>:</para>
 
     <programlisting>link acd0 dvd
 link acd0 rdvd</programlisting>
 
-    <para>DVD decryption invokes
-      special DVD-ROM functions and requires write permission on the
-DVD
-      devices.</para>
+    <para>DVD decryption invokes special DVD-ROM functions and
+      requires write permission on the DVD devices.</para>
 
     <para>To enhance the shared memory
-<application>&xorg;</application> interface, it is
+      <application>&xorg;</application> interface, it is
       recommended to increase the values of these &man.sysctl.8;
-variables:</para>
+      variables:</para>
 
     <programlisting>kern.ipc.shmmax=67108864
 kern.ipc.shmall=32768</programlisting>
@@ -820,33 +780,32 @@ kern.ipc.shmall=32768</programlisting>
     <indexterm><primary>DGA</primary></indexterm>
 
     <para>There are several possible ways to display video under
-<application>&xorg;</application>.
-      What works is largely hardware dependent.  Each
-      method described below will have varying quality across
-      different hardware.</para>
+      <application>&xorg;</application>.  What works is largely
+      hardware dependent.  Each method described below will have
+      varying quality across different hardware.</para>
 
     <para>Common video interfaces include:</para>
 
     <orderedlist>
       <listitem>
-	<para><application>&xorg;</application>: normal output
-using shared memory.</para>
+	<para><application>&xorg;</application>: normal output using
+	  shared memory.</para>
       </listitem>
 
       <listitem>
 	<para>XVideo: an extension to the
-<application>&xorg;</application> interface which supports
+	  <application>&xorg;</application> interface which supports
 	  video in any drawable object.</para>
       </listitem>
 
       <listitem>
 	<para><acronym>SDL</acronym>: the Simple Directmedia
-Layer.</para>
+	  Layer.</para>
       </listitem>
 
       <listitem>
 	<para><acronym>DGA</acronym>: the Direct Graphics
-Access.</para>
+	  Access.</para>
       </listitem>
 
       <listitem>
@@ -858,9 +817,8 @@ Access.</para>
       <title>XVideo</title>
 
       <para><application>&xorg;</application> has an extension called
-	<emphasis>XVideo</emphasis>, also known as Xvideo,
-Xv, and xv.  It
-	allows video to be directly displayed in drawable objects
+	<emphasis>XVideo</emphasis>, also known as Xvideo, Xv, and xv.
+	It allows video to be directly displayed in drawable objects
 	through a special acceleration.  This extension provides
 	good quality playback even on low-end machines.</para>
 
@@ -941,9 +899,9 @@ Xv, and xv.  It
         depth: 1
         red, green, blue masks: 0x0, 0x0, 0x0</screen>
 
-    <para>The formats listed, such as YUV2 and YUV12, are
-      not present with every implementation of XVideo and their
-      absence may hinder some players.</para>
+    <para>The formats listed, such as YUV2 and YUV12, are not present
+      with every implementation of XVideo and their absence may hinder
+      some players.</para>
 
     <para>If the result looks like:</para>
 
@@ -951,26 +909,24 @@ Xv, and xv.  It
 screen #0
 no adaptors present</screen>
 
-    <para>XVideo is probably not supported for the card.  This
-means
+    <para>XVideo is probably not supported for the card.  This means
       that it will be more difficult for the display to meet the
       computational demands of rendering video.  Depending on the
-      video card and processor, one might still be able to
-      have a satisfying experience.</para>
+      video card and processor, one might still be able to have a
+      satisfying experience.</para>
 
   </sect3>
 
   <sect3 id="video-interface-SDL">
     <title>Simple Directmedia Layer</title>
 
-    <para><acronym>SDL</acronym> is intended to be a
-      porting layer between &microsoft.windows; and &unix;,
-      allowing cross-platform applications to be developed which make
-      efficient use of sound and graphics.  The <acronym>SDL</acronym>
-layer provides a
+    <para><acronym>SDL</acronym> is intended to be a porting layer
+      between &microsoft.windows; and &unix;, allowing cross-platform
+      applications to be developed which make efficient use of sound
+      and graphics.  The <acronym>SDL</acronym> layer provides a
       low-level abstraction to the hardware which can sometimes be
       more efficient than the <application>&xorg;</application>
-interface.</para>
+      interface.</para>
 
     <para><acronym>SDL</acronym> can be installed using the <filename
 	role="package">devel/sdl12</filename> package or port.</para>
@@ -981,18 +937,16 @@ interface.</para>
     <title>Direct Graphics Access</title>
 
     <para><acronym>DGA</acronym> is an
-<application>&xorg;</application> extension which allows
-      a program to bypass the <application>&xorg;</application> server
-and directly alter the
-      framebuffer.  Because it relies on a low level memory mapping,
-programs using it must be run as
+      <application>&xorg;</application> extension which allows a
+      program to bypass the <application>&xorg;</application> server
+      and directly alter the framebuffer.  Because it relies on a low
+      level memory mapping, programs using it must be run as
       <username>root</username>.</para>
 
     <para>The <acronym>DGA</acronym> extension can be tested and
-benchmarked using
-      &man.dga.1;.  When <command>dga</command> is running, it
-      changes the colors of the display whenever a key is pressed.  To
-      quit, press <keycap>q</keycap>.</para>
+      benchmarked using &man.dga.1;.  When <command>dga</command> is
+      running, it changes the colors of the display whenever a key is
+      pressed.  To quit, press <keycap>q</keycap>.</para>
 
   </sect3>
 </sect2>
@@ -1004,15 +958,13 @@ benchmarked using
     <indexterm><primary>video packages</primary></indexterm>
 
     <para>This section introduces some of the software available from
-the
-      &os; Ports Collection which can be used for video
-playback.</para>
-
-    <para>Many of the video
-      applications which run on &os; were developed as &linux;
-      applications.  Many of these applications are still
-      beta-quality.  Some of the problems commonly encountered with
-      video packages on &os; include:</para>
+      the &os; Ports Collection which can be used for video
+      playback.</para>
+
+    <para>Many of the video applications which run on &os; were
+      developed as &linux; applications.  Many of these applications
+      are still beta-quality.  Some of the problems commonly
+      encountered with video packages on &os; include:</para>
 
     <orderedlist>
 
@@ -1052,13 +1004,12 @@ playback.</para>
     </orderedlist>
 
     <para>Many applications may also exhibit
-      <quote>&linux;-isms</quote>.  There may be issues
-      resulting from the way some standard libraries are
-      implemented in the &linux; distributions, or some features of
-      the &linux; kernel which have been assumed by the authors of the
-      applications.  These issues are not always noticed and worked
-      around by the port maintainers, which can lead to problems like
-      these:</para>
+      <quote>&linux;-isms</quote>.  There may be issues resulting from
+      the way some standard libraries are implemented in the &linux;
+      distributions, or some features of the &linux; kernel which have
+      been assumed by the authors of the applications.  These issues
+      are not always noticed and worked around by the port
+      maintainers, which can lead to problems like these:</para>
 
     <orderedlist>
       <listitem>
@@ -1073,7 +1024,7 @@ playback.</para>
 
       <listitem>
 	<para>Relies on software which is not yet available in the
-&os; Ports Collection.</para>
+	  &os; Ports Collection.</para>
       </listitem>
     </orderedlist>
 
@@ -1093,21 +1044,20 @@ playback.</para>
 	  <secondary>making</secondary></indexterm>
 
 	<para><application>MPlayer</application> is available as a
-package or port in <filename
-	    role="package">multimedia/mplayer</filename>.
-Several compile options are available and a variety of hardware
+	  package or port in <filename
+	    role="package">multimedia/mplayer</filename>.  Several
+	  compile options are available and a variety of hardware
 	  checks occur during the build process.  For these reasons,
 	  some users prefer to build the port rather than install the
-	  package.  The available options will be displayed in
-	  a menu after these commands are input:</para>
+	  package.  The available options will be displayed in a
+	  menu after these commands are input:</para>
 
 	<screen>&prompt.root; <userinput>cd /usr/ports/multimedia/mplayer</userinput>
 &prompt.root; <userinput>make</userinput></screen>
 
 	<para>The menu options should be reviewed to determine the
-type of
-	  support to compile into the port.  If an option is not
-	  selected, <application>MPlayer</application> will not be
+	  type of support to compile into the port.  If an option is
+	  not selected, <application>MPlayer</application> will not be
 	  able to display that type of video format.  Use the arrow
 	  keys and spacebar to select the required formats.  When
 	  finished, press <keycap>Enter</keycap> to continue the port
@@ -1175,8 +1125,8 @@ type of
 	    including the
 	    <makevar>WITH_DVD_DEVICE=/path/to/desired/device</makevar>
 	    option.  By default, the device is
-	    <filename>/dev/acd0</filename>.  More
-	    details can be found in the port's
+	    <filename>/dev/acd0</filename>.  More details can be found
+	    in the port's
 	    <filename>Makefile.options</filename>.</para>
 	</note>
 
@@ -1185,21 +1135,20 @@ type of
 	    -h</command>, or read the manual page.</para>
 
 	<para>Additional playback options include
-	  <option>-fs -zoom</option>, which engages fullscreen
-mode,
+	  <option>-fs -zoom</option>, which engages fullscreen mode,
 	  and <option>-framedrop</option>, which helps
 	  performance.</para>
 
 	<para>Each user can add commonly used options to their
 	  <filename>~/.mplayer/config</filename> like so:</para>
-	  
+
 	<programlisting>vo=xv
 fs=yes
 zoom=yes</programlisting>
 
-	<para><command>mplayer</command> can be used to rip a
-	  DVD title to a <filename>.vob</filename>.  To dump
-	  the second title from a DVD:</para>
+	<para><command>mplayer</command> can be used to rip a DVD
+	  title to a <filename>.vob</filename>.  To dump the second
+	  title from a DVD:</para>
 
 	  <screen>&prompt.root; <userinput>mplayer -dumpstream -dumpfile out.vob dvd://2 -dvd-device /dev/dvd</userinput></screen>
 
@@ -1226,13 +1175,12 @@ zoom=yes</programlisting>
 
 	<para>Before using <command>mencoder</command>, it is a good
 	  idea to become familiar with the options described in the
-<ulink
-url="http://www.mplayerhq.hu/DOCS/HTML/en/mencoder.html">HTML
-	  documentation</ulink>.  There are
-	  innumerable ways to improve quality, lower bitrate, and
-	  change formats, and some of these options may make the
-	  difference between good or bad performance.  Improper
-combinations of command line options
+	  <ulink
+	    url="http://www.mplayerhq.hu/DOCS/HTML/en/mencoder.html">HTML
+	  documentation</ulink>.  There are innumerable ways to
+	  improve quality, lower bitrate, and change formats, and some
+	  of these options may make the difference between good or bad
+	  performance.  Improper combinations of command line options
 	  can yield output files that are unplayable even by
 	  <command>mplayer</command>.</para>
 
@@ -1240,8 +1188,7 @@ combinations of command line options
 
 	 <screen>&prompt.user; <userinput>mencoder <replaceable>input.avi</replaceable> -oac copy -ovc copy -o <replaceable>output.avi</replaceable></userinput></screen>
 
-	<para>To rip
-	  to a file, use <option>-dumpfile</option> with
+	<para>To rip to a file, use <option>-dumpfile</option> with
 	  <command>mplayer</command>.</para>
 
 	<para>To convert
@@ -1255,17 +1202,15 @@ combinations of command line options
 	 -ovc lavc -lavcopts vcodec=mpeg4:vhq -o <replaceable>output.avi</replaceable></userinput></screen>
 
 	<para>This will produce output playable by applications such
-as
-	  <command>mplayer</command> and
+	  as <command>mplayer</command> and
 	  <command>xine</command>.</para>
 
 	<para><filename><replaceable>input.avi</replaceable></filename>
 	  can be replaced with <option>dvd://1 -dvd-device
 	    /dev/dvd</option> and run as <username>root</username>
 	  to re-encode a DVD title directly.  Since it may take a few
-tries to get the desired result,
-	  it is recommended to dump the title to a file and to work on
-	  the file.</para>
+	  tries to get the desired result, it is recommended to dump
+	  the title to a file and to work on the file.</para>
       </sect4>
 
     </sect3>
@@ -1274,20 +1219,19 @@ tries to get the desired result,
       <title>The <application>xine</application> Video Player</title>
 
       <para><application>xine</application> is a video player with a
-reusable base library
-	and a modular executable which can be extended with plugins.
-	It can be installed using the <filename
-	  role="package">multimedia/xine</filename> package or
-port.</para>
-
-      <para>In practice, <application>xine</application>
-	requires either a fast CPU with a fast video card, or support
-	for the XVideo extension.  The <application>xine</application>
-	video player performs best on XVideo interfaces.</para>
+	reusable base library and a modular executable which can be
+	extended with plugins.  It can be installed using the
+	<filename role="package">multimedia/xine</filename> package or
+	port.</para>
+
+      <para>In practice, <application>xine</application> requires
+	either a fast CPU with a fast video card, or support for the
+	XVideo extension.  The <application>xine</application> video
+	player performs best on XVideo interfaces.</para>
 
       <para>By default, the <application>xine</application> player
-	starts a graphical user interface.  The menus can then
-	be used to open a specific file.</para>
+	starts a graphical user interface.  The menus can then be used
+	to open a specific file.</para>
 
       <para>Alternatively, <application>xine</application> may be
 	invoked to play a file immediately without the graphical
@@ -1301,21 +1245,21 @@ port.</para>
       <screen>&prompt.user; <userinput>xine -g -p <replaceable>mymovie.avi</replaceable></userinput></screen>
 
       <para>The <ulink
-url="http://dvd.sourceforge.net/xine-howto/en_GB/html/howto.html">
+	  url="http://dvd.sourceforge.net/xine-howto/en_GB/html/howto.html">
 	xine HOWTO</ulink> contains a chapter on performance
 	improvement which is general to all players.</para>
     </sect3>
 
     <sect3 id="video-ports-transcode">
       <title>The <application>transcode</application>
-Utilities</title>
+	Utilities</title>
 
       <para><application>transcode</application> provides a suite of
-tools for re-encoding video and audio
-	files.  <application>transcode</application> can be used
-	to merge video files or repair broken files using
-	command line tools with <filename>stdin/stdout</filename>
-	stream interfaces.</para>
+	tools for re-encoding video and audio files.
+	<application>transcode</application> can be used to merge
+	video files or repair broken files using command line tools
+	with <filename>stdin/stdout</filename> stream
+	interfaces.</para>
 
       <para><application>transcode</application> can be installed
 	using the <filename
@@ -1329,7 +1273,7 @@ tools for re-encoding video and audio
 	<keycap>Enter</keycap> to continue the port compile and
 	installation.</para>
 
-    <para>This example demonstrates how to convert a DivX file into
+      <para>This example demonstrates how to convert a DivX file into
 	a PAL MPEG-1 file (PAL VCD):</para>
 
     <screen>&prompt.user; <userinput>transcode -i
@@ -1339,15 +1283,13 @@ tools for re-encoding video and audio
     <para>The resulting MPEG file,
       <filename><replaceable>output_vcd.mpg</replaceable></filename>,
       is ready to be played with <application>MPlayer</application>.
-      The file can be burned on a CD-R media to create a
-Video
-      CD.  In this, install and use the
-<filename
+      The file can be burned on a CD-R media to create a Video CD.  In
+      this, install and use the <filename
 	role="package">multimedia/vcdimager</filename> and <filename
 	role="package">sysutils/cdrdao</filename> programs.</para>
 
     <para>In addition to the manual page for
-<command>transcode</command>, refer to the <ulink
+      <command>transcode</command>, refer to the <ulink
 	url="http://www.transcoding.org/cgi-bin/transcode">transcode
 	wiki</ulink> for further information and examples.</para>
   </sect3>
@@ -1383,34 +1325,29 @@ Video
     <title>Introduction</title>
 
     <para>TV cards allow can be used to watch broadcast or cable TV on
-a
-      computer.  Most cards accept composite video via an RCA or
-      S-video input and some cards include a FM radio
-      tuner.</para>

*** DIFF OUTPUT TRUNCATED AT 1000 LINES ***


More information about the svn-doc-projects mailing list