diff options
author | torinthiel <torinthiel@b3059339-0415-0410-9bf9-f77b7e298cf2> | 2006-12-08 11:38:06 +0000 |
---|---|---|
committer | torinthiel <torinthiel@b3059339-0415-0410-9bf9-f77b7e298cf2> | 2006-12-08 11:38:06 +0000 |
commit | dc86f6ed17b8e7a702856baefc1d8c3dbd8e229a (patch) | |
tree | c264928fb78e3044f7bf3d8c2eafe2ca607561c4 /DOCS/xml/en/video.xml | |
parent | bd007d8968b264bda27028d280c042f3e23178fa (diff) | |
download | mpv-dc86f6ed17b8e7a702856baefc1d8c3dbd8e229a.tar.bz2 mpv-dc86f6ed17b8e7a702856baefc1d8c3dbd8e229a.tar.xz |
General reformatting round:
- fix some " -> "
- reindent with more consistency
- visual markup of <sect?> tags
- break overly long lines
- add missing <replaceable> tags in examples
- cola truck standing by
git-svn-id: svn://svn.mplayerhq.hu/mplayer/trunk@21537 b3059339-0415-0410-9bf9-f77b7e298cf2
Diffstat (limited to 'DOCS/xml/en/video.xml')
-rw-r--r-- | DOCS/xml/en/video.xml | 645 |
1 files changed, 321 insertions, 324 deletions
diff --git a/DOCS/xml/en/video.xml b/DOCS/xml/en/video.xml index 807d0f89d0..6bb088c066 100644 --- a/DOCS/xml/en/video.xml +++ b/DOCS/xml/en/video.xml @@ -58,12 +58,12 @@ size to hexadecimal, or use this table: <informaltable frame="none"> <tgroup cols="2"> <tbody> -<row><entry>1 MB</entry><entry>0x100000</entry></row> -<row><entry>2 MB</entry><entry>0x200000</entry></row> -<row><entry>4 MB</entry><entry>0x400000</entry></row> -<row><entry>8 MB</entry><entry>0x800000</entry></row> -<row><entry>16 MB</entry><entry>0x1000000</entry></row> -<row><entry>32 MB</entry><entry>0x2000000</entry></row> + <row><entry>1 MB</entry><entry>0x100000</entry></row> + <row><entry>2 MB</entry><entry>0x200000</entry></row> + <row><entry>4 MB</entry><entry>0x400000</entry></row> + <row><entry>8 MB</entry><entry>0x800000</entry></row> + <row><entry>16 MB</entry><entry>0x1000000</entry></row> + <row><entry>32 MB</entry><entry>0x2000000</entry></row> </tbody> </tgroup> </informaltable> @@ -119,8 +119,8 @@ In order to make this work, be sure to check the following: in <filename>/var/log/XFree86.0.log</filename> <note><para> This loads only the XFree86's extension. In a good install, this is - always loaded, and doesn't mean that the <emphasis role="bold">card's</emphasis> - XVideo support is loaded! + always loaded, and doesn't mean that the + <emphasis role="bold">card's</emphasis> XVideo support is loaded! </para></note> </para></listitem> <listitem><para> @@ -159,9 +159,7 @@ screen #0 And finally, check if <application>MPlayer</application> was compiled with 'xv' support. Do a <command>mplayer -vo help | grep xv </command>. If 'xv' support was built a line similar to this should appear: - <screen> - xv X11/Xv<!-- - --></screen> + <screen> xv X11/Xv</screen> </para></listitem> </orderedlist> </para> @@ -205,13 +203,11 @@ tdfxfb. Set up your framebuffer (e.g. append will also help). </para> -<note> -<para> +<note><para> It's currently unclear which Savage models lack YV12 support, and convert by driver (slow). If you suspect your card, get a newer driver, or ask politely on the MPlayer-users mailing list for an MMX/3DNow! enabled driver. -</para> -</note> +</para></note> </sect3> @@ -254,8 +250,9 @@ set refresh rate to a n*(fps of the movie) Hz. <para> Radeon VE - if you need X, use XFree86 4.2.0 or greater for this card. No TV out support. Of course with <application>MPlayer</application> you can -happily get <emphasis role="bold">accelerated</emphasis> display, with or without -<emphasis role="bold">TV output</emphasis>, and no libraries or X are needed. +happily get <emphasis role="bold">accelerated</emphasis> display, with or +without <emphasis role="bold">TV output</emphasis>, and no libraries or X are +needed. Read the <link linkend="vidix">VIDIX</link> section. </para> </sect3> @@ -275,8 +272,8 @@ Just choose the one that applies to your version of XFree86. XFree86 4.3.0 includes Xv support, yet Bohdan Horst sent a small <ulink url="http://www.mplayerhq.hu/MPlayer/contrib/NeoMagic-driver/neo_driver.patch">patch</ulink> against the XFree86 sources that speeds up framebuffer operations (so XVideo) -up to four times. The patch has been included in XFree86 CVS and should be in the -next release after 4.3.0. +up to four times. The patch has been included in XFree86 CVS and should be in +the next release after 4.3.0. </para> <para> @@ -381,7 +378,8 @@ First make sure X loads the DGA extension, see in <programlisting>(II) Loading extension XFree86-DGA</programlisting> -See, XFree86 4.0.x or greater is <emphasis role="bold">highly recommended</emphasis>! +See, XFree86 4.0.x or greater is +<emphasis role="bold">highly recommended</emphasis>! <application>MPlayer</application>'s DGA driver is autodetected by <filename>./configure</filename>, or you can force it with <option>--enable-dga</option>. @@ -413,9 +411,9 @@ Now it works as a simple user, too. <title>Security risk</title> <para> This is a <emphasis role="bold">big</emphasis> security risk! -<emphasis role="bold">Never</emphasis> do this on a server or on a computer that can be -accessed by other people because they can gain root privileges through SUID root -<application>MPlayer</application>. +<emphasis role="bold">Never</emphasis> do this on a server or on a computer +that can be accessed by other people because they can gain root privileges +through SUID root <application>MPlayer</application>. </para> </caution> @@ -605,7 +603,6 @@ with every chipset driver for XFree out there. </itemizedlist> </sect2> -<!--</sect1>--> <!-- ********** --> @@ -655,14 +652,12 @@ but can be forced), and don't forget to edit </para> </formalpara> -<note> -<para> +<note><para> Be sure not to use the <option>-fs</option> switch, since it toggles the usage of the software scaler, and it's slow. If you really need it, use the <option>-sws 4</option> option which will produce bad quality, but is somewhat faster. -</para> -</note> +</para></note> <formalpara> <title>EGA (4BPP) SUPPORT</title> @@ -790,8 +785,8 @@ mplayer -vm -fbmode <replaceable>name_of_mode</replaceable> <replaceable>filenam <option>-bpp</option> option, then that. </para></listitem> <listitem><para> - <option>-zoom</option> option isn't supported (use <option>-vf scale</option>). - You can't use 8bpp (or less) modes. + <option>-zoom</option> option isn't supported + (use <option>-vf scale</option>). You can't use 8bpp (or less) modes. </para></listitem> <listitem><para> You possibly want to turn the cursor off: @@ -807,13 +802,11 @@ mplayer -vm -fbmode <replaceable>name_of_mode</replaceable> <replaceable>filenam </para></listitem> </itemizedlist> -<note> -<para> +<note><para> FBdev video mode changing <emphasis>does not work</emphasis> with the VESA framebuffer, and don't ask for it, since it's not an <application>MPlayer</application> limitation. -</para> -</note> +</para></note> </sect2> <!-- ********** --> @@ -828,12 +821,10 @@ It has hardware VSYNC support with triple buffering. It works on both framebuffer console and under X. </para> -<warning> -<para> +<warning><para> This is Linux only! On non-Linux (tested on FreeBSD) systems, you can use <link linkend="vidix">VIDIX</link> instead! -</para> -</warning> +</para></warning> <procedure> <title>Installation:</title> @@ -948,7 +939,7 @@ least on nVidia): <!-- ********** --> <sect2 id="aalib"> -<title>AAlib - text mode displaying</title> +<title>AAlib – text mode displaying</title> <para> AAlib is a library for displaying graphics in text mode, using powerful @@ -1049,15 +1040,13 @@ important:</title> </varlistentry> </variablelist> -<note> -<para> +<note><para> The rendering is very CPU intensive, especially when using AA-on-X (using aalib on X), and it's least CPU intensive on standard, non-framebuffer console. Use SVGATextMode to set up a big textmode, then enjoy! (secondary head Hercules cards rock :)) (but IMHO you can use <option>-vf 1bpp</option> option to get graphics on hgafb:) -</para> -</note> +</para></note> <para> Use the <option>-framedrop</option> option if your computer isn't fast @@ -1078,7 +1067,9 @@ tuning issues. <!-- ********** --> <sect2 id="caca"> -<title><systemitem class="library">libcaca</systemitem> - Color ASCII Art library</title> +<title> +<systemitem class="library">libcaca</systemitem> – Color ASCII Art library +</title> <para> The <ulink url="http://sam.zoy.org/projects/libcaca/"><systemitem class="library">libcaca</systemitem></ulink> @@ -1141,7 +1132,8 @@ You can use some keys in the caca window to change rendering options: </informaltable> <variablelist> -<title><systemitem class="library">libcaca</systemitem> will also look for certain environment variables:</title> +<title><systemitem class="library">libcaca</systemitem> will also look for + certain environment variables:</title> <varlistentry> <term><option>CACA_DRIVER</option></term> <listitem><simpara> @@ -1255,12 +1247,10 @@ at least.) </simpara></listitem> </itemizedlist> -<important> -<para> +<important><para> Don't use this driver with <emphasis role="bold">GCC 2.96</emphasis>! It won't work! -</para> -</important> +</para></important> <variablelist> <title>COMMAND LINE OPTIONS AVAILABLE FOR VESA</title> @@ -1296,8 +1286,9 @@ It won't work! be activated anyway and you will need restart your computer. </simpara></listitem> <listitem><simpara> - Often after terminating VESA driver you get <emphasis role="bold">black</emphasis> - screen. To return your screen to original state - simply switch to other console + Often after terminating VESA driver you get + <emphasis role="bold">black</emphasis> screen. To return your screen to + original state - simply switch to other console (by pressing <keycap>Alt</keycap>+<keycap>F<x></keycap>) then switch to your previous console by the same way. </simpara></listitem> @@ -1363,16 +1354,18 @@ video modes. <sect2 id="vidix"> <title>VIDIX</title> -<formalpara> -<title>PREAMBLE</title> +<formalpara><title>PREAMBLE</title> <para> -<acronym>VIDIX</acronym> is the abbreviation for <emphasis role="bold">VID</emphasis>eo -<emphasis role="bold">I</emphasis>nterface for *ni<emphasis role="bold">X</emphasis>. +<acronym>VIDIX</acronym> is the abbreviation for +<emphasis role="bold">VID</emphasis>eo +<emphasis role="bold">I</emphasis>nterface +for *ni<emphasis role="bold">X</emphasis>. VIDIX was designed and introduced as an interface for fast user-space drivers -providing such video performance as mga_vid does for Matrox cards. It's also very -portable. +providing such video performance as mga_vid does for Matrox cards. It's also +very portable. </para> </formalpara> + <para> This interface was designed as an attempt to fit existing video acceleration interfaces (known as mga_vid, rage128_vid, radeon_vid, @@ -1443,8 +1436,7 @@ Indeed it doesn't matter which video output driver is used with </simpara></listitem> </itemizedlist> -<formalpara> -<title>USAGE METHODS</title> +<formalpara><title>USAGE METHODS</title> <para> When VIDIX is used as <emphasis role="bold">subdevice</emphasis> (<option>-vo vesa:vidix</option>) then video mode configuration is performed by video @@ -1460,9 +1452,13 @@ recognizes the following options: <option>-fs -zoom -x -y -double</option>. <para> Also you can specify VIDIX's driver directly as third subargument in command line: -<screen>mplayer -vo xvidix:mga_vid.so -fs -zoom -double <replaceable>file.avi</replaceable></screen> +<screen> +mplayer -vo xvidix:mga_vid.so -fs -zoom -double <replaceable>file.avi</replaceable> +</screen> or -<screen>mplayer -vo vesa:vidix:radeon_vid.so -fs -zoom -double -bpp 32 <replaceable>file.avi</replaceable></screen> +<screen> +mplayer -vo vesa:vidix:radeon_vid.so -fs -zoom -double -bpp 32 <replaceable>file.avi</replaceable> +</screen> But it's dangerous, and you shouldn't do that. In this case given driver will be forced and result is unpredictable (it may <emphasis role="bold">freeze</emphasis> your computer). You should do that @@ -1481,29 +1477,34 @@ Alternatively, you can use a special kernel module, like this: <procedure> <step><para> - Download the <ulink url="http://www.arava.co.il/matan/svgalib/">development version</ulink> + Download the + <ulink url="http://www.arava.co.il/matan/svgalib/">development version</ulink> of svgalib (for example 1.9.17), <emphasis role="bold">OR</emphasis> - download a version made by Alex especially for usage with <application>MPlayer</application> - (it doesn't need the svgalib source to compile) from + download a version made by Alex especially for usage with + <application>MPlayer</application> (it doesn't need the svgalib source to + compile) from <ulink url="http://www.mplayerhq.hu/MPlayer/contrib/svgalib/svgalib_helper-1.9.17-mplayer.tar.bz2">here</ulink>. </para></step> <step><para> - Compile the module in the <filename class="directory">svgalib_helper</filename> - directory (it can be found inside the <filename class="directory">svgalib-1.9.17/kernel/</filename> - directory if you've downloaded the source from the svgalib site) and insmod it. + Compile the module in the + <filename class="directory">svgalib_helper</filename> directory (it can be + found inside the + <filename class="directory">svgalib-1.9.17/kernel/</filename> directory if + you've downloaded the source from the svgalib site) and insmod it. </para></step> <step><para> - To create the necessary devices in the <filename class="directory">/dev</filename> - directory, do a <screen>make device</screen> in the <filename class="directory">svgalib_helper</filename> - dir, as root. + To create the necessary devices in the + <filename class="directory">/dev</filename> directory, do a + <screen>make device</screen> in the + <filename class="directory">svgalib_helper</filename> dir, as root. </para></step> <step><para> Move the <filename class="directory">svgalib_helper</filename> directory to <filename class="directory">mplayer/main/libdha/svgalib_helper</filename>. </para></step> <step><para> - Required if you download the source from the svgalib site: Remove the comment before the - CFLAGS line containing "svgalib_helper" string from the + Required if you download the source from the svgalib site: Remove the comment + before the CFLAGS line containing "svgalib_helper" string from the <filename class="directory">libdha/Makefile</filename>. </para></step> <step><para> @@ -1571,11 +1572,11 @@ has tested it, so reports are welcome. <title>nVidia cards</title> <para> - An unique feature of the nvidia_vid driver is its ability to display video on - <emphasis role="bold">plain, pure, text-only console</emphasis> - with no - framebuffer or X magic whatsoever. For this purpose, we'll have to use the - <option>cvidix</option> video output, as the following example shows: - <screen>mplayer -vo cvidix <replaceable>example.avi</replaceable></screen> +An unique feature of the nvidia_vid driver is its ability to display video on +<emphasis role="bold">plain, pure, text-only console</emphasis> - with no +framebuffer or X magic whatsoever. For this purpose, we'll have to use the +<option>cvidix</option> video output, as the following example shows: +<screen>mplayer -vo cvidix <replaceable>example.avi</replaceable></screen> </para> </sect3> @@ -1606,23 +1607,24 @@ Reports awaited! <blockquote><para> "DirectFB is a graphics library which was designed with embedded systems in mind. It offers maximum hardware accelerated performance at a minimum -of resource usage and overhead." - quoted from <ulink url="http://www.directfb.org"/> +of resource usage and overhead." - quoted from +<ulink url="http://www.directfb.org"/> </para></blockquote> <para>I'll exclude DirectFB features from this section.</para> <para> Though <application>MPlayer</application> is not supported as a "video -provider" in DirectFB, this output driver will enable video playback through -DirectFB. It will - of course - be accelerated, on my Matrox G400 DirectFB's speed -was the same as XVideo. +provider" in DirectFB, this output driver will enable video playback +through DirectFB. It will - of course - be accelerated, on my Matrox G400 +DirectFB's speed was the same as XVideo. </para> <para> -Always try to use the newest version of DirectFB. You can use DirectFB options on -the command line, using the <option>-dfbopts</option> option. Layer selection can -be done by the subdevice method, e.g.: <option>-vo directfb:2</option> -(layer -1 is default: autodetect) +Always try to use the newest version of DirectFB. You can use DirectFB options +on the command line, using the <option>-dfbopts</option> option. Layer +selection can be done by the subdevice method, e.g.: +<option>-vo directfb:2</option> (layer -1 is default: autodetect) </para> </sect2> @@ -1632,8 +1634,8 @@ be done by the subdevice method, e.g.: <option>-vo directfb:2</option> <title>DirectFB/Matrox (dfbmga)</title> <para> -Please read the <link linkend="directfb">main DirectFB</link> section for general -information. +Please read the <link linkend="directfb">main DirectFB</link> section for +general information. </para> <para> @@ -1673,78 +1675,68 @@ patch from the URL above). Porting the CRTC2 code to <para> <application>MPlayer</application> supports cards with the Siemens DVB chipset from vendors like Siemens, Technotrend, Galaxis or Hauppauge. The latest DVB -drivers are available from the <ulink url="http://www.linuxtv.org">Linux TV site</ulink>. +drivers are available from the +<ulink url="http://www.linuxtv.org">Linux TV site</ulink>. If you want to do software transcoding you should have at least a 1GHz CPU. </para> <para> Configure should detect your DVB card. If it did not, force detection with -</para> - -<para><screen>./configure --enable-dvb</screen></para> - -<para>If you have ost headers at a non-standard path, set the path with</para> - -<para><screen>./configure --with-extraincdir=<replaceable>DVB source directory</replaceable>/ost/include -</screen></para> - -<para>Then compile and install as usual.</para> +<screen>./configure --enable-dvb</screen> +If you have ost headers at a non-standard path, set the path with +<screen> +./configure --with-extraincdir=<replaceable>DVB source directory</replaceable>/ost/include +</screen> +Then compile and install as usual.</para> -<formalpara> -<title>USAGE</title> +<formalpara><title>USAGE</title> <para> -Hardware decoding (playing standard MPEG-1/2 files) can be done with this command: +Hardware decoding (playing standard MPEG-1/2 files) can be done with this +command: +<screen> +mplayer -ao mpegpes -vo mpegpes <replaceable>file.mpg|vob</replaceable> +</screen> </para> </formalpara> <para> -<screen>mplayer -ao mpegpes -vo mpegpes <replaceable>file.mpg|vob</replaceable></screen> -</para> - -<para> -Software decoding or transcoding different formats to MPEG-1 can be achieved using -a command like this: -</para> -<para><screen> +Software decoding or transcoding different formats to MPEG-1 can be achieved +using a command like this: +<screen> mplayer -ao mpegpes -vo mpegpes <replaceable>yourfile.ext</replaceable> mplayer -ao mpegpes -vo mpegpes -vf expand <replaceable>yourfile.ext</replaceable> </screen></para> <para> Note that DVB cards only support heights 288 and 576 for PAL or 240 and 480 for -NTSC. You <emphasis role="bold">must</emphasis> rescale for other heights by adding -<option>scale=width:height</option> with the width and height you want to the -<option>-vf</option> option. DVB cards accept various widths, like 720, 704, -640, 512, 480, 352 etc. and do hardware scaling in horizontal direction, so you -do not need to scale horizontally in most cases. For a 512x384 (aspect 4:3) -MPEG-4 (DivX) try: +NTSC. You <emphasis role="bold">must</emphasis> rescale for other heights by +adding <option>scale=width:height</option> with the width and height you want +to the <option>-vf</option> option. DVB cards accept various widths, like 720, +704, 640, 512, 480, 352 etc. and do hardware scaling in horizontal direction, +so you do not need to scale horizontally in most cases. +For a 512x384 (aspect 4:3) MPEG-4 (DivX) try: +<screen>mplayer -ao mpegpes -vo mpegpes -vf scale=512:576</screen> </para> -<para><screen>mplayer -ao mpegpes -vo mpegpes -vf scale=512:576</screen></para> - -<para>If you have a widescreen movie and you do not want to scale it to full height, +<para> +If you have a widescreen movie and you do not want to scale it to full height, you can use the <option>expand=w:h</option> filter to add black bands. To view a 640x384 MPEG-4 (DivX), try: -</para> - -<para> -<screen>mplayer -ao mpegpes -vo mpegpes -vf expand=640:576 <replaceable>file.avi</replaceable> +<screen> +mplayer -ao mpegpes -vo mpegpes -vf expand=640:576 <replaceable>file.avi</replaceable> </screen> </para> <para> If your CPU is too slow for a full size 720x576 MPEG-4 (DivX), try downscaling: -</para> - -<para> -<screen>mplayer -ao mpegpes -vo mpegpes -vf scale=352:576 <replaceable>file.avi</replaceable> +<screen> +mplayer -ao mpegpes -vo mpegpes -vf scale=352:576 <replaceable>file.avi</replaceable> </screen> </para> -<para>If speed does not improve, try vertical downscaling, too:</para> - -<para> -<screen>mplayer -ao mpegpes -vo mpegpes -vf scale=352:288 <replaceable>file.avi</replaceable> +<para>If speed does not improve, try vertical downscaling, too: +<screen> +mplayer -ao mpegpes -vo mpegpes -vf scale=352:288 <replaceable>file.avi</replaceable> </screen> </para> @@ -1753,8 +1745,9 @@ For OSD and subtitles use the OSD feature of the expand filter. So, instead of <option>expand=w:h</option> or <option>expand=w:h:x:y</option>, use <option>expand=w:h:x:y:1</option> (the 5th parameter <option>:1</option> at the end will enable OSD rendering). You may want to move the image up a bit -to get a bigger black zone for subtitles. You may also want to move subtitles up, -if they are outside your TV screen, use the <option>-subpos <0-100></option> +to get a bigger black zone for subtitles. You may also want to move subtitles +up, if they are outside your TV screen, use the +<option>-subpos <0-100></option> option to adjust this (<option>-subpos 80</option> is a good choice). </para> @@ -1767,140 +1760,127 @@ In order to play non-25fps movies on a PAL TV or with a slow CPU, add the To keep the aspect ratio of MPEG-4 (DivX) files and get the optimal scaling parameters (hardware horizontal scaling and software vertical scaling while keeping the right aspect ratio), use the new dvbscale filter: -</para> - -<para><screen> +<screen> for a 4:3 TV: -vf dvbscale,scale=-1:0,expand=-1:576:-1:-1:1 for a 16:9 TV: -vf dvbscale=1024,scale=-1:0,expand=-1:576:-1:-1:1 -</screen></para> +</screen> +</para> -<formalpara> -<title>Digital TV (DVB input module)</title> +<formalpara><title>Digital TV (DVB input module)</title> <para>You can use your DVB card for watching Digital TV.</para> </formalpara> <para> - You should have the programs <command>scan</command> and - <command>szap/tzap/czap/azap</command> installed; they are all included in - the drivers package. +You should have the programs <command>scan</command> and +<command>szap/tzap/czap/azap</command> installed; they are all included in +the drivers package. </para> <para> - Verify that your drivers are working properly with a program such as - <ulink url="http://sf.net/projects/dvbtools/"><command>dvbstream</command></ulink> - (that is the base of the DVB input module). +Verify that your drivers are working properly with a program such as +<ulink url="http://sf.net/projects/dvbtools/"><command>dvbstream</command></ulink> +(that is the base of the DVB input module). </para> <para> - Now you should compile a <filename>~/.mplayer/channels.conf</filename> - file, with the syntax accepted by <command>szap/tzap/czap/azap</command>, or - have <command>scan</command> compile it for you. +Now you should compile a <filename>~/.mplayer/channels.conf</filename> +file, with the syntax accepted by <command>szap/tzap/czap/azap</command>, or +have <command>scan</command> compile it for you. </para> <para> - If you have more than one card type (e.g. Satellitar, Terrestrial, Cable and ATSC) - you can save your channels files as - <filename>~/.mplayer/channels.conf.sat</filename>, - <filename>~/.mplayer/channels.conf.ter</filename>, - <filename>~/.mplayer/channels.conf.cbl</filename>, - and <filename>~/.mplayer/channels.conf.atsc</filename>, - respectively, so as to implicitly hint <application>MPlayer</application> - to use these files rather than <filename>~/.mplayer/channels.conf</filename>, - and you only need to specify which card to use. +If you have more than one card type (e.g. Satellitar, Terrestrial, Cable and ATSC) +you can save your channels files as +<filename>~/.mplayer/channels.conf.sat</filename>, +<filename>~/.mplayer/channels.conf.ter</filename>, +<filename>~/.mplayer/channels.conf.cbl</filename>, +and <filename>~/.mplayer/channels.conf.atsc</filename>, +respectively, so as to implicitly hint <application>MPlayer</application> +to use these files rather than <filename>~/.mplayer/channels.conf</filename>, +and you only need to specify which card to use. </para> <para> - Make sure that you have have <emphasis>only</emphasis> Free to Air - channels in your <filename>channels.conf</filename> file, or - <application>MPlayer</application> will try to skip to the next visible one, - but it may take long if there are many consecutive encrypted channels. +Make sure that you have have <emphasis>only</emphasis> Free to Air +channels in your <filename>channels.conf</filename> file, or +<application>MPlayer</application> will try to skip to the next visible one, +but it may take long if there are many consecutive encrypted channels. </para> <para> - In your audio and video fields you can use an extended syntax: - <option>...:pid[+pid]:...</option> (for a maximum of 6 pids each); - in this case <application>MPlayer</application> will include in the - stream all the indicated pids, plus pid 0 (that contains the PAT). - You are encouraged to include in each row the PMT pid for the - corresponding channel (if you know it). - Other possible uses are: televideo pid, second audio track, etc. +In your audio and video fields you can use an extended syntax: +<option>...:pid[+pid]:...</option> (for a maximum of 6 pids each); +in this case <application>MPlayer</application> will include in the +stream all the indicated pids, plus pid 0 (that contains the PAT). +You are encouraged to include in each row the PMT pid for the +corresponding channel (if you know it). +Other possible uses are: televideo pid, second audio track, etc. </para> <para> - If <application>MPlayer</application> complains frequently about - <screen>Too many video/audio packets in the buffer</screen> or - if you notice a growing desynchronization between audio and - video try to use the libavformat MPEG-TS demuxer by adding - <option>-demuxer lavf -lavfdopts probesize=128</option> - to your command line. +If <application>MPlayer</application> complains frequently about +<screen>Too many video/audio packets in the buffer</screen> or +if you notice a growing desynchronization between audio and +video try to use the libavformat MPEG-TS demuxer by adding +<option>-demuxer lavf -lavfdopts probesize=128</option> +to your command line. </para> <para> - To show the first of the channels present in your list, run +To show the first of the channels present in your list, run +<screen>mplayer dvb://</screen> </para> -<screen> - mplayer dvb:// -</screen> - <para> - If you want to watch a specific channel, such as R1, run +If you want to watch a specific channel, such as R1, run +<screen>mplayer dvb://<replaceable>R1</replaceable></screen> </para> -<screen> - mplayer dvb://R1 -</screen> - <para> - If you have more than one card you also need to specify the number of the card - where the channel is visible (e.g. 2) with the syntax: +If you have more than one card you also need to specify the number of the card +where the channel is visible (e.g. 2) with the syntax: +<screen>mplayer dvb://<replaceable>2@R1</replaceable></screen> </para> -<screen> - mplayer dvb://2@R1 -</screen> - <para> - To change channels press the <keycap>h</keycap> (next) and - <keycap>k</keycap> (previous) keys, or use the - <link linkend="osdmenu">OSD menu</link>. +To change channels press the <keycap>h</keycap> (next) and +<keycap>k</keycap> (previous) keys, or use the +<link linkend="osdmenu">OSD menu</link>. </para> <para> - If your <filename>~/.mplayer/menu.conf</filename> contains a - <literal><dvbsel></literal> entry, such as the one in the example - file <filename>etc/dvb-menu.conf</filename> (that you can use to overwrite - <filename>~/.mplayer/menu.conf</filename>), the main menu will show a - sub-menu entry that will permit you to choose one of the channels present - in your <filename>channels.conf</filename>, possibly preceded by a menu - with the list of cards available if more than one is usable by - <application>MPlayer</application>. +If your <filename>~/.mplayer/menu.conf</filename> contains a +<literal><dvbsel></literal> entry, such as the one in the example +file <filename>etc/dvb-menu.conf</filename> (that you can use to overwrite +<filename>~/.mplayer/menu.conf</filename>), the main menu will show a +sub-menu entry that will permit you to choose one of the channels present +in your <filename>channels.conf</filename>, possibly preceded by a menu +with the list of cards available if more than one is usable by +<application>MPlayer</application>. </para> <para> - If you want to save a program to disk you can use -</para> - +If you want to save a program to disk you can use <screen> - mplayer -dumpfile r1.ts -dumpstream dvb://R1 +mplayer -dumpfile <replaceable>r1.ts</replaceable> -dumpstream dvb://<replaceable>R1</replaceable> </screen> - -<para> - If you want to record it in a different format (re-encoding it) instead - you can run a command such as </para> +<para> +If you want to record it in a different format (re-encoding it) instead +you can run a command such as <screen> - mencoder -o r1.avi -ovc xvid -xvidencopts bitrate=800 -oac mp3lame -lameopts cbr:br=128 -pp=ci dvb://R1 +mencoder -o <replaceable>r1.avi</replaceable> -ovc xvid -xvidencopts bitrate=800 \ + -oac mp3lame -lameopts cbr:br=128 -pp=ci dvb://<replaceable>R1</replaceable> </screen> +</para> <para> - Read the man page for a list of options that you can pass to the - DVB input module. +Read the man page for a list of options that you can pass to the +DVB input module. </para> -<formalpara> -<title>FUTURE</title> +<formalpara><title>FUTURE</title> <para> If you have questions or want to hear feature announcements and take part in discussions on this subject, join our @@ -1922,29 +1902,31 @@ decompression). <sect2 id="dxr2"> <title>DXR2</title> -<para><application>MPlayer</application> supports hardware accelerated playback - with the Creative DXR2 card.</para> +<para> +<application>MPlayer</application> supports hardware accelerated playback +with the Creative DXR2 card. +</para> + <para> First of all you will need properly installed DXR2 drivers. You can find the drivers and installation instructions at the <ulink url="http://dxr2.sf.net/">DXR2 Resource Center</ulink> site. </para> -<variablelist> -<title>USAGE</title> +<variablelist><title>USAGE</title> <varlistentry> -<term><option>-vo dxr2</option></term> -<listitem><para>Enable TV output.</para></listitem> + <term><option>-vo dxr2</option></term> + <listitem><para>Enable TV output.</para></listitem> </varlistentry> - <varlistentry> -<term><option>-vo dxr2:x11</option> or <option>-vo dxr2:xv</option></term> -<listitem><para>Enable Overlay output in X11.</para></listitem> + <term><option>-vo dxr2:x11</option> or <option>-vo dxr2:xv</option></term> + <listitem><para>Enable Overlay output in X11.</para></listitem> </varlistentry> - <varlistentry> -<term><option>-dxr2 <option1:option2:...></option></term> -<listitem><para>This option is used to control the DXR2 driver.</para></listitem> + <term><option>-dxr2 <option1:option2:...></option></term> + <listitem><para> + This option is used to control the DXR2 driver. + </para></listitem> </varlistentry> </variablelist> @@ -1993,11 +1975,13 @@ tweak the overlay settings and see the effects in realtime, perhaps this feature will be supported by the <application>MPlayer</application> GUI in the future. When overlay is properly set up you will no longer need to use dxr3view. <option>prebuf</option> turns on prebuffering. Prebuffering is a feature of the -em8300 chip that enables it to hold more than one frame of video at a time. This -means that when you are running with prebuffering <application>MPlayer</application> -will try to keep the video buffer filled with data at all times. If you are on -a slow machine <application>MPlayer</application> will probably use close to, -or precisely 100% of CPU. This is especially common if you play pure MPEG streams +em8300 chip that enables it to hold more than one frame of video at a time. +This means that when you are running with prebuffering +<application>MPlayer</application> will try to keep the video buffer filled +with data at all times. +If you are on |