Mercurial > mplayer.hg
comparison DOCS/xml/en/video.xml @ 10111:a570a78537aa
various fixes and updates
author | nicolas |
---|---|
date | Fri, 16 May 2003 13:30:51 +0000 |
parents | 60c4fd2cb179 |
children | c1b56a757f85 |
comparison
equal
deleted
inserted
replaced
10110:0768c63a7bd3 | 10111:a570a78537aa |
---|---|
162 <para> | 162 <para> |
163 Older 3dfx drivers were known to have problems with XVideo acceleration, it | 163 Older 3dfx drivers were known to have problems with XVideo acceleration, it |
164 didn't support either YUY2 or YV12, and so. Verify that you have XFree86 | 164 didn't support either YUY2 or YV12, and so. Verify that you have XFree86 |
165 version 4.2.0 or greater, it works OK with YV12 and YUY2. Previous | 165 version 4.2.0 or greater, it works OK with YV12 and YUY2. Previous |
166 versions, including 4.1.0, <emphasis role="bold">crashes with YV12</emphasis>. | 166 versions, including 4.1.0, <emphasis role="bold">crashes with YV12</emphasis>. |
167 If you experience strange effects using -vo xv, try SDL (it has XVideo too) and | 167 If you experience strange effects using <option>-vo xv</option>, try SDL (it has XVideo too) and |
168 see if it helps. Check the <link linkend="sdl">SDL section</link> for details. | 168 see if it helps. Check the <link linkend="sdl">SDL section</link> for details. |
169 </para> | 169 </para> |
170 | 170 |
171 <para> | 171 <para> |
172 <emphasis role="bold">OR</emphasis>, try the NEW | 172 <emphasis role="bold">OR</emphasis>, try the NEW |
382 </para> | 382 </para> |
383 | 383 |
384 <caution> | 384 <caution> |
385 <title>Security risk</title> | 385 <title>Security risk</title> |
386 <para> | 386 <para> |
387 This is a <emphasis role="bold">big</emphasis> security risk! Never do this | 387 This is a <emphasis role="bold">big</emphasis> security risk! |
388 on a server or on a computer can be accessed by other people because they | 388 <emphasis role="bold">Never</emphasis> do this on a server or on a computer can be |
389 can gain root privileges through SUID root | 389 accessed by other people because they can gain root privileges through SUID root |
390 <application>MPlayer</application>. | 390 <application>MPlayer</application>. |
391 </para> | 391 </para> |
392 </caution> | 392 </caution> |
393 | 393 |
394 <para> | 394 <para> |
584 | 584 |
585 <sect4 id="sdl"> | 585 <sect4 id="sdl"> |
586 <title>SDL</title> | 586 <title>SDL</title> |
587 | 587 |
588 <para> | 588 <para> |
589 SDL (Simple Directmedia Layer) is basically a unified | 589 <acronym>SDL</acronym> (Simple Directmedia Layer) is basically a unified |
590 video/audio interface. Programs that use it know only about SDL, and not | 590 video/audio interface. Programs that use it know only about SDL, and not |
591 about what video or audio driver does SDL actually use. For example a Doom | 591 about what video or audio driver does SDL actually use. For example a Doom |
592 port using SDL can run on svgalib, aalib, X, fbdev, and others, you only | 592 port using SDL can run on svgalib, aalib, X, fbdev, and others, you only |
593 have to specify the (for example) video driver to use with the | 593 have to specify the (for example) video driver to use with the |
594 <envar>SDL_VIDEODRIVER</envar> environment variable. Well, in theory. | 594 <envar>SDL_VIDEODRIVER</envar> environment variable. Well, in theory. |
755 <sect4 id="fbdev"> | 755 <sect4 id="fbdev"> |
756 <title>Framebuffer output (FBdev)</title> | 756 <title>Framebuffer output (FBdev)</title> |
757 | 757 |
758 <para> | 758 <para> |
759 Whether to build the FBdev target is autodetected during | 759 Whether to build the FBdev target is autodetected during |
760 <filename>./configure</filename>. Read the framebuffer documentation in | 760 <filename>./configure</filename>. Read the framebuffer documentation in |
761 the kernel sources (<filename>Documentation/fb/*</filename>) for more | 761 the kernel sources (<filename>Documentation/fb/*</filename>) for more |
762 information. | 762 information. |
763 </para> | 763 </para> |
764 | 764 |
765 <para> | 765 <para> |
968 | 968 |
969 <para> | 969 <para> |
970 AAlib is a library for displaying graphics in text mode, using powerful | 970 AAlib is a library for displaying graphics in text mode, using powerful |
971 ASCII renderer. There are <emphasis>lots</emphasis> of programs already | 971 ASCII renderer. There are <emphasis>lots</emphasis> of programs already |
972 supporting it, like Doom, Quake, etc. <application>MPlayer</application> | 972 supporting it, like Doom, Quake, etc. <application>MPlayer</application> |
973 contains a very usable driver for it. If <filename>./configure</filename> | 973 contains a very usable driver for it. If <filename>./configure</filename> |
974 detects aalib installed, the aalib libvo driver will be built. | 974 detects aalib installed, the aalib libvo driver will be built. |
975 </para> | 975 </para> |
976 | 976 |
977 <para> | 977 <para> |
978 You can use some keys in the AA Window to change rendering options: | 978 You can use some keys in the AA Window to change rendering options: |
1069 <para> | 1069 <para> |
1070 The rendering is very CPU intensive, especially when using AA-on-X | 1070 The rendering is very CPU intensive, especially when using AA-on-X |
1071 (using aalib on X), and it's least CPU intensive on standard, | 1071 (using aalib on X), and it's least CPU intensive on standard, |
1072 non-framebuffer console. Use SVGATextMode to set up a big textmode, | 1072 non-framebuffer console. Use SVGATextMode to set up a big textmode, |
1073 then enjoy! (secondary head Hercules cards rock :)) (but imho you | 1073 then enjoy! (secondary head Hercules cards rock :)) (but imho you |
1074 can use -vf 1bpp option to get graphics on hgafb:) | 1074 can use <option>-vf 1bpp</option> option to get graphics on hgafb:) |
1075 </para> | 1075 </para> |
1076 </note> | 1076 </note> |
1077 | 1077 |
1078 <para> | 1078 <para> |
1079 Use the <option>-framedrop</option> option if your computer isn't fast | 1079 Use the <option>-framedrop</option> option if your computer isn't fast |
1152 <listitem><simpara> | 1152 <listitem><simpara> |
1153 You can use VIDIX with it, thus getting accelerated video display | 1153 You can use VIDIX with it, thus getting accelerated video display |
1154 <emphasis role="bold">and</emphasis> TV output at the same time! | 1154 <emphasis role="bold">and</emphasis> TV output at the same time! |
1155 (Recommended for ATI cards.) | 1155 (Recommended for ATI cards.) |
1156 </simpara></listitem> | 1156 </simpara></listitem> |
1157 <listitem><simpara> | |
1158 If you have VESA VBE 3.0+, and you had specified | |
1159 <systemitem>monitor_hfreq, monitor_vfreq, monitor_dotclock</systemitem> somewhere | |
1160 (config file, or commandline) you will get the highest possible refresh rate. | |
1161 (Using General Timing Formula). To enable this feature you have to specify | |
1162 <emphasis role="bold">all</emphasis> your monitor options. | |
1163 </simpara></listitem> | |
1157 </itemizedlist> | 1164 </itemizedlist> |
1158 | 1165 |
1159 <itemizedlist spacing="compact"> | 1166 <itemizedlist spacing="compact"> |
1160 <title>DISADVANTAGES</title> | 1167 <title>DISADVANTAGES</title> |
1161 <listitem><simpara> | 1168 <listitem><simpara> |
1181 <varlistentry> | 1188 <varlistentry> |
1182 <term><option>-vo vesa:<replaceable>opts</replaceable></option></term> | 1189 <term><option>-vo vesa:<replaceable>opts</replaceable></option></term> |
1183 <listitem><simpara> | 1190 <listitem><simpara> |
1184 currently recognized: <literal>dga</literal> to force dga mode and | 1191 currently recognized: <literal>dga</literal> to force dga mode and |
1185 <literal>nodga</literal> to disable dga mode. In dga mode you can enable | 1192 <literal>nodga</literal> to disable dga mode. In dga mode you can enable |
1186 double buffering via the -double option. Note: you may omit these parameters | 1193 double buffering via the <option>-double</option> option. Note: you may omit |
1187 to enable <emphasis role="bold">autodetection</emphasis> of dga mode. | 1194 these parameters to enable <emphasis role="bold">autodetection</emphasis> of |
1195 dga mode. | |
1188 </simpara></listitem> | 1196 </simpara></listitem> |
1189 </varlistentry> | 1197 </varlistentry> |
1190 </variablelist> | 1198 </variablelist> |
1191 | 1199 |
1192 <itemizedlist spacing="compact"> | 1200 <itemizedlist spacing="compact"> |
1207 So if you have such problem - always use VESA driver only from | 1215 So if you have such problem - always use VESA driver only from |
1208 <emphasis role="bold">text-mode</emphasis>. Otherwise text-mode (#03) will | 1216 <emphasis role="bold">text-mode</emphasis>. Otherwise text-mode (#03) will |
1209 be activated anyway and you will need restart your computer. | 1217 be activated anyway and you will need restart your computer. |
1210 </simpara></listitem> | 1218 </simpara></listitem> |
1211 <listitem><simpara> | 1219 <listitem><simpara> |
1212 Often after terminating VESA driver you get black screen. To return your | 1220 Often after terminating VESA driver you get <emphasis role="bold">black</emphasis> |
1213 screen to original state - simply switch to other console (by pressing | 1221 screen. To return your screen to original state - simply switch to other console |
1214 <keycap>Alt</keycap>+<keycap>F<x></keycap>) | 1222 (by pressing <keycap>Alt</keycap>+<keycap>F<x></keycap>) |
1215 then switch to your previous console by the same way. | 1223 then switch to your previous console by the same way. |
1216 </simpara></listitem> | 1224 </simpara></listitem> |
1217 <listitem><simpara> | 1225 <listitem><simpara> |
1218 To get <emphasis role="bold">working TV-out</emphasis> you need have plugged | 1226 To get <emphasis role="bold">working TV-out</emphasis> you need have plugged |
1219 TV-connector in before booting your PC since video BIOS initializes | 1227 TV-connector in before booting your PC since video BIOS initializes |
1275 <title>VIDIX</title> | 1283 <title>VIDIX</title> |
1276 | 1284 |
1277 <formalpara> | 1285 <formalpara> |
1278 <title>PREAMBLE</title> | 1286 <title>PREAMBLE</title> |
1279 <para> | 1287 <para> |
1280 VIDIX is the abbreviation for <emphasis role="bold">VID</emphasis>eo | 1288 <acronym>VIDIX</acronym> is the abbreviation for <emphasis role="bold">VID</emphasis>eo |
1281 <emphasis role="bold">I</emphasis>nterface for *ni<emphasis role="bold">X</emphasis>. | 1289 <emphasis role="bold">I</emphasis>nterface for *ni<emphasis role="bold">X</emphasis>. |
1282 VIDIX was designed and introduced as an interface for fast user-space drivers | 1290 VIDIX was designed and introduced as an interface for fast user-space drivers |
1283 providing such video performance as mga_vid does for Matrox cards. It's also very | 1291 providing such video performance as mga_vid does for Matrox cards. It's also very |
1284 portable. | 1292 portable. |
1285 </para> | 1293 </para> |
1337 </itemizedlist> | 1345 </itemizedlist> |
1338 | 1346 |
1339 <formalpara> | 1347 <formalpara> |
1340 <title>USAGE METHODS</title> | 1348 <title>USAGE METHODS</title> |
1341 <para> | 1349 <para> |
1342 When VIDIX is used as <emphasis>subdevice</emphasis> (<option>-vo | 1350 When VIDIX is used as <emphasis role="bold">subdevice</emphasis> (<option>-vo |
1343 vesa:vidix</option>) then video mode configuration is performed by video | 1351 vesa:vidix</option>) then video mode configuration is performed by video |
1344 output device (<emphasis>vo_server</emphasis> in short). Therefore you can | 1352 output device (<emphasis role="bold">vo_server</emphasis> in short). Therefore you can |
1345 pass into command line of <application>MPlayer</application> the same keys | 1353 pass into command line of <application>MPlayer</application> the same keys |
1346 as for vo_server. In addition it understands <option>-double</option> key | 1354 as for vo_server. In addition it understands <option>-double</option> key |
1347 as globally visible parameter. (I recommend using this key with VIDIX at | 1355 as globally visible parameter. (I recommend using this key with VIDIX at |
1348 least for ATI's card). As for <option>-vo xvidix</option> : currently it | 1356 least for ATI's card). As for <option>-vo xvidix</option> : currently it |
1349 recognizes the following options: <option>-fs -zoom -x -y -double</option>. | 1357 recognizes the following options: <option>-fs -zoom -x -y -double</option>. |
1374 </para> | 1382 </para> |
1375 | 1383 |
1376 <para> | 1384 <para> |
1377 Since VIDIX requires direct hardware access you can either run it as root | 1385 Since VIDIX requires direct hardware access you can either run it as root |
1378 or set the SUID bit on the <application>MPlayer</application> binary | 1386 or set the SUID bit on the <application>MPlayer</application> binary |
1379 (<emphasis role="bold">Warning: This is a security risk!</emphasis> | 1387 (<emphasis role="bold">Warning: This is a security risk!</emphasis>). |
1380 Alternatively, you can use a special kernel module, like this: | 1388 Alternatively, you can use a special kernel module, like this: |
1381 </para> | 1389 </para> |
1382 | 1390 |
1383 <procedure> | 1391 <procedure> |
1384 <step><para> | 1392 <step><para> |
1388 (it doesn't need the svgalib source to compile) from | 1396 (it doesn't need the svgalib source to compile) from |
1389 <ulink url="http://www.mplayerhq.hu/~alex/svgalib_helper-1.9.17-mplayer.tar.bz2">here</ulink>. | 1397 <ulink url="http://www.mplayerhq.hu/~alex/svgalib_helper-1.9.17-mplayer.tar.bz2">here</ulink>. |
1390 </para></step> | 1398 </para></step> |
1391 <step><para> | 1399 <step><para> |
1392 Compile the module in the <filename class="directory">svgalib_helper</filename> | 1400 Compile the module in the <filename class="directory">svgalib_helper</filename> |
1401 directory (it can be found inside the <filename class="directory">svgalib-1.9.17/kernel/</filename> | |
1393 directory if you've downloaded the source from the svgalib site) and insmod it. | 1402 directory if you've downloaded the source from the svgalib site) and insmod it. |
1394 </para></step> | 1403 </para></step> |
1395 <step><para> | 1404 <step><para> |
1396 Move the <filename class="directory">svgalib_helper</filename> directory to | 1405 Move the <filename class="directory">svgalib_helper</filename> directory to |
1397 <filename class="directory">mplayer/main/libdha/svgalib_helper</filename>. | 1406 <filename class="directory">mplayer/main/libdha/svgalib_helper</filename>. |
1441 | 1450 |
1442 <para> | 1451 <para> |
1443 The driver was written and is maintained by Alastair M. Robinson, who | 1452 The driver was written and is maintained by Alastair M. Robinson, who |
1444 offers the very latest driver versions for download from his | 1453 offers the very latest driver versions for download from his |
1445 <ulink url="http://www.blackfiveservices.co.uk/EPIAVidix.shtml">homepage</ulink>. | 1454 <ulink url="http://www.blackfiveservices.co.uk/EPIAVidix.shtml">homepage</ulink>. |
1446 The drivers are added to MPlayer with only a short delay, so CVS should always | 1455 The drivers are added to <application>MPlayer</application> with only a short |
1447 be up to date. | 1456 delay, so CVS should always be up to date. |
1448 </para> | 1457 </para> |
1449 </sect5> | 1458 </sect5> |
1450 | 1459 |
1451 <sect5 id="vidix-3dlabs"> | 1460 <sect5 id="vidix-3dlabs"> |
1452 <title>3DLabs cards</title> | 1461 <title>3DLabs cards</title> |
1466 </para></blockquote> | 1475 </para></blockquote> |
1467 | 1476 |
1468 <para>I'll exclude DirectFB features from this section.</para> | 1477 <para>I'll exclude DirectFB features from this section.</para> |
1469 | 1478 |
1470 <para> | 1479 <para> |
1471 Though MPlayer is not supported as a "video provider" in DirectFB, this | 1480 Though <application>MPlayer</application> is not supported as a "video |
1472 output driver will enable video playback through DirectFB. It will - of course - | 1481 provider" in DirectFB, this output driver will enable video playback through |
1473 be accelerated, on my Matrox G400 DirectFB's speed was the same as XVideo. | 1482 DirectFB. It will - of course - be accelerated, on my Matrox G400 DirectFB's speed |
1483 was the same as XVideo. | |
1474 </para> | 1484 </para> |
1475 | 1485 |
1476 <para> | 1486 <para> |
1477 Always try to use the newest version of DirectFB. You can use DirectFB options on | 1487 Always try to use the newest version of DirectFB. You can use DirectFB options on |
1478 the command line, using the <option>-dfbopts</option> option. Layer selection can | 1488 the command line, using the <option>-dfbopts</option> option. Layer selection can |
1525 | 1535 |
1526 <para><screen>./configure --enable-dvb</screen></para> | 1536 <para><screen>./configure --enable-dvb</screen></para> |
1527 | 1537 |
1528 <para>If you have ost headers at a non-standard path, set the path with</para> | 1538 <para>If you have ost headers at a non-standard path, set the path with</para> |
1529 | 1539 |
1530 <para><screen>./configure --with-extraincdir=<DVB source directory>/ost/include | 1540 <para><screen>./configure --with-extraincdir=<replaceable>DVB source directory</replaceable>/ost/include |
1531 </screen></para> | 1541 </screen></para> |
1532 | 1542 |
1533 <para>Then compile and install as usual.</para> | 1543 <para>Then compile and install as usual.</para> |
1534 | 1544 |
1535 <formalpara> | 1545 <formalpara> |
1599 parameters (hardware horizontal scaling and software vertical scaling | 1609 parameters (hardware horizontal scaling and software vertical scaling |
1600 while keeping the right aspect ratio), use the new dvbscale filter: | 1610 while keeping the right aspect ratio), use the new dvbscale filter: |
1601 </para> | 1611 </para> |
1602 | 1612 |
1603 <para><screen> | 1613 <para><screen> |
1604 for 3:4 TV: -vf dvbscale,scale=-1:0,expand=-1:576:-1:-1:1 | 1614 for 4:3 TV: -vf dvbscale,scale=-1:0,expand=-1:576:-1:-1:1 |
1605 for 16:9 TV: -vf dvbscale=1024,scale=-1:0,expand=-1:576:-1:-1:1 | 1615 for 16:9 TV: -vf dvbscale=1024,scale=-1:0,expand=-1:576:-1:-1:1 |
1606 </screen></para> | 1616 </screen></para> |
1607 | 1617 |
1608 <formalpara> | 1618 <formalpara> |
1609 <title>FUTURE</title> | 1619 <title>FUTURE</title> |
1672 | 1682 |
1673 <para> | 1683 <para> |
1674 First of all you will need properly installed DXR3/H+ drivers, version 0.12.0 | 1684 First of all you will need properly installed DXR3/H+ drivers, version 0.12.0 |
1675 or later. You can find the drivers and installation instructions at the | 1685 or later. You can find the drivers and installation instructions at the |
1676 <ulink url="http://dxr3.sourceforge.net/">DXR3 & Hollywood Plus for Linux</ulink> | 1686 <ulink url="http://dxr3.sourceforge.net/">DXR3 & Hollywood Plus for Linux</ulink> |
1677 site. Configure should detect your card automatically, compilation should go | 1687 site. <filename>configure</filename> should detect your card automatically, |
1678 without problems. | 1688 compilation should go without problems. |
1679 </para> | 1689 </para> |
1680 | 1690 |
1681 <!-- FIXME: find a more clear presentation --> | 1691 <!-- FIXME: find a more clear presentation --> |
1682 <variablelist> | 1692 <variablelist> |
1683 <title>USAGE</title> | 1693 <title>USAGE</title> |
1684 <varlistentry> | 1694 <varlistentry> |
1685 <term><option>-vo dxr3:prebuf:sync:norm=x:<device></option></term> | 1695 <term><option>-vo dxr3:prebuf:sync:norm=x:<replaceable>device</replaceable></option></term> |
1686 <listitem><para> | 1696 <listitem><para> |
1687 <option>overlay</option> activates the overlay instead of TVOut. It requires | 1697 <option>overlay</option> activates the overlay instead of TVOut. It requires |
1688 that you have a properly configured overlay setup to work right. The easiest | 1698 that you have a properly configured overlay setup to work right. The easiest |
1689 way to configure the overlay is to first run autocal. Then run mplayer with | 1699 way to configure the overlay is to first run autocal. Then run mplayer with |
1690 dxr3 output and without overlay turned on, run dxr3view. In dxr3view you can | 1700 dxr3 output and without overlay turned on, run dxr3view. In dxr3view you can |
1691 tweak the overlay settings and see the effects in realtime, perhaps this feature | 1701 tweak the overlay settings and see the effects in realtime, perhaps this feature |
1692 will be supported by the MPlayer GUI in the future. When overlay is properly set | 1702 will be supported by the MPlayer GUI in the future. When overlay is properly set |
1693 up you will no longer need to use dxr3view.
 | 1703 up you will no longer need to use dxr3view. |
1694 <option>prebuf</option> turns on prebuffering. Prebuffering is a feature of the | 1704 <option>prebuf</option> turns on prebuffering. Prebuffering is a feature of the |
1695 em8300 chip that enables it to hold more than one frame of video at a time. This | 1705 em8300 chip that enables it to hold more than one frame of video at a time. This |
1696 means that when you are running with prebuffering MPlayer will try to keep the | 1706 means that when you are running with prebuffering MPlayer will try to keep the |
1697 video buffer filled with data at all times. If you are on a slow machine MPlayer | 1707 video buffer filled with data at all times. If you are on a slow machine MPlayer |
1698 will probably use close to, or precisely 100% of CPU. This is especially common | 1708 will probably use close to, or precisely 100% of CPU. This is especially common |
1711 <option>norm=x</option> will set the TV norm of the DXR3 card without the need | 1721 <option>norm=x</option> will set the TV norm of the DXR3 card without the need |
1712 for external tools like em8300setup. Valid norms are 5 = NTSC, 4 = PAL-60, | 1722 for external tools like em8300setup. Valid norms are 5 = NTSC, 4 = PAL-60, |
1713 3 = PAL. Special norms are 2 (auto-adjust using PAL/PAL-60) and 1 (auto-adjust | 1723 3 = PAL. Special norms are 2 (auto-adjust using PAL/PAL-60) and 1 (auto-adjust |
1714 using PAL/NTSC) because they decide which norm to use by looking at the frame | 1724 using PAL/NTSC) because they decide which norm to use by looking at the frame |
1715 rate of the movie. norm = 0 (default) does not change the current norm. | 1725 rate of the movie. norm = 0 (default) does not change the current norm. |
1716 <option><device></option> = device number to use if you have more than one em8300 | 1726 <option><replaceable>device</replaceable></option> = device number to use if you have more than one em8300 |
1717 card. | 1727 card. |
1718 Any of these options may be left out. | 1728 Any of these options may be left out. |
1719 <option>:prebuf:sync</option> seems to work great when playing DivX movies. People | 1729 <option>:prebuf:sync</option> seems to work great when playing DivX movies. People |
1720 have reported problems using the prebuf option when playing MPEG1/2 files. You | 1730 have reported problems using the prebuf option when playing MPEG1/2 files. You |
1721 might want to try running without any options first, if you have sync problems, | 1731 might want to try running without any options first, if you have sync problems, |
1749 the moment lavc is both faster and gives better image quality, it is suggested | 1759 the moment lavc is both faster and gives better image quality, it is suggested |
1750 that you use that unless you have problems with it. See the man page for further | 1760 that you use that unless you have problems with it. See the man page for further |
1751 info about <option>-vf lavc/fame</option>. | 1761 info about <option>-vf lavc/fame</option>. |
1752 Using lavc is highly recommended. Currently there is no way of setting the fps | 1762 Using lavc is highly recommended. Currently there is no way of setting the fps |
1753 of the em8300 which means that it is fixed to 29.97fps. Because of this it is | 1763 of the em8300 which means that it is fixed to 29.97fps. Because of this it is |
1754 highly recommended that you use <option>-vf lavc=<quality>:25</option> | 1764 highly recommended that you use <option>-vf lavc=<replaceable>quality</replaceable>:25</option> |
1755 especially if you are using prebuffering. Then why 25 and not 29.97? Well, the | 1765 especially if you are using prebuffering. Then why 25 and not 29.97? Well, the |
1756 thing is that when you use 29.97 the picture becomes a bit jumpy. The reason for | 1766 thing is that when you use 29.97 the picture becomes a bit jumpy. The reason for |
1757 this is unknown to us. If you set it to somewhere between 25 and 27 the picture | 1767 this is unknown to us. If you set it to somewhere between 25 and 27 the picture |
1758 becomes stable. For now all we can do is accept this for a fact. | 1768 becomes stable. For now all we can do is accept this for a fact. |
1759 </para></listitem> | 1769 </para></listitem> |
1836 then you would issue the following command | 1846 then you would issue the following command |
1837 <screen>mplayer -vo zr -zrcrop 720x320+80+0 benhur.avi</screen> | 1847 <screen>mplayer -vo zr -zrcrop 720x320+80+0 benhur.avi</screen> |
1838 </para> | 1848 </para> |
1839 | 1849 |
1840 <para> | 1850 <para> |
1841 if you want to use the <systemitem>crop</systemitem> filter, you would do | 1851 if you want to use the <option>crop</option> filter, you would do |
1842 <screen>mplayer -vo zr -vf crop=720:320:80:0 benhur.avi</screen> | 1852 <screen>mplayer -vo zr -vf crop=720:320:80:0 benhur.avi</screen> |
1843 </para> | 1853 </para> |
1844 | 1854 |
1845 <para> | 1855 <para> |
1846 Extra occurances of <option>-zrcrop</option> invoke <emphasis>cinerama</emphasis> | 1856 Extra occurances of <option>-zrcrop</option> invoke <emphasis>cinerama</emphasis> |
1864 participating in <emphasis>cinerama</emphasis> is four, so you can build a | 1874 participating in <emphasis>cinerama</emphasis> is four, so you can build a |
1865 2x2 vidiwall. | 1875 2x2 vidiwall. |
1866 </para> | 1876 </para> |
1867 | 1877 |
1868 <para> | 1878 <para> |
1869 inally an important remark: Do not start or stop XawTV on the playback device | 1879 Finally an important remark: Do not start or stop XawTV on the playback device |
1870 during playback, it will crash your computer. It is, however, fine to | 1880 during playback, it will crash your computer. It is, however, fine to |
1871 <emphasis role="bold">FIRST</emphasis> start XawTV, <emphasis role="bold">THEN</emphasis> | 1881 <emphasis role="bold">FIRST</emphasis> start XawTV, <emphasis role="bold">THEN</emphasis> |
1872 start MPlayer, wait for MPlayer to finish and <emphasis role="bold">THEN</emphasis> | 1882 start MPlayer, wait for MPlayer to finish and <emphasis role="bold">THEN</emphasis> |
1873 stop XawTV. | 1883 stop XawTV. |
1874 </para> | 1884 </para> |
1915 using the 3D engine to zoom, and the YUV framebuffer to display the | 1925 using the 3D engine to zoom, and the YUV framebuffer to display the |
1916 zoomed image. If you really want to use X, use the <option>-vo x11 -fs | 1926 zoomed image. If you really want to use X, use the <option>-vo x11 -fs |
1917 -zoom</option> options, but it will be <emphasis role="bold">SLOW</emphasis>, | 1927 -zoom</option> options, but it will be <emphasis role="bold">SLOW</emphasis>, |
1918 and has <emphasis role="bold">Macrovision</emphasis> copy protection enabled | 1928 and has <emphasis role="bold">Macrovision</emphasis> copy protection enabled |
1919 (you can "workaround" Macrovision using this | 1929 (you can "workaround" Macrovision using this |
1920 <ulink url="http://avifile.sourceforge.net/mgamacro.pl">perl | 1930 <ulink url="http://avifile.sourceforge.net/mgamacro.pl">perl script</ulink>). |
1921 script</ulink>. | |
1922 </para></listitem> | 1931 </para></listitem> |
1923 </varlistentry> | 1932 </varlistentry> |
1924 <varlistentry> | 1933 <varlistentry> |
1925 <term>Framebuffer</term> | 1934 <term>Framebuffer</term> |
1926 <listitem><para> | 1935 <listitem><para> |
1951 </para></step> | 1960 </para></step> |
1952 <step><para> | 1961 <step><para> |
1953 Next, EDIT and run the <filename>./matroxtv</filename> script. This will | 1962 Next, EDIT and run the <filename>./matroxtv</filename> script. This will |
1954 present you to a very simple menu. Press <keycap>2</keycap> and | 1963 present you to a very simple menu. Press <keycap>2</keycap> and |
1955 <keycap>Enter</keycap>. Now you should have the same picture on your | 1964 <keycap>Enter</keycap>. Now you should have the same picture on your |
1956 monitor, and TV. The 3rd option will turn on independent display, but | 1965 monitor, and TV. If the TV (PAL by default) |
1957 then you <emphasis>can't use X!</emphasis> If the TV (PAL by default) | |
1958 picture has some weird stripes on it, the script wasn't able to set the | 1966 picture has some weird stripes on it, the script wasn't able to set the |
1959 resolution correctly (to 640x512 by default). Try other resolutions | 1967 resolution correctly (to 640x512 by default). Try other resolutions |
1960 from the menu and/or experiment with fbset. | 1968 from the menu and/or experiment with fbset. |
1961 </para></step> | 1969 </para></step> |
1962 <step><para> | 1970 <step><para> |
2105 Check <ulink url="http://www.iki.fi/too/tvout-voodoo3-3000-xfree">this URL</ulink>. | 2113 Check <ulink url="http://www.iki.fi/too/tvout-voodoo3-3000-xfree">this URL</ulink>. |
2106 </para> | 2114 </para> |
2107 </sect4> | 2115 </sect4> |
2108 | 2116 |
2109 <sect4 id="tvout-nvidia"> | 2117 <sect4 id="tvout-nvidia"> |
2110 <title>Voodoo 3</title> | 2118 <title>nVidia</title> |
2111 <para> | 2119 <para> |
2112 First, you MUST download the closed-source drivers from <ulink url="http://nvidia.com"/>. | 2120 First, you MUST download the closed-source drivers from <ulink url="http://nvidia.com"/>. |
2113 I will not describe the installation and configuration process because it does not cover | 2121 I will not describe the installation and configuration process because it does not cover |
2114 the scope of this documentation. | 2122 the scope of this documentation. |
2115 </para> | 2123 </para> |