diff options
Diffstat (limited to 'doc/faq/faq.sgml')
| -rw-r--r-- | doc/faq/faq.sgml | 330 |
1 files changed, 185 insertions, 145 deletions
diff --git a/doc/faq/faq.sgml b/doc/faq/faq.sgml index 9743cf361..b3490ea2a 100644 --- a/doc/faq/faq.sgml +++ b/doc/faq/faq.sgml @@ -6,7 +6,7 @@ <title>The xine engine FAQ</title> <titleabbrev>xine FAQ</titleabbrev> <copyright> - <year>2001-2003</year> + <year>2001-2008</year> <holder>the xine project team</holder> </copyright> </bookinfo> @@ -17,7 +17,7 @@ <sect2 id="about"> <title>What is the xine engine?</title> - <para> + <para> The xine engine is a free media player engine. It comes in the form of a shared libarary and is typically used by media player frontends and other multimedia applications for playback of multimedia streams @@ -43,7 +43,7 @@ </sect2> <sect2 id="wheretogethelp"> - <title>My question is not yet covered here - where can I ask for help?</title> + <title>My question is not yet covered here – where can I ask for help?</title> <para> First of all be sure that your question is really not covered here and that you haven't just been a bit too lazy to read through all of this @@ -52,7 +52,7 @@ <command>totem</command>). </para> <para> - That said - you are welcome to mail to our user mailing list: + That said – you are welcome to mail to our user mailing list: <email>xine-user@lists.sourceforge.net</email> Please provide some info about your setup so people have a chance to help you, e.g. include information about your audio/video hardware @@ -64,7 +64,7 @@ may have installed on your system. </para> </sect2> - + <sect2 id="pronounce"> <title>How do I pronounce "xine"?</title> <para> @@ -75,7 +75,7 @@ </sect2> <sect2 id="modules"> - <title>What are those xine-lib, xine-ui, gnome-xine, ... modules in cvs for?</title> + <title>What are those xine-lib, xine-ui, gnome-xine, … modules in cvs for?</title> <para> Some time ago xine just became too complex to be just one big program. Therefore it was split into two major parts. @@ -86,7 +86,7 @@ is covered in this FAQ.) </para> <para> - Then there are frontends - applications that use xine. The most + Then there are frontends – applications that use xine. The most common frontend is that of a media player. There are currently two frontends being developed in the xine project, xine-ui (skinned dvd-player style frontend directly based on xlib) and gxine, @@ -103,7 +103,7 @@ </para> <para> Other modules in CVS are: <filename>xine-plugin</filename> a mozilla browser plugin - for streaming media playback using xine, + for streaming media playback using xine, <filename>xine_www</filename> the xine project website sources. </para> @@ -152,7 +152,7 @@ <para> First, make sure that you're using a current development version (see above) or at least the current release version. Then, once you're - ready to send the patch... + ready to send the patch… </para> <para> Generate your patch using either <command>cvs diff -u > @@ -162,17 +162,17 @@ patch. Your patch should be applicable using <command>patch -p0 -i my.patch</command> or, preferably, <command>patch -p1 -i my.patch</command> from the top-level directory in the source tree - (i.e. where configure.ac is) - this is fairly important for our + (i.e. where configure.ac is) – this is fairly important for our Mercurial-based repositories since it makes importing your patch that much easier (hg import defaults to -p1). </para> <para> Alternatively, if you've been hacking away at a module which is - maintained using mercurial, you can make them available as diffs - use + maintained using mercurial, you can make them available as diffs – use <command>hg export</command> or, if you have several patches, you could use <command>hg bundle</command> instead (both require extra parameters; <command>hg help export</command> and <command>hg help - bundle</command> for more details) - or via HTTP by using <command>hg + bundle</command> for more details) – or via HTTP by using <command>hg serve</command>. In the latter case, you'll need to post a URL from which a developer can pull the changes. </para> @@ -194,12 +194,12 @@ <para> The xine project does not provide pre-compiled binaries for legal reasons (some parts of xine may be covered by patents in some countries). - Some OS projects/vendors (e.g. debian, freebsd, ...) offer binaries - for their distributions - please contact them or use their package search + Some OS projects/vendors (e.g. Debian, FreeBSD, …) offer binaries + for their distributions – please contact them or use their package search tools for further info. You can also find links to third parties providing xine RPMs on the xine homepage at - <ulink url="http://xinehq.de/index.php/releases">http://xinehq.de/index.php/releases</ulink>. + <ulink url="http://www.xine-project.org/releases">http://www.xine-project.org/releases</ulink>. </para> <para> See the next section of this FAQ for instructions on how to build xine @@ -215,19 +215,19 @@ <sect2 id="buildrequirements"> <title>What do I need to compile everything properly?</title> <para> - First of all an official and stable release of gcc. Also be aware - that patched gcc versions may break parts of xine and are therefore + First of all an official and stable release of gcc. Also be aware + that patched gcc versions may break parts of xine and are therefore not supported by the xine project. </para> <para> Furthermore you'll have to use GNU make to compile xine. On most GNU/Linux - systems "make" is GNU make - on other platforms use "gmake" instead. + systems "make" is GNU make – on other platforms use "gmake" instead. Also, zlib is required (including the appropriate header files, which are often found in a package called zlib-devel or similar.) </para> <para> If you want to compile xine from CVS, you'll need to have the autobuild tools - installed (automake, autoconf and libtool - in recent versions). + installed (automake, autoconf and libtool – in recent versions). </para> <para> Frontends might need additional libraries, e.g. for gxine you'll need to have @@ -269,17 +269,17 @@ <command>make install</command></screen> </para> <para> - Make sure your <filename>/etc/ld.so.conf</filename> contains + Make sure your <filename>/etc/ld.so.conf</filename> contains <filename>/usr/local/lib</filename> and continue with: <screen> <command>ldconfig</command></screen> </para> <para> - Now unpack your frontend (gxine or xine-ui or ...), then: + Now unpack your frontend (gxine or xine-ui or …), then: <screen> <command>./configure</command> <command>make install</command></screen> </para> - </sect3> + </sect3> <sect3 id="completebuildinstr"> <title>Complete build instructions</title> <para> @@ -292,7 +292,7 @@ <para> If you have installed xine-lib to a non-standard prefix, make sure that you have <filename>$prefix/bin</filename> in your PATH and that your linker finds - libs in <filename>$prefix/lib</filename> - otherwise trying to build modules that + libs in <filename>$prefix/lib</filename> – otherwise trying to build modules that rely on xine-lib will fail with configure complaining about not finding certain parts of libxine. Using bash you can do something like: <screen> @@ -304,12 +304,12 @@ Last but not least. Here the build instructions. As stated earlier, those are the same for every xine module. <screen> - <command>./autogen.sh</command> [-> *only* if you checked your sources out of CVS] + <command>./autogen.sh</command> [→ <emphasis>only</emphasis> if you checked your sources out of CVS] <command>./configure</command> <command>make</command> <command>make install</command></screen> </para> - </sect3> + </sect3> </sect2> <sect2 id="rpmbuild"> @@ -331,7 +331,7 @@ In case that you have a fresh CVS checkout, you will need to do the following first in order to get a tarball release out of it which you can later use with the <command>rpmbuild -ta</command> command above: - <screen> <command>./autogen.sh && make clean && make dist</command></screen> + <screen> <command>./autogen.sh && make clean && make dist</command></screen> </para> <para> In any case, please keep in mind that you have to build and install @@ -362,7 +362,7 @@ <screen> <command>cd ..</command> <command>ls *.deb</command> - <command>su - -c 'cd '"`pwd`"' && dpkg -i <DEB_PACKAGES>'</command> + <command>su - -c 'cd '"`pwd`"' && dpkg -i <DEB_PACKAGES>'</command> </screen> Ubuntu users will probably want to use this instead of that <command>su</command>: <screen> @@ -454,7 +454,7 @@ <title>The Xv video-out plugin fails to compile!</title> <para> If you want to have Xv support compiled in, make sure you either have - a shared Xv library on your system, e.g. + a shared Xv library on your system, e.g. <command>ls /usr/X11R6/lib/libXv*</command> should give you some .so libs, like this: <screen> @@ -463,7 +463,7 @@ /usr/X11R6/lib/libXv.so.1</screen> </para> <para> - Alternatively you need to have libtool 1.4 or newer installed, then + Alternatively you need to have libtool 1.4 or newer installed, then libXv.a is sufficient. Otherwise you can create the shared versions yourself: <screen> <command>ld --whole-archive -shared -o libXv.so.1 libXv.a</command> @@ -477,11 +477,11 @@ </sect2> <sect2> - <title>Build problems in frontends (gxine/xine-ui/...)</title> + <title>Build problems in frontends (gxine/xine-ui/…)</title> <sect3 id="xinelibnotfound"> <title>I have installed xine-lib but the frontend complains about not finding it!</title> <para> - First of all take a closer look at the compilation instructions above again. + First of all take a closer look at the compilation instructions above again. You will probably find your answer there right away. </para> <para> @@ -504,14 +504,14 @@ <screen> <command>mkdir ~/xine</command></screen> </para> <para> - Then you have to set a few environment variables - it's probably a good + Then you have to set a few environment variables – it's probably a good idea to add this to your <filename>~/.bashrc</filename> (or somewhere similar): <screen> <command>export PATH="$HOME/xine/bin:$PATH"</command> <command>export LD_LIBRARY_PATH="$HOME/xine/lib:$LD_LIBRARY_PATH"</command></screen> </para> <para> - Now you can unpack tarballs e.g. in <filename>~/xine/src</filename> + Now you can unpack tarballs e.g. in <filename>~/xine/src</filename> (<command>mkdir ~/xine/src</command> if necessary) and do a <screen> <command>./configure --prefix=$HOME/xine</command> @@ -561,10 +561,10 @@ check out you boot/kernel logs (or run <command>cdrecord -scanbus</command>) to find out which device it got mapped to and set the symlink accordingly (should be something like <filename>/dev/scd0</filename>, - <filename>/dev/scd1</filename>, ... in that case). + <filename>/dev/scd1</filename>, … in that case). Also make sure you (as a user) have sufficient (read and write) permissions on your DVD drive. This could mean you either have to change the device - permissions or add your user to a special group + permissions or add your user to a special group (e.g. <command>addgroup cdrom username</command>), depending on your setup and/or distribution. </para> @@ -574,7 +574,7 @@ smooth video output). Use a command like <command>hdparm -d 1 <device></command> on your DVD device. Please note that even if you're using ide-scsi - you will have to set the dma flag on the ide device node (e.g. + you will have to set the dma flag on the ide device node (e.g. <filename>/dev/hdc</filename>), not the mapped <filename>/dev/scd</filename> scsi device. </para> @@ -612,7 +612,7 @@ Once you have everything set up, try something like <command>gxine dvd:/</command> or <command>xine -p dvd:/</command> to start dvd playback. Some frontend also offer so-called autoplay - buttons or menu entries that start dvd playback immediately. + buttons or menu entries that start dvd playback immediately. </para> <para> Important: do not try to mount the DVD. Just insert it and hit the DVD autoplay @@ -643,7 +643,7 @@ drives is limited (usually about 5 times), after that your drive will stay locked to the region you last set it up for. </para> - </sect3> + </sect3> <sect3 id="regionset"> <title>I have problems setting up my RPC-2 drive for the right region!</title> <para> @@ -657,7 +657,7 @@ drives is limited (usually about 5 times), after that your drive will stay locked to the region you last set it up for. </para> - </sect3> + </sect3> </sect2> <sect2 id="vcdsupport"> @@ -718,7 +718,7 @@ <filename>test_svcd_pal.bin</filename>. Run xine with the MRL <!-- FIXME: This MRL needs to be changed --> <filename>vcd:/test_svcd_pal.cue:E0</filename>. - If you see something playing then this is a hardware problem. + If you see something playing then this is a hardware problem. You might also want to try starting playback-control with <!-- FIXME: This MRL needs to be changed --> <filename>vcd:/test_svcd_pal.cue:P1</filename>. @@ -782,7 +782,7 @@ If you have the VideoCD from the last step, then run the MRL <!-- FIXME: This MRL needs to be changed --> <filename>vcd:/test_svcd_pal.cue:P1</filename> - If this shows a still frame, but it just does not show when you + If this shows a still frame, but it just does not show when you hit either the "VCD" autoscan button or give a MRL without the P1 at the end then go to the next step. </para> @@ -797,7 +797,7 @@ </listitem> <listitem> <para> - You have a VideoCD with menu at beginning and can see it using an MRL + You have a VideoCD with menu at beginning and can see it using an MRL with P1 at the end, but you want to see it by hitting the "VCD" autoscan button as well? Check to see that you have the configuration entry <parameter>media.vcd.autoplay</parameter> set to <parameter>playlist</parameter>. @@ -833,7 +833,7 @@ <sect2 id="quicktime"> <title>Can I watch Quicktime (.mov, .mp4) files using xine?</title> <para> - Quicktime is just a system layer (container format) which can contain various + Quicktime is just a system layer (container format) which can contain various different audio and video formats. The system layer itself is fully supported in xine. However, some quicktime audio/video codecs are not natively supported yet. Luckily, if you are using a x86 compatible machine (any recent PC hardware should do) @@ -852,7 +852,7 @@ have to set <parameter>decoder.external.win32_codecs_path</parameter> in your xine config file accordingly). Restart xine then and you should be able to watch Quicktime trailers. - </para> + </para> </sect2> <sect2> @@ -866,8 +866,16 @@ xine. </para> <para> - Possibly the most convenient way to get the Real codecs is to download - them from the MPlayer website + Possibly the most convenient way to get the Real codecs is to install + RealPlayer 9 or RealPlayer 10 and set the + <parameter>decoder.external.real_codecs_path</parameter> in your xine + config file to the name of the directory which contains the codecs + (look for drvc.so); it's probably something like + <filename>/opt/real/RealPlayer/codecs/</filename>. Restart xine then + and you should be able to watch Real files/streams. + </para> + <para> + Another way to get the Real codecs is to download them from the MPlayer website <ulink url="http://www.mplayerhq.hu/design7/dload.html"> http://www.mplayerhq.hu/design7/dload.html </ulink>. @@ -946,7 +954,7 @@ Latest xine-lib modules (1-beta3 or newer) support external subtitles for any media file, not only AVI. In order to use it you can pass a special MRL construction like: - <screen> <command>xine test.mpg#subtitle:file.sub</command></screen> + <screen> <command>xine file://path/to/test.mpg#subtitle:/path/to/file.sub</command></screen> The external subtitles support can also be used by any xine frontend. Currently xine-ui and kaffeine implement this feature with a subtitle selection dialog. @@ -959,7 +967,7 @@ <title>Running xine</title> <sect2 id="speedup"> - <title>I have a lot of dropped frames - what can I do?</title> + <title>I have a lot of dropped frames – what can I do?</title> <para> Your hardware might be too slow for xine. Make sure you turn on all speed optimizing options. A few things you should check (in order of @@ -1005,7 +1013,7 @@ Try to use the Xv driver, it greatly improves performance and quality because your graphics card does image scaling and colourspace conversion. The <link linkend="video">video section</link> contains important information - about several Xv drivers. + about several Xv drivers. </para> <para> If Xv cannot be used for some reason, make sure your display is set up @@ -1067,7 +1075,7 @@ be enough (use a recent kernel!). </para> <para> - Try a <command>cat /proc/mtrr</command> - if the file exists and you find an entry + Try a <command>cat /proc/mtrr</command> – if the file exists and you find an entry corresponding to the amount of graphics memory you have, everything should be fine. </para> @@ -1077,13 +1085,13 @@ Have your X-server (usually X.org or XFree86) running with higher priority. Most recent linux distributions (like RedHat 8.0 or Mandrake 9.0) should do that for you, improving not only xine but desktop responsiveness - in general. + in general. </para> <para> Use the "top" utility and verify under the "NI" column if the X process has a negative value, this indicates a higher priority. - See "The X Window User HOWTO - Performance considerations" for - further instructions + See "The X Window User HOWTO – Performance considerations" for + further instructions <ulink url="http://www.tldp.org/HOWTO/XWindow-User-HOWTO/performance.html"> http://www.tldp.org/HOWTO/XWindow-User-HOWTO/performance.html </ulink>. @@ -1107,7 +1115,7 @@ <listitem> <para> xine needs high speed memory access which depends on your chip set. - Make sure you enable all speed-improving options. + Make sure you enable all speed-improving options. </para> <para> Especially the via apollo pro chipset is known to be quite weird, @@ -1120,7 +1128,7 @@ </para> <para> This website centers around a windows-tool to tweak the chipset, you - can do the same on FreeBSD with <command>pciconf</command>. + can do the same on FreeBSD with <command>pciconf</command>. On some linux distributions there are similar tools. </para> </listitem> @@ -1165,7 +1173,7 @@ <parameter>engine.buffers.video_num_buffers:500</parameter> to a higher value (e.g. 1000 or 2500). </para> - </listitem> + </listitem> </itemizedlist> </para> </sect2> @@ -1199,7 +1207,7 @@ </sect2> <sect2 id="ports"> - <title>I have problems when using xine on FreeBSD, Solaris, ... !</title> + <title>I have problems when using xine on FreeBSD, Solaris, … !</title> <para> Check out the the corresponding README files in the directory <filename>xine-lib/doc</filename>. </para> @@ -1210,14 +1218,14 @@ <para> aalib is an ascii art library. xine comes with an aalib video output plugin so you can watch movies in your xterm, on the console or on your - old vt100 - very cool ;> ... another nice option is to preview movies + old vt100 – very cool ;> … another nice option is to preview movies on a remote server in your shell over ssh. </para> <para> To use it make sure you have aalib installed correctly before you configure/build xine-lib and xine-ui. In addition to the <command>xine</command> binary a binary named <command>aaxine</command> should get built and installed. You can then use - something like: + something like: <screen> <command>aaxine foo.mpg</command></screen> to use aalib video output. </para> @@ -1245,7 +1253,7 @@ <para> Currently xine support audio output via OSS (kernel audio drivers), ALSA 0.9.x (ALSA 0.5.x is no longer supported), arts (KDE's sound daemon) - and esound (esd, gnome's sound daemon - not recommended because it has + and esound (esd, gnome's sound daemon – not recommended because it has serious issues with a/v sync). </para> </sect2> @@ -1262,7 +1270,7 @@ <para> You can enable xine's audio compressor. Most frontends have a settings window and in that you'll find a slider for the - compressor setting. The values are percent values, so a + compressor setting. The values are percent values, so a slider setting of 200 means that xine will double the volume of silent parts of the movie (loud parts stay the same). </para> @@ -1289,7 +1297,7 @@ <para> If this happens with any video, first try a different audio driver (<command>gxine -A oss</command>, <command>gxine -A arts</command>, - <command>xine -A alsa</command> ...). + <command>xine -A alsa</command> …). </para> <para> If this problem only occurs with one specific stream, maybe switching to @@ -1299,8 +1307,8 @@ <para> If all this doesn't help, maybe you're missing an audio codec or you found a bug. If you decide to post your problem on the xine-user mailing list, - make sure to include all console output xine produced and also clearly - state what type of stream you tried to play back or, even better, make + make sure to include all console output xine produced and also clearly + state what type of stream you tried to play back or, even better, make a test stream available somewhere for developers to download and try. </para> </sect2> @@ -1338,8 +1346,8 @@ <sect2 id="sblivespdif"> <title>Getting SPDIF output from a SBLive 5.1 using OSS drivers</title> <para> - The following explains how to get the above configuration - going with xine. Some parts of it may applicable to other + The following explains how to get the above configuration + going with xine. Some parts of it may applicable to other configurations (cards that use the EMU10k1 chip) as well. </para> <sect3> @@ -1368,24 +1376,24 @@ <para> The OSS driver is maintained by creative and can be downloaded at <ulink url="http://opensource.creative.com/">http://opensource.creative.com/</ulink>. - The driver package contains documentation on how to install it. + The driver package contains documentation on how to install it. Besides that I'd like to add the following notes. </para> <para> In order to compile and install these drivers, you need a valid kernel configuration file. For RedHat Linux's pre-compiled kernels these - configuration files can be found in + configuration files can be found in <filename>/usr/src/linux/configs</filename>. After you've located the correct config file for your kernel, you need to copy it to <filename>/usr/src/linux/.config</filename> For example, when you run the 2.4.18-i686 kernel do : <screen> <command>cp /usr/src/linux/configs/kernel-2.4.18-i686.config /usr/src/linux/.config</command></screen> - Make sure that the emu10k1 module that is currently installed is + Make sure that the emu10k1 module that is currently installed is not loaded. To unload the modules: <screen> <command>/sbin/modprobe -rv emu10k1.o ac97_codec.o</command></screen> - If this mentions that the device is busy, some program is - using the driver. Some example could be a mixer application - or sound daemon like artsd. You'll need to close down the + If this mentions that the device is busy, some program is + using the driver. Some example could be a mixer application + or sound daemon like artsd. You'll need to close down the applications before continuing. At success it should print something like: <screen> @@ -1394,15 +1402,15 @@ # delete soundcore</screen> Run make in the directory where you unpacked the driver and follow the instructions printed at the end of each step. - The last step should be: + The last step should be: <screen> <command>make install-tools</command></screen> - As the README of the driver package mentions the SPDIF AC3 - output doesn't work by default. In the directory + As the README of the driver package mentions the SPDIF AC3 + output doesn't work by default. In the directory <filename>utils/scripts</filename> an <filename>emu10k1.conf</filename> file can be found which need to be placed in the default - installation directory (<filename>/usr/local/etc</filename>). + installation directory (<filename>/usr/local/etc</filename>). After this the <filename>emu10k1.conf</filename> needs to be modified. - The following settings worked fine for me (I don't use the analog + The following settings worked fine for me (I don't use the analog outputs of the card): <programlisting> CARD_IS_5_1=yes @@ -1416,20 +1424,20 @@ ANALOG_FRONT_BOOST=no SURROUND=no PROLOGIC=no - ENABLE_CD_Spdif=yes - ENABLE_OPTICAL_SPDIF=no - ENABLE_LINE2_MIC2=no - ENABLE_RCA_SPDIF=no + ENABLE_CD_Spdif=yes + ENABLE_OPTICAL_SPDIF=no + ENABLE_LINE2_MIC2=no + ENABLE_RCA_SPDIF=no ENABLE_RCA_AUX=no</programlisting> - After modifying the <filename>emu10k1.conf</filename>, + After modifying the <filename>emu10k1.conf</filename>, you need to modify your <filename>/etc/modules.conf</filename> and make sure the following lines are in there. <programlisting> alias sound-slot-0 emu10k1 post-install emu10k1 /usr/local/etc/emu-script</programlisting> - After saving the changes to <filename>modules.conf</filename>, run + After saving the changes to <filename>modules.conf</filename>, run <screen> <command>/sbin/depmod -a</command></screen> - Now, you're ready to load the new modules and set the correct + Now, you're ready to load the new modules and set the correct options for it. To load the modules run: <screen> <command>/sbin/modprobe emu10k1</command></screen> </para> @@ -1445,7 +1453,7 @@ </sect3> <sect3> <title> - The cable used for the SBLive can easily be self-made + The cable used for the SBLive can easily be self-made or buy a stereo 3.5mm jack to dual RCA cable. </title> <para> @@ -1462,10 +1470,10 @@ </para> <para> In order to test it use a DVD with AC3 or DTS track - start xine and select the right audio track - from user interface or start xine as: + start xine and select the right audio track + from user interface or start xine as: <screen> <command>xine dvd:/1 -a 0</command></screen> - The external decoder should display something like + The external decoder should display something like "Dolby Digital" in case the selected audio track contains AC3 data or "DTS" in case the selected audio track contains DTS data. Of course stereo audio also goes @@ -1486,7 +1494,7 @@ <para> Note that recently we added support to "simulate" volume in aRts by changing sample values on-the-fly before delivering them to the driver. - Not as good as having access to sound card's mixer but at least users + Not as good as having access to sound card's mixer but at least users will not complain about lacking of volume bar anymore! :) </para> </sect2> @@ -1495,7 +1503,7 @@ <title>Audio is stuttering and i see a lot of "metronom: fixing sound card drift by -2115 pts" on the console output</title> <para> Might be a soundcard problem, if it only comes in longer intervals. - Your soundcard does not keep it's sampling frequency accurately + Your soundcard does not keep it's sampling frequency accurately enough, which results in audio and video getting out of sync and xine has to compensate. If you see the message only from time to time, you might remedy it by using the resampling sync @@ -1511,12 +1519,12 @@ </para> <para> Another, whole different possibility is that you have some background - process running which is messing with the clock (like some ntp client - - chronny, ntpd, ...). + process running which is messing with the clock (like some ntp client – + chrony, ntpd, …). </para> <para> Occasional messages of "fixing sound card drift" may happen on start and - when playing a long stream (like a movie). This is normal behaviour, + when playing a long stream (like a movie). This is normal behaviour, nothing to worry about. </para> </sect2> @@ -1550,9 +1558,9 @@ <title>Video related questions</title> <sect2 id="novideo"> - <title>I can hear the audio - but I don't see a picture!</title> + <title>I can hear the audio – but I don't see a picture!</title> <para> - Probably your hardware is simply too slow - see above for some + Probably your hardware is simply too slow – see above for some hints on how to speed things up. </para> <para> @@ -1560,7 +1568,7 @@ questions. </para> </sect2> - + <sect2 id="bluescreen"> <title>I only see a blue (or green or black) video image most of the time.</title> <para> @@ -1574,7 +1582,7 @@ <filename>/etc/X11/xorg.conf</filename> or <filename>/etc/X11/XF86Config</filename>). </para> </sect2> - + <sect2 id="buggyxv"> <title>The image looks strange, it is shifted, cropped or shows weird lines!</title> <para> @@ -1619,18 +1627,18 @@ hardware. Here are some hints for individual gfx chips: <itemizedlist> <listitem> - <para> + <para> 3Dfx: if all you get is a solid black window, upgrade to X.org or XFree 4.1.0 or later. </para> </listitem> <listitem> - <para> + <para> ATI: if you only get "half a picture", try lowering your resolution - or bit depth, disable DRI (looks like you ran out of video RAM) + or bit depth, disable DRI (looks like you ran out of video RAM) </para> </listitem> <listitem> - <para> + <para> Trident card: If you see vertical bands jumbled, upgrade to the latest xfree/experimental trident drivers (for the CyberBlade XP a driver exists here: @@ -1638,61 +1646,61 @@ </para> </listitem> <listitem> - <para> + <para> nVidia: With newer GeForce cards, Xv should work with XFree 4.2.0 or newer, for older RivaTNT cards use the binary drivers from nvidia (of course the binary drivers work as well for GeForce cards) </para> </listitem> <listitem> - <para> + <para> Mach64/Rage3D (not Rage128/Radeon) cards/chips get no XVideo with - standard drivers, try + standard drivers, try <ulink url="http://gatos.sourceforge.net/">GATOS drivers </ulink> instead </para> </listitem> <listitem> - <para> + <para> intel: i815 has Xv support in XFree 4.x, others unknown </para> </listitem> <listitem> - <para> + <para> Permedia 2/3 has Xv support in XFree 4.x </para> </listitem> <listitem> - <para> + <para> Savage: at least some older drivers tend to lock up the whole machine, - try the drivers available from + try the drivers available from <ulink url="http://www.probo.com/timr/savage40.html"> http://www.probo.com/timr/savage40.html </ulink>. </para> </listitem> <listitem> - <para> + <para> SIS: certain controllers (more info needed!) have Xv support in XFree 4.x </para> </listitem> <listitem> - <para> + <para> Chips and Tech 6555x, 68554, 69000, 69030 have Xv support in XFree 4.x </para> </listitem> <listitem> - <para> + <para> NeoMagic: certain controllers (more info needed!) have Xv support in Xfree 4.x </para> </listitem> <listitem> - <para> + <para> SiliconMotion: certain controllers (more info needed!) have Xv support in Xfree 4.x </para> </listitem> <listitem> - <para> + <para> Matrox: G200 or newer (but not Parhelia) have Xv support in XFree 4.x. For Parhelia, use the binary only drivers available from matrox' website. </para> @@ -1706,23 +1714,56 @@ <para> Looks like some colours on your GUI match the colour key which Xv uses. You can change the colour key value to avoid this. There should be a line like: - <programlisting> video.XV_COLORKEY:2110</programlisting> + <programlisting> video.device.xv_colorkey:2110</programlisting> in your <filename>~/.xine/config</filename> file where you can change the colour that's used by xine for the video overlay. </para> </sect2> + <sect2 id="texturedvideo"> + <title>How do I get Xv working with compiz?</title> + <para> + Tell xine to prefer textured video. There should be a line like: + <programlisting> video.device.xv_preferred_method:Any</programlisting> + in your <filename>~/.xine/config</filename> file where you can change the preferred method + used by xine for the video overlay. + </para> + <para> + It may be that your graphics card or driver doesn't have the necessary + support for textured video, or the video is rendered too slowly. + </para> + <itemizedlist> + <listitem><para> + ATI: you are likely to need xf86-video-ati later than 6.8.0; 6.9.0.91 + or newer is recommended for slower/older hardware (< X1300) because + the rendering speed has been improved a lot. + </para></listitem> + <listitem><para> + Intel: 945 and later, at least, should be fine with xf86-video-intel + 2.0 or later. Certainly with 2.2 or later. + </para></listitem> + <listitem><para> + nVidia: will probably be fine. (FIXME) + </para></listitem> + </itemizedlist> + <para> + If you find that textured video is significantly slower or isn't + supported, you should either not use compiz or tell xine to use the + xshm video output driver. + </para> + </sect2> + <sect2 id="aspectratio"> <title>The aspect ratio of the video is wrong!</title> <para> Usually xine discovers the screen aspect ratio by querying the X-server and then adjusts the video automatically - to make it look right. However, if that doesn't work try + to make it look right. However, if that doesn't work try pressing "a" to manually change the aspect ratio. </para> <para> If you have a wide screen monitor, make sure the X-server - is correctly configured. The X-server must know the physical + is correctly configured. The X-server must know the physical size of the screen, which is independent of the resolution being used. </para> @@ -1741,7 +1782,7 @@ For XFree86, the filename is normally <filename>/etc/X11/XF86Config</filename>. </para> <para> - Where <parameter>DisplaySize</parameter> specifies, + Where <parameter>DisplaySize</parameter> specifies, in millimeters, the physical size of the monitor's picture area. </para> </sect2> @@ -1755,7 +1796,7 @@ <para> The difference between these counters is a little subtle for the non developer. There are two threads running in order to display video: - the decoder thread will deliver frames to the video output thread. + the decoder thread will deliver frames to the video output thread. The latter is responsible for scheduling the frames to be displayed at the right time. </para> @@ -1792,7 +1833,7 @@ </para> <para> Please note that some frontends save these settings in their config file - so when you have found a working combination, make sure you exit + so when you have found a working combination, make sure you exit xine cleanly so the values are saved. </para> </sect2> @@ -1811,14 +1852,14 @@ Xv by default. </para> <para> - However some users may want to explore better the available hardware + However some users may want to explore better the available hardware capabilities (eg. syncing frame drawing with monitor refresh). Also some Xv drivers contain slow copies and accessing the video card directly may yield performance gains. </para> <para> - Drivers that access hardware directly includes VIDIX (warning: requires - root priviledges or kernel helper) and SyncFB (requires kernel helper - Matrox only). + Drivers that access hardware directly includes VIDIX (warning: requires + root priviledges or kernel helper) and SyncFB (requires kernel helper – Matrox only). User may try one of those, but should be warned that with root access they can cause the system to crash hard. The support is also limited to a couple of graphics cards only. @@ -1857,7 +1898,7 @@ altogether. </para> <para> - Unscaled OSD usage by subtitles and xine-ui is controlled by + Unscaled OSD usage by subtitles and xine-ui is controlled by the following settings (<filename>~/.xine/config</filename> or <filename>~/.gxine/config</filename>): <programlisting> gui.osd_use_unscaled:0</programlisting> @@ -1869,17 +1910,17 @@ <title>I can't see the OSD or it leaves a black box over the image!</title> <para> If you are using xine-lib version 1-rc3 or newer, this is probably - due buggy XV drivers that do not support + due buggy XV drivers that do not support <link linkend="unscaledosd">unscaled OSD</link> (the XShape - extension) properly. + extension) properly. </para> <para> - There have being reports of some ATI drivers that don't allow + There have being reports of some ATI drivers that don't allow displaying anything over the video. The VIA Epia binary drivers is reported to leave a black box where the OSD was displayed. </para> <para> - The problem may be fixed by either updating the video driver, + The problem may be fixed by either updating the video driver, or disabling xine unscaled OSD support. </para> </sect2> @@ -1904,7 +1945,7 @@ <title>Why external subtitles look so ugly?</title> <para> You are probably using a xine-lib version older than 1-rc3. - Try upgrading your copy and read the + Try upgrading your copy and read the <link linkend="unscaledosd">section about unscaled osd</link>. </para> </sect2> @@ -1934,7 +1975,7 @@ </para> <para> Also notice that DVD overlays (including subtitles) are meant to - be displayed in a fixed position, this is how the DVD menu + be displayed in a fixed position, this is how the DVD menu highlighting works. xine does not support moving them. </para> </sect2> @@ -1967,7 +2008,7 @@ <para> The font for text subtitles is selected via config option <parameter>subtitles.separate.font</parameter>. You can specify xine font name - (<parameter>sans</parameter>, <parameter>serif</parameter>, ...) + (<parameter>sans</parameter>, <parameter>serif</parameter>, …) or file name of the TTF font. The directories <filename>$prefix/share/xine/libxine1/fonts</filename> and <filename>~/.xine/fonts</filename> are searched for the fonts, with @@ -2004,7 +2045,7 @@ </para> <para> Syntax is: - <screen> <command>./xine-fontconf font.ttf font_name [encoding1 [encoding2 [...]]]</command></screen> + <screen> <command>./xine-fontconf font.ttf font_name [encoding1 [encoding2 […]]]</command></screen> </para> <para> For example default font <filename>sans</filename> was generated with @@ -2023,7 +2064,7 @@ <sect2 id="subencoding"> <title>Encoding of external subtitles is bad. What is wrong?</title> <para> - The encoding of the external subtitles is expected to be iso-8859-1 by + The encoding of the external subtitles is expected to be iso-8859-1 by default. You need to set an appropriate encoding in the config option <parameter>subtitles.separate.src_encoding</parameter>. Note that you also need a font which contains all characters from the given encoding. @@ -2101,15 +2142,15 @@ <title>"Unable to open dvd drive (/dev/dvd)"</title> <para> You probably don't have /dev/dvd (check that). If so, simply create a - link /dev/dvd that points to your DVD device. Something like... + link /dev/dvd that points to your DVD device. Something like… <screen> <command>ln -s hdc /dev/dvd</command></screen> - ...should do the job. Also make sure you have read and write access on + … should do the job. Also make sure you have read and write access on the device the symlink points to. See the <link linkend="dvdplayback">dvd playback section</link> for more information. </para> </sect2> - + <sect2 id="status0x51"> <title>My drive doesn't work and the kernel says "status=0x51 { DriveReady SeekComplete Error }"</title> <para> @@ -2153,9 +2194,9 @@ have two possibilities. Either deactivate ESD (temporarily) by right clicking on the sound monitor applet and selecting "Place Esound in standby" or just kill it. Then xine will use OSS audio output. The other - method is to make xine use ESD for audio output with: + method is to make xine use ESD for audio output with: <screen> <command>gxine -A esd</command></screen> - This may result in worse playback - exact syncronization is not possible + This may result in worse playback – exact syncronization is not possible with esd, so using oss should be preferred. </para> <para> @@ -2169,7 +2210,7 @@ your aRts control. (recommended) </para> <para> - Newer versions of arts have an auto-suspend mode - this can lead to + Newer versions of arts have an auto-suspend mode – this can lead to some nondeterministic behaviour of xine if it is set up to use the audio device directly. Using arts is recommended in that case; however, you will lose the ability to do four/five channel audio output. @@ -2208,12 +2249,12 @@ </sect2> <sect2 id="xinecrashed"> - <title>xine just crashed on me - i didn't get any error message</title> + <title>xine just crashed on me – i didn't get any error message</title> <para> OK, yes, that shouldn't happen and you're upset. We can understand that. But, to help you and of course to fix this, we need some information. So, let's go through the checklist and maybe prepare a nice bug report - for the xine-user mailing list: + for the <ulink url="http://bugs.xine-project.org/">xine bug tracker</ulink>: <itemizedlist> <listitem> <para> @@ -2223,7 +2264,7 @@ <listitem> <para> Can you reproduce the bug? (e.g. do you remember what you - did and when you do it again it crashes again?) + did and when you do it again it crashes again?) </para> </listitem> <listitem> @@ -2243,7 +2284,7 @@ Your X server just froze on you? unfortunately that's a known problem with some chipsets and drivers (most commonly Savage chipsets) when using Xv. You might want to try running <command>gxine -V XShm</command> - to see if the problem is related to the Xv driver. This will unfortunately + to see if the problem is related to the Xv driver. This will unfortunately be much slower, as lots of things are now done in software instead of hardware scaling/colour space conversion. </para> @@ -2259,11 +2300,10 @@ still under heavy development (nice excuse, isn't it? *grin*). </para> <para> - If you write to the xine user mailing list - <email>xine-user@lists.sourceforge.net</email> + If you write to the <ulink url="http://bugs.xine-project.org/">xine bug tracker</ulink> make sure you include a the above information (when applicable) and also some information about your machine (operating system, cpu type and - speed, gfx card, sound card, ...) and please use a meaningfull subject + speed, gfx card, sound card, …) and please use a meaningfull subject line ("xine bug" is bad, "xine fails to play this quicktime trailer in fullscreen mode" ist much better). </para> |