Mercurial > mplayer.hg
comparison DOCS/xml/en/faq.xml @ 15901:7938b1ee8986
Remove obsolete/outdated entries.
author | diego |
---|---|
date | Sun, 03 Jul 2005 12:13:48 +0000 |
parents | 26204cc17ab7 |
children | c821dbc2c21b |
comparison
equal
deleted
inserted
replaced
15900:4dc4f5b19e3c | 15901:7938b1ee8986 |
---|---|
111 </para></answer> | 111 </para></answer> |
112 </qandaentry> | 112 </qandaentry> |
113 | 113 |
114 <qandaentry> | 114 <qandaentry> |
115 <question><para> | 115 <question><para> |
116 Compilation stops with an error message similar to this one: | |
117 <screen> | |
118 cfft.c: In function`passf2': | |
119 cfft.c:556: unable to find a register to spill in class `FLOAT_REGS' | |
120 cfft.c:556: this is the insn: | |
121 (insn 235 233 246 (set (subreg:SF (reg/v:DI 29 rmm0 [110]) 0) | |
122 (minus:SF (mem:SF (plus:SI (mult:SI (reg:SI 1 edx [112]) | |
123 (const_int 8 [0x8])) | |
124 (reg/v/f:SI 3 ebx [62])) [4 S4 A32]) | |
125 (reg:SF 8 st(0) [132]))) 533 {*fop_sf_1_nosse} (insn_list | |
126 232 (nil)) (expr_list:REG_DEAD (reg:SF 8 st(0) [132]) | |
127 (nil))) | |
128 cfft.c:556: confused by earlier errors, bailing out | |
129 </screen> | |
130 </para></question> | |
131 <answer><para> | |
132 This is a known problem of <application>gcc</application> 3.2, upgrade | |
133 to 3.3 to solve the problem. How to install gcc is described in the | |
134 <link linkend="gcc-296">gcc 2.96</link> section. Alternatively you can use | |
135 an external FAAD library as described in the | |
136 <link linkend="aac">AAC</link> section. | |
137 </para></answer> | |
138 </qandaentry> | |
139 | |
140 <qandaentry> | |
141 <question><para> | |
142 Compilation stops with an error message similar to this one: | |
143 <screen> | |
144 In file included from mplayer.c:34: | |
145 mw.h: In function `mplMainDraw': | |
146 mw.h:209: Internal compiler error in print_rtl_and_abort, at flow.c:6458 | |
147 Please submit a full bug report, | |
148 with preprocessed source if appropriate. | |
149 </screen> | |
150 </para></question> | |
151 <answer><para> | |
152 This is a known problem of <application>gcc</application> 3.0.4, upgrade | |
153 to 3.1 to solve the problem. How to install gcc is described in the | |
154 <link linkend="gcc-296">gcc 2.96</link> section. | |
155 </para></answer> | |
156 </qandaentry> | |
157 | |
158 <qandaentry> | |
159 <question><para> | |
160 Configure ends with this text, and <application>MPlayer</application> won't compile! | 116 Configure ends with this text, and <application>MPlayer</application> won't compile! |
161 <screen>Your gcc does not support even i386 for '-march' and '-mcpu'</screen> | 117 <screen>Your gcc does not support even i386 for '-march' and '-mcpu'</screen> |
162 </para></question> | 118 </para></question> |
163 <answer><para> | 119 <answer><para> |
164 Your gcc isn't installed correctly, check the <filename>configure.log</filename> | 120 Your gcc isn't installed correctly, check the <filename>configure.log</filename> |
165 file for details. | 121 file for details. |
166 </para></answer> | |
167 </qandaentry> | |
168 | |
169 <qandaentry> | |
170 <question><para> | |
171 What's the problem with gcc 2.96? | |
172 </para></question> | |
173 <answer><para> | |
174 <emphasis role="bold">We strongly discourage the use of gcc 2.96!</emphasis> | |
175 Read <link linkend="gcc-296">this</link> document for details about why Red Hat | |
176 released gcc 2.96 and what the problems are all about. If you still really really | |
177 want to use it, be sure to get the latest release and give the | |
178 <option>--disable-gcc-checking</option> option to configure. Remember that you | |
179 are on your own from this point. Do <emphasis role="bold">not</emphasis> report | |
180 bugs, do <emphasis role="bold">not</emphasis> ask for help on the mailing lists. | |
181 We will <emphasis role="bold">not</emphasis> provide any support in case you run | |
182 into problems. | |
183 </para></answer> | |
184 </qandaentry> | |
185 | |
186 <qandaentry> | |
187 <question><para> | |
188 Great, I have gcc 3.0.1 from Red Hat/Mandrake, then I'm fine! | |
189 </para></question> | |
190 <answer><para> | |
191 No, since there have been/are issues with these compilers as well. | |
192 To check the status of current compilers' <application>MPlayer</application> | |
193 support, see the <link linkend="install">Installation</link> section. | |
194 </para></answer> | |
195 </qandaentry> | |
196 | |
197 <qandaentry> | |
198 <question><para> | |
199 .. gcc 2.96 ... (Yes, some people are STILL flaming about gcc 2.96!) | |
200 </para></question> | |
201 <answer><para> | |
202 Quoted from a <ulink url="http://www.mplayerhq.hu/pipermail/mplayer-users/2001-October/005351.html">mail</ulink> | |
203 A'rpi sent to the <ulink url="http://mplayerhq.hu/pipermail/mplayer-users/">MPlayer-users</ulink> | |
204 list (the word 'ideg' is described below): | |
205 <blockquote> | |
206 <para> | |
207 And we have idegs. And our idegcounter overflowed again and again. | |
208 </para> | |
209 <para> | |
210 Unfortunately <application>MPlayer</application> is out of our control. | |
211 It's used by lamers, Linux users who can't even use Windows, and never | |
212 tried to compile a kernel. They installed (with default options) Mandrake | |
213 or Red Hat or SuSE, and without RTFM'ing they send messages saying | |
214 'it doesn't work! help me! please! i'm new to Linux! help! oh! help me!'. | |
215 We can't stop them, but at least we try to force them to RTFM and to read | |
216 the messages of ./configure and <application>MPlayer</application>. | |
217 </para> | |
218 <para> | |
219 And you clever guys come and flame us with gcc 2.96 and binary packages. | |
220 Instead of helping users or making patches to help solve problems. | |
221 </para> | |
222 <para> | |
223 Half of our spare/free time is spent by answering silly mails here and | |
224 making newer tricks and checks to configure to avoid such mails. | |
225 </para> | |
226 <para> | |
227 And there is a balance. On the one side are you, clever guys, saying we | |
228 are very bad because we don't like buggy gcc 2.96, and on the other side | |
229 there are the 'new to Linux' guys who are showing us gcc 2.96 is buggy. | |
230 </para> | |
231 <para> | |
232 Conclusion: We can't be good. Half the people will always say we are bad. | |
233 </para> | |
234 <para> | |
235 Maybe we should close the project, make it closed source, commercial, and | |
236 provide install support for it. then we could leave current work, so development | |
237 could go faster, and we could earn lots of money with it and buy a big house, | |
238 etc etc. Do you really want it? It seems. | |
239 </para> | |
240 </blockquote> | |
241 </para></answer> | |
242 </qandaentry> | |
243 | |
244 <qandaentry> | |
245 <question><para> | |
246 SDL output doesn't work or compile. The problem is ... | |
247 </para></question> | |
248 <answer><para> | |
249 It was tested to work with SDL 1.2.x and may run on SDL 1.1.7+. It does | |
250 <emphasis role="bold">not</emphasis> work with any previous version. So | |
251 if you choose to use such a version, you are on your own. | |
252 </para></answer> | |
253 </qandaentry> | |
254 | |
255 <qandaentry> | |
256 <question><para> | |
257 I am still having trouble compiling with SDL support. gcc says something | |
258 about <screen>undefined reference to SDL_EnableKeyRepeat</screen>. What now? | |
259 </para></question> | |
260 <answer><para> | |
261 Where did you install the SDL library? If you installed in | |
262 <filename class="directory">/usr/local</filename> (the default) then edit the | |
263 top level <filename>config.mak</filename> and add | |
264 <systemitem>-L/usr/local/lib</systemitem> after <systemitem>X_LIBS=</systemitem>. | |
265 Now type <command>make</command>. You're done! | |
266 </para></answer> | 122 </para></answer> |
267 </qandaentry> | 123 </qandaentry> |
268 | 124 |
269 <qandaentry> | 125 <qandaentry> |
270 <question><para> | 126 <question><para> |
297 </para></answer> | 153 </para></answer> |
298 </qandaentry> | 154 </qandaentry> |
299 | 155 |
300 <qandaentry> | 156 <qandaentry> |
301 <question><para> | 157 <question><para> |
302 I can't compile SVGAlib. I'm using kernel 2.3/2.4 ... | |
303 </para></question> | |
304 <answer><para> | |
305 You have to edit SVGAlib's <filename>Makefile.cfg</filename> and comment | |
306 <systemitem>BACKGROUND = y</systemitem> out. | |
307 </para></answer> | |
308 </qandaentry> | |
309 | |
310 <qandaentry> | |
311 <question><para> | |
312 I compiled <application>MPlayer</application> with libdvdcss/libdivxdecore support, | 158 I compiled <application>MPlayer</application> with libdvdcss/libdivxdecore support, |
313 but when I try to start it, it says: | 159 but when I try to start it, it says: |
314 <screen> | 160 <screen> |
315 error while loading shared libraries: lib*.so.0: cannot load shared object file: No such file or directory | 161 error while loading shared libraries: lib*.so.0: cannot load shared object file: No such file or directory |
316 </screen> | 162 </screen> |
317 I checked up on the file and it IS there in <filename class="directory">/usr/local/lib</filename> ... | 163 I checked up on the file and it IS there in <filename class="directory">/usr/local/lib</filename> ... |
318 </para></question> | 164 </para></question> |
319 <answer><para> | 165 <answer><para> |
320 Add <filename class="directory">/usr/local/lib</filename> to <filename>/etc/ld.so.conf</filename> | 166 Add <filename class="directory">/usr/local/lib</filename> to <filename>/etc/ld.so.conf</filename> |
321 and run <command>ldconfig</command>. | 167 and run <command>ldconfig</command>. |
322 </para></answer> | |
323 </qandaentry> | |
324 | |
325 <qandaentry> | |
326 <question><para> | |
327 When compiling <application>MEncoder</application>, it segfaults at linking! | |
328 </para></question> | |
329 <answer><para> | |
330 This is a linker problem. Upgrading binutils should help (2.11.92.* | |
331 or newer should be good). Since it is not our fault, please do | |
332 <emphasis role="bold">not</emphasis> report! | |
333 </para></answer> | 168 </para></answer> |
334 </qandaentry> | 169 </qandaentry> |
335 | 170 |
336 <qandaentry> | 171 <qandaentry> |
337 <question><para> | 172 <question><para> |
405 </para></question> | 240 </para></question> |
406 <answer><para> | 241 <answer><para> |
407 You have to use a video output driver that does not employ an overlay to be | 242 You have to use a video output driver that does not employ an overlay to be |
408 able to take a screenshot. Under X11, <option>-vo x11</option> will do, under | 243 able to take a screenshot. Under X11, <option>-vo x11</option> will do, under |
409 Windows <option>-vo directx:noaccel</option> works. | 244 Windows <option>-vo directx:noaccel</option> works. |
410 </para></answer> | |
411 </qandaentry> | |
412 | |
413 <qandaentry> | |
414 <question><para> | |
415 There is a timer in the upper left corner. How can I get rid of it? | |
416 </para></question> | |
417 <answer><para> | |
418 Press <keycap>o</keycap> and try the <option>-osdlevel</option> option. | |
419 </para></answer> | 245 </para></answer> |
420 </qandaentry> | 246 </qandaentry> |
421 | 247 |
422 <qandaentry> | 248 <qandaentry> |
423 <question><para> | 249 <question><para> |
773 </para></answer> | 599 </para></answer> |
774 </qandaentry> | 600 </qandaentry> |
775 | 601 |
776 <qandaentry> | 602 <qandaentry> |
777 <question><para> | 603 <question><para> |
778 <application>MPlayer</application> exits with some error when using <filename>l3codeca.acm</filename>. | |
779 </para></question> | |
780 <answer><para> | |
781 Check <command>ldd /usr/local/bin/mplayer</command> output. If it contains | |
782 <screen>libc.so.6 => /lib/libc.so.6 (0x4???????)</screen> | |
783 where "?" is any number then it's OK, the error is not here. If it is: | |
784 <screen>libc.so.6 => /lib/libc.so.6 (0x00??????)</screen> | |
785 then there is a problem with your kernel/libc. Maybe you are using some security | |
786 patches (for example Solar Designer's OpenWall patch) which forces loading | |
787 libraries to very low addresses. Because <filename>l3codeca.acm</filename> is a | |
788 non-relocatable DLL, it must be loaded to <literal>0x40000000</literal>, we can't | |
789 change this. You should use a non-patched kernel, or use <application>MPlayer</application>'s | |
790 <option>-afm 1</option> option to disable using <filename>l3codeca.acm</filename>. | |
791 </para></answer> | |
792 </qandaentry> | |
793 | |
794 <qandaentry> | |
795 <question><para> | |
796 My computer plays MS DivX AVIs with resolutions ~ 640x300 and stereo MP3 sound | 604 My computer plays MS DivX AVIs with resolutions ~ 640x300 and stereo MP3 sound |
797 too slow. When I use <option>-nosound</option> option, everything is OK (but quiet). | 605 too slow. When I use <option>-nosound</option> option, everything is OK (but quiet). |
798 </para></question> | 606 </para></question> |
799 <answer><para> | 607 <answer><para> |
800 Your machine is too slow or your sound card driver is broken. Consult the | 608 Your machine is too slow or your sound card driver is broken. Consult the |
822 </para></question> | 630 </para></question> |
823 <answer><para> | 631 <answer><para> |
824 Read the <link linkend="bugreports">bug reporting guidelines</link> and send us | 632 Read the <link linkend="bugreports">bug reporting guidelines</link> and send us |
825 a proper bug report. | 633 a proper bug report. |
826 Also try experimenting with the <option>-fstype</option> option. | 634 Also try experimenting with the <option>-fstype</option> option. |
827 </para></answer> | |
828 </qandaentry> | |
829 | |
830 <qandaentry> | |
831 <question><para> | |
832 I got this playing MPEG files: Can't find codec for video format 0x10000001! | |
833 </para></question> | |
834 <answer><para> | |
835 You have an old version of <filename>codecs.conf</filename> in | |
836 <filename class="directory">~/.mplayer/</filename>, | |
837 <filename class="directory">/etc/</filename>, | |
838 <filename class="directory">/usr/local/etc/</filename> or similar. Remove it, | |
839 it's not needed anymore. | |
840 <emphasis role="bold">OR</emphasis> you have the <option>vc=</option> option or | |
841 something similar in your config file(s). | |
842 </para></answer> | 635 </para></answer> |
843 </qandaentry> | 636 </qandaentry> |
844 | 637 |
845 <qandaentry> | 638 <qandaentry> |
846 <question><para> | 639 <question><para> |
852 video starts or disable the arts-daemon in control center. If you want to use | 645 video starts or disable the arts-daemon in control center. If you want to use |
853 arts sound, specify audio output via our native arts audio driver | 646 arts sound, specify audio output via our native arts audio driver |
854 (<option>-ao arts</option>). If it fails or isn't compiled in, try SDL | 647 (<option>-ao arts</option>). If it fails or isn't compiled in, try SDL |
855 (<option>-ao sdl</option>) and make sure your SDL can handle arts sound. Yet | 648 (<option>-ao sdl</option>) and make sure your SDL can handle arts sound. Yet |
856 another option is to start <application>MPlayer</application> with artsdsp. | 649 another option is to start <application>MPlayer</application> with artsdsp. |
857 </para></answer> | |
858 </qandaentry> | |
859 | |
860 <qandaentry> | |
861 <question><para> | |
862 I have an AVI that produces a gray screen when played with <option>-vc odivx</option> | |
863 and a green one with <option>-vc divx4</option>. | |
864 </para></question> | |
865 <answer><para> | |
866 It's not a DivX file, but an MS MPEG4v3. | |
867 If you have an old version of <filename>codecs.conf</filename> in | |
868 <filename class="directory">~/.mplayer/</filename>, | |
869 <filename class="directory">/etc/</filename>, | |
870 <filename class="directory">/usr/local/etc/</filename> or similar, remove it. | |
871 </para></answer> | 650 </para></answer> |
872 </qandaentry> | 651 </qandaentry> |
873 | 652 |
874 <qandaentry> | 653 <qandaentry> |
875 <question><para> | 654 <question><para> |
899 </para></answer> | 678 </para></answer> |
900 </qandaentry> | 679 </qandaentry> |
901 | 680 |
902 <qandaentry> | 681 <qandaentry> |
903 <question><para> | 682 <question><para> |
904 I have an MJPEG file which works with other players but displays only a black image in | |
905 <application>MPlayer</application> | |
906 </para></question> | |
907 <answer><para> | |
908 Use another codec to play the file, try <option>-vc ffmjpeg</option>. | |
909 </para></answer> | |
910 </qandaentry> | |
911 | |
912 <qandaentry> | |
913 <question><para> | |
914 When I try to grab from my tuner, it works, but colors are strange. It's OK with other | 683 When I try to grab from my tuner, it works, but colors are strange. It's OK with other |
915 applications. | 684 applications. |
916 </para></question> | 685 </para></question> |
917 <answer><para> | 686 <answer><para> |
918 Your card probably reports some colorspaces as supported when in fact | 687 Your card probably reports some colorspaces as supported when in fact |
926 I have A/V sync problems. Some of my AVIs play fine, but some play with double speed! | 695 I have A/V sync problems. Some of my AVIs play fine, but some play with double speed! |
927 </para></question> | 696 </para></question> |
928 <answer><para> | 697 <answer><para> |
929 You have a buggy sound card/driver. Most likely it's fixed at 44100Hz, and you | 698 You have a buggy sound card/driver. Most likely it's fixed at 44100Hz, and you |
930 try to play a file which has 22050Hz audio. Try the resample audio filter. | 699 try to play a file which has 22050Hz audio. Try the resample audio filter. |
931 </para></answer> | |
932 </qandaentry> | |
933 | |
934 <qandaentry> | |
935 <question><para> | |
936 All the WMV (or other..) files I play create a green/gray window and there is | |
937 only sound! <application>MPlayer</application> prints: | |
938 <screen>Detected video codec: [null] drv:0 (NULL codec (no decoding))</screen> | |
939 </para></question> | |
940 <answer><para> | |
941 If you have an old version of <filename>codecs.conf</filename> in | |
942 <filename class="directory">~/.mplayer/</filename>, | |
943 <filename class="directory">/etc/</filename>, | |
944 <filename class="directory">/usr/local/etc/</filename> or similar, remove it. | |
945 </para></answer> | 700 </para></answer> |
946 </qandaentry> | 701 </qandaentry> |
947 | 702 |
948 <qandaentry> | 703 <qandaentry> |
949 <question><para> | 704 <question><para> |
1018 </para></answer> | 773 </para></answer> |
1019 </qandaentry> | 774 </qandaentry> |
1020 | 775 |
1021 <qandaentry> | 776 <qandaentry> |
1022 <question><para> | 777 <question><para> |
1023 What about the DGA driver? I can't find it! | |
1024 </para></question> | |
1025 <answer><para> | |
1026 <filename>./configure</filename> autodetects your DGA driver. If <option>-vo help</option> | |
1027 doesn't show DGA, then there's a problem with your X installation. Try | |
1028 <command>./configure --enable-dga</command> and read the | |
1029 <link linkend="dga">DGA</link> section. Alternatively, try SDL's DGA driver | |
1030 with the <option>-vo sdl:dga</option> option. | |
1031 </para></answer> | |
1032 </qandaentry> | |
1033 | |
1034 <qandaentry> | |
1035 <question><para> | |
1036 OK, <option>-vo help</option> shows DGA driver, but it complains about permissions. | |
1037 Help me! | |
1038 </para></question> | |
1039 <answer><para> | |
1040 It works only if running as root! It's a DGA limitation. You should become root | |
1041 (<command>su -</command>), and try again. Another solution is making | |
1042 <application>MPlayer</application> SUID root, but it's not recommended! | |
1043 <screen> | |
1044 chown root /usr/local/bin/mplayer | |
1045 chmod 755 /usr/local/bin/mplayer | |
1046 chmod +s /usr/local/bin/mplayer | |
1047 </screen> | |
1048 <warning><para> | |
1049 This is a <emphasis role="bold">big</emphasis> security risk! <emphasis role="bold">Never</emphasis> | |
1050 do this on a server or on a computer that you do not control completely because | |
1051 other users can gain root privileges through SUID root <application>MPlayer</application>. | |
1052 <emphasis role="bold">You have been warned</emphasis>. | |
1053 </para></warning> | |
1054 </para></answer> | |
1055 </qandaentry> | |
1056 | |
1057 <qandaentry> | |
1058 <question><para> | |
1059 When using XVideo, my Voodoo 3/Banshee says: | |
1060 <screen> | |
1061 X Error of failed request: BadAccess (attempt to access private resource denied) | |
1062 Major opcode of failed request: 147 (MIT-SHM) | |
1063 Minor opcode of failed request: 1 (X_ShmAttach) | |
1064 Serial number of failed request: 26 | |
1065 Current serial number in output stream:27 | |
1066 </screen> | |
1067 </para></question> | |
1068 <answer><para> | |
1069 The <systemitem>tdfx</systemitem> driver in XFree86 4.0.2/4.0.3 had this bug. This was | |
1070 solved by <ulink url="http://www.xfree86.org/cvs/changes_4_1.html">bug fix #621 | |
1071 of the XFree86 4.1.0 CVS log</ulink>. So upgrade to XFree86 4.1.0 or later. | |
1072 Alternatively, either download (at least) DRI version 0.6 from the | |
1073 <ulink url="http://dri.sf.net">DRI homepage</ulink>, or use CVS DRI. | |
1074 </para></answer> | |
1075 </qandaentry> | |
1076 | |
1077 <qandaentry> | |
1078 <question><para> | |
1079 OpenGL (<option>-vo gl</option>) output doesn't work (hang/black window/X11 | 778 OpenGL (<option>-vo gl</option>) output doesn't work (hang/black window/X11 |
1080 errors/...). | 779 errors/...). |
1081 </para></question> | 780 </para></question> |
1082 <answer><para> | 781 <answer><para> |
1083 Your OpenGL driver doesn't support dynamic texture changes (glTexSubImage). | 782 Your OpenGL driver doesn't support dynamic texture changes (glTexSubImage). |
1084 It's known not to work with nVidia's binary mess. It's known to work with | 783 It's known not to work with nVidia's binary mess. It's known to work with |
1085 Utah-GLX/DRI and Matrox G400 cards. Also with DRI and Radeon cards. It won't | 784 Utah-GLX/DRI and Matrox G400 cards. Also with DRI and Radeon cards. It won't |
1086 work with DRI and other cards. it will not work with 3DFX cards because of | 785 work with DRI and other cards. it will not work with 3DFX cards because of |
1087 the 256x256 texture size limit. | 786 the 256x256 texture size limit. |
1088 </para></answer> | |
1089 </qandaentry> | |
1090 | |
1091 <qandaentry> | |
1092 <question><para> | |
1093 I have an nVidia TNT/TNT2 card, and I have a band with strange colors, right | |
1094 under the movie! Whose fault is this? | |
1095 </para></question> | |
1096 <answer><para> | |
1097 This is a bug of nVidia's binary X driver. These bugs appear ONLY with the | |
1098 TNT/TNT2 cards, and we can't do anything about it. To fix the problem, upgrade | |
1099 to the latest nVidia binary driver version. If still bad, complain to nVidia! | |
1100 </para></answer> | |
1101 </qandaentry> | |
1102 | |
1103 <qandaentry> | |
1104 <question><para> | |
1105 I have an nVidia XYZ card, and when I click on the GUI's display window to | |
1106 toggle displaying the GUI panel, a black square appears where I clicked. I have | |
1107 the newest driver. | |
1108 </para></question> | |
1109 <answer><para> | |
1110 Yes, nVidia corrected a previous bug (above), and introduced a new one. | |
1111 Let's congratulate them. UPDATE: According to <link linkend="nvidia">nVidia</link>, | |
1112 this has already been fixed. | |
1113 </para></answer> | |
1114 </qandaentry> | |
1115 | |
1116 <qandaentry> | |
1117 <question><para> | |
1118 Oh the world is cruel ...! SDL has only <systemitem>x11</systemitem> target, | |
1119 but not <systemitem>xv</systemitem>! | |
1120 </para></question> | |
1121 <answer><para> | |
1122 Try that <systemitem>x11</systemitem> target again. Now try <option>-vo x11 | |
1123 -fs -zoom</option>. See the difference? No?! OK, here comes the enlightenment: | |
1124 SDL's <systemitem>x11</systemitem> target uses xv when available, you don't have | |
1125 to worry about it ... Note: With SDL you can force/disable Xv using | |
1126 <option>-forcexv</option> and <option>-noxv</option>. | |
1127 </para></answer> | 787 </para></answer> |
1128 </qandaentry> | 788 </qandaentry> |
1129 </qandadiv> | 789 </qandadiv> |
1130 | 790 |
1131 <qandadiv id="faq-dvd"> | 791 <qandadiv id="faq-dvd"> |
1141 another player like <application>xine</application>, | 801 another player like <application>xine</application>, |
1142 <application>vlc</application> or <application>Ogle</application>. | 802 <application>vlc</application> or <application>Ogle</application>. |
1143 If you want to see DVD navigation in <application>MPlayer</application> you | 803 If you want to see DVD navigation in <application>MPlayer</application> you |
1144 will have to implement it yourself, but be aware that it is a major | 804 will have to implement it yourself, but be aware that it is a major |
1145 undertaking. | 805 undertaking. |
1146 </para></answer> | |
1147 </qandaentry> | |
1148 | |
1149 <qandaentry> | |
1150 <question><para> | |
1151 While playing a DVD, I encountered this error: | |
1152 <screen>mplayer: ifo_read.c:1143: ifoRead_C_ADT_internal: Assertion nfo_length / sizeof(cell_adr_t) >= c_adt->nr_of_vobs' failed.</screen> | |
1153 </para></question> | |
1154 <answer><para> | |
1155 This is a known libdvdread 0.9.1/0.9.2 bug. Use <emphasis role="bold">libmpdvdkit2</emphasis>, | |
1156 which is present in <application>MPlayer</application> source, and used by default. | |
1157 </para></answer> | |
1158 </qandaentry> | |
1159 | |
1160 <qandaentry> | |
1161 <question><para> | |
1162 Can I compile libdvdread and libdvdcss on my sweet SPARC under Solaris? | |
1163 </para></question> | |
1164 <answer><para> | |
1165 Who knows ... It's said to work, so please test it and send feedback. Refer to | |
1166 the documentation of libdvdread and its homepage as well. We're not the authors | |
1167 of libdvdread. Use <emphasis role="bold">libmpdvdkit2</emphasis>, which is present | |
1168 in <application>MPlayer</application> source, and used by default. | |
1169 </para></answer> | 806 </para></answer> |
1170 </qandaentry> | 807 </qandaentry> |
1171 | 808 |
1172 <qandaentry> | 809 <qandaentry> |
1173 <question><para> | 810 <question><para> |