svn commit: r41492 - projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/multimedia
Dru Lavigne
dru at FreeBSD.org
Wed Apr 24 20:49:20 UTC 2013
Author: dru
Date: Wed Apr 24 20:49:19 2013
New Revision: 41492
URL: http://svnweb.freebsd.org/changeset/doc/41492
Log:
Initial content fixup, more patches to follow. The next patch will fix the whitespace.
Fixes &os;, you, and obvious grammos. The technical content has not yet been reviewed to
see if it is still relevant.
Approved by: bcr (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 20:11:30 2013 (r41491)
+++ projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/multimedia/chapter.xml Wed Apr 24 20:49:19 2013 (r41492)
@@ -21,70 +21,64 @@
<sect1 id="multimedia-synopsis">
<title>Synopsis</title>
- <para>FreeBSD supports a wide variety of sound cards, allowing you
- to enjoy high fidelity output from your computer. This includes
+ <para>&os; supports a wide variety of sound cards, allowing users
+ to enjoy high fidelity output from a &os; system. This includes
the ability to record and playback audio in the MPEG Audio Layer
- 3 (MP3), WAV, and Ogg Vorbis formats as well as many other
- formats. The FreeBSD Ports Collection also contains
- applications allowing you to edit your recorded audio, add sound
- effects, and control attached MIDI devices.</para>
-
- <para>With some experimentation, &os; can support
- playback of video files and DVDs. The number of applications
- to encode, convert, and playback various video media is more
- limited than the number of sound applications. For example as
- of this writing, there are no good re-encoding applications
- in the FreeBSD Ports Collection that could be used to convert
- between formats, as there is with <filename
- role="package">audio/sox</filename>. However, the software
- landscape in this area is changing rapidly.</para>
-
- <para>This chapter will describe the necessary steps to configure
- your sound card. The configuration and installation of X11
- (<xref linkend="x11"/>) has already taken care of the
- hardware issues for your video card, though there may be some
- tweaks to apply for better playback.</para>
+ 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>
+
+ <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
+ playback, TV tuner cards, and scanners on &os;. It also
+ describes some of the applications which are available for
+ using these devices.</para>
- <para>After reading this chapter, you will know:</para>
+ <para>After reading this chapter, you will know how to:</para>
<itemizedlist>
<listitem>
- <para>How to configure your system so that your sound card
- is recognized.</para>
+ <para>Configure a sound card
+ on os;.</para>
</listitem>
<listitem>
- <para>Methods to test whether your card is working.</para>
+ <para>Troubleshoot the sound setup.</para>
</listitem>
<listitem>
- <para>How to troubleshoot your sound setup.</para>
+ <para>Playback and encode MP3s and other audio.</para>
</listitem>
<listitem>
- <para>How to playback and encode MP3s and other audio.</para>
+ <para>Prepare a &os; system for video playback.</para>
</listitem>
<listitem>
- <para>How video is supported by the X server.</para>
+ <para>Playback DVDs, <filename>.mpg</filename>, and
+ <filename>.avi</filename> files.</para>
</listitem>
<listitem>
- <para>Some video player/encoder ports which give good
- results.</para>
+ <para>Rip CD and DVD content into files.</para>
</listitem>
<listitem>
- <para>How to playback DVDs, <filename>.mpg</filename> and
- <filename>.avi</filename> files.</para>
+ <para>Configure a TV card.</para>
</listitem>
<listitem>
- <para>How to rip CD and DVD content into files.</para>
+ <para>Install and setup MythTV on &os;</para>
</listitem>
<listitem>
- <para>How to configure a TV card.</para>
+ <para>Configure an image scanner.</para>
</listitem>
<listitem>
@@ -100,10 +94,9 @@
</itemizedlist>
<warning>
- <para>Trying to mount audio CDs with the &man.mount.8; command
- will result in an error, at least, and a <emphasis>kernel
- panic</emphasis>, at worst. These media have specialized
- encodings which differ from the usual ISO-filesystem.</para>
+ <para>Audio CDs have specialized encodings which differ from the
+ usual ISO-filesystem. This means that they should not be
+ mounted using &man.mount.8;.</para>
</warning>
</sect1>
@@ -134,101 +127,101 @@
<title>Configuring the System</title>
<indexterm><primary>PCI</primary></indexterm>
- <indexterm><primary>ISA</primary></indexterm>
<indexterm><primary>sound cards</primary></indexterm>
- <para>Before you begin, you should know the model of the card
- you have, the chip it uses, and whether it is a PCI or ISA
- card. FreeBSD supports a wide variety of both PCI and ISA
- cards. Check the supported audio devices list of the <ulink
- url="&rel.current.hardware;">Hardware Notes</ulink> to
- see if your card is supported. The Hardware Notes will
- also mention which driver supports your card.</para>
+ <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;
+ driver it uses.</para>
<indexterm>
<primary>kernel</primary>
<secondary>configuration</secondary>
</indexterm>
- <para>To use your sound device, you will need to load the proper
- device driver. This may be accomplished in one of two ways.
- The easiest way is to simply load a kernel module for your
- sound card with &man.kldload.8; which can either be done from
- the command line:</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>or by adding the appropriate line to the file
- <filename>/boot/loader.conf</filename> like this:</para>
+ <para>To automate the loading of this driver at boot time, add the
+ driver to
+ <filename>/boot/loader.conf</filename>. The line for
+ this driver is:</para>
<programlisting>snd_emu10k1_load="YES"</programlisting>
- <para>These examples are for a Creative &soundblaster; Live! sound
- card. Other available loadable sound modules are listed in
+ <para>Other available sound modules are listed in
<filename>/boot/defaults/loader.conf</filename>.
- If you are not sure which driver to use, you may try to load
+ 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 loading the most common device drivers
- at once. This speeds up the search for the correct driver. It
- is also possible to load all sound drivers via the
- <filename>/boot/loader.conf</filename> facility.</para>
-
- <para>If you wish to find out the driver selected for your
- soundcard after loading the <filename>snd_driver</filename>
- metadriver, you may check the <filename>/dev/sndstat</filename>
- file with the <command>cat /dev/sndstat</command>
- command.</para>
-
- <para>A second method is to statically
- compile in support for your sound card in your kernel. The
- section below provides the information you need to add support
- for your hardware in this manner. For more information about
- recompiling your kernel, please see <xref
+ <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
+ <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>
<sect3>
<title>Configuring a Custom Kernel with Sound Support</title>
- <para>The first thing to do is add the audio framework driver
- &man.sound.4; to the kernel; for that you will need to
- add the following line to the kernel configuration file:</para>
+ <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>
<programlisting>device sound</programlisting>
- <para>Next, you have to add the support for your sound card.
+ <para>Next, add support for the sound card.
Therefore, you need to know which driver supports the card.
- Check the supported audio devices list of the <ulink
- url="&rel.current.hardware;">Hardware Notes</ulink>, to
- determine the correct driver for your sound card. For
- example, a Creative &soundblaster; Live! sound card is
- supported by the &man.snd.emu10k1.4; driver. To add the support
- for this card, use the following:</para>
+ 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>
<para>Be sure to read the manual page of the driver for the
syntax to use. The explicit syntax for the kernel
configuration of every supported sound driver can also be
- found in the <filename>/usr/src/sys/conf/NOTES</filename>
- file.</para>
+ found in <filename>/usr/src/sys/conf/NOTES</filename>.</para>
- <para>Non-PnP ISA sound cards may require you to provide the
- kernel with information on the card settings (IRQ, I/O port,
- etc), as is true of all non-PnP ISA cards. This is done via
- the <filename>/boot/device.hints</filename> file. During the
- boot process, the &man.loader.8; will read this file and pass
+ <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
&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
+ <literal>snd_sb16</literal>. For this card, the following
lines must be added to the kernel configuration file:</para>
<programlisting>device snd_sbc
device snd_sb16</programlisting>
- <para>and these to
+ <para>If the card uses the <literal>0x220</literal> I/O port and
+ IRQ <literal>5</literal>, these lines must also be added to
<filename>/boot/device.hints</filename>:</para>
<programlisting>hint.sbc.0.at="isa"
@@ -240,14 +233,14 @@ hint.sbc.0.flags="0x15"</programlisting>
<para>In this case, the card uses the <literal>0x220</literal>
I/O port and the IRQ <literal>5</literal>.</para>
- <para>The syntax used in the
- <filename>/boot/device.hints</filename> file is covered in the
- &man.sound.4; driver manual page and the manual page
- for the driver in question.</para>
+ <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>
<para>The settings shown above are the defaults. In some
- cases, you may need to change the IRQ or the other settings to
- match your card. See the &man.snd.sbc.4; manual page for more
+ 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>
</sect3>
</sect2>
@@ -255,16 +248,17 @@ hint.sbc.0.flags="0x15"</programlisting>
<sect2 id="sound-testing">
<title>Testing the Sound Card</title>
- <para>After rebooting with the modified kernel, or after loading
- the required module, the sound card should appear in your system
- message buffer (&man.dmesg.8;) as something like:</para>
+ <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>
<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 be checked via the
- <filename>/dev/sndstat</filename> file:</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,46 +266,47 @@ Installed devices:
pcm0: <Intel ICH3 (82801CA)> at io 0xd800, 0xdc80 irq 5 bufsz 16384
kld snd_ich (1p/2r/0v channels duplex default)</screen>
- <para>The output from your system may vary. If no
+ <para>The output may vary between systems. If no
<devicename>pcm</devicename> devices are listed, go back and
- review what was done earlier. Go through your kernel
- configuration file again and make sure the correct
+ review the kernel configuration file and make sure the correct
device driver was chosen. Common problems are listed in <xref
linkend="troubleshooting"/>.</para>
- <para>If all goes well, you should now have a functioning sound
- card. If your CD-ROM or DVD-ROM drive's audio-out pins are
- properly connected to your sound card, you can put a 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> can provide a
- friendlier interface. You may want to install an application
- such as <filename role="package">audio/mpg123</filename> to
+ 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 sending data
- to <filename>/dev/dsp</filename>, like this:</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 line should produce some noise,
- confirming 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 device nodes <filename>/dev/dsp*</filename> will be
- created automatically when needed. If they are not used, they
+ <para>The <devicename>/dev/dsp*</devicename> 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>
- <para>Sound card mixer levels can be changed via the &man.mixer.8;
- command. More details can be found in the &man.mixer.8; manual
- page.</para>
+ <para>Sound card mixer levels can be changed using &man.mixer.8;.
+ More details can be found in &man.mixer.8;.</para>
<sect3 id="troubleshooting">
<title>Common Problems</title>
@@ -370,8 +365,8 @@ kld snd_ich (1p/2r/0v channels duplex de
<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 actual soundcard and the
- soundcard will subsequently not be used as the default
+ 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
@@ -397,16 +392,17 @@ 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 default playback
- device, change <literal>hw.snd.default_unit</literal> to the
- unit that should be used for playback, enter the
- following:</para>
+ 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>
<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 <literal>4</literal>. You can
- make this change permanent by adding the following line to
+ device to use. In this example, it should be
+<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>
@@ -426,20 +422,15 @@ pcm7: <HDA Realtek ALC889 PCM #3 Digi
<title>Utilizing Multiple Sound Sources</title>
<para>It is often desirable to have multiple sources of sound that
- are able to play simultaneously, such as when
- <application>esound</application> or
- <application>artsd</application> do not support sharing of the
- sound device with a certain application.</para>
-
- <para>FreeBSD lets you do this through <emphasis>Virtual Sound
- Channels</emphasis>, which can be enabled with the
- &man.sysctl.8; facility. Virtual channels allow you to
- multiplex your sound card's playback by mixing sound in the
+ 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, there are three
- sysctl knobs which, if you are the <username>root</username>
- user, can be set like this:</para>
+ <para>To set the number of virtual channels, three
+ &man.sysctl.8; knobs are available:</para>
<screen>&prompt.root; <userinput>sysctl dev.pcm.0.play.vchans=4</userinput>
&prompt.root; <userinput>sysctl dev.pcm.0.rec.vchans=4</userinput>
@@ -450,19 +441,20 @@ pcm7: <HDA Realtek ALC889 PCM #3 Digi
<varname>dev.pcm.0.play.vchans=4</varname> and
<varname>dev.pcm.0.rec.vchans=4</varname> are the number of
virtual channels <devicename>pcm0</devicename> has for playback
- and recording, and are configurable once a device has been
+ and recording, and are configurable after a device has been
attached. <literal>hw.snd.maxautovchans</literal> is the number
of virtual channels a new audio device is given when it is
attached using &man.kldload.8;. Since the
<devicename>pcm</devicename> module can be loaded independently
of the hardware drivers, <varname>hw.snd.maxautovchans</varname>
- can store how many virtual channels any devices which are
- attached later will be given. Refer to &man.pcm.4; manual page
+ indicates how many virtual channels will be given to devices
+when they are attached. Refer to &man.pcm.4;
for more information.</para>
<note>
- <para>You cannot change the number of virtual channels for a
- device 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>
@@ -486,18 +478,20 @@ pcm7: <HDA Realtek ALC889 PCM #3 Digi
<title>Setting Default Values for Mixer Channels</title>
<para>The default values for the different mixer channels are
- hardcoded in the sourcecode of the &man.pcm.4; driver. There
+ hardcoded in the source code of the &man.pcm.4; driver. There
are many different applications and daemons that allow
- you to set values for the mixer that are remembered between
+ 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
+ to set default mixer values at the driver level. This
is accomplished by defining the appropriate values in
- <filename>/boot/device.hints</filename>, e.g.:</para>
+ <filename>/boot/device.hints</filename>, as seen in this
+example:</para>
<programlisting>hint.pcm.0.vol="50"</programlisting>
<para>This will set the volume channel to a default value of
- 50 when the &man.pcm.4; module is loaded.</para>
+ <literal>50</literal> when the &man.pcm.4; module is
+loaded.</para>
</sect2>
</sect1>
@@ -515,18 +509,18 @@ pcm7: <HDA Realtek ALC889 PCM #3 Digi
<title>MP3 Audio</title>
- <para>MP3 (MPEG Layer 3 Audio) accomplishes near CD-quality sound,
- leaving no reason to let your FreeBSD workstation fall short of
- its offerings.</para>
+ <para>This section describes some <acronym>MP3</acronym>
+ 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">
<title>MP3 Players</title>
- <para>By far, the most popular X11 MP3 player is
- <application>XMMS</application> (X Multimedia System).
+ <para>A popular graphical <acronym>MP3</acronym> player is
+ <application>XMMS</application>.
<application>Winamp</application>
skins can be used with <application>XMMS</application> since
- the GUI is almost identical to that of Nullsoft's
+ the interface is almost identical to that of Nullsoft's
<application>Winamp</application>.
<application>XMMS</application> also has native plug-in
support.</para>
@@ -541,14 +535,17 @@ pcm7: <HDA Realtek ALC889 PCM #3 Digi
<application>XMMS</application> simple to use.</para>
<para>The <filename role="package">audio/mpg123</filename> port
- is an alternative, command-line MP3 player.</para>
+ provides an alternative, command-line <acronym>MP3</acronym>
+player.</para>
<para><application>mpg123</application> can be run by specifying
- the sound device and the MP3 file on the command line.
- Assuming your audio device is
- <devicename>/dev/dsp1.0</devicename> and you want to play the
- MP3 file <replaceable>Foobar-GreatestHits.mp3</replaceable>
- you would enter the following:</para>
+ 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
+ <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>
High Performance MPEG 1.0/2.0/2.5 Audio Player for Layer 1, 2 and 3.
@@ -567,22 +564,32 @@ MPEG 1.0 layer III, 128 kbit/s, 44100 Hz
<sect2 id="rip-cd">
<title>Ripping CD Audio Tracks</title>
- <para>Before encoding a CD or CD track to MP3, the audio data on
- the CD must be ripped onto the hard drive. This is done by
- copying the raw CDDA (CD Digital Audio) data to WAV
+ <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
+ Digital Audio (<acronym>CDDA</acronym>) data to
+<acronym>WAV</acronym>
files.</para>
- <para>The <command>cdda2wav</command> tool, which is a part of
+ <para>The <command>cdda2wav</command> tool, which is installed
+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) WAV files:</para>
+ be issued as <username>root</username> 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>
+ <para>The <option>-D <replaceable>0,1,0</replaceable></option>
+ indicates the SCSI device <devicename>0,1,0</devicename>,
+ 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
@@ -590,40 +597,35 @@ MPEG 1.0 layer III, 128 kbit/s, 44100 Hz
<screen>&prompt.root; <userinput>cdda2wav -D <replaceable>/dev/acd0</replaceable> -t 7</userinput></screen>
- <para>The <option>-D <replaceable>0,1,0</replaceable></option>
- indicates the SCSI device <devicename>0,1,0</devicename>,
- which corresponds to the output of <command>cdrecord
- -scanbus</command>.</para>
-
<para>To rip individual tracks, make use of the
- <option>-t</option> option as shown:</para>
+ <option>-t</option> as shown:</para>
<screen>&prompt.root; <userinput>cdda2wav -D <replaceable>0,1,0</replaceable> -t 7</userinput></screen>
<para>This example rips track seven of the audio CDROM. To rip
- a range of tracks, for example, track one to seven, specify a
+ 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>
- <para>The utility &man.dd.1; can also be used to extract audio
- tracks on ATAPI drives, read <xref
- linkend="duplicating-audiocds"/> for more information on
- that possibility.</para>
+ <para>&man.dd.1; can also be used to extract audio
+ tracks on ATAPI drives, as described in <xref
+ linkend="duplicating-audiocds"/>.</para>
</sect2>
<sect2 id="mp3-encoding">
<title>Encoding MP3s</title>
- <para>Nowadays, the mp3 encoder of choice is
- <application>lame</application>.
- <application>Lame</application> can be found at
- <filename role="package">audio/lame</filename> in the ports
- tree.</para>
-
- <para>Using the ripped WAV files, the following command will
- convert
+ <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
+ 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>
to
<filename><replaceable>audio01.mp3</replaceable></filename>:</para>
@@ -637,25 +639,29 @@ MPEG 1.0 layer III, 128 kbit/s, 44100 Hz
--tg "<replaceable>Genre</replaceable>" \
<replaceable>audio01.wav audio01.mp3</replaceable></userinput></screen>
- <para>128 kbits seems to be the standard MP3 bitrate in
- use. Many enjoy the higher quality 160, or 192. The higher
- the bitrate, the more disk space the resulting MP3 will
- consume--but the quality will be higher. The
- <option>-h</option> option turns on the <quote>higher quality
+ <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 MP3 file.
- Additional encoding options can be found by consulting the
- <application>lame</application> man page.</para>
+ 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 MP3s, they must be
- converted to a non-compressed WAV format. Both
+ <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
<application>XMMS</application> and
- <application>mpg123</application> support the output of MP3
+ <application>mpg123</application> support the output of
+<acronym>MP3</acronym>
to an uncompressed file format.</para>
<para>Writing to Disk in <application>XMMS</application>:</para>
@@ -666,12 +672,12 @@ MPEG 1.0 layer III, 128 kbit/s, 44100 Hz
</step>
<step>
- <para>Right-click on the window to bring up the
+ <para>Right-click the window to bring up the
<application>XMMS</application> menu.</para>
</step>
<step>
- <para>Select <literal>Preference</literal> under
+ <para>Select <literal>Preferences</literal> under
<literal>Options</literal>.</para>
</step>
@@ -685,26 +691,31 @@ MPEG 1.0 layer III, 128 kbit/s, 44100 Hz
</step>
<step>
- <para>Enter (or choose browse) a directory to write the
+ <para>Enter or browse to a directory to write the
uncompressed files to.</para>
</step>
<step>
- <para>Load the MP3 file into <application>XMMS</application>
+ <para>Load the <acronym>MP3</acronym> file into
+<application>XMMS</application>
as usual, with volume at 100% and EQ settings turned
off.</para>
</step>
<step>
- <para>Press <literal>Play</literal> —
+ <para>Press <literal>Play</literal>. The
<application>XMMS</application> will appear as if it is
- playing the MP3, but no music will be heard. It is
- actually playing the MP3 to a file.</para>
+ playing the <acronym>MP3</acronym>, but no music will be
+heard. It is
+ actually playing the <acronym>MP3</acronym> to a
+file.</para>
</step>
<step>
- <para>Be sure to set the default Output Plugin back to what
- it was before in order to listen to MP3s again.</para>
+ <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>
</step>
</procedure>
@@ -719,22 +730,28 @@ MPEG 1.0 layer III, 128 kbit/s, 44100 Hz
</step>
</procedure>
- <para><application>XMMS</application> writes a file in the WAV
+ <para><application>XMMS</application> writes a file in the
+<acronym>WAV</acronym>
format, while <application>mpg123</application> converts the
- MP3 into raw PCM audio data. Both of these formats can be
+ <acronym>MP3</acronym> into raw PCM audio data. Both of these
+formats can be
used with <application>cdrecord</application> to create audio
- CDs. You have to use raw PCM with &man.burncd.8;. If you
- use WAV files, you will notice a small tick sound at the
- beginning of each track, this sound is the header of the WAV
- file. You can simply remove the header of a WAV file with
- the utility <application>SoX</application> (it can be
+ 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
installed from the <filename
- role="package">audio/sox</filename> port or package):</para>
+ 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>Read <xref linkend="creating-cds"/> for more information
- on using a CD burner in FreeBSD.</para>
+ <para>Refer to <xref linkend="creating-cds"/> for more
+information
+ on using a CD burner in &os;.</para>
</sect2>
</sect1>
@@ -752,43 +769,45 @@ MPEG 1.0 layer III, 128 kbit/s, 44100 Hz
<title>Video Playback</title>
- <para>Video playback is a very new and rapidly developing
- application area. Be patient. Not everything is going to work
- as smoothly as it did with sound.</para>
-
- <para>Before you begin, you should know the model of the video
- card you have and the chip it uses. While
+ <para>Before configuring video playback, determine the model
+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 X server using your card
- use the command &man.xdpyinfo.1; while X11 is running.</para>
-
- <para>It is a good idea to have a short MPEG file which can be
- treated as a test file for evaluating various players and
- options. Since some DVD players will look for DVD media in
- <filename>/dev/dvd</filename> by default, or have this device
- name hardcoded in them, you might find it useful to make
+ a list of extensions supported by the
+<application>&xorg;</application> server using the card, run
+ &man.xdpyinfo.1; while <application>&xorg;</application> is
+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
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>Note that due to the nature of &man.devfs.5;,
- manually created links like these will not persist if you reboot
- your system. In order to create the symbolic links
- automatically whenever you boot your system, add the following
+ <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>Additionally, DVD decryption, which requires invoking
- special DVD-ROM functions, requires write permission on the DVD
+ <para>DVD decryption invokes
+ special DVD-ROM functions and requires write permission on the
+DVD
devices.</para>
- <para>To enhance the shared memory X11 interface, it is
- recommended that the values of some &man.sysctl.8; variables
- should be increased:</para>
+ <para>To enhance the shared memory
+<application>&xorg;</application> interface, it is
+ recommended to increase the values of these &man.sysctl.8;
+variables:</para>
<programlisting>kern.ipc.shmmax=67108864
kern.ipc.shmall=32768</programlisting>
@@ -800,32 +819,34 @@ kern.ipc.shmall=32768</programlisting>
<indexterm><primary>SDL</primary></indexterm>
<indexterm><primary>DGA</primary></indexterm>
- <para>There are several possible ways to display video under X11.
- What will really work is largely hardware dependent. Each
+ <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. Secondly, the rendering of video in X11
- is a topic receiving a lot of attention lately, and with each
- version of <application>&xorg;</application>, there may be
- significant improvement.</para>
+ different hardware.</para>
- <para>A list of common video interfaces:</para>
+ <para>Common video interfaces include:</para>
<orderedlist>
<listitem>
- <para>X11: normal X11 output using shared memory.</para>
+ <para><application>&xorg;</application>: normal output
+using shared memory.</para>
</listitem>
<listitem>
- <para>XVideo: an extension to the X11 interface which supports
- video in any X11 drawable.</para>
+ <para>XVideo: an extension to the
+<application>&xorg;</application> interface which supports
+ video in any drawable object.</para>
</listitem>
<listitem>
- <para>SDL: the Simple Directmedia Layer.</para>
+ <para><acronym>SDL</acronym>: the Simple Directmedia
+Layer.</para>
</listitem>
<listitem>
- <para>DGA: the Direct Graphics Access.</para>
+ <para><para><acronym>DGA</acronym>: the Direct Graphics
+Access.</para>
</listitem>
<listitem>
@@ -837,9 +858,10 @@ kern.ipc.shmall=32768</programlisting>
<title>XVideo</title>
<para><application>&xorg;</application> has an extension called
- <emphasis>XVideo</emphasis> (aka Xvideo, aka Xv, aka xv) which
+ <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 very
+ through a special acceleration. This extension provides
good quality playback even on low-end machines.</para>
<para>To check whether the extension is running, use
@@ -847,7 +869,7 @@ kern.ipc.shmall=32768</programlisting>
<screen>&prompt.user; <userinput>xvinfo</userinput></screen>
- <para>XVideo is supported for your card if the result looks
+ <para>XVideo is supported for the card if the result looks
like:</para>
<screen>X-Video Extension version 2.2
@@ -919,7 +941,7 @@ kern.ipc.shmall=32768</programlisting>
depth: 1
red, green, blue masks: 0x0, 0x0, 0x0</screen>
- <para>Also note that the formats listed (YUV2, YUV12, etc) are
+ <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>
@@ -929,46 +951,48 @@ kern.ipc.shmall=32768</programlisting>
screen #0
no adaptors present</screen>
- <para>Then XVideo is probably not supported for your card.</para>
-
- <para>If XVideo is not supported for your card, this only means
- that it will be more difficult for your display to meet the
- computational demands of rendering video. Depending on your
- video card and processor, though, you might still be able to
- have a satisfying experience. You should probably read about
- ways of improving performance in the advanced reading <xref
- linkend="video-further-reading"/>.</para>
+ <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>
</sect3>
<sect3 id="video-interface-SDL">
<title>Simple Directmedia Layer</title>
- <para>The Simple Directmedia Layer, SDL, was intended to be a
- porting layer between µsoft.windows;, BeOS, and &unix;,
- allowing cross-platform applications to be developed which made
- efficient use of sound and graphics. The SDL layer provides a
+ <para><acronym>SDL</acronym> is intended to be a
+ porting layer between µsoft.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 X11 interface.</para>
+ more efficient than the <application>&xorg;</application>
+interface.</para>
- <para>The SDL can be found at <filename
- role="package">devel/sdl12</filename>.</para>
+ <para><acronym>SDL</acronym> can be installed using the <filename
+ role="package">devel/sdl12</filename> package or port.</para>
</sect3>
<sect3 id="video-interface-DGA">
<title>Direct Graphics Access</title>
- <para>Direct Graphics Access is an X11 extension which allows
- a program to bypass the X server and directly alter the
- framebuffer. Because it relies on a low level memory mapping to
- effect this sharing, programs using it must be run as
+ <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
<username>root</username>.</para>
- <para>The DGA extension can be tested and benchmarked by
+ <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, use <keycap>q</keycap>.</para>
+ quit, press <keycap>q</keycap>.</para>
</sect3>
</sect2>
@@ -979,17 +1003,16 @@ no adaptors present</screen>
<indexterm><primary>video ports</primary></indexterm>
<indexterm><primary>video packages</primary></indexterm>
- <para>This section discusses the software available from the
- FreeBSD Ports Collection which can be used for video playback.
- Video playback is a very active area of software development,
- and the capabilities of various applications are bound to
- diverge somewhat from the descriptions given here.</para>
*** DIFF OUTPUT TRUNCATED AT 1000 LINES ***
More information about the svn-doc-projects
mailing list