From owner-svn-doc-projects@FreeBSD.ORG Wed Apr 24 20:49:20 2013 Return-Path: Delivered-To: svn-doc-projects@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 3AF99D85; Wed, 24 Apr 2013 20:49:20 +0000 (UTC) (envelope-from dru@FreeBSD.org) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) by mx1.freebsd.org (Postfix) with ESMTP id 2CB7F1DE1; Wed, 24 Apr 2013 20:49:20 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.6/8.14.6) with ESMTP id r3OKnKYi021362; Wed, 24 Apr 2013 20:49:20 GMT (envelope-from dru@svn.freebsd.org) Received: (from dru@localhost) by svn.freebsd.org (8.14.6/8.14.5/Submit) id r3OKnKKW021361; Wed, 24 Apr 2013 20:49:20 GMT (envelope-from dru@svn.freebsd.org) Message-Id: <201304242049.r3OKnKKW021361@svn.freebsd.org> From: Dru Lavigne Date: Wed, 24 Apr 2013 20:49:20 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-projects@freebsd.org Subject: svn commit: r41492 - projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/multimedia X-SVN-Group: doc-projects MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-projects@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: SVN commit messages for doc projects trees List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Apr 2013 20:49:20 -0000 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 @@ Synopsis - FreeBSD supports a wide variety of sound cards, allowing you - to enjoy high fidelity output from your computer. This includes + &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. - - 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 audio/sox. However, the software - landscape in this area is changing rapidly. - - This chapter will describe the necessary steps to configure - your sound card. The configuration and installation of X11 - () has already taken care of the - hardware issues for your video card, though there may be some - tweaks to apply for better playback. + 3 (MP3), Waveform Audio File + (WAV), Ogg Vorbis, and other + formats. The &os; Ports Collection contains many + applications for editing recorded audio, adding sound + effects, and controlling attached MIDI devices. + + &os; also supports the playback of video files and DVDs. + The &os; Ports Collection contains applications to encode, + convert, and playback various video media. + + 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. - After reading this chapter, you will know: + After reading this chapter, you will know how to: - How to configure your system so that your sound card - is recognized. + Configure a sound card + on os;. - Methods to test whether your card is working. + Troubleshoot the sound setup. - How to troubleshoot your sound setup. + Playback and encode MP3s and other audio. - How to playback and encode MP3s and other audio. + Prepare a &os; system for video playback. - How video is supported by the X server. + Playback DVDs, .mpg, and + .avi files. - Some video player/encoder ports which give good - results. + Rip CD and DVD content into files. - How to playback DVDs, .mpg and - .avi files. + Configure a TV card. - How to rip CD and DVD content into files. + Install and setup MythTV on &os; - How to configure a TV card. + Configure an image scanner. @@ -100,10 +94,9 @@ - Trying to mount audio CDs with the &man.mount.8; command - will result in an error, at least, and a kernel - panic, at worst. These media have specialized - encodings which differ from the usual ISO-filesystem. + Audio CDs have specialized encodings which differ from the + usual ISO-filesystem. This means that they should not be + mounted using &man.mount.8;. @@ -134,101 +127,101 @@ Configuring the System PCI - ISA sound cards - 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 Hardware Notes to - see if your card is supported. The Hardware Notes will - also mention which driver supports your card. + 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 Hardware + Notes to see if the card is supported and which &os; + driver it uses. kernel configuration - 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: + 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: &prompt.root; kldload snd_emu10k1 - or by adding the appropriate line to the file - /boot/loader.conf like this: + To automate the loading of this driver at boot time, add the + driver to + /boot/loader.conf. The line for + this driver is: snd_emu10k1_load="YES" - These examples are for a Creative &soundblaster; Live! sound - card. Other available loadable sound modules are listed in + Other available sound modules are listed in /boot/defaults/loader.conf. - If you are not sure which driver to use, you may try to load + When unsure which driver to use, load the snd_driver module: &prompt.root; kldload snd_driver - 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 - /boot/loader.conf facility. - - If you wish to find out the driver selected for your - soundcard after loading the snd_driver - metadriver, you may check the /dev/sndstat - file with the cat /dev/sndstat - command. - - 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 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 + /boot/loader.conf. + + To determine which driver was selected for the + sound card after loading the snd_driver + metadriver, type cat /dev/sndstat. + + 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 . Configuring a Custom Kernel with Sound Support - 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: + When using a custom kernel to provide sound support, make + sure that the audio framework driver +exists in the custom kernel configuration file: device sound - Next, you have to add the support for your sound card. + 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 Hardware Notes, 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: + 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: device snd_emu10k1 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 /usr/src/sys/conf/NOTES - file. + found in /usr/src/sys/conf/NOTES. - 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 /boot/device.hints file. During the - boot process, the &man.loader.8; will read this file and pass + Non-PnP ISA sound cards may require the IRQ and I/O port + settings of the card to be added +to /boot/device.hints. 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 - snd_sb16. For this card the following + snd_sb16. For this card, the following lines must be added to the kernel configuration file: device snd_sbc device snd_sb16 - and these to + If the card uses the 0x220 I/O port and + IRQ 5, these lines must also be added to /boot/device.hints: hint.sbc.0.at="isa" @@ -240,14 +233,14 @@ hint.sbc.0.flags="0x15" In this case, the card uses the 0x220 I/O port and the IRQ 5. - The syntax used in the - /boot/device.hints file is covered in the - &man.sound.4; driver manual page and the manual page - for the driver in question. + The syntax used in + /boot/device.hints is described in + &man.sound.4; and the manual page + for the driver of the sound card. 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. @@ -255,16 +248,17 @@ hint.sbc.0.flags="0x15" Testing the Sound Card - 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: + 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: 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> - The status of the sound card may be checked via the - /dev/sndstat file: + The status of the sound card may also be checked +using this command: &prompt.root; cat /dev/sndstat 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) - The output from your system may vary. If no + The output may vary between systems. If no pcm 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 . - 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 + 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;: &prompt.user; cdcontrol -f /dev/acd0 play 1 Various applications, such as audio/workman can provide a - friendlier interface. You may want to install an application - such as audio/mpg123 to + role="package">audio/workman provide a + friendlier interface. The audio/mpg123 port can be installed to listen to MP3 audio files. - Another quick way to test the card is sending data - to /dev/dsp, like this: + Another quick way to test the card is to send data + to /dev/dsp: &prompt.user; cat filename > /dev/dsp where filename can - be any file. This command line should produce some noise, - confirming the sound card is actually working. + be any file. This command should produce some noise, + confirming that the sound card is actually working. - The device nodes /dev/dsp* will be - created automatically when needed. If they are not used, they + The /dev/dsp* 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;. - 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. + Sound card mixer levels can be changed using &man.mixer.8;. + More details can be found in &man.mixer.8;. Common Problems @@ -370,8 +365,8 @@ kld snd_ich (1p/2r/0v channels duplex de Another issue is that modern graphics cards often come with their own sound driver, for use with HDMI 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 dmesg and look for pcm. The output looks something like @@ -397,16 +392,17 @@ pcm7: <HDA Realtek ALC889 PCM #3 Digi Here the graphics card (NVidia) has been enumerated before the sound card (Realtek - ALC889). To use the sound card as default playback - device, change hw.snd.default_unit to the - unit that should be used for playback, enter the - following: + ALC889). To use the sound card as the default +playback + device, change hw.snd.default_unit to the + unit that should be used for playback: &prompt.root; sysctl hw.snd.default_unit=n Here, n is the number of the sound - device to use, in this example 4. You can - make this change permanent by adding the following line to + device to use. In this example, it should be +4. + Make this change permanent by adding the following line to /etc/sysctl.conf: hw.snd.default_unit=4 @@ -426,20 +422,15 @@ pcm7: <HDA Realtek ALC889 PCM #3 Digi Utilizing Multiple Sound Sources It is often desirable to have multiple sources of sound that - are able to play simultaneously, such as when - esound or - artsd do not support sharing of the - sound device with a certain application. - - FreeBSD lets you do this through Virtual Sound - Channels, 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 +Virtual Sound + Channels, 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. - To set the number of virtual channels, there are three - sysctl knobs which, if you are the root - user, can be set like this: + To set the number of virtual channels, three + &man.sysctl.8; knobs are available: &prompt.root; sysctl dev.pcm.0.play.vchans=4 &prompt.root; sysctl dev.pcm.0.rec.vchans=4 @@ -450,19 +441,20 @@ pcm7: <HDA Realtek ALC889 PCM #3 Digi dev.pcm.0.play.vchans=4 and dev.pcm.0.rec.vchans=4 are the number of virtual channels pcm0 has for playback - and recording, and are configurable once a device has been + and recording, and are configurable after a device has been attached. hw.snd.maxautovchans is the number of virtual channels a new audio device is given when it is attached using &man.kldload.8;. Since the pcm module can be loaded independently of the hardware drivers, hw.snd.maxautovchans - 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. - You cannot change the number of virtual channels for a - device while it is in use. First close any programs using + 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. @@ -486,18 +478,20 @@ pcm7: <HDA Realtek ALC889 PCM #3 Digi Setting Default Values for Mixer Channels 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 - /boot/device.hints, e.g.: + /boot/device.hints, as seen in this +example: hint.pcm.0.vol="50" This will set the volume channel to a default value of - 50 when the &man.pcm.4; module is loaded. + 50 when the &man.pcm.4; module is +loaded. @@ -515,18 +509,18 @@ pcm7: <HDA Realtek ALC889 PCM #3 Digi MP3 Audio - MP3 (MPEG Layer 3 Audio) accomplishes near CD-quality sound, - leaving no reason to let your FreeBSD workstation fall short of - its offerings. + This section describes some MP3 + players available for &os;, how to rip audio CD tracks, and + how to encode and decode MP3s. MP3 Players - By far, the most popular X11 MP3 player is - XMMS (X Multimedia System). + A popular graphical MP3 player is + XMMS. Winamp skins can be used with XMMS since - the GUI is almost identical to that of Nullsoft's + the interface is almost identical to that of Nullsoft's Winamp. XMMS also has native plug-in support. @@ -541,14 +535,17 @@ pcm7: <HDA Realtek ALC889 PCM #3 Digi XMMS simple to use. The audio/mpg123 port - is an alternative, command-line MP3 player. + provides an alternative, command-line MP3 +player. mpg123 can be run by specifying - the sound device and the MP3 file on the command line. - Assuming your audio device is - /dev/dsp1.0 and you want to play the - MP3 file Foobar-GreatestHits.mp3 - you would enter the following: + the sound device and the MP3 file on the +command line. + Assuming the audio device is + /dev/dsp1.0 and the + MP3 file is +Foobar-GreatestHits.mp3, + enter the following to play the file: &prompt.root; mpg123 -a /dev/dsp1.0 Foobar-GreatestHits.mp3 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 Ripping CD Audio Tracks - 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 + Before encoding a CD or CD track to +MP3, the audio data on + the CD must be ripped to the hard drive. This is done by + copying the raw CD + Digital Audio (CDDA) data to +WAV files. - The cdda2wav tool, which is a part of + The cdda2wav tool, which is installed +with the sysutils/cdrtools suite, is used for ripping audio information from CDs and the information associated with them. With the audio CD in the drive, the following command can - be issued (as root) to rip an entire CD - into individual (per track) WAV files: + be issued as root to rip an entire CD + into individual (per track) WAV +files: &prompt.root; cdda2wav -D 0,1,0 -B + The + indicates the SCSI device 0,1,0, + which corresponds to the output of cdrecord + -scanbus. + cdda2wav 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 &prompt.root; cdda2wav -D /dev/acd0 -t 7 - The - indicates the SCSI device 0,1,0, - which corresponds to the output of cdrecord - -scanbus. - To rip individual tracks, make use of the - option as shown: + as shown: &prompt.root; cdda2wav -D 0,1,0 -t 7 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: &prompt.root; cdda2wav -D 0,1,0 -t 1+7 - The utility &man.dd.1; can also be used to extract audio - tracks on ATAPI drives, read for more information on - that possibility. + &man.dd.1; can also be used to extract audio + tracks on ATAPI drives, as described in . Encoding MP3s - Nowadays, the mp3 encoder of choice is - lame. - Lame can be found at - audio/lame in the ports - tree. - - Using the ripped WAV files, the following command will - convert + + Lame is a popular +MP3 encoder which can be installed from the + audio/lame port. Due to + licensing restrictions, a package is not available. + + The following command will + convert the ripped + WAV files audio01.wav to audio01.mp3: @@ -637,25 +639,29 @@ MPEG 1.0 layer III, 128 kbit/s, 44100 Hz --tg "Genre" \ audio01.wav audio01.mp3 - 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 turns on the higher quality + 128 kbits is a standard MP3 +bitrate. The 160 and 192 bitrates provide higher quality. The higher + the bitrate, the larger the size of the resulting + MP3. + turns on the higher quality but a little slower mode. The options beginning with indicate ID3 tags, which usually contain - song information, to be embedded within the MP3 file. - Additional encoding options can be found by consulting the - lame man page. + song information, to be embedded within the +MP3 file. + Additional encoding options can be found in the + lame manual page. Decoding MP3s - In order to burn an audio CD from MP3s, they must be - converted to a non-compressed WAV format. Both + In order to burn an audio CD from MP3s, +they must first be + converted to a non-compressed WAV format. +Both XMMS and - mpg123 support the output of MP3 + mpg123 support the output of +MP3 to an uncompressed file format. Writing to Disk in XMMS: @@ -666,12 +672,12 @@ MPEG 1.0 layer III, 128 kbit/s, 44100 Hz - Right-click on the window to bring up the + Right-click the window to bring up the XMMS menu. - Select Preference under + Select Preferences under Options. @@ -685,26 +691,31 @@ MPEG 1.0 layer III, 128 kbit/s, 44100 Hz - Enter (or choose browse) a directory to write the + Enter or browse to a directory to write the uncompressed files to. - Load the MP3 file into XMMS + Load the MP3 file into +XMMS as usual, with volume at 100% and EQ settings turned off. - Press Play — + Press Play. The XMMS will appear as if it is - playing the MP3, but no music will be heard. It is - actually playing the MP3 to a file. + playing the MP3, but no music will be +heard. It is + actually playing the MP3 to a +file. - Be sure to set the default Output Plugin back to what - it was before in order to listen to MP3s again. + When finished, be sure to set the default Output +Plugin back to what + it was before in order to listen to +MP3s again. @@ -719,22 +730,28 @@ MPEG 1.0 layer III, 128 kbit/s, 44100 Hz - XMMS writes a file in the WAV + XMMS writes a file in the +WAV format, while mpg123 converts the - MP3 into raw PCM audio data. Both of these formats can be + MP3 into raw PCM audio data. Both of these +formats can be used with cdrecord 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 SoX (it can be + CDs, whereas &man.burncd.8; requires a raw Pulse-Code +Modulation (PCM. When using + WAV files, there will be a small tick +sound at the + beginning of each track. This sound is the header of the +WAV + file. One can remove the header with + SoX, which can be installed from the audio/sox port or package): + role="package">audio/sox port or package: &prompt.user; sox -t wav -r 44100 -s -w -c 2 track.wav track.raw - Read for more information - on using a CD burner in FreeBSD. + Refer to for more +information + on using a CD burner in &os;. @@ -752,43 +769,45 @@ MPEG 1.0 layer III, 128 kbit/s, 44100 Hz Video Playback - 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. - - Before you begin, you should know the model of the video - card you have and the chip it uses. While + Before configuring video playback, determine the model +of the video + card and the chip it uses. While &xorg; 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. - - 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 - /dev/dvd by default, or have this device - name hardcoded in them, you might find it useful to make + a list of extensions supported by the +&xorg; server using the card, run + &man.xdpyinfo.1; while &xorg; is +running. + + 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 + /dev/dvd by default, or +have this device + name hardcoded in them, it might be useful to make symbolic links to the proper devices: &prompt.root; ln -sf /dev/acd0 /dev/dvd &prompt.root; ln -sf /dev/acd0 /dev/rdvd - 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 + 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 /etc/devfs.conf: link acd0 dvd link acd0 rdvd - Additionally, DVD decryption, which requires invoking - special DVD-ROM functions, requires write permission on the DVD + DVD decryption invokes + special DVD-ROM functions and requires write permission on the +DVD devices. - To enhance the shared memory X11 interface, it is - recommended that the values of some &man.sysctl.8; variables - should be increased: + To enhance the shared memory +&xorg; interface, it is + recommended to increase the values of these &man.sysctl.8; +variables: kern.ipc.shmmax=67108864 kern.ipc.shmall=32768 @@ -800,32 +819,34 @@ kern.ipc.shmall=32768 SDL DGA - There are several possible ways to display video under X11. - What will really work is largely hardware dependent. Each + There are several possible ways to display video under +&xorg;. + 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 &xorg;, there may be - significant improvement. + different hardware. - A list of common video interfaces: + Common video interfaces include: - X11: normal X11 output using shared memory. + &xorg;: normal output +using shared memory. - XVideo: an extension to the X11 interface which supports - video in any X11 drawable. + XVideo: an extension to the +&xorg; interface which supports + video in any drawable object. - SDL: the Simple Directmedia Layer. + SDL: the Simple Directmedia +Layer. - DGA: the Direct Graphics Access. + DGA: the Direct Graphics +Access. @@ -837,9 +858,10 @@ kern.ipc.shmall=32768 XVideo &xorg; has an extension called - XVideo (aka Xvideo, aka Xv, aka xv) which + XVideo, 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. To check whether the extension is running, use @@ -847,7 +869,7 @@ kern.ipc.shmall=32768 &prompt.user; xvinfo - XVideo is supported for your card if the result looks + XVideo is supported for the card if the result looks like: X-Video Extension version 2.2 @@ -919,7 +941,7 @@ kern.ipc.shmall=32768 depth: 1 red, green, blue masks: 0x0, 0x0, 0x0 - Also note that the formats listed (YUV2, YUV12, etc) are + The formats listed, such as YUV2 and YUV12, are not present with every implementation of XVideo and their absence may hinder some players. @@ -929,46 +951,48 @@ kern.ipc.shmall=32768 screen #0 no adaptors present - Then XVideo is probably not supported for your card. - - 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 . + 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. Simple Directmedia Layer - 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 + SDL 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 SDL +layer provides a low-level abstraction to the hardware which can sometimes be - more efficient than the X11 interface. + more efficient than the &xorg; +interface. - The SDL can be found at devel/sdl12. + SDL can be installed using the devel/sdl12 package or port. Direct Graphics Access - 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 + DGA is an +&xorg; extension which allows + a program to bypass the &xorg; server +and directly alter the + framebuffer. Because it relies on a low level memory mapping, +programs using it must be run as root. - The DGA extension can be tested and benchmarked by + The DGA extension can be tested and +benchmarked using &man.dga.1;. When dga is running, it changes the colors of the display whenever a key is pressed. To - quit, use q. + quit, press q. @@ -979,17 +1003,16 @@ no adaptors present video ports video packages - 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. *** DIFF OUTPUT TRUNCATED AT 1000 LINES ***