From owner-svn-doc-all@FreeBSD.ORG Thu Oct 24 01:28:40 2013 Return-Path: Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 78974FAB; Thu, 24 Oct 2013 01:28:40 +0000 (UTC) (envelope-from dru@FreeBSD.org) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 646F82EEF; Thu, 24 Oct 2013 01:28:40 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.7/8.14.7) with ESMTP id r9O1SecR037266; Thu, 24 Oct 2013 01:28:40 GMT (envelope-from dru@svn.freebsd.org) Received: (from dru@localhost) by svn.freebsd.org (8.14.7/8.14.5/Submit) id r9O1SepG037265; Thu, 24 Oct 2013 01:28:40 GMT (envelope-from dru@svn.freebsd.org) Message-Id: <201310240128.r9O1SepG037265@svn.freebsd.org> From: Dru Lavigne Date: Thu, 24 Oct 2013 01:28:40 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r43037 - head/en_US.ISO8859-1/books/handbook/multimedia X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Oct 2013 01:28:40 -0000 Author: dru Date: Thu Oct 24 01:28:39 2013 New Revision: 43037 URL: http://svnweb.freebsd.org/changeset/doc/43037 Log: White space fix only. Translators can ignore. 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 Wed Oct 23 23:35:27 2013 (r43036) +++ head/en_US.ISO8859-1/books/handbook/multimedia/chapter.xml Thu Oct 24 01:28:39 2013 (r43037) @@ -32,9 +32,10 @@ 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. + &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 @@ -61,12 +62,13 @@ - Play DVDs, .mpg, and - .avi files. + Play DVDs, .mpg, + and .avi files. - Rip CD and DVD content into files. + Rip CD and DVD content into + files. @@ -87,7 +89,7 @@ Know how to install applications as described in . - + @@ -112,25 +114,25 @@ Setting Up the Sound Card - PCI - sound cards - 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. + PCI + sound cards + 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 - + + kernel + configuration + - In order to use the sound device, its device driver - must be loaded. - The easiest way is to load a kernel module for the sound card - with &man.kldload.8;. This example loads the driver for a - built-in audio chipset based on the Intel specification: + In order to use the sound device, its device driver must be + loaded. The easiest way is to load a kernel module for the + sound card with &man.kldload.8;. This example loads the driver + for a built-in audio chipset based on the Intel + specification: &prompt.root; kldload snd_hda @@ -157,23 +159,24 @@ after loading the snd_driver metadriver, type cat /dev/sndstat. - - Configuring a Custom Kernel with Sound Support + + Configuring a Custom Kernel with Sound Support - This section is for users who prefer to statically compile in support for the - sound card in a custom kernel. For more information about recompiling a - kernel, refer to . - - 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, add support for the sound card. To continue the example - of the built-in audio chipset based on the Intel specification from the - previous section, use the following line in the custom kernel - configuration file: + This section is for users who prefer to statically compile + in support for the sound card in a custom kernel. For more + information about recompiling a kernel, refer to . + + 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, add support for the sound card. To continue the + example of the built-in audio chipset based on the Intel + specification from the previous section, use the following + line in the custom kernel configuration file: device snd_hda @@ -215,69 +218,71 @@ hint.sbc.0.flags="0x15" 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. - + - - Testing Sound + + Testing Sound - After loading - the required module or rebooting into the custom kernel, - the sound card should be detected. - To confirm, run dmesg | grep pcm. This - example is from a system with a built-in Conexant CX20590 chipset: + After loading the required module or rebooting into the + custom kernel, the sound card should be detected. To confirm, + run dmesg | grep pcm. This example is + from a system with a built-in Conexant CX20590 chipset: - pcm0: <NVIDIA (0x001c) (HDMI/DP 8ch)> at nid 5 on hdaa0 + pcm0: <NVIDIA (0x001c) (HDMI/DP 8ch)> at nid 5 on hdaa0 pcm1: <NVIDIA (0x001c) (HDMI/DP 8ch)> at nid 6 on hdaa0 pcm2: <Conexant CX20590 (Analog 2.0+HP/2.0)> at nid 31,25 and 35,27 on hdaa1 - 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 + &prompt.root; cat /dev/sndstat FreeBSD Audio Driver (newpcm: 64bit 2009061500/amd64) Installed devices: pcm0: <NVIDIA (0x001c) (HDMI/DP 8ch)> (play) pcm1: <NVIDIA (0x001c) (HDMI/DP 8ch)> (play) pcm2: <Conexant CX20590 (Analog 2.0+HP/2.0)> (play/rec) default - The output will vary depending upon the sound card. If no - pcm devices are listed, double-check that the correct - device driver was loaded or compiled into the kernel. The - next section lists some common problems and their solutions. - - If all goes well, the sound card should now work in os;. If - the CD or DVD drive is properly - connected to the sound card, one can insert an audio CD in the - drive and play it with &man.cdcontrol.1;: + The output will vary depending upon the sound card. If no + pcm devices are listed, double-check + that the correct device driver was loaded or compiled into the + kernel. The next section lists some common problems and their + solutions. + + If all goes well, the sound card should now work in os;. + If the CD or DVD drive + is 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 - - Audio CDs have specialized encodings which means that they should not be - mounted using &man.mount.8;. - - - Various applications, such as 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: - - &prompt.user; cat filename > /dev/dsp - - where - filename can - be any type of file. This command should produce some noise, confirming - that the sound card is working. + + Audio CDs have specialized encodings which means that + they should not be mounted using &man.mount.8;. + + + Various applications, such as 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: + + &prompt.user; cat filename > /dev/dsp + + where + filename can + be any type of file. This command should produce some noise, + confirming that the sound card is working. - - 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;. - + + 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;. + @@ -292,7 +297,8 @@ pcm2: <Conexant CX20590 (Analog 2.0+H solutions: - Common Error Messages + Common Error Messages + @@ -327,8 +333,8 @@ pcm2: <Conexant CX20590 (Analog 2.0+H xxx: can't open /dev/dsp! Type fstat | grep - dsp to check if another application is holding the - device open. Noteworthy troublemakers are + dsp to check if another application is + holding the device open. Noteworthy troublemakers are esound and KDE's sound support. @@ -337,11 +343,10 @@ pcm2: <Conexant CX20590 (Analog 2.0+H
- Modern graphics cards often come - with their own sound driver for use with - HDMI. This sound device is - sometimes enumerated before the sound card meaning that the sound - card will not be used as the default playback + Modern graphics cards often come with their own sound + driver for use with HDMI. This sound + device is sometimes enumerated before the sound card meaning + that the sound card will 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 @@ -365,11 +370,12 @@ pcm6: <HDA Realtek ALC889 PCM #2 Digi pcm7: <HDA Realtek ALC889 PCM #3 Digital> at cad 2 nid 1 on hdac1 ... - In this example, 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: + In this example, 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: &prompt.root; sysctl hw.snd.default_unit=n @@ -401,25 +407,24 @@ pcm7: <HDA Realtek ALC889 PCM #3 Digi Sound Channels to multiplex the sound card's playback by mixing sound in the kernel. - Three - &man.sysctl.8; knobs are available for configuring virtual channels: + Three &man.sysctl.8; knobs are available for configuring + virtual channels: &prompt.root; sysctl dev.pcm.0.play.vchans=4 &prompt.root; sysctl dev.pcm.0.rec.vchans=4 &prompt.root; sysctl hw.snd.maxautovchans=4 - This example allocates four virtual channels, which - is a practical number for everyday use. Both + This example allocates four virtual channels, which is a + practical number for everyday use. Both dev.pcm.0.play.vchans=4 and - dev.pcm.0.rec.vchans=4 are configurable after a device has been - attached and represent the number of - virtual channels pcm0 has for playback - and recording. Since the - pcm module can be loaded independently - of the hardware drivers, hw.snd.maxautovchans - indicates how many virtual channels will be given to an audio device - when it is attached. Refer to &man.pcm.4; for more - information. + dev.pcm.0.rec.vchans=4 are configurable after + a device has been attached and represent the number of virtual + channels pcm0 has for playback and + recording. Since the pcm module can be + loaded independently of the hardware drivers, + hw.snd.maxautovchans indicates how many + virtual channels will be given to an audio device when it is + attached. Refer to &man.pcm.4; for more information. The number of virtual channels for a device cannot be @@ -451,10 +456,9 @@ pcm7: <HDA Realtek ALC889 PCM #3 Digi The default values for the different mixer channels are hardcoded in the source code of the &man.pcm.4; driver. While sound card mixer levels can be changed using &man.mixer.8; or - third-party applications and daemons, this is not a permanent solution. - To instead set default - mixer values at the driver level, - define the appropriate values in + third-party applications and daemons, this is not a permanent + solution. To instead set default mixer values at the driver + level, define the appropriate values in /boot/device.hints, as seen in this example: @@ -727,18 +731,19 @@ MPEG 1.0 layer III, 128 kbit/s, 44100 Hz Video Playback - Before configuring video playback, determine the model - and chipset of the video card. While + Before configuring video playback, determine the model and + chipset of the video card. While &xorg; supports a wide variety of - video cards, not all provide good playback performance. To obtain - a list of extensions supported by the + video cards, not all provide good playback performance. To + obtain a list of extensions supported by the &xorg; server using the card, run - xdpyinfo while &xorg; is - running. + xdpyinfo 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 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 a symbolic links to the proper device: @@ -746,14 +751,15 @@ MPEG 1.0 layer III, 128 kbit/s, 44100 Hz &prompt.root; ln -sf /dev/cd0 /dev/dvd Due to the nature of &man.devfs.5;, manually created links - will not persist after a system reboot. In order to recreate the - symbolic link automatically when the system boots, add the + will not persist after a system reboot. In order to recreate + the symbolic link automatically when the system boots, add the following line to /etc/devfs.conf: link cd0 dvd - DVD decryption invokes certain functions that - require write permission to the DVD device. + DVD decryption invokes certain functions + that require write permission to the DVD + device. To enhance the shared memory &xorg; interface, it is @@ -785,35 +791,38 @@ kern.ipc.shmall=32768 XVideo: an extension to the - &xorg; interface which - allows video to be directly displayed in drawable objects - through a special acceleration. This extension provides - good quality playback even on low-end machines. The next section describes - how to determine if this extension is running. + &xorg; interface which + allows video to be directly displayed in drawable objects + through a special acceleration. This extension provides + good quality playback even on low-end machines. The next + section describes how to determine if this extension is + running. - SDL: the Simple Directmedia - Layer is a porting layer for many operating systems, - allowing cross-platform applications to be developed which make - efficient use of sound and graphics. SDL provides a - low-level abstraction to the hardware which can sometimes be - more efficient than the &xorg; - interface. On &os;, SDL can be installed using the devel/sdl20 package or port. + SDL: the Simple Directmedia Layer is + a porting layer for many operating systems, allowing + cross-platform applications to be developed which make + efficient use of sound and graphics. SDL + provides a low-level abstraction to the hardware which can + sometimes be more efficient than the + &xorg; interface. On &os;, + SDL can be installed using the devel/sdl20 package or + port. - DGA: the Direct Graphics - Access 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 using &man.dga.1;. When dga is - running, it changes the colors of the display whenever a key is - pressed. To quit, press q. + DGA: the Direct Graphics Access 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 using &man.dga.1;. When dga + is running, it changes the colors of the display whenever a + key is pressed. To quit, press q. @@ -901,23 +910,22 @@ kern.ipc.shmall=32768 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 instead looks like: + If the result instead looks like: - X-Video Extension version 2.2 + X-Video Extension version 2.2 screen #0 no adaptors present - 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. - - - + 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. + + Ports and Packages Dealing with Video @@ -930,162 +938,163 @@ no adaptors present playback. - <application>MPlayer</application> and <application>MEncoder</application> + <application>MPlayer</application> and + <application>MEncoder</application> MPlayer is a command-line video player with an optional graphical interface which aims to - provide speed and flexibility. Other - graphical front-ends to MPlayer are available from the &os; Ports - Collection. + provide speed and flexibility. Other graphical front-ends to + MPlayer are available from the &os; + Ports Collection. + + MPlayer + + MPlayer can be installed using + the multimedia/mplayer + package or port. Several compile options are available and a + variety of hardware checks occur during the build process. + For these reasons, some users prefer to build the port rather + than install the package. + + When compiling the port, 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 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 compile + and installation. + + By default, the package or port will build the + mplayer command line utility and the + gmplayer graphical utility. To encode + videos, compile the multimedia/mencoder port. Due to + licensing restrictions, a package is not available for + MEncoder. + + The first time MPlayer is run, + it will create ~/.mplayer in the user's home + directory. This subdirectory contains default versions of + the user-specific configuration files. + + This section describes only a few common uses. Refer to + mplayer(1) for a complete description of its numerous + options. + + To play the file + testfile.avi, + specify the video interfaces with , as + seen in the following examples: + + &prompt.user; mplayer -vo xv testfile.avi + + &prompt.user; mplayer -vo sdl testfile.avi + + &prompt.user; mplayer -vo x11 testfile.avi + + &prompt.root; mplayer -vo dga testfile.avi + + &prompt.root; mplayer -vo 'sdl:dga' testfile.avi + + It is worth trying all of these options, as their + relative performance depends on many factors and will vary + significantly with hardware. + + To play a DVD, replace + testfile.avi + with , where + N is the title number to play and + DEVICE is the device node for the + DVD. For example, to play title 3 from + /dev/dvd: - MPlayer + &prompt.root; mplayer -vo xv dvd://3 -dvd-device /dev/dvd - MPlayer can be installed using - the multimedia/mplayer package or port. Several - compile options are available and a variety of hardware - checks occur during the build process. For these reasons, - some users prefer to build the port rather than install the - package. - - When compiling the port, 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 - 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 - compile and installation. - - By default, the package or port will build the - mplayer command line utility and the - gmplayer graphical utility. To encode - videos, compile the multimedia/mencoder port. Due - to licensing restrictions, a package is not available for - MEncoder. - - The first time MPlayer is - run, it will create ~/.mplayer in the user's - home directory. This subdirectory contains default versions - of the user-specific configuration files. - - This section describes only a few common uses. Refer - to mplayer(1) for a complete - description of its numerous options. - - To play the file - testfile.avi, - specify the video interfaces with - , as seen in the following examples: - - &prompt.user; mplayer -vo xv testfile.avi - - &prompt.user; mplayer -vo sdl testfile.avi - -&prompt.user; mplayer -vo x11 testfile.avi - -&prompt.root; mplayer -vo dga testfile.avi - -&prompt.root; mplayer -vo 'sdl:dga' testfile.avi - - It is worth trying all of these options, as their - relative performance depends on many factors and will vary - significantly with hardware. - - To play a DVD, replace - testfile.avi - with , where - N is the title number to play - and DEVICE - is the device node for the DVD. For example, to play - title 3 from /dev/dvd: - - &prompt.root; mplayer -vo xv dvd://3 -dvd-device /dev/dvd - - - The default DVD device can be defined during the build - of the MPlayer port by - including the - WITH_DVD_DEVICE=/path/to/desired/device - option. By default, the device is - /dev/cd0. More details can be found - in the port's - Makefile.options. - - - To stop, pause, advance, and so on, use a - keybinding. To see the list of keybindings, run mplayer - -h or read mplayer(1). - - Additional playback options include - , which engages fullscreen mode, - and , which helps - performance. + + The default DVD device can be defined + during the build of the MPlayer + port by including the + WITH_DVD_DEVICE=/path/to/desired/device + option. By default, the device is + /dev/cd0. More details can be found in + the port's Makefile.options. + - Each user can add commonly used options to their - ~/.mplayer/config like so: + To stop, pause, advance, and so on, use a keybinding. To + see the list of keybindings, run mplayer + -h or read mplayer(1). + + Additional playback options include , which engages fullscreen mode, and + , which helps performance. - vo=xv + 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: - - &prompt.root; mplayer -dumpstream -dumpfile out.vob dvd://2 -dvd-device /dev/dvd - - The output file, out.vob, will be - in MPEG format. - - Anyone wishing to obtain a high level - of expertise with &unix; video should consult mplayerhq.hu/DOCS as it is technically informative. - This documentation should be considered as required reading - before submitting any bug reports. - - - mencoder - - - Before using mencoder, it is a good - idea to become familiar with the options described at - mplayerhq.hu/DOCS/HTML/en/mencoder.html. 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. - - Here is an example of a simple copy: - - &prompt.user; mencoder input.avi -oac copy -ovc copy -o output.avi - - To rip to a file, use with - mplayer. - - To convert - input.avi - to the MPEG4 codec with MPEG3 audio encoding, first install - the audio/lame port. - Due to licensing restrictions, a package is not available. - Once installed, type: + 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 + + The output file, out.vob, will be in + MPEG format. + + Anyone wishing to obtain a high level of expertise with + &unix; video should consult mplayerhq.hu/DOCS + as it is technically informative. This documentation should + be considered as required reading before submitting any bug + reports. - &prompt.user; mencoder input.avi -oac mp3lame -lameopts br=192 \ + + mencoder + + + Before using mencoder, it is a good + idea to become familiar with the options described at + mplayerhq.hu/DOCS/HTML/en/mencoder.html. + 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. + + Here is an example of a simple copy: + + &prompt.user; mencoder input.avi -oac copy -ovc copy -o output.avi + + To rip to a file, use with + mplayer. + + To convert + input.avi to + the MPEG4 codec with MPEG3 audio encoding, first install the + audio/lame port. Due to + licensing restrictions, a package is not available. Once + installed, type: + + &prompt.user; mencoder input.avi -oac mp3lame -lameopts br=192 \ -ovc lavc -lavcopts vcodec=mpeg4:vhq -o output.avi - This will produce output playable by applications such - 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 instead dump - the title to a file and to work on the file. + This will produce output playable by applications such 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 instead dump the title to a file and to work on + the file. @@ -1129,8 +1138,8 @@ zoom=yes with stdin/stdout stream interfaces. - In &os;, Transcode can be installed - using the In &os;, Transcode can be + installed using the multimedia/transcode package or port. Many users prefer to compile the port as it provides a menu of compile options for specifying the support and codecs @@ -1144,23 +1153,25 @@ zoom=yes This example demonstrates how to convert a DivX file into a PAL MPEG-1 file (PAL VCD): - &prompt.user; transcode -i + &prompt.user; transcode -i input.avi -V --export_prof vcd-pal -o output_vcd &prompt.user; mplex -f 1 -o output_vcd.mpg output_vcd.m1v output_vcd.mpa - The resulting MPEG file, - output_vcd.mpg, - is ready to be played with MPlayer. - The file can be burned on a CD media to create a video CD using a utility such as - multimedia/vcdimager or sysutils/cdrdao. - - In addition to the manual page for - transcode, refer to transcoding.org/cgi-bin/transcode for further information and examples. - - + The resulting MPEG file, + output_vcd.mpg, + is ready to be played with MPlayer. + The file can be burned on a CD media to + create a video CD using a utility such as + multimedia/vcdimager or sysutils/cdrdao. + + In addition to the manual page for + transcode, refer to transcoding.org/cgi-bin/transcode + for further information and examples. + + @@ -1189,16 +1200,16 @@ zoom=yes TV cards - TV cards 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. - - &os; provides support for PCI-based TV cards using a - Brooktree Bt848/849/878/879 - video capture chip with the &man.bktr.4; driver. This driver - supports most Pinnacle PCTV video cards. Before purchasing a TV card, - onsult &man.bktr.4; for a - list of supported tuners. + TV cards 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. + + &os; provides support for PCI-based TV cards using a + Brooktree Bt848/849/878/879 video capture chip with the + &man.bktr.4; driver. This driver supports most Pinnacle PCTV + video cards. Before purchasing a TV card, onsult &man.bktr.4; for + a list of supported tuners. Loading the Driver @@ -1223,9 +1234,9 @@ device smbus components are interconnected via an I2C bus. Then, build and install a new kernel. - To test that the tuner is correctly detected, reboot the system. The TV card - should appear in the boot messages, as seen in this - example: + To test that the tuner is correctly detected, reboot the + system. The TV card should appear in the boot messages, as + seen in this example: bktr0: <BrookTree 848A> mem 0xd7000000-0xd7000fff irq 10 at device 10.0 on pci0 iicbb0: <I2C bit-banging driver> on bti2c0 @@ -1247,8 +1258,8 @@ bktr0: Pinnacle/Miro TV, Philips SECAM t &prompt.root; sysctl hw.bt848.tuner=6 - Refer to &man.bktr.4; for a description - of the available &man.sysctl.8; parameters and kernel options. + Refer to &man.bktr.4; for a description of the available + &man.sysctl.8; parameters and kernel options. @@ -1281,10 +1292,10 @@ bktr0: Pinnacle/Miro TV, Philips SECAM t Troubleshooting - If any problems are encountered with the TV card, - check that the video capture chip and the tuner are - supported by &man.bktr.4; and that the right configuration - options were used. For more support or to ask questions + If any problems are encountered with the TV card, check + that the video capture chip and the tuner are supported by + &man.bktr.4; and that the right configuration options were + used. For more support or to ask questions about supported TV cards, refer to the &a.multimedia.name; mailing list. @@ -1294,44 +1305,45 @@ bktr0: Pinnacle/Miro TV, Philips SECAM t MythTV MythTV is a popular, open source Personal Video Recorder - (PVR) - application. This section demonstrates how to install and - setup MythTV on &os;. Refer to PVR) application. This section demonstrates + how to install and setup MythTV on &os;. Refer to mythtv.org/wiki for more information on how to use MythTV. - MythTV requires a frontend and a backend. These components - can either be installed on the same system or on - different machines. - - The frontend can be installed on &os; using the multimedia/mythtv-frontend package or port. - &xorg; must also be installed and configured as described in - . Ideally, this - system has a video card that supports X-Video Motion Compensation - (XvMC) and, - optionally, a Linux Infrared Remote Control - (LIRC)-compatible remote. - - To install both the backend and the frontend on &os;, use the multimedia/mythtv package or port. - A &mysql; database server is also required and should - automatically be installed as a dependency. - Optionally, this system should have a tuner card - and sufficient storage to hold recorded data. + MythTV requires a frontend and a backend. These + components can either be installed on the same system or on + different machines. + + The frontend can be installed on &os; using the multimedia/mythtv-frontend package + or port. &xorg; must also be + installed and configured as described in . Ideally, this system has a video card that + supports X-Video Motion Compensation + (XvMC) and, optionally, a Linux Infrared + Remote Control (LIRC)-compatible + remote. + + To install both the backend and the frontend on &os;, use + the multimedia/mythtv + package or port. A &mysql; database server is also required + and should automatically be installed as a dependency. + Optionally, this system should have a tuner card and + sufficient storage to hold recorded data. Hardware - MythTV uses Video for Linux (V4L) to access video input - devices such as encoders and tuners. In &os;, MythTV - works best with USB DVB-S/C/T cards as they are well supported by the multimedia/webcamd package or port which provides - a V4L userland application. - Any Digital Video Broadcasting (DVB) - card supported by webcamd should - work with MythTV. A list of known working cards can be - found at MythTV uses Video for Linux (V4L) to + access video input devices such as encoders and tuners. In + &os;, MythTV works best with USB DVB-S/C/T + cards as they are well supported by the multimedia/webcamd package or port + which provides a V4L userland application. + Any Digital Video Broadcasting (DVB) card + supported by webcamd should work + with MythTV. A list of known working cards can be found at + wiki.freebsd.org/WebcamCompat. Drivers are also available for Hauppauge cards in the *** DIFF OUTPUT TRUNCATED AT 1000 LINES ***