svn commit: r40784 - head/en_US.ISO8859-1/books/handbook/multimedia
Dru Lavigne
dru at FreeBSD.org
Mon Jan 28 15:35:07 UTC 2013
Author: dru
Date: Mon Jan 28 15:35:06 2013
New Revision: 40784
URL: http://svnweb.freebsd.org/changeset/doc/40784
Log:
White space fix only. Translators can ignore.
Approved by: bcr (mentor)
Modified:
head/en_US.ISO8859-1/books/handbook/multimedia/chapter.xml
Modified: head/en_US.ISO8859-1/books/handbook/multimedia/chapter.xml
==============================================================================
--- head/en_US.ISO8859-1/books/handbook/multimedia/chapter.xml Mon Jan 28 15:15:46 2013 (r40783)
+++ head/en_US.ISO8859-1/books/handbook/multimedia/chapter.xml Mon Jan 28 15:35:06 2013 (r40784)
@@ -6,19 +6,20 @@
-->
<chapter id="multimedia">
- <chapterinfo>
- <authorgroup>
- <author>
- <firstname>Ross</firstname>
- <surname>Lippert</surname>
- <contrib>Edited by </contrib>
- </author>
- </authorgroup>
- </chapterinfo>
+ <chapterinfo>
+ <authorgroup>
+ <author>
+ <firstname>Ross</firstname>
+ <surname>Lippert</surname>
+ <contrib>Edited by </contrib>
+ </author>
+ </authorgroup>
+ </chapterinfo>
+
+ <title>Multimedia</title>
- <title>Multimedia</title>
<sect1 id="multimedia-synopsis">
- <title>Synopsis</title>
+ <title>Synopsis</title>
<para>FreeBSD supports a wide variety of sound cards, allowing you
to enjoy high fidelity output from your computer. This includes
@@ -32,10 +33,10 @@
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
+ 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
+ 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
@@ -48,37 +49,38 @@
<itemizedlist>
<listitem>
- <para>How to configure your system so that your sound card is
- recognized.</para>
+ <para>How to configure your system so that your sound card
+ is recognized.</para>
</listitem>
<listitem>
- <para>Methods to test whether your card is working.</para>
+ <para>Methods to test whether your card is working.</para>
</listitem>
<listitem>
- <para>How to troubleshoot your sound setup.</para>
+ <para>How to troubleshoot your sound setup.</para>
</listitem>
<listitem>
- <para>How to playback and encode MP3s and other audio.</para>
+ <para>How to playback and encode MP3s and other audio.</para>
</listitem>
<listitem>
- <para>How video is supported by the X server.</para>
+ <para>How video is supported by the X server.</para>
</listitem>
<listitem>
- <para>Some video player/encoder ports which give good results.</para>
+ <para>Some video player/encoder ports which give good
+ results.</para>
</listitem>
<listitem>
- <para>How to playback DVDs, <filename>.mpg</filename> and
- <filename>.avi</filename> files.</para>
+ <para>How to playback DVDs, <filename>.mpg</filename> and
+ <filename>.avi</filename> files.</para>
</listitem>
<listitem>
- <para>How to rip CD and DVD content into files.</para>
+ <para>How to rip CD and DVD content into files.</para>
</listitem>
<listitem>
@@ -93,16 +95,15 @@
<para>Before reading this chapter, you should:</para>
<itemizedlist>
- <listitem><para>Know how to configure and install a new kernel (<xref
- linkend="kernelconfig"/>).</para></listitem>
+ <listitem><para>Know how to configure and install a new kernel
+ (<xref linkend="kernelconfig"/>).</para></listitem>
</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>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>
</warning>
</sect1>
@@ -110,49 +111,49 @@
<sect1 id="sound-setup">
<sect1info>
<authorgroup>
- <author>
- <firstname>Moses</firstname>
- <surname>Moore</surname>
- <contrib>Contributed by </contrib>
- <!-- 20 November 2000 -->
- </author>
+ <author>
+ <firstname>Moses</firstname>
+ <surname>Moore</surname>
+ <contrib>Contributed by </contrib>
+ <!-- 20 November 2000 -->
+ </author>
</authorgroup>
<authorgroup>
- <author>
- <firstname>Marc</firstname>
- <surname>Fonvieille</surname>
- <contrib>Enhanced by </contrib>
- <!-- 13 September 2004 -->
- </author>
+ <author>
+ <firstname>Marc</firstname>
+ <surname>Fonvieille</surname>
+ <contrib>Enhanced by </contrib>
+ <!-- 13 September 2004 -->
+ </author>
</authorgroup>
</sect1info>
<title>Setting Up the Sound Card</title>
- <sect2 id="sound-device">
- <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>
+ <sect2 id="sound-device">
+ <title>Configuring the System</title>
- <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>
+ <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>
+
+ <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>
<screen>&prompt.root; <userinput>kldload snd_emu10k1</userinput></screen>
@@ -187,40 +188,42 @@
recompiling your kernel, please see <xref
linkend="kernelconfig"/>.</para>
- <sect3>
- <title>Configuring a Custom Kernel with Sound Support</title>
+ <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>
+
+ <programlisting>device sound</programlisting>
- <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>
-
- <programlisting>device sound</programlisting>
-
- <para>Next, you have to add the support for your sound card.
- Therefore, you need to know which driver supports the card.
- Check the supported audio devices list of the <ulink
+ <para>Next, you have to add the support for your 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>
+ 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>
<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>
-
- <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 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 lines must be added to
- the kernel configuration file:</para>
+ 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>
+
+ <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
+ 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
+ lines must be added to the kernel configuration file:</para>
<programlisting>device snd_sbc
device snd_sb16</programlisting>
@@ -270,33 +273,34 @@ pcm0: <Intel ICH3 (82801CA)> at io
kld snd_ich (1p/2r/0v channels duplex default)</screen>
<para>The output from your system may vary. If no
- <devicename>pcm</devicename> devices are listed, go back and review
- what was done earlier. Go through your kernel
+ <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
device driver was chosen. Common problems are listed in <xref
- linkend="troubleshooting"/>.</para>
+ 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 drive and play it
- with &man.cdcontrol.1;:</para>
+ 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
+ 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 listen to
- MP3 audio files.</para>
+ 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
+ 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>
<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>
+ <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>
<note>
<para>The device nodes <filename>/dev/dsp*</filename> will be
@@ -318,52 +322,62 @@ kld snd_ich (1p/2r/0v channels duplex de
<indexterm><primary>DSP</primary></indexterm>
<informaltable frame="none" pgwide="1">
- <tgroup cols="2">
- <thead>
+ <tgroup cols="2">
+ <thead>
<row>
- <entry>Error</entry>
+ <entry>Error</entry>
<entry>Solution</entry>
</row>
- </thead>
+ </thead>
<tbody>
- <row>
- <entry><errorname>sb_dspwr(XX) timed out</errorname></entry>
- <entry><para>The I/O port is not set correctly.</para></entry>
- </row>
-
- <row>
- <entry><errorname>bad irq XX</errorname></entry>
- <entry><para>The IRQ is set incorrectly. Make sure that
- the set IRQ and the sound IRQ are the same.</para></entry>
- </row>
-
- <row>
- <entry><errorname>xxx: gus pcm not attached, out of memory</errorname></entry>
- <entry><para>There is not enough available memory to use
- the device.</para></entry>
- </row>
-
- <row>
- <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 <application>esound</application> and <application>KDE</application>'s sound
- support.</para></entry>
- </row>
- </tbody>
- </tgroup>
+ <row>
+ <entry><errorname>sb_dspwr(XX) timed
+ out</errorname></entry>
+ <entry><para>The I/O port is not set
+ correctly.</para></entry>
+ </row>
+
+ <row>
+ <entry><errorname>bad irq XX</errorname></entry>
+ <entry><para>The IRQ is set incorrectly. Make sure
+ that the set IRQ and the sound IRQ are the
+ same.</para></entry>
+ </row>
+
+ <row>
+ <entry><errorname>xxx: gus pcm not attached, out of
+ memory</errorname></entry>
+ <entry><para>There is not enough available memory to
+ use the device.</para></entry>
+ </row>
+
+ <row>
+ <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
+ <application>esound</application> and
+ <application>KDE</application>'s sound
+ support.</para></entry>
+ </row>
+ </tbody>
+ </tgroup>
</informaltable>
- <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 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>
+ <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
+ 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>
-<programlisting>...
+ <programlisting>...
hdac0: HDA Driver Revision: 20100226_0142
hdac1: HDA Driver Revision: 20100226_0142
hdac0: HDA Codec #0: NVidia (Unknown)
@@ -381,18 +395,19 @@ pcm6: <HDA Realtek ALC889 PCM #2 Digi
pcm7: <HDA Realtek ALC889 PCM #3 Digital> at cad 2 nid 1 on hdac1
...</programlisting>
- <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>
+ <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>
<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
- <filename>/etc/sysctl.conf</filename>:</para>
+ <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
+ <filename>/etc/sysctl.conf</filename>:</para>
<programlisting>hw.snd.default_unit=<replaceable>4</replaceable></programlisting>
</sect3>
@@ -400,13 +415,13 @@ pcm7: <HDA Realtek ALC889 PCM #3 Digi
<sect2 id="sound-multiple-sources">
<sect2info>
- <authorgroup>
- <author>
- <firstname>Munish</firstname>
- <surname>Chopra</surname>
- <contrib>Contributed by </contrib>
- </author>
- </authorgroup>
+ <authorgroup>
+ <author>
+ <firstname>Munish</firstname>
+ <surname>Chopra</surname>
+ <contrib>Contributed by </contrib>
+ </author>
+ </authorgroup>
</sect2info>
<title>Utilizing Multiple Sound Sources</title>
@@ -417,42 +432,45 @@ pcm7: <HDA Realtek ALC889 PCM #3 Digi
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 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>
+ 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
+ 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>
+
<screen>&prompt.root; <userinput>sysctl dev.pcm.0.play.vchans=4</userinput>
&prompt.root; <userinput>sysctl dev.pcm.0.rec.vchans=4</userinput>
&prompt.root; <userinput>sysctl hw.snd.maxautovchans=4</userinput></screen>
- <para>The above example allocates four virtual channels, which is a
- practical number for everyday use. Both <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 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 for more
- information.</para>
+ <para>The above example allocates four virtual channels, which
+ is a practical number for everyday use. Both
+ <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
+ 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
+ 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 the
- device, such as music players or sound daemons.</para>
+ device 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>
- </sect2>
+ </sect2>
<sect2>
<sect2info>
@@ -468,32 +486,32 @@ 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 are
- many different applications and daemons that allow
+ hardcoded in the sourcecode 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
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>, e.g.:</para>
+ is accomplished by defining the appropriate values in
+ <filename>/boot/device.hints</filename>, e.g.:</para>
-<programlisting>hint.pcm.0.vol="50"</programlisting>
+ <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>
</sect2>
</sect1>
- <sect1 id="sound-mp3">
- <sect1info>
- <authorgroup>
- <author>
- <firstname>Chern</firstname>
- <surname>Lee</surname>
- <contrib>Contributed by </contrib>
- </author>
- </authorgroup>
- <!-- 11 Sept 2001 -->
- </sect1info>
+<sect1 id="sound-mp3">
+ <sect1info>
+ <authorgroup>
+ <author>
+ <firstname>Chern</firstname>
+ <surname>Lee</surname>
+ <contrib>Contributed by </contrib>
+ </author>
+ </authorgroup>
+ <!-- 11 Sept 2001 -->
+ </sect1info>
<title>MP3 Audio</title>
@@ -507,27 +525,29 @@ pcm7: <HDA Realtek ALC889 PCM #3 Digi
<para>By far, the most popular X11 MP3 player is
<application>XMMS</application> (X Multimedia System).
<application>Winamp</application>
- skins can be used with <application>XMMS</application> since the
- GUI is almost identical to that of Nullsoft's
+ skins can be used with <application>XMMS</application> since
+ the GUI is almost identical to that of Nullsoft's
<application>Winamp</application>.
<application>XMMS</application> also has native plug-in
support.</para>
- <para><application>XMMS</application> can be installed from the
- <filename role="package">multimedia/xmms</filename> port or package.</para>
+ <para><application>XMMS</application> can be installed from
+ the <filename role="package">multimedia/xmms</filename> port
+ or package.</para>
<para><application>XMMS</application>'s interface is intuitive,
with a playlist, graphic equalizer, and more. Those familiar
with <application>Winamp</application> will find
<application>XMMS</application> simple to use.</para>
- <para>The <filename role="package">audio/mpg123</filename> port is an alternative,
- command-line MP3 player.</para>
+ <para>The <filename role="package">audio/mpg123</filename> port
+ is an alternative, command-line MP3 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>
+ 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>
<screen>&prompt.root; <userinput>mpg123 -a <devicename>/dev/dsp1.0</devicename> <replaceable>Foobar-GreatestHits.mp3</replaceable></userinput>
@@ -541,8 +561,7 @@ THIS SOFTWARE COMES WITH ABSOLUTELY NO W
Playing MPEG stream from Foobar-GreatestHits.mp3 ...
-MPEG 1.0 layer III, 128 kbit/s, 44100 Hz joint-stereo
-</screen>
+MPEG 1.0 layer III, 128 kbit/s, 44100 Hz joint-stereo</screen>
</sect2>
<sect2 id="rip-cd">
@@ -574,7 +593,7 @@ MPEG 1.0 layer III, 128 kbit/s, 44100 Hz
<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>
+ -scanbus</command>.</para>
<para>To rip individual tracks, make use of the
<option>-t</option> option as shown:</para>
@@ -587,9 +606,10 @@ MPEG 1.0 layer III, 128 kbit/s, 44100 Hz
<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>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>
</sect2>
@@ -599,10 +619,13 @@ MPEG 1.0 layer III, 128 kbit/s, 44100 Hz
<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>
+ <filename role="package">audio/lame</filename> in the ports
+ tree.</para>
<para>Using the ripped WAV files, the following command will
- convert <filename><replaceable>audio01.wav</replaceable></filename> to
+ convert
+ <filename><replaceable>audio01.wav</replaceable></filename>
+ to
<filename><replaceable>audio01.mp3</replaceable></filename>:</para>
<screen>&prompt.root; <userinput>lame -h -b <replaceable>128</replaceable> \
@@ -614,9 +637,9 @@ 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
+ <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
but a little slower</quote> mode. The options beginning with
@@ -632,8 +655,8 @@ MPEG 1.0 layer III, 128 kbit/s, 44100 Hz
<para>In order to burn an audio CD from MP3s, they must be
converted to a non-compressed WAV format. Both
<application>XMMS</application> and
- <application>mpg123</application> support the output of MP3 to
- an uncompressed file format.</para>
+ <application>mpg123</application> support the output of MP3
+ to an uncompressed file format.</para>
<para>Writing to Disk in <application>XMMS</application>:</para>
@@ -685,58 +708,60 @@ MPEG 1.0 layer III, 128 kbit/s, 44100 Hz
</step>
</procedure>
- <para>Writing to stdout in <application>mpg123</application>:</para>
+ <para>Writing to stdout in
+ <application>mpg123</application>:</para>
<procedure>
<step>
- <para>Run <command>mpg123 -s <replaceable>audio01.mp3</replaceable>
- > <replaceable>audio01.pcm</replaceable></command></para>
+ <para>Run <command>mpg123 -s
+ <replaceable>audio01.mp3</replaceable> >
+ <replaceable>audio01.pcm</replaceable></command></para>
</step>
</procedure>
<para><application>XMMS</application> writes a file in the WAV
format, while <application>mpg123</application> converts the
MP3 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
+ 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 installed from
- the <filename role="package">audio/sox</filename> port or
- package):</para>
+ file. You can simply remove the header of a WAV file with
+ the utility <application>SoX</application> (it 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>Read <xref linkend="creating-cds"/> for more information on using a
- CD burner in FreeBSD.</para>
+ <para>Read <xref linkend="creating-cds"/> for more information
+ on using a CD burner in FreeBSD.</para>
</sect2>
- </sect1>
+ </sect1>
- <sect1 id="video-playback">
- <sect1info>
- <authorgroup>
- <author>
- <firstname>Ross</firstname>
- <surname>Lippert</surname>
- <contrib>Contributed by </contrib>
- </author>
- </authorgroup>
- <!-- 5 June 2002 -->
- </sect1info>
+ <sect1 id="video-playback">
+ <sect1info>
+ <authorgroup>
+ <author>
+ <firstname>Ross</firstname>
+ <surname>Lippert</surname>
+ <contrib>Contributed by </contrib>
+ </author>
+ </authorgroup>
+ <!-- 5 June 2002 -->
+ </sect1info>
- <title>Video Playback</title>
+ <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>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 <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>
+ card you have 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
@@ -745,7 +770,7 @@ MPEG 1.0 layer III, 128 kbit/s, 44100 Hz
name hardcoded in them, you might find it useful to make
symbolic links to the proper devices:</para>
- <screen>&prompt.root; <userinput>ln -sf /dev/acd0 /dev/dvd</userinput>
+ <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;,
@@ -765,7 +790,7 @@ link acd0 rdvd</programlisting>
recommended that the values of some &man.sysctl.8; variables
should be increased:</para>
- <programlisting>kern.ipc.shmmax=67108864
+ <programlisting>kern.ipc.shmmax=67108864
kern.ipc.shmall=32768</programlisting>
<sect2 id="video-interface">
@@ -778,48 +803,55 @@ kern.ipc.shmall=32768</programlisting>
<para>There are several possible ways to display video under X11.
What will really work 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. 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>
<para>A list of common video interfaces:</para>
<orderedlist>
- <listitem>
- <para>X11: normal X11 output using shared memory.</para>
- </listitem>
- <listitem>
- <para>XVideo: an extension to the X11
- interface which supports video in any X11 drawable.</para>
- </listitem>
- <listitem>
- <para>SDL: the Simple Directmedia Layer.</para>
- </listitem>
- <listitem>
- <para>DGA: the Direct Graphics Access.</para>
- </listitem>
- <listitem>
- <para>SVGAlib: low level console graphics layer.</para>
- </listitem>
+ <listitem>
+ <para>X11: normal X11 output using shared memory.</para>
+ </listitem>
+
+ <listitem>
+ <para>XVideo: an extension to the X11 interface which supports
+ video in any X11 drawable.</para>
+ </listitem>
+
+ <listitem>
+ <para>SDL: the Simple Directmedia Layer.</para>
+ </listitem>
+
+ <listitem>
+ <para>DGA: the Direct Graphics Access.</para>
+ </listitem>
+
+ <listitem>
+ <para>SVGAlib: low level console graphics layer.</para>
+ </listitem>
</orderedlist>
<sect3 id="video-interface-xvideo">
- <title>XVideo</title>
+ <title>XVideo</title>
<para><application>&xorg;</application> has an extension called
- <emphasis>XVideo</emphasis> (aka Xvideo, aka Xv, aka xv) which
- allows video to be directly displayed in drawable objects
- through a special acceleration. This extension provides very
- good quality playback even on low-end machines.</para>
+ <emphasis>XVideo</emphasis> (aka Xvideo, aka Xv, aka xv) which
+ allows video to be directly displayed in drawable objects
+ through a special acceleration. This extension provides very
+ good quality playback even on low-end machines.</para>
- <para>To check whether the extension is running,
- use <command>xvinfo</command>:</para>
+ <para>To check whether the extension is running, use
+ <command>xvinfo</command>:</para>
- <screen>&prompt.user; <userinput>xvinfo</userinput></screen>
+ <screen>&prompt.user; <userinput>xvinfo</userinput></screen>
- <para>XVideo is supported for your card if the result looks like:</para>
-<screen>X-Video Extension version 2.2
-screen #0
+ <para>XVideo is supported for your card if the result looks
+ like:</para>
+
+ <screen>X-Video Extension version 2.2
+ screen #0
Adaptor #0: "Savage Streams Engine"
number of ports: 1
port base: 43
@@ -887,12 +919,13 @@ screen #0
depth: 1
red, green, blue masks: 0x0, 0x0, 0x0</screen>
- <para>Also note that the formats listed (YUV2, YUV12, etc) are not
- present with every implementation of XVideo and their absence may
- hinder some players.</para>
+ <para>Also note that the formats listed (YUV2, YUV12, etc) are
+ not present with every implementation of XVideo and their
+ absence may hinder some players.</para>
<para>If the result looks like:</para>
-<screen>X-Video Extension version 2.2
+
+ <screen>X-Video Extension version 2.2
screen #0
no adaptors present</screen>
@@ -904,11 +937,11 @@ no adaptors present</screen>
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>
+ linkend="video-further-reading"/>.</para>
- </sect3>
+ </sect3>
- <sect3 id="video-interface-SDL">
+ <sect3 id="video-interface-SDL">
<title>Simple Directmedia Layer</title>
<para>The Simple Directmedia Layer, SDL, was intended to be a
@@ -918,11 +951,12 @@ no adaptors present</screen>
low-level abstraction to the hardware which can sometimes be
more efficient than the X11 interface.</para>
- <para>The SDL can be found at <filename role="package">devel/sdl12</filename>.</para>
+ <para>The SDL can be found at <filename
+ role="package">devel/sdl12</filename>.</para>
- </sect3>
+ </sect3>
- <sect3 id="video-interface-DGA">
+ <sect3 id="video-interface-DGA">
<title>Direct Graphics Access</title>
<para>Direct Graphics Access is an X11 extension which allows
@@ -936,9 +970,8 @@ no adaptors present</screen>
changes the colors of the display whenever a key is pressed. To
quit, use <keycap>q</keycap>.</para>
- </sect3>
-
- </sect2>
+ </sect3>
+</sect2>
<sect2 id="video-ports">
<title>Ports and Packages Dealing with Video</title>
@@ -958,101 +991,105 @@ no adaptors present</screen>
beta-quality. Some of the problems that you may encounter with
video packages on FreeBSD include:</para>
- <orderedlist>
+ <orderedlist>
<listitem>
- <para>An application cannot playback a file which another
- application produced.</para>
+ <para>An application cannot playback a file which another
+ application produced.</para>
</listitem>
<listitem>
- <para>An application cannot playback a file which the
- application itself produced.</para>
+ <para>An application cannot playback a file which the
+ application itself produced.</para>
</listitem>
<listitem>
- <para>The same application on two different machines,
- rebuilt on each machine for that machine, plays back the same
- file differently.</para>
+ <para>The same application on two different machines,
+ rebuilt on each machine for that machine, plays back the
+ same file differently.</para>
</listitem>
<listitem>
- <para>A seemingly trivial filter like rescaling of the image
- size results in very bad artifacts from a buggy rescaling
- routine.</para>
+ <para>A seemingly trivial filter like rescaling of the image
+ size results in very bad artifacts from a buggy rescaling
*** DIFF OUTPUT TRUNCATED AT 1000 LINES ***
More information about the svn-doc-all
mailing list