aboutsummaryrefslogtreecommitdiff
path: root/en_US.ISO8859-1/books/handbook/multimedia/chapter.xml
diff options
context:
space:
mode:
authorGabor Kovesdan <gabor@FreeBSD.org>2013-11-07 15:39:28 +0000
committerGabor Kovesdan <gabor@FreeBSD.org>2013-11-07 15:39:28 +0000
commit24d129e8d1984a0b46a543bc523b63d216813bb0 (patch)
tree7dd0501c857c6f2139f4a71191c93bf19136412a /en_US.ISO8859-1/books/handbook/multimedia/chapter.xml
parent35f1d6c78be90eb13320d655cd68f94333a0ab26 (diff)
downloaddoc-24d129e8d1984a0b46a543bc523b63d216813bb0.tar.gz
doc-24d129e8d1984a0b46a543bc523b63d216813bb0.zip
- Definitively upgrade to DocBook 5.0
Notes
Notes: svn path=/projects/db5/; revision=43125
Diffstat (limited to 'en_US.ISO8859-1/books/handbook/multimedia/chapter.xml')
-rw-r--r--en_US.ISO8859-1/books/handbook/multimedia/chapter.xml287
1 files changed, 127 insertions, 160 deletions
diff --git a/en_US.ISO8859-1/books/handbook/multimedia/chapter.xml b/en_US.ISO8859-1/books/handbook/multimedia/chapter.xml
index bdcac98391..fc1b285374 100644
--- a/en_US.ISO8859-1/books/handbook/multimedia/chapter.xml
+++ b/en_US.ISO8859-1/books/handbook/multimedia/chapter.xml
@@ -4,8 +4,7 @@
$FreeBSD$
-->
-
-<chapter id="multimedia">
+<chapter xmlns="http://docbook.org/ns/docbook" xmlns:xlink="http://www.w3.org/1999/xlink" version="5.0" xml:id="multimedia">
<!--
<chapterinfo>
<authorgroup>
@@ -20,7 +19,7 @@
<title>Multimedia</title>
- <sect1 id="multimedia-synopsis">
+ <sect1 xml:id="multimedia-synopsis">
<title>Synopsis</title>
<para>&os; supports a wide variety of sound cards, allowing users
@@ -92,7 +91,7 @@
</itemizedlist>
</sect1>
- <sect1 id="sound-setup">
+ <sect1 xml:id="sound-setup">
<!--
<sect1info>
<authorgroup>
@@ -119,8 +118,8 @@
<para>Before beginning the configuration, determine the model of
the sound card and the chip it uses. &os; supports a wide
variety of sound cards. Check the supported audio devices
- list of the <ulink url="&rel.current.hardware;">Hardware
- Notes</ulink> to see if the card is supported and which &os;
+ list of the <link xlink:href="&rel.current.hardware;">Hardware
+ Notes</link> to see if the card is supported and which &os;
driver it uses.</para>
<indexterm>
@@ -164,8 +163,7 @@
<para>This section is for users who prefer to statically compile
in support for the sound card in a custom kernel. For more
- information about recompiling a kernel, refer to <xref
- linkend="kernelconfig"/>.</para>
+ information about recompiling a kernel, refer to <xref linkend="kernelconfig"/>.</para>
<para>When using a custom kernel to provide sound support, make
sure that the audio framework driver exists in the custom
@@ -220,7 +218,7 @@ hint.sbc.0.flags="0x15"</programlisting>
about this card.</para>
</sect2>
- <sect2 id="sound-testing">
+ <sect2 xml:id="sound-testing">
<title>Testing Sound</title>
<para>After loading the required module or rebooting into the
@@ -243,7 +241,7 @@ pcm1: &lt;NVIDIA (0x001c) (HDMI/DP 8ch)&gt; (play)
pcm2: &lt;Conexant CX20590 (Analog 2.0+HP/2.0)&gt; (play/rec) default</screen>
<para>The output will vary depending upon the sound card. If no
- <devicename>pcm</devicename> devices are listed, double-check
+ <filename>pcm</filename> devices are listed, double-check
that the correct device driver was loaded or compiled into the
kernel. The next section lists some common problems and their
solutions.</para>
@@ -261,31 +259,29 @@ pcm2: &lt;Conexant CX20590 (Analog 2.0+HP/2.0)&gt; (play/rec) default</screen>
they should not be mounted using &man.mount.8;.</para>
</warning>
- <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
+ <para>Various applications, such as <package>audio/workman</package>, provide a
+ friendlier interface. The <package>audio/mpg123</package> port can be installed
to listen to MP3 audio files.</para>
<para>Another quick way to test the card is to send data to
- <devicename>/dev/dsp</devicename>:</para>
+ <filename>/dev/dsp</filename>:</para>
- <screen>&prompt.user; <userinput>cat <replaceable>filename</replaceable> &gt; /dev/dsp</userinput></screen>
+ <screen>&prompt.user; <userinput>cat filename &gt; /dev/dsp</userinput></screen>
<para>where
- <filename><replaceable>filename</replaceable></filename> can
+ <filename>filename</filename> can
be any type of file. This command should produce some noise,
confirming that the sound card is working.</para>
<note>
- <para>The <devicename>/dev/dsp*</devicename> device nodes will
+ <para>The <filename>/dev/dsp*</filename> device nodes will
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>
</sect2>
- <sect2 id="troubleshooting">
+ <sect2 xml:id="troubleshooting">
<title>Troubleshooting Sound</title>
<indexterm><primary>device nodes</primary></indexterm>
@@ -377,7 +373,7 @@ pcm7: &lt;HDA Realtek ALC889 PCM #3 Digital&gt; at cad 2 nid 1 on hdac1
<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>
+ <screen>&prompt.root; <userinput>sysctl hw.snd.default_unit=n</userinput></screen>
<para>where <literal>n</literal> is the number of the sound
device to use. In this example, it should be
@@ -388,7 +384,7 @@ pcm7: &lt;HDA Realtek ALC889 PCM #3 Digital&gt; at cad 2 nid 1 on hdac1
<programlisting>hw.snd.default_unit=<replaceable>4</replaceable></programlisting>
</sect2>
- <sect2 id="sound-multiple-sources">
+ <sect2 xml:id="sound-multiple-sources">
<!--
<sect2info>
<authorgroup>
@@ -419,8 +415,8 @@ pcm7: &lt;HDA Realtek ALC889 PCM #3 Digital&gt; at cad 2 nid 1 on hdac1
<varname>dev.pcm.0.play.vchans=4</varname> and
<varname>dev.pcm.0.rec.vchans=4</varname> are configurable after
a device has been attached and represent the number of virtual
- channels <devicename>pcm0</devicename> has for playback and
- recording. Since the <devicename>pcm</devicename> module can be
+ channels <filename>pcm0</filename> has for playback and
+ recording. Since the <filename>pcm</filename> module can be
loaded independently of the hardware drivers,
<varname>hw.snd.maxautovchans</varname> indicates how many
virtual channels will be given to an audio device when it is
@@ -433,7 +429,7 @@ pcm7: &lt;HDA Realtek ALC889 PCM #3 Digital&gt; at cad 2 nid 1 on hdac1
</note>
<para>
- The correct <devicename>pcm</devicename> device will
+ The correct <filename>pcm</filename> device will
automatically be allocated transparently to a program that
requests <filename>/dev/dsp0</filename>.</para>
</sect2>
@@ -470,7 +466,7 @@ pcm7: &lt;HDA Realtek ALC889 PCM #3 Digital&gt; at cad 2 nid 1 on hdac1
</sect2>
</sect1>
-<sect1 id="sound-mp3">
+<sect1 xml:id="sound-mp3">
<!--
<sect1info>
<authorgroup>
@@ -489,7 +485,7 @@ pcm7: &lt;HDA Realtek ALC889 PCM #3 Digital&gt; at cad 2 nid 1 on hdac1
players available for &os;, how to rip audio CD tracks, and
how to encode and decode <acronym>MP3</acronym>s.</para>
- <sect2 id="mp3-players">
+ <sect2 xml:id="mp3-players">
<title>MP3 Players</title>
<para>A popular graphical <acronym>MP3</acronym> player is
@@ -502,7 +498,7 @@ pcm7: &lt;HDA Realtek ALC889 PCM #3 Digital&gt; at cad 2 nid 1 on hdac1
support.</para>
<para><application>XMMS</application> can be installed from
- the <filename role="package">multimedia/xmms</filename> port
+ the <package>multimedia/xmms</package> port
or package.</para>
<para><application>XMMS</application>'s interface is intuitive,
@@ -510,19 +506,19 @@ pcm7: &lt;HDA Realtek ALC889 PCM #3 Digital&gt; at cad 2 nid 1 on hdac1
with <application>Winamp</application> will find
<application>XMMS</application> simple to use.</para>
- <para>The <filename role="package">audio/mpg123</filename> port
+ <para>The <package>audio/mpg123</package> port
provides an alternative, command-line <acronym>MP3</acronym>
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
- <devicename>/dev/dsp1.0</devicename> and the
+ <filename>/dev/dsp1.0</filename> and the
<acronym>MP3</acronym> file is
<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>
+ <screen>&prompt.root; <userinput>mpg123 -a /dev/dsp1.0 Foobar-GreatestHits.mp3</userinput>
High Performance MPEG 1.0/2.0/2.5 Audio Player for Layer 1, 2 and 3.
Version 0.59r (1999/Jun/15). Written and copyrights by Michael Hipp.
Uses code from various people. See 'README' for more!
@@ -536,7 +532,7 @@ Playing MPEG stream from Foobar-GreatestHits.mp3 ...
MPEG 1.0 layer III, 128 kbit/s, 44100 Hz joint-stereo</screen>
</sect2>
- <sect2 id="rip-cd">
+ <sect2 xml:id="rip-cd">
<title>Ripping CD Audio Tracks</title>
<para>Before encoding a CD or CD track to
@@ -546,19 +542,19 @@ MPEG 1.0 layer III, 128 kbit/s, 44100 Hz joint-stereo</screen>
<acronym>WAV</acronym> files.</para>
<para>The <command>cdda2wav</command> tool, which is installed
- with the <filename role="package">sysutils/cdrtools</filename>
+ with the <package>sysutils/cdrtools</package>
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
+ be issued as <systemitem class="username">root</systemitem> to rip an entire CD
into individual (per track) <acronym>WAV</acronym>
files:</para>
- <screen>&prompt.root; <userinput>cdda2wav -D <replaceable>0,1,0</replaceable> -B</userinput></screen>
+ <screen>&prompt.root; <userinput>cdda2wav -D 0,1,0 -B</userinput></screen>
<para>The <option>-D <replaceable>0,1,0</replaceable></option>
- indicates the SCSI device <devicename>0,1,0</devicename>,
+ indicates the SCSI device <filename>0,1,0</filename>,
which corresponds to the output of <command>cdrecord
-scanbus</command>.</para>
@@ -567,48 +563,47 @@ MPEG 1.0 layer III, 128 kbit/s, 44100 Hz joint-stereo</screen>
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>
+ <screen>&prompt.root; <userinput>cdda2wav -D /dev/acd0 -t 7</userinput></screen>
<para>To rip individual tracks, make use of the
<option>-t</option> as shown:</para>
- <screen>&prompt.root; <userinput>cdda2wav -D <replaceable>0,1,0</replaceable> -t 7</userinput></screen>
+ <screen>&prompt.root; <userinput>cdda2wav -D 0,1,0 -t 7</userinput></screen>
<para>This example rips track seven of the audio CDROM. To rip
a range of tracks, such as track one to seven, specify a
range:</para>
- <screen>&prompt.root; <userinput>cdda2wav -D <replaceable>0,1,0</replaceable> -t 1+7</userinput></screen>
+ <screen>&prompt.root; <userinput>cdda2wav -D 0,1,0 -t 1+7</userinput></screen>
<para>&man.dd.1; can also be used to extract audio tracks on
- ATAPI drives, as described in <xref
- linkend="duplicating-audiocds"/>.</para>
+ ATAPI drives, as described in <xref linkend="duplicating-audiocds"/>.</para>
</sect2>
- <sect2 id="mp3-encoding">
+ <sect2 xml:id="mp3-encoding">
<title>Encoding MP3s</title>
<para>
<application>Lame</application> is a popular
<acronym>MP3</acronym> encoder which can be installed from the
- <filename role="package">audio/lame</filename> port. Due to
+ <package>audio/lame</package> port. Due to
licensing restrictions, a package is not available.</para>
<para>The following command will convert the ripped
<acronym>WAV</acronym> files
- <filename><replaceable>audio01.wav</replaceable></filename>
+ <filename>audio01.wav</filename>
to
- <filename><replaceable>audio01.mp3</replaceable></filename>:</para>
+ <filename>audio01.mp3</filename>:</para>
- <screen>&prompt.root; <userinput>lame -h -b <replaceable>128</replaceable> \
---tt "<replaceable>Foo Song Title</replaceable>" \
---ta "<replaceable>FooBar Artist</replaceable>" \
---tl "<replaceable>FooBar Album</replaceable>" \
---ty "<replaceable>2001</replaceable>" \
---tc "<replaceable>Ripped and encoded by Foo</replaceable>" \
---tg "<replaceable>Genre</replaceable>" \
-<replaceable>audio01.wav audio01.mp3</replaceable></userinput></screen>
+ <screen>&prompt.root; <userinput>lame -h -b 128 \
+--tt "Foo Song Title" \
+--ta "FooBar Artist" \
+--tl "FooBar Album" \
+--ty "2001" \
+--tc "Ripped and encoded by Foo" \
+--tg "Genre" \
+audio01.wav audio01.mp3</userinput></screen>
<para>128&nbsp;kbits is a standard <acronym>MP3</acronym>
bitrate. The 160 and 192 bitrates provide higher quality.
@@ -622,7 +617,7 @@ MPEG 1.0 layer III, 128 kbit/s, 44100 Hz joint-stereo</screen>
page.</para>
</sect2>
- <sect2 id="mp3-decoding">
+ <sect2 xml:id="mp3-decoding">
<title>Decoding MP3s</title>
<para>In order to burn an audio CD from <acronym>MP3</acronym>s,
@@ -690,8 +685,8 @@ MPEG 1.0 layer III, 128 kbit/s, 44100 Hz joint-stereo</screen>
<procedure>
<step>
<para>Run <command>mpg123 -s
- <replaceable>audio01.mp3</replaceable> &gt;
- <replaceable>audio01.pcm</replaceable></command></para>
+ audio01.mp3 &gt;
+ audio01.pcm</command></para>
</step>
</procedure>
@@ -706,17 +701,16 @@ MPEG 1.0 layer III, 128 kbit/s, 44100 Hz joint-stereo</screen>
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>
+ installed from the <package>audio/sox</package> 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>
+ <screen>&prompt.user; <userinput>sox -t wav -r 44100 -s -w -c 2 track.wav track.raw</userinput></screen>
<para>Refer to <xref linkend="creating-cds"/> for more
information on using a CD burner in &os;.</para>
</sect2>
</sect1>
- <sect1 id="video-playback">
+ <sect1 xml:id="video-playback">
<!--
<sect1info>
<authorgroup>
@@ -743,8 +737,7 @@ MPEG 1.0 layer III, 128 kbit/s, 44100 Hz joint-stereo</screen>
<para>It is a good idea to have a short MPEG test file for
evaluating various players and options. Since some
<acronym>DVD</acronym> applications look for
- <acronym>DVD</acronym> media in <filename
- class="directory">/dev/dvd</filename> by default, or have this
+ <acronym>DVD</acronym> media in <filename>/dev/dvd</filename> by default, or have this
device name hardcoded in them, it might be useful to make a
symbolic links to the proper device:</para>
@@ -769,7 +762,7 @@ MPEG 1.0 layer III, 128 kbit/s, 44100 Hz joint-stereo</screen>
<programlisting>kern.ipc.shmmax=67108864
kern.ipc.shmall=32768</programlisting>
- <sect2 id="video-interface">
+ <sect2 xml:id="video-interface">
<title>Determining Video Capabilities</title>
<indexterm><primary>XVideo</primary></indexterm>
@@ -807,8 +800,7 @@ kern.ipc.shmall=32768</programlisting>
provides a low-level abstraction to the hardware which can
sometimes be more efficient than the
<application>&xorg;</application> interface. On &os;,
- <acronym>SDL</acronym> can be installed using the <filename
- role="package">devel/sdl20</filename> package or
+ <acronym>SDL</acronym> can be installed using the <package>devel/sdl20</package> package or
port.</para>
</listitem>
@@ -818,7 +810,7 @@ kern.ipc.shmall=32768</programlisting>
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>. The
+ be run as <systemitem class="username">root</systemitem>. 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
@@ -830,7 +822,7 @@ kern.ipc.shmall=32768</programlisting>
</listitem>
</orderedlist>
- <sect3 id="video-interface-xvideo">
+ <sect3 xml:id="video-interface-xvideo">
<title>XVideo</title>
<para>To check whether this extension is running, use
@@ -927,7 +919,7 @@ no adaptors present</screen>
</sect3>
</sect2>
- <sect2 id="video-ports">
+ <sect2 xml:id="video-ports">
<title>Ports and Packages Dealing with Video</title>
<indexterm><primary>video ports</primary></indexterm>
@@ -937,7 +929,7 @@ no adaptors present</screen>
the &os; Ports Collection which can be used for video
playback.</para>
- <sect3 id="video-mplayer">
+ <sect3 xml:id="video-mplayer">
<title><application>MPlayer</application> and
<application>MEncoder</application></title>
@@ -950,7 +942,7 @@ no adaptors present</screen>
<indexterm><primary>MPlayer</primary></indexterm>
<para><application>MPlayer</application> can be installed using
- the <filename role="package">multimedia/mplayer</filename>
+ the <package>multimedia/mplayer</package>
package or port. 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
@@ -968,14 +960,12 @@ no adaptors present</screen>
<para>By default, the package or port will build the
<command>mplayer</command> command line utility and the
<command>gmplayer</command> graphical utility. To encode
- videos, compile the <filename
- role="package">multimedia/mencoder</filename> port. Due to
+ videos, compile the <package>multimedia/mencoder</package> port. Due to
licensing restrictions, a package is not available for
<application>MEncoder</application>.</para>
<para>The first time <application>MPlayer</application> is run,
- it will create <filename
- class="directory">~/.mplayer</filename> in the user's home
+ it will create <filename>~/.mplayer</filename> in the user's home
directory. This subdirectory contains default versions of
the user-specific configuration files.</para>
@@ -984,32 +974,32 @@ no adaptors present</screen>
options.</para>
<para>To play the file
- <filename><replaceable>testfile.avi</replaceable></filename>,
+ <filename>testfile.avi</filename>,
specify the video interfaces with <option>-vo</option>, as
seen in the following examples:</para>
- <screen>&prompt.user; <userinput>mplayer -vo xv <replaceable>testfile.avi</replaceable></userinput></screen>
+ <screen>&prompt.user; <userinput>mplayer -vo xv testfile.avi</userinput></screen>
- <screen>&prompt.user; <userinput>mplayer -vo sdl <replaceable>testfile.avi</replaceable></userinput></screen>
+ <screen>&prompt.user; <userinput>mplayer -vo sdl testfile.avi</userinput></screen>
- <screen>&prompt.user; <userinput>mplayer -vo x11 <replaceable>testfile.avi</replaceable></userinput></screen>
+ <screen>&prompt.user; <userinput>mplayer -vo x11 testfile.avi</userinput></screen>
- <screen>&prompt.root; <userinput>mplayer -vo dga <replaceable>testfile.avi</replaceable></userinput></screen>
+ <screen>&prompt.root; <userinput>mplayer -vo dga testfile.avi</userinput></screen>
- <screen>&prompt.root; <userinput>mplayer -vo 'sdl:dga' <replaceable>testfile.avi</replaceable></userinput></screen>
+ <screen>&prompt.root; <userinput>mplayer -vo 'sdl:dga' testfile.avi</userinput></screen>
<para>It is worth trying all of these options, as their
relative performance depends on many factors and will vary
significantly with hardware.</para>
<para>To play a <acronym>DVD</acronym>, replace
- <filename><replaceable>testfile.avi</replaceable></filename>
+ <filename>testfile.avi</filename>
with <option>dvd://<replaceable>N</replaceable> -dvd-device
<replaceable>DEVICE</replaceable></option>, where
<replaceable>N</replaceable> is the title number to play and
<replaceable>DEVICE</replaceable> is the device node for the
<acronym>DVD</acronym>. For example, to play title 3 from
- <devicename>/dev/dvd</devicename>:</para>
+ <filename>/dev/dvd</filename>:</para>
<screen>&prompt.root; <userinput>mplayer -vo xv dvd://3 -dvd-device /dev/dvd</userinput></screen>
@@ -1017,7 +1007,7 @@ no adaptors present</screen>
<para>The default <acronym>DVD</acronym> device can be defined
during the build of the <application>MPlayer</application>
port by including the
- <makevar>WITH_DVD_DEVICE=/path/to/desired/device</makevar>
+ <varname>WITH_DVD_DEVICE=/path/to/desired/device</varname>
option. By default, the device is
<filename>/dev/cd0</filename>. More details can be found in
the port's <filename>Makefile.options</filename>.</para>
@@ -1048,8 +1038,7 @@ zoom=yes</programlisting>
<acronym>MPEG</acronym> format.</para>
<para>Anyone wishing to obtain a high level of expertise with
- &unix; video should consult <ulink
- url="http://www.mplayerhq.hu/DOCS/">mplayerhq.hu/DOCS</ulink>
+ &unix; video should consult <link xlink:href="http://www.mplayerhq.hu/DOCS/">mplayerhq.hu/DOCS</link>
as it is technically informative. This documentation should
be considered as required reading before submitting any bug
reports.</para>
@@ -1060,8 +1049,7 @@ zoom=yes</programlisting>
<para>Before using <command>mencoder</command>, it is a good
idea to become familiar with the options described at
- <ulink
- url="http://www.mplayerhq.hu/DOCS/HTML/en/mencoder.html">mplayerhq.hu/DOCS/HTML/en/mencoder.html</ulink>.
+ <link xlink:href="http://www.mplayerhq.hu/DOCS/HTML/en/mencoder.html">mplayerhq.hu/DOCS/HTML/en/mencoder.html</link>.
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
@@ -1070,40 +1058,40 @@ zoom=yes</programlisting>
<para>Here is an example of a simple copy:</para>
- <screen>&prompt.user; <userinput>mencoder <replaceable>input.avi</replaceable> -oac copy -ovc copy -o <replaceable>output.avi</replaceable></userinput></screen>
+ <screen>&prompt.user; <userinput>mencoder input.avi -oac copy -ovc copy -o output.avi</userinput></screen>
<para>To rip to a file, use <option>-dumpfile</option> with
<command>mplayer</command>.</para>
<para>To convert
- <filename><replaceable>input.avi</replaceable></filename> to
+ <filename>input.avi</filename> to
the MPEG4 codec with MPEG3 audio encoding, first install the
- <filename role="package">audio/lame</filename> port. Due to
+ <package>audio/lame</package> port. Due to
licensing restrictions, a package is not available. Once
installed, type:</para>
- <screen>&prompt.user; <userinput>mencoder <replaceable>input.avi</replaceable> -oac mp3lame -lameopts br=192 \
- -ovc lavc -lavcopts vcodec=mpeg4:vhq -o <replaceable>output.avi</replaceable></userinput></screen>
+ <screen>&prompt.user; <userinput>mencoder input.avi -oac mp3lame -lameopts br=192 \
+ -ovc lavc -lavcopts vcodec=mpeg4:vhq -o output.avi</userinput></screen>
<para>This will produce output playable by applications such as
<command>mplayer</command> and <command>xine</command>.</para>
- <para><filename><replaceable>input.avi</replaceable></filename>
+ <para><filename>input.avi</filename>
can be replaced with <option>dvd://1 -dvd-device
- /dev/dvd</option> and run as <username>root</username> to
+ /dev/dvd</option> and run as <systemitem class="username">root</systemitem> to
re-encode a <acronym>DVD</acronym> title directly. Since it
may take a few tries to get the desired result, it is
recommended to instead dump the title to a file and to work on
the file.</para>
</sect3>
- <sect3 id="video-xine">
+ <sect3 xml:id="video-xine">
<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
+ <package>multimedia/xine</package> package or
port.</para>
<para>In practice, <application>xine</application> requires
@@ -1119,15 +1107,14 @@ zoom=yes</programlisting>
invoked from the command line
by specifying the name of the file to play:</para>
- <screen>&prompt.user; <userinput>xine -g -p <replaceable>mymovie.avi</replaceable></userinput></screen>
+ <screen>&prompt.user; <userinput>xine -g -p mymovie.avi</userinput></screen>
- <para>Refer to <ulink
- url="http://www.xine-project.org/faq">
- xine-project.org/faq</ulink> for more information and
+ <para>Refer to <link xlink:href="http://www.xine-project.org/faq">
+ xine-project.org/faq</link> for more information and
troubleshooting tips.</para>
</sect3>
- <sect3 id="video-ports-transcode">
+ <sect3 xml:id="video-ports-transcode">
<title>The <application>Transcode</application>
Utilities</title>
@@ -1139,8 +1126,7 @@ zoom=yes</programlisting>
interfaces.</para>
<para>In &os;, <application>Transcode</application> can be
- installed using the <filename
- role="package">multimedia/transcode</filename> package or
+ installed using the <package>multimedia/transcode</package> package or
port. Many users prefer to compile the port as it provides a
menu of compile options for specifying the support and codecs
to compile in. If an option is not selected,
@@ -1154,27 +1140,24 @@ zoom=yes</programlisting>
a PAL MPEG-1 file (PAL VCD):</para>
<screen>&prompt.user; <userinput>transcode -i
-<replaceable>input.avi</replaceable> -V --export_prof vcd-pal -o output_vcd</userinput>
-&prompt.user; <userinput>mplex -f 1 -o <replaceable>output_vcd.mpg output_vcd.m1v output_vcd.mpa</replaceable></userinput></screen>
+input.avi -V --export_prof vcd-pal -o output_vcd</userinput>
+&prompt.user; <userinput>mplex -f 1 -o output_vcd.mpg output_vcd.m1v output_vcd.mpa</userinput></screen>
<para>The resulting <acronym>MPEG</acronym> file,
- <filename><replaceable>output_vcd.mpg</replaceable></filename>,
+ <filename>output_vcd.mpg</filename>,
is ready to be played with <application>MPlayer</application>.
The file can be burned on a <acronym>CD</acronym> media to
create a video <acronym>CD</acronym> using a utility such as
- <filename
- role="package">multimedia/vcdimager</filename> or <filename
- role="package">sysutils/cdrdao</filename>.</para>
+ <package>multimedia/vcdimager</package> or <package>sysutils/cdrdao</package>.</para>
<para>In addition to the manual page for
- <command>transcode</command>, refer to <ulink
- url="http://www.transcoding.org/cgi-bin/transcode">transcoding.org/cgi-bin/transcode</ulink>
+ <command>transcode</command>, refer to <link xlink:href="http://www.transcoding.org/cgi-bin/transcode">transcoding.org/cgi-bin/transcode</link>
for further information and examples.</para>
</sect3>
</sect2>
</sect1>
-<sect1 id="tvcard">
+<sect1 xml:id="tvcard">
<!--
<sect1info>
<authorgroup>
@@ -1270,16 +1253,16 @@ bktr0: Pinnacle/Miro TV, Philips SECAM tuner.</programlisting>
<itemizedlist>
<listitem>
- <para><filename role="package">multimedia/fxtv</filename>
+ <para><package>multimedia/fxtv</package>
provides TV-in-a-window and image/audio/video capture
capabilities.</para>
</listitem>
<listitem>
- <para><filename role="package">multimedia/xawtv</filename>
+ <para><package>multimedia/xawtv</package>
is another TV application with similar features.</para>
</listitem>
<listitem>
- <para><filename role="package">audio/xmradio</filename>
+ <para><package>audio/xmradio</package>
provides an application for using the FM radio tuner of a
TV card.</para>
</listitem>
@@ -1301,31 +1284,28 @@ bktr0: Pinnacle/Miro TV, Philips SECAM tuner.</programlisting>
</sect2>
</sect1>
- <sect1 id="mythtv">
+ <sect1 xml:id="mythtv">
<title>MythTV</title>
<para>MythTV is a popular, open source Personal Video Recorder
(<acronym>PVR</acronym>) application. This section demonstrates
- how to install and setup MythTV on &os;. Refer to <ulink
- url="http://www.mythtv.org/wiki/">mythtv.org/wiki</ulink> for
+ how to install and setup MythTV on &os;. Refer to <link xlink:href="http://www.mythtv.org/wiki/">mythtv.org/wiki</link> for
more information on how to use MythTV.</para>
<para>MythTV requires a frontend and a backend. These
components can either be installed on the same system or on
different machines.</para>
- <para>The frontend can be installed on &os; using the <filename
- role="package">multimedia/mythtv-frontend</filename> package
+ <para>The frontend can be installed on &os; using the <package>multimedia/mythtv-frontend</package> package
or port. <application>&xorg;</application> must also be
- installed and configured as described in <xref
- linkend="x11"/>. Ideally, this system has a video card that
+ installed and configured as described in <xref linkend="x11"/>. Ideally, this system has a video card that
supports X-Video Motion Compensation
(<acronym>XvMC</acronym>) and, optionally, a Linux Infrared
Remote Control (<acronym>LIRC</acronym>)-compatible
remote.</para>
<para>To install both the backend and the frontend on &os;, use
- the <filename role="package">multimedia/mythtv</filename>
+ the <package>multimedia/mythtv</package>
package or port. A &mysql; database server is also required
and should automatically be installed as a dependency.
Optionally, this system should have a tuner card and
@@ -1337,25 +1317,20 @@ bktr0: Pinnacle/Miro TV, Philips SECAM tuner.</programlisting>
<para>MythTV uses Video for Linux (<acronym>V4L</acronym>) to
access video input devices such as encoders and tuners. In
&os;, MythTV works best with <acronym>USB</acronym> DVB-S/C/T
- cards as they are well supported by the <filename
- role="package">multimedia/webcamd</filename> package or port
+ cards as they are well supported by the <package>multimedia/webcamd</package> package or port
which provides a <acronym>V4L</acronym> userland application.
Any Digital Video Broadcasting (<acronym>DVB</acronym>) card
supported by <application>webcamd</application> should work
with MythTV. A list of known working cards can be found at
- <ulink
- url="http://wiki.freebsd.org/WebcamCompat">wiki.freebsd.org/WebcamCompat</ulink>.
+ <link xlink:href="http://wiki.freebsd.org/WebcamCompat">wiki.freebsd.org/WebcamCompat</link>.
Drivers are also available for Hauppauge cards in the
- <filename
- role="package">multimedia/pvr250</filename> and <filename
- role="package">multimedia/pvrxxx</filename> ports, but they
+ <package>multimedia/pvr250</package> and <package>multimedia/pvrxxx</package> ports, but they
provide a non-standard driver interface that does not work
with versions of MythTV greater than 0.23. Due to licensing
restrictions, no packages are available and these two ports
must be compiled.</para>
- <para>The <ulink
- url="http://wiki.freebsd.org/HTPC">wiki.freebsd.org/HTPC</ulink>
+ <para>The <link xlink:href="http://wiki.freebsd.org/HTPC">wiki.freebsd.org/HTPC</link>
page contains a list of all available <acronym>DVB</acronym>
drivers.</para>
</sect2>
@@ -1383,7 +1358,7 @@ bktr0: Pinnacle/Miro TV, Philips SECAM tuner.</programlisting>
</sect2>
</sect1>
- <sect1 id="scanners">
+ <sect1 xml:id="scanners">
<!--
<sect1info>
<authorgroup>
@@ -1404,17 +1379,15 @@ bktr0: Pinnacle/Miro TV, Philips SECAM tuner.</programlisting>
<para>In &os;, access to image scanners is provided by the
<application>SANE</application> (Scanner Access Now Easy)
- <acronym role="Application Programming
- Interface">API</acronym> available through the &os; Ports
+ <acronym role="Application Programming Interface">API</acronym> available through the &os; Ports
Collection. <application>SANE</application> will also use
some &os; device drivers to provide access to the scanner
hardware.</para>
<para>&os; supports both SCSI and USB scanners. Be sure the
scanner is supported by <application>SANE</application> prior
- to performing any configuration. Refer to the <ulink
- url="http://www.sane-project.org/sane-supported-devices.html">
- supported devices list</ulink> for more information about
+ to performing any configuration. Refer to the <link xlink:href="http://www.sane-project.org/sane-supported-devices.html">
+ supported devices list</link> for more information about
supported scanners.</para>
<sect2>
@@ -1424,7 +1397,7 @@ bktr0: Pinnacle/Miro TV, Philips SECAM tuner.</programlisting>
upon the scanner interface, different device drivers are
required.</para>
- <sect3 id="scanners-kernel-usb">
+ <sect3 xml:id="scanners-kernel-usb">
<title>USB Interface</title>
<para>The <filename>GENERIC</filename> kernel by default
@@ -1503,20 +1476,16 @@ Re-scan of bus 3 was successful</screen>
<title>SANE Configuration</title>
<para>The <application>SANE</application> system is split in two
- parts: the backends (<filename
- role="package">graphics/sane-backends</filename>) and the
- frontends (<filename
- role="package">graphics/sane-frontends</filename>). The
+ parts: the backends (<package>graphics/sane-backends</package>) and the
+ frontends (<package>graphics/sane-frontends</package>). The
backends provide access to the scanner. The
- <application>SANE</application>'s <ulink
- url="http://www.sane-project.org/sane-supported-devices.html">supported
- devices</ulink> list specifies which backend will support the
+ <application>SANE</application>'s <link xlink:href="http://www.sane-project.org/sane-supported-devices.html">supported
+ devices</link> list specifies which backend will support the
image scanner. The correct backend is needed in order to use
the scanner. The frontends provide the graphical scanning
interface, <application>xscanimage</application>.</para>
- <para>After installing the <filename
- role="package">graphics/sane-backends</filename> port or
+ <para>After installing the <package>graphics/sane-backends</package> port or
package, use <command>sane-find-scanner</command> to check the
scanner detection by the
<application>SANE</application> system:</para>
@@ -1544,8 +1513,7 @@ found SCSI scanner "AGFA SNAPSCAN 600 1.10" at /dev/pass3</screen>
<screen>&prompt.root; <userinput>scanimage -L</userinput>
device `snapscan:/dev/pass3' is a AGFA SNAPSCAN 600 flatbed scanner</screen>
- <para>Here is the output for the USB scanner used in <xref
- linkend="scanners-kernel-usb"/>:</para>
+ <para>Here is the output for the USB scanner used in <xref linkend="scanners-kernel-usb"/>:</para>
<screen>&prompt.root; <userinput>scanimage -L</userinput>
device 'epson2:libusb:/dev/usb:/dev/ugen0.2' is a Epson GT-8200 flatbed scanner</screen>
@@ -1560,8 +1528,7 @@ device 'epson2:libusb:/dev/usb:/dev/ugen0.2' is a Epson GT-8200 flatbed scanner<
<para>No output or a message saying that no scanners were
identified indicates that &man.scanimage.1; is unable to
identify the scanner. If this happens, edit the backend
- configuration file in <filename
- class="directory">/usr/local/etc/sane.d/</filename>
+ configuration file in <filename>/usr/local/etc/sane.d/</filename>
and define the scanner device used.</para>
<para>In the above example, the USB scanner is perfectly
@@ -1610,12 +1577,12 @@ device `epson:/dev/uscanner0' is a Epson GT-8200 flatbed scanner</screen>
<para>While &man.scanimage.1; can be used to perform an image
acquisition from the command line, it is often preferable to
use a graphical interface to perform image scanning. The
- <filename role="package">graphics/sane-frontends</filename>
+ <package>graphics/sane-frontends</package>
package or port installs a simple but efficient graphical
interface, <application>xscanimage</application>.</para>
<para><application>Xsane</application>, which is installed with
- the <filename role="package">graphics/xsane</filename> package
+ the <package>graphics/xsane</package> package
or port, is another popular graphical scanning frontend. It
offers advanced features such as various scanning modes, color
correction, and batch scans. Both of these applications are
@@ -1632,23 +1599,23 @@ device `epson:/dev/uscanner0' is a Epson GT-8200 flatbed scanner</screen>
symlink to the real device node
<filename>/dev/usb/0.2.0</filename>. The symlink and the device
node are owned, respectively, by the
- <groupname>wheel</groupname> and
- <groupname>operator</groupname> groups. Adding the user to
+ <systemitem class="groupname">wheel</systemitem> and
+ <systemitem class="groupname">operator</systemitem> groups. Adding the user to
these groups will allow access to the scanner. However, for
security reasons, always think twice before adding a user
- to any group, especially <groupname>wheel</groupname>. A better
+ to any group, especially <systemitem class="groupname">wheel</systemitem>. A better
solution is to create a group to make the scanner device
accessible to members of this group.</para>
<para>This example creates a group called
- <groupname><replaceable>usb</replaceable></groupname> using
+ <systemitem class="groupname"><replaceable>usb</replaceable></systemitem> using
&man.pw.8;:</para>
<screen>&prompt.root; <userinput>pw groupadd usb</userinput></screen>
<para>Then, make the <filename>/dev/ugen0.2</filename> symlink
and the <filename>/dev/usb/0.2.0</filename> device node
- accessible to the <groupname>usb</groupname> group with write
+ accessible to the <systemitem class="groupname">usb</systemitem> group with write
permissions of (<literal>0660</literal> or
<literal>0664</literal>. All of this is done by adding the
following lines to
@@ -1659,10 +1626,10 @@ add path ugen0.2 mode 0660 group usb
add path usb/0.2.0 mode 0666 group usb</programlisting>
<para>Finally, add the users to
- <groupname><replaceable>usb</replaceable></groupname> in order
+ <systemitem class="groupname"><replaceable>usb</replaceable></systemitem> in order
to allow access to the scanner:</para>
- <screen>&prompt.root; <userinput>pw groupmod usb -m <replaceable>joe</replaceable></userinput></screen>
+ <screen>&prompt.root; <userinput>pw groupmod usb -m joe</userinput></screen>
<para>For more details refer to &man.pw.8;.</para>
</sect2>