From owner-svn-doc-projects@FreeBSD.ORG Wed Apr 24 22:34:32 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 E92BEDC6; Wed, 24 Apr 2013 22:34:32 +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 DABCF11A9; Wed, 24 Apr 2013 22:34:32 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.6/8.14.6) with ESMTP id r3OMYW62059046; Wed, 24 Apr 2013 22:34:32 GMT (envelope-from dru@svn.freebsd.org) Received: (from dru@localhost) by svn.freebsd.org (8.14.6/8.14.5/Submit) id r3OMYWFp059045; Wed, 24 Apr 2013 22:34:32 GMT (envelope-from dru@svn.freebsd.org) Message-Id: <201304242234.r3OMYWFp059045@svn.freebsd.org> From: Dru Lavigne Date: Wed, 24 Apr 2013 22:34:32 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-projects@freebsd.org Subject: svn commit: r41494 - 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 22:34:33 -0000 Author: dru Date: Wed Apr 24 22:34:32 2013 New Revision: 41494 URL: http://svnweb.freebsd.org/changeset/doc/41494 Log: White space fix only. Translators can ignore. Approved by: gjb (mentor) Modified: projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/multimedia/chapter.xml Modified: projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/multimedia/chapter.xml ============================================================================== --- projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/multimedia/chapter.xml Wed Apr 24 21:47:19 2013 (r41493) +++ projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/multimedia/chapter.xml Wed Apr 24 22:34:32 2013 (r41494) @@ -25,17 +25,16 @@ to enjoy high fidelity output from a &os; system. This includes the ability to record and playback audio in the MPEG Audio Layer 3 (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. + (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 + 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. @@ -44,8 +43,7 @@ - Configure a sound card - on os;. + Configure a sound card on os;. @@ -140,65 +138,56 @@ configuration - 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: + 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 To automate the loading of this driver at boot time, add the - driver to - /boot/loader.conf. The line for + driver to /boot/loader.conf. The line for this driver is: snd_emu10k1_load="YES" Other available sound modules are listed in - /boot/defaults/loader.conf. - When unsure which driver to use, load - the snd_driver module: + /boot/defaults/loader.conf. When unsure + which driver to use, load the snd_driver + module: &prompt.root; kldload snd_driver This is a metadriver which loads all of the most common -sound drivers - and can be used to speed up the search for the correct driver. -It - is also possible to load all sound drivers by adding the -metadriver to + sound drivers and can be used to speed up the search for the + correct driver. It is also possible to load all sound drivers + by adding the metadriver to /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 . + 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 When using a custom kernel to provide sound support, make - sure that the audio framework driver -exists in the custom kernel configuration file: + sure that the audio framework driver exists in the custom kernel + configuration file: device sound - Next, add support for the sound card. - Therefore, you need to know which driver supports the card. - To - continue the example of the Creative &soundblaster; Live! - sound card from the previous section, use the following line - in the custom kernel configuration file: + Next, add support for the sound card. Therefore, you need + to know which driver supports the card. To continue the example + of the Creative &soundblaster; Live! sound card from the + previous section, use the following line in the custom kernel + configuration file: device snd_emu10k1 @@ -208,10 +197,10 @@ exists in the custom kernel configuratio found in /usr/src/sys/conf/NOTES. 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 + 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 @@ -235,13 +224,13 @@ hint.sbc.0.flags="0x15" The syntax used in /boot/device.hints is described in - &man.sound.4; and the manual page - for the driver of the sound card. + &man.sound.4; and the manual page for the driver of the sound + card. The settings shown above are the defaults. In some cases, the IRQ or other settings may need to be changed to - match the card. Refer to &man.snd.sbc.4; for more - information about this card. + match the card. Refer to &man.snd.sbc.4; for more information + about this card. @@ -251,14 +240,14 @@ hint.sbc.0.flags="0x15" 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: + 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 also be checked -using this command: + The status of the sound card may also be checked using this + command: &prompt.root; cat /dev/sndstat FreeBSD Audio Driver (newpcm) @@ -272,35 +261,31 @@ kld snd_ich (1p/2r/0v channels duplex de device driver was chosen. Common problems are listed in . - 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 + 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 provide a - friendlier interface. The audio/mpg123 port can be installed to - listen to MP3 audio files. + 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 to send data - to /dev/dsp: + 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 should produce some noise, - confirming that the sound card is actually working. + be any file. This command should produce some noise, confirming + that the sound card is actually working. The /dev/dsp* device nodes will -be - created automatically as needed. When not in use, they + be created automatically as needed. When not in use, they do not exist and will not appear in the output of &man.ls.1;. @@ -351,9 +336,8 @@ be xxx: can't open /dev/dsp! Check with fstat | grep - dsp - if another application is holding the device open. - Noteworthy troublemakers are + dsp if another application is holding the + device open. Noteworthy troublemakers are esound and KDE's sound support. @@ -365,9 +349,9 @@ be 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 sound card and the - sound card will subsequently not be used as the default - playback device. To check if this is the case, run + sometimes be enumerated before the sound card and the sound + card will subsequently not be used as the default playback + device. To check if this is the case, run dmesg and look for pcm. The output looks something like this: @@ -393,16 +377,15 @@ 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 the default -playback - device, change hw.snd.default_unit to the - unit that should be used for playback: + 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, it should be -4. - Make this change permanent by adding the following line to + 4. Make this change permanent by adding + the following line to /etc/sysctl.conf: hw.snd.default_unit=4 @@ -422,12 +405,10 @@ playback Utilizing Multiple Sound Sources It is often desirable to have multiple sources of sound that - 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. + 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, three &man.sysctl.8; knobs are available: @@ -448,20 +429,19 @@ playback pcm module can be loaded independently of the hardware drivers, hw.snd.maxautovchans indicates how many virtual channels will be given to devices -when they are attached. Refer to &man.pcm.4; - for more information. + when they are attached. Refer to &man.pcm.4; for more + information. - The number of virtual channels for a - device cannot be changed 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. The correct pcm device will - automatically be allocated transparently to a program - that requests /dev/dsp0. + automatically be allocated transparently to a program that + requests /dev/dsp0. @@ -479,19 +459,19 @@ programs using The default values for the different mixer channels are hardcoded in the source code of the &man.pcm.4; driver. There - are many different applications and daemons that allow - values to be set for the mixer that are remembered between - invocations, but this is not a clean solution. It is possible - to set default mixer values at the driver level. This - is accomplished by defining the appropriate values in + are many different applications and daemons that allow values to + be set for the mixer that are remembered between invocations, + but this is not a clean solution. It is possible to set default + mixer values at the driver level. This is accomplished by + defining the appropriate values in /boot/device.hints, as seen in this -example: + 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. + loaded. @@ -536,16 +516,15 @@ loaded. The audio/mpg123 port provides an alternative, command-line MP3 -player. + player. mpg123 can be run by specifying the sound device and the MP3 file on the -command line. - Assuming the audio device is + 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: + 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. @@ -565,23 +544,20 @@ 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 to the hard drive. This is done by - copying the raw CD + 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. + WAV files. The cdda2wav tool, which is installed -with - the sysutils/cdrtools + 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: + files: &prompt.root; cdda2wav -D 0,1,0 -B @@ -590,10 +566,10 @@ files: 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 - example, to rip track 7 from an IDE drive: + 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 example, + to rip track 7 from an IDE drive: &prompt.root; cdda2wav -D /dev/acd0 -t 7 @@ -608,8 +584,8 @@ files: &prompt.root; cdda2wav -D 0,1,0 -t 1+7 - &man.dd.1; can also be used to extract audio - tracks on ATAPI drives, as described in &man.dd.1; can also be used to extract audio tracks on + ATAPI drives, as described in . @@ -619,12 +595,11 @@ files: Lame is a popular -MP3 encoder which can be installed from the + 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 + The following command will convert the ripped WAV files audio01.wav to @@ -640,29 +615,26 @@ files: audio01.wav audio01.mp3 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 in the - lame manual page. + 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 in the lame manual + page. Decoding MP3s In order to burn an audio CD from MP3s, -they must first be - converted to a non-compressed WAV format. -Both + they must first be converted to a non-compressed + WAV format. Both XMMS and mpg123 support the output of -MP3 - to an uncompressed file format. + MP3 to an uncompressed file format. Writing to Disk in XMMS: @@ -697,25 +669,22 @@ Both Load the MP3 file into -XMMS - as usual, with volume at 100% and EQ settings turned - off. + XMMS as usual, with volume at + 100% and EQ settings turned off. 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. + heard. It is actually playing the MP3 + to a file. When finished, be sure to set the default Output -Plugin back to what - it was before in order to listen to -MP3s again. + Plugin back to what it was before in order to listen to + MP3s again. @@ -731,27 +700,23 @@ Plugin back to what XMMS writes a file in the -WAV - format, while mpg123 converts the + WAV format, while + mpg123 converts the MP3 into raw PCM audio data. Both of these -formats can be - used with cdrecord to create audio - CDs, whereas &man.burncd.8; requires a raw Pulse-Code -Modulation (PCM. When using + formats can be used with cdrecord + to create audio 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 + 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: &prompt.user; sox -t wav -r 44100 -s -w -c 2 track.wav track.raw Refer to for more -information - on using a CD burner in &os;. + information on using a CD burner in &os;. @@ -770,44 +735,39 @@ information Video Playback Before configuring video playback, determine the model -of the video - card and the chip it uses. While + of the video card and the chip it uses. While &xorg; supports a wide variety of video cards, fewer give good playback performance. To obtain a list of extensions supported by the -&xorg; server using the card, run + &xorg; server using the card, run &man.xdpyinfo.1; while &xorg; is -running. + 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 + 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 - 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: + 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 - DVD decryption invokes - special DVD-ROM functions and requires write permission on the -DVD - devices. + DVD decryption invokes special DVD-ROM functions and + requires write permission on the DVD devices. To enhance the shared memory -&xorg; interface, it is + &xorg; interface, it is recommended to increase the values of these &man.sysctl.8; -variables: + variables: kern.ipc.shmmax=67108864 kern.ipc.shmall=32768 @@ -820,33 +780,32 @@ kern.ipc.shmall=32768 DGA 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. + &xorg;. What works is largely + hardware dependent. Each method described below will have + varying quality across different hardware. Common video interfaces include: - &xorg;: normal output -using shared memory. + &xorg;: normal output using + shared memory. XVideo: an extension to the -&xorg; interface which supports + &xorg; interface which supports video in any drawable object. SDL: the Simple Directmedia -Layer. + Layer. DGA: the Direct Graphics -Access. + Access. @@ -858,9 +817,8 @@ Access. XVideo &xorg; has an extension called - XVideo, also known as Xvideo, -Xv, and xv. It - allows video to be directly displayed in drawable objects + 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 good quality playback even on low-end machines. @@ -941,9 +899,9 @@ Xv, and xv. It depth: 1 red, green, blue masks: 0x0, 0x0, 0x0 - The formats listed, such as YUV2 and YUV12, are - not present with every implementation of XVideo and their - absence may hinder some players. + The formats listed, such as YUV2 and YUV12, are not present + with every implementation of XVideo and their absence may hinder + some players. If the result looks like: @@ -951,26 +909,24 @@ Xv, and xv. It screen #0 no adaptors present - XVideo is probably not supported for the card. This -means + 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. + video card and processor, one might still be able to have a + satisfying experience. Simple Directmedia Layer - 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 + 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 &xorg; -interface. + interface. SDL can be installed using the devel/sdl12 package or port. @@ -981,18 +937,16 @@ interface. Direct Graphics Access 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 + &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 using - &man.dga.1;. When dga is running, it - changes the colors of the display whenever a key is pressed. To - quit, press q. + benchmarked using &man.dga.1;. When dga is + running, it changes the colors of the display whenever a key is + pressed. To quit, press q. @@ -1004,15 +958,13 @@ benchmarked using video packages This section introduces some of the software available from -the - &os; Ports Collection which can be used for video -playback. - - Many of the video - applications which run on &os; were developed as &linux; - applications. Many of these applications are still - beta-quality. Some of the problems commonly encountered with - video packages on &os; include: + the &os; Ports Collection which can be used for video + playback. + + Many of the video applications which run on &os; were + developed as &linux; applications. Many of these applications + are still beta-quality. Some of the problems commonly + encountered with video packages on &os; include: @@ -1052,13 +1004,12 @@ playback. Many applications may also exhibit - &linux;-isms. There may be issues - resulting from the way some standard libraries are - implemented in the &linux; distributions, or some features of - the &linux; kernel which have been assumed by the authors of the - applications. These issues are not always noticed and worked - around by the port maintainers, which can lead to problems like - these: + &linux;-isms. There may be issues resulting from + the way some standard libraries are implemented in the &linux; + distributions, or some features of the &linux; kernel which have + been assumed by the authors of the applications. These issues + are not always noticed and worked around by the port + maintainers, which can lead to problems like these: @@ -1073,7 +1024,7 @@ playback. Relies on software which is not yet available in the -&os; Ports Collection. + &os; Ports Collection. @@ -1093,21 +1044,20 @@ playback. making MPlayer is available as a -package or port in multimedia/mplayer. -Several compile options are available and a variety of hardware + package or port in multimedia/mplayer. Several + compile options are available and a variety of hardware checks occur during the build process. For these reasons, some users prefer to build the port rather than install the - package. The available options will be displayed in - a menu after these commands are input: + package. The available options will be displayed in a + menu after these commands are input: &prompt.root; cd /usr/ports/multimedia/mplayer &prompt.root; make The menu options should be reviewed to determine the -type of - support to compile into the port. If an option is not - selected, MPlayer will not be + type of support to compile into the port. If an option is + not selected, MPlayer will not be able to display that type of video format. Use the arrow keys and spacebar to select the required formats. When finished, press Enter to continue the port @@ -1175,8 +1125,8 @@ type of including the WITH_DVD_DEVICE=/path/to/desired/device option. By default, the device is - /dev/acd0. More - details can be found in the port's + /dev/acd0. More details can be found + in the port's Makefile.options. @@ -1185,21 +1135,20 @@ type of -h, or read the manual page. Additional playback options include - , which engages fullscreen -mode, + , which engages fullscreen mode, and , which helps performance. Each user can add commonly used options to their ~/.mplayer/config like so: - + vo=xv fs=yes zoom=yes - mplayer can be used to rip a - DVD title to a .vob. To dump - the second title from a DVD: + mplayer can be used to rip a DVD + title to a .vob. To dump the second + title from a DVD: &prompt.root; mplayer -dumpstream -dumpfile out.vob dvd://2 -dvd-device /dev/dvd @@ -1226,13 +1175,12 @@ zoom=yes Before using mencoder, it is a good idea to become familiar with the options described in the -HTML - documentation. There are - innumerable ways to improve quality, lower bitrate, and - change formats, and some of these options may make the - difference between good or bad performance. Improper -combinations of command line options + HTML + documentation. There are innumerable ways to + improve quality, lower bitrate, and change formats, and some + of these options may make the difference between good or bad + performance. Improper combinations of command line options can yield output files that are unplayable even by mplayer. @@ -1240,8 +1188,7 @@ combinations of command line options &prompt.user; mencoder input.avi -oac copy -ovc copy -o output.avi - To rip - to a file, use with + To rip to a file, use with mplayer. To convert @@ -1255,17 +1202,15 @@ combinations of command line options -ovc lavc -lavcopts vcodec=mpeg4:vhq -o output.avi This will produce output playable by applications such -as - mplayer and + as mplayer and xine. input.avi can be replaced with and run as root to re-encode a DVD title directly. Since it may take a few -tries to get the desired result, - it is recommended to dump the title to a file and to work on - the file. + tries to get the desired result, it is recommended to dump + the title to a file and to work on the file. @@ -1274,20 +1219,19 @@ tries to get the desired result, The <application>xine</application> Video Player xine is a video player with a -reusable base library - and a modular executable which can be extended with plugins. - It can be installed using the multimedia/xine package or -port. - - In practice, xine - requires either a fast CPU with a fast video card, or support - for the XVideo extension. The xine - video player performs best on XVideo interfaces. + reusable base library and a modular executable which can be + extended with plugins. It can be installed using the + multimedia/xine package or + port. + + In practice, xine requires + either a fast CPU with a fast video card, or support for the + XVideo extension. The xine video + player performs best on XVideo interfaces. By default, the xine player - starts a graphical user interface. The menus can then - be used to open a specific file. + starts a graphical user interface. The menus can then be used + to open a specific file. Alternatively, xine may be invoked to play a file immediately without the graphical @@ -1301,21 +1245,21 @@ port. &prompt.user; xine -g -p mymovie.avi The + url="http://dvd.sourceforge.net/xine-howto/en_GB/html/howto.html"> xine HOWTO contains a chapter on performance improvement which is general to all players. The <application>transcode</application> -Utilities + Utilities transcode provides a suite of -tools for re-encoding video and audio - files. transcode can be used - to merge video files or repair broken files using - command line tools with stdin/stdout - stream interfaces. + tools for re-encoding video and audio files. + transcode can be used to merge + video files or repair broken files using command line tools + with stdin/stdout stream + interfaces. transcode can be installed using the Enter to continue the port compile and installation. - This example demonstrates how to convert a DivX file into + This example demonstrates how to convert a DivX file into a PAL MPEG-1 file (PAL VCD): &prompt.user; transcode -i @@ -1339,15 +1283,13 @@ tools for re-encoding video and audio The resulting MPEG file, output_vcd.mpg, is ready to be played with MPlayer. - The file can be burned on a CD-R media to create a -Video - CD. In this, install and use the -multimedia/vcdimager and sysutils/cdrdao programs. In addition to the manual page for -transcode, refer to the transcode, refer to the transcode wiki for further information and examples. @@ -1383,34 +1325,29 @@ Video Introduction TV cards allow can be used to watch broadcast or cable TV on -a - computer. Most cards accept composite video via an RCA or - S-video input and some cards include a FM radio - tuner. *** DIFF OUTPUT TRUNCATED AT 1000 LINES ***