September 2025 - MPlayer-cvslog - lists.mplayerhq.hu

None
by None 11 Sep '25

11 Sep '25

This amount $21.5m represents the balance of the Estimated revenue total value executed on behalf of my Department by foreign contracting firm, which we the officials over-invoiced deliberately. Though the actual Estimated revenue cost have been paid to the original contractor, leaving the balance in the Tune of the said amount which we have in principles gotten approval to remit by Key tested Telegraphic Transfer (K.T.T) to any foreign bank account you will provide by filing in an application through the Justice Ministry here in South Africa for the transfer of rights and privileges of the former contractor to you. I have the authority of my partners involved to propose that should you be willing to assist us in the transaction, your share of the sum will be 25% of the $21.5 million, 70% for us and 5% for taxation and miscellaneous expenses. The business itself is 100% safe, on your part provided you treat it with utmost secrecy and confidentiality. Also your area of specialization is not a hindrance to the successful execution of this transaction. I have reposed my confidence in you and hope that you will not disappoint me. Endeavor to contact me immediately on my e-mail address or phone number whether or not you are interested in this deal. If you are not, it will enable me scout for another foreign partner to carry out this deal I want to assure you that my partners and myself are in a position to make the payment of this claim possible provided you can give us a very strong Assurance and guarantee that our share will be secured and please remember to treat this matter as very confidential matter, because we will not comprehend with any form of exposure as we are still in active Government Service and remember once again that time is of the essence in this business. I wait in anticipation of your fullest co-operation. Yours faithfully, Mr. FORTUNE M. GROTE. Please reply only to this email account below coopratetrust(a)netscape.net

1 0

None
by None 11 Sep '25

11 Sep '25

This amount $21.5m represents the balance of the Estimated revenue total value executed on behalf of my Department by foreign contracting firm, which we the officials over-invoiced deliberately. Though the actual Estimated revenue cost have been paid to the original contractor, leaving the balance in the Tune of the said amount which we have in principles gotten approval to remit by Key tested Telegraphic Transfer (K.T.T) to any foreign bank account you will provide by filing in an application through the Justice Ministry here in South Africa for the transfer of rights and privileges of the former contractor to you. I have the authority of my partners involved to propose that should you be willing to assist us in the transaction, your share of the sum will be 25% of the $21.5 million, 70% for us and 5% for taxation and miscellaneous expenses. The business itself is 100% safe, on your part provided you treat it with utmost secrecy and confidentiality. Also your area of specialization is not a hindrance to the successful execution of this transaction. I have reposed my confidence in you and hope that you will not disappoint me. Endeavor to contact me immediately on my e-mail address or phone number whether or not you are interested in this deal. If you are not, it will enable me scout for another foreign partner to carry out this deal I want to assure you that my partners and myself are in a position to make the payment of this claim possible provided you can give us a very strong Assurance and guarantee that our share will be secured and please remember to treat this matter as very confidential matter, because we will not comprehend with any form of exposure as we are still in active Government Service and remember once again that time is of the essence in this business. I wait in anticipation of your fullest co-operation. Yours faithfully, Mr. FORTUNE M. GROTE. Please reply only to this email account below coopratetrust(a)netscape.net http://www.dme.gov.za/

1 0

None
by None 11 Sep '25

11 Sep '25

Renamed "TaskScheduler::blockMyself()" to "doEventLoop()", to better describe what this member function actually does. Patch from Andreas Hess <jaska(a)gmx.net> Index: demux_rtp.cpp =================================================================== RCS file: /cvsroot/mplayer/main/libmpdemux/demux_rtp.cpp,v retrieving revision 1.7 retrieving revision 1.8 diff -u -r1.7 -r1.8 --- demux_rtp.cpp 16 Oct 2002 15:15:43 -0000 1.7 +++ demux_rtp.cpp 6 Dec 2002 09:41:13 -0000 1.8 @@ -314,7 +314,11 @@ // block myself until one comes available: TaskScheduler& scheduler = bufferQueue->readSource()->envir().taskScheduler(); +#if USAGEENVIRONMENT_LIBRARY_VERSION_INT >= 1038614400 + scheduler.doEventLoop(&bufferQueue->blockingFlag); +#else scheduler.blockMyself(&bufferQueue->blockingFlag); +#endif } if (demuxer->stream->eof) return 0; // source stream has closed down

1 0

None
by None 11 Sep '25

11 Sep '25

Dr. Bill Akulunon Reply To : fmysc_fmysc(a)indiatimes.com Dear Sir, Confidential Business Proposal I am Dr Bill Akulunon, the Accountant of the Federal Ministry of Youths,Sports,and culture - Parent body of the LocalOrganizing Committee of the 8th All African game tagged "COJA 2003" holding in my country next year .In the course of our preparation to host the 8th All African games, a huge sum of money running into millions of United States Dollars was budgeted by the present civilian administration of our president, Chief Olusegun Obasanjo for the successful prosecution of this competition. In the same vein, the supreme council for sport in Africa also made millions of dollars available for the same competition. However, in my capacity as the Chief Accountant, of both local organizing committee (LOC), and the Federal Ministry of Youths,Sports and culture , my colleagues and I in sensitive positions were able to influence the award of the contract, for the supply and installation of some of the equipment that will be used for the competition. The contractor who handled these projects agreed to give us 10% of the total contract sum, if we were able to influence the award of the contract in their favour. Other foreign firms bided for this same contract, but we were able to influence the board to award the contract to the firm we had this agreement with. This contract has been successfully executed and they have been paid 90% of their total contract sum, remaining the balance of 10% which we never wanted them to collect on our behalf because of the fear that they might not fulfil their promise. It is pertinent to note that, the remaining balance of seven million, united states dollars (US$7,000,000.00) is lying in the suspense account of the First Chartered Bank Lagos, ready for transfer into an oversea account. I have been unanimously mandated to seek for an honest and trustworthy foreign partner who will assist in ensuring the successful transfer of the above sum of money into his Personal/Company account since the Nigerian Code of Conduct Bureau does not permit us to operate a foreign account as public servants. On the successful remittance of the fund (US $7,000,000.00) into your nominated account, for your kind assistance you will be adequately compensated. Be rest assured that, the modalities and logistics towards the successful transfer of this fund have been worked out. All we require from you is your cooperation. This transaction is 100% risk free. We kindly request that you accord it the highest level of secrecy it deserves. Your swift response will be highly appreciated and kindly provide your phone and fax number for further information. Upon your acknowledgement of this proposal, I will forward to you the detailed procedure for this transaction. Note that, this transaction is legal and free from all sorts of risk and trouble. It does not contravene the laws of my country nor any International laws; hence the whole approval for the transfer will be official and legally processed. This transaction will be concluded within five (5) working days if we follow it up and give the serious attention it deserves. Awaiting your prompt response. Best Regards, Dr. Bill Akulunon. ****************************************************** This is an Opti-Target network mailing. You were subscribed to this free service through one of our partner sites. If you believe this email has reached you in error or if you no longer wish to receive these updates, please, **DO NOT** reply to this e-mail.

1 0

None
by None 11 Sep '25

11 Sep '25

[...] p The void * pointer argument is printed in hexadeci- mal (as if by %#x or %#lx). [...] -- MPlayer RPMs maintainer: http://www.piorunek.pl/~dominik/linux/pkgs/mplayer/ "The Universe doesn't give you any points for doing things that are easy." -- Sheridan to Garibaldi in Babylon 5:"The Geometry of Shadows"

1 0

None
by None 11 Sep '25

11 Sep '25

<A HREF="http://www.dtek.chalmers.se/groups/dvd">http://www.dtek.chalmers.se/groups/dvd</A>. </TD><TR><TD COLSPAN=3> </TD><TR> </TABLE> </BODY> </HTML> --- NEW FILE --- <HTML><HEAD> <TITLE>mplayer - codec status table</TITLE> <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1"> </HEAD> <BODY BGCOLOR=#FFFFFF text="#000000" link="#666666" vlink="#666666" alink="#666666" leftmargin="0" topmargin="0" marginwidth="0" marginheight="0"> <table width=750 border="0"> <tr> <td align="right">   Status of codecs support </td> </tr> <td> <a href="#vc">Video codecs</a> <a href="#ac">Audio codecs</a> </td> </tr> <tr> <td align="center"> <a name="vc">Video codecs:</a> <table width="100%" border="1" cellspacing="0" cellpadding="5" bordercolor=#DDDDDD> <tr> <td colspan=6 bgcolor=#CCCCCC>Built-in native codecs</td> </tr> <tr> <td width=150 align=center>codec name</td> <td width=70 align=center>fourcc</td> <td width=120 align=center>codecfile</td> <td width=40 align=center>out</td> <td align=center colspan=2>comments</td> </tr>  <tr> <td align=center>%i</td> <td align=center>%F</td> <td align=center>%d</td> <td align=center>%Y</td> <td align=center colspan=2>%c</td> </tr>  <tr> <td colspan=6 bgcolor=#CCCCCC>Fully functional Win32 VfW/DShow codecs</td> </tr> <tr> <td width=150 align=center>codec name</td> <td width=70 align=center>fourcc</td> <td width=120 align=center>codecfile</td> <td width=40 align=center>out</td> <td align=center>DShow</td> <td align=center>comments</td> </tr>  <tr> <td align=center>%i</td> <td align=center>%F</td> <td align=center>%d</td> <td align=center>%Y</td> <td align=center>%D</td> <td align=center>%c</td> </tr>  <tr> <td colspan=6 bgcolor=#CCCCCC>Codecs with problems</td> </tr> <tr> <td width=150 align=center>codec name</td> <td width=70 align=center>fourcc</td> <td width=120 align=center>codecfile</td> <td colspan=3 align=center>problem</td> </tr>  <tr> <td align=center>%i</td> <td align=center>%F</td> <td align=center>%d</td> <td align=center colspan=3>%c</td> </tr>  <tr> <td colspan=6 bgcolor=#CCCCCC>Not yet working codecs:</td> </tr> <tr> <td width=150 align=center>codec name</td> <td width=70 align=center>fourcc</td> <td width=120 align=center>codecfile</td> <td colspan=3 align=center>problem</td> </tr>  <tr> <td align=center>%i</td> <td align=center>%F</td> <td align=center>%d</td> <td align=center colspan=3>%c</td> </tr>  <tr> <td colspan=6 bgcolor=#CCCCCC>Not tested codecs:</td> </tr> <tr> <td width=150 align=center>codec name</td> <td width=70 align=center>fourcc</td> <td width=120 align=center>codecfile</td> <td colspan=3 align=center>problem</td> </tr>  <tr> <td align=center>%i</td> <td align=center>%F</td> <td align=center>%d</td> <td align=center colspan=3>%c</td> </tr>  </table> <a name="ac">Audio codecs:</a> <table width="100%" border="1" cellspacing="0" cellpadding="5" bordercolor=#DDDDDD> <tr> <td colspan=6 bgcolor=#CCCCCC>Built-in native codecs</td> </tr> <tr> <td width=150 align=center>codec name</td> <td width=70 align=center>format</td> <td width=120 align=center>codecfile</td> <td align=center colspan=3>comments</td> </tr>  <tr> <td align=center>%i</td> <td align=center>%f</td> <td align=center>%d</td> <td align=center colspan=3>%c</td> </tr>  <tr> <td colspan=6 bgcolor=#CCCCCC>Fully functional Win32 ACM/DShow codecs</td> </tr> <tr> <td width=150 align=center>codec name</td> <td width=70 align=center>format</td> <td width=120 align=center>codecfile</td> <td width=40 align=center>DShow</td> <td align=center colspan=2>comments</td> </tr>  <tr> <td align=center>%i</td> <td align=center>%f</td> <td align=center>%d</td> <td align=center>%D</td> <td align=center colspan=2>%c</td> </tr>  <tr> <td colspan=6 bgcolor=#CCCCCC>Codecs with problems</td> </tr> <tr> <td width=150 align=center>codec name</td> <td width=70 align=center>format</td> <td width=120 align=center>codecfile</td> <td colspan=3 align=center>problem</td> </tr>  <tr> <td align=center>%i</td> <td align=center>%f</td> <td align=center>%d</td> <td align=center colspan=3>%c</td> </tr>  <tr> <td colspan=6 bgcolor=#CCCCCC>Not yet working codecs</td> </tr> <tr> <td width=150 align=center>codec name</td> <td width=70 align=center>format</td> <td width=120 align=center>codecfile</td> <td colspan=3 align=center>problem</td> </tr>  <tr> <td align=center>%i</td> <td align=center>%f</td> <td align=center>%d</td> <td align=center colspan=3>%c</td> </tr>  <tr> <td colspan=6 bgcolor=#CCCCCC>Not yet tested codecs</td> </tr> <tr> <td width=150 align=center>codec name</td> <td width=70 align=center>format</td> <td width=120 align=center>codecfile</td> <td colspan=3 align=center>problem</td> </tr>  <tr> <td align=center>%i</td> <td align=center>%f</td> <td align=center>%d</td> <td align=center colspan=3>%c</td> </tr>  </table> </td> </tr> </table> </BODY> </HTML> --- NEW FILE --- <HTML> <BODY BGCOLOR=WHITE> <A NAME=2.2>2.2. Wspierane kodeki</A> <A NAME=2.2.1>2.2.1. Kodeki Video</A> Zobacz: <A HREF="http://www.mplayerhq.hu/DOCS/codecs-status.html"> http://www.mplayerhq.hu/DOCS/codecs-status.html</A>. Znajdziesz tam kompletn±, codziennie tworzon± listê!!! Najwa¿niejsze kodeki video: <UL> <LI>MPEG1 (VCD) i MPEG2 (DVD) video</LI> <LI>DivX ;-), OpenDivX (DivX4), 3ivx i inne warianty MPEG4</LI> <LI>Windows Media Video 7 (WMV1) i 8 (WMV2) wykorzystywany w plikach .wmv</LI> <LI>Kodeki Intel Indeo (3.1,3.2,4.1,5.0)</LI> <LI>MJPEG, ASV2 i inne formaty sprzêtowe</LI> <LI>Kodeki XAnim</LI> <LI>VIVO</LI> </UL> Je¶li masz kodeka Win32 nie wymienionego tutaj, oraz jeszcze nie obs³ugiwanego, przeczytaj <A HREF="#2.2.3">importowanie kodeków</A>, by uzyskaæ informacje o tym, jak pomóc nam w dodaniu wsparcia dla niego! <A NAME=2.2.1.1>2.2.1.1. DivX4</A> Ta sekcja zawiera informacje o kodekach DivX4 z <A HREF="http://www.projectmayo.com">ProjectMayo</A>. Ich pierwsz± dostêpn± wersj± alfa by³ OpenDivX 4.0 alfa 47 oraz 48. Wsparcie dla nich zosta³o do³±czone w MPlayerze, i jest kompilowane standardowo. Dawniej u¿ywali¶my kodu postprocessing z tych kodeków do opcjonalnego zwiêkszenia jako¶ci filmów MPEG1/2. Teraz ju¿ stosujemy w³asny. Nowa generacja tych kodeków potrafi nawet dekodowaæ filmy zrobione z u¿yciem nies³awnych kodeków DivX! Ale to jeszcze nie wszystko! S± one DU¯O szybsze, ni¿ tradycyjne DLLe Win32 DivX. Zobacz poni¿ej opis konfiguracji. Jedyn± wad± tych kodeków jest fakt, ¿e aktualnie s± one closed-source. :( Kodeki mo¿na ¶ci±gn±æ z nastêpuj±cego URL:     <A HREF="http://download2.projectmayo.com/dnload/divx4linux/divx4linux-20010718.zip">http://download2.projectmayo.com/dnload/divx4linux/divx4linux-20010718.zip</A> Rozpakuj je i uruchom, jako root, polecenie: <CODE>./install.sh</CODE> . Uwaga: NIE zapomnij dodaæ /usr/local/lib do /etc/ld.so.conf ! MPlayer automatycznie wykrywa czy DivX4 jest (w³a¶ciwie) zainstalowany, wystarczy go, tak jak zawsze, skompilowaæ. Je¶li mplayer nie wykrywa DivX4, oznacza to, ¿e nie zainstalowa³e¶ go w taki sposób jak powy¿ej podano, i/lub popsu³e¶ konfiguracjê (zobacz ostatnie pytanie w sekcji 5.1). U¿ywanie tego kodeka jest trochê skomplikowane. Poniewa¿ powstaje konflikt ze starym OpenDivX (jego API jest bardzo podobne do do tego z OpenDivX), kod OpenDivX jest wy³±czony, równie¿ sterownik OpenDivX wywo³uje t± bibliotekê. Ogólnie mo¿emy sprowadziæ to zagadnienie do faktu, ¿e masz dwie opcje do zastosowania tego kodeka: <TABLE BORDER=0> <TD>  </TD><TD VALIGN=top>-vc odivx</TD><TD>  </TD> <TD>u¿ycie kodeka divx4 jako nowej wersji OpenDivX. W tym przypadku produkuje on we w³asnym buforze obrazy YV12 oraz MPlayer (libvo) dokonuje konwersji przestrzeni kolorów. (REKOMENDOWANE!)</TD><TR> <TD></TD><TD VALIGN=top>-vc divx4</TD><TD></TD> <TD>u¿ycie konwersji przestrzeni kolorów z kodeka divx4. W tym trybie mo¿na u¿yæ równie¿ YUY2/UYVY.</TD></TR> </TABLE> Metoda 'odivx' jest zazwyczaj szybsza, ze wzglêdu na fakt, ¿e przenosi ona dane obrazu do formatu YV12 (planar YUV 4:2:0), a to wymaga du¿o mniejszego pasma przenoszenia na szynie. W trybie spakowanego YUV (YUY2, UYVY) stosuj metodê 'divx4'. W trybie RGB mo¿esz dowolnie wybieraæ, poniewa¿ prêdko¶ci ich s± takie same, ró¿ni± siê byæ mo¿e tylko w odniesieniu do aktualnego bpp. Uwaga: ten kodek wspiera równie¿ postprocessing, ale zakres warto¶ci jest dziwny: (UAKTUALNIÆ) <TABLE BORDER=0> <TD>  </TD><TD>0</TD><TD>  </TD> <TD>bez postproc</TD><TR> <TD></TD><TD>10 .. 20</TD> <TD></TD><TD>postprocessing, normalny (jak na poziomie 2 z divxd)</TD><TR> <TD></TD><TD>30 .. 60</TD> <TD></TD><TD>mocny prostprocessing, obci±¿a mocno CPU (podobnie jak poziom 4 z divxd</TD><TR> </TABLE> <A NAME=2.2.1.2>2.2.1.2. DivX/libavcodec z ffmpeg</A> Poczynaj±c od wersji 0.4.2, <A HREF="http://ffmpeg.sourceforge.net">ffmpeg</A> zawiera kodek DivX opensource, który jest kompatybilny z tradycyjnym DivX. MPlayer wspiera ten kodek i dziêki temu mo¿liwe staje siê ogl±danie filmów DivX/DivX4 na platformach innych ni¿ x86 oraz osi±ganie du¿o szybszej prêdko¶ci dekodowania DivX/DivX4, ni¿ za pomoc± kodeków Win32 i oryginalnych bibliotek DivX4 . Poniewa¿ zosta³o to usuniête z drzewa cvs MPlayera, musisz ¶ci±gn±æ to rêcznie bezpo¶rednio z drzewa cvs FFmpeg. <CODE> cvs -d:pserver:anonymous@cvs.ffmpeg.sourceforge.net:/cvsroot/ffmpeg login cvs -d:pserver:anonymous@cvs.ffmpeg.sourceforge.net:/cvsroot/ffmpeg co ffmpeg </CODE> UWAGA: Je¶li kopiujesz z podkatalogami CVS, nastêpnym razem wystarczy zrobiæ 'cvs update'. Teraz przenie¶ nowo ¶ci±gniête Œród³a ffmpeg: katalog libavcodec, (ze wszystkimi jego podkatalogami) do drzewa katalogowego MPlayera, tak, aby to wygl±da³o w taki sposób:     <CODE>main/libavcodec</CODE> Linkowanie symboliczne NIE jest wystarczaj±ce. Musisz to skopiowaæ b±dŒ przenie¶æ!!! Nastêpnie skompiluj. configure wykrywa czy wszystko jest w porz±dku i mo¿e byæ skompilowane. Ten kodek równie¿ wspiera postprocessing! W celu u¿ycia go, od¶wie¿ swój plik codecs.conf, zgodnie z tym, co mówi± strony podrêcznika lub example.conf (opcja -vfm). Aby osi±gn±æ najwiêksz± prêdko¶æ na moim K6, usuwam sekcjê <CODE>ffmpeg12</CODE> z codecs.conf (ten kodek nie jest zoptymalizowany a libmpeg2 jest dwa razy szybszy), i wpisujê <CODE>vfm=5</CODE> w moim pliku konfiguracyjnym. Po czym MPlayer zawsze ju¿ u¿ywa ffdivx/ffodivx do dekodowania plików DivX/DivX4 oraz libmpeg2 do plików MPEG1/2. Przy takiej konfiguracji na moim K6/2 500 z Matrox G400 mogê ogl±daæ filmy DivX/DivX4 w najwy¿szej rozdzielczo¶ci, bez straty klatek (framedrop). <A NAME=2.2.1.3>2.2.1.3. Kodeki XAnim</A> U¿ywanie (niektórych) kodeków XAnim z innym programem ni¿ XAnim, jest NIELEGALNE. TWOIM obowi±zkiem jest przeczytanie licencji i zastosowanie siê do niej. Autorzy MPlayera nie mog± zostaæ poci±gniêci do odpowiedzialno¶ci za jakiekolwiek, sprzeczne z prawem, zachowania u¿ytkowników. A wiêc: tak, MPlayer potrafi u¿ywaæ do dekodowania kodeków XAnim. W³±czenie ich jest bardzo proste: <UL> <LI>Šci±gnij kodeki, których chcesz u¿ywaæ ze <A HREF="http://xanim.va.pubnix.com">strony XAnim</A>. Nie ma tam kodeka 3ivx , wiêc ¶ci±gnij go ze <A HREF="http://www.3ivx.com">strony 3ivx</A>.</LI> <LI>U¿yj opcji <CODE>--with-xanimlibdir</CODE>, aby podaæ dla configure, gdzie znajduj± siê kodeki xanim. Domy¶lnie s± one szukane w katalogu <CODE>/</CODE> (...) .</LI> <LI>Zmieñ nazwy plików, obcinaj±c czê¶æ dotycz±c± architektury tak, aby wygl±da³y one nastêpuj±co: <CODE>vid_cvid.xa, vid_h263.xa, vid_iv50.xa</CODE> </UL> Jest to rodzina kodeków video o numerze 10, przydatne wiêc bêdzie u¿ycie opcji <CODE>-vfm 10</CODE> i poinformowanie MPlayera, by ich u¿y³ je¶li to mo¿liwe. Testowane kodeki: Indeo 3.2, 4.1, 5.0, CVID, 3ivX, h263. <A NAME=2.2.1.4>2.2.1.4. Obraz VIVO</A> MPlayer potrafi odgrywaæ obrazy Vivo (1.0 i 2.0). Najbardziej odpowiedni kodek do plików 1.0, to dekoder FFmpeg's H263, Mo¿esz go u¿yæ za pomoc± opcji <CODE>-vc ffh263</CODE> (bêdziesz potrzebowa³ najnowszego libavcodec!). Do plików 2.0 u¿yj <CODE>ivvideo.dll</CODE> pliku DLL Win32 (do sci±gniêcia <A HREF="http://www.mplayerhq.hu/MPlayer/samples/drivers32/ivvideo.dll">tutaj</A>), zainstaluj go w <CODE>/usr/lib/win32</CODE>, b±dŒ w innym miejscu, w którym przechowujesz kodeki Win32. Ten póŒniejszy kodek nie obs³uguje trybów YV12 ani YUY2, a tylko BGR i jest u¿yteczny wy³±cznie z wyj¶ciami X11 i OpenGL. Miejmy nadziejê, ¿e ffh263 bêdzie wspiera³ pliki VIVO 2.0 w przysz³o¶ci. <A NAME=2.2.1.5>2.2.1.5. Obraz MPEG 1/2</A> MPEG1 i MPEG2 s± dekodowane za pomoc± biblioteki w³asnej libmpeg2. Jej kod Œród³owy jest zawarty w MPlayerze i oczywi¶cie jest wieloplatformowy. Obs³ugujemy pliki video MPEG1/2 z b³êdami przez sprawdzanie, jak± sygnaturê zwraca libmpeg2, i kiedy jest to sig11 (segmentation fault), szybko inicjalizujemy ponownie kodek, i kontynuujemy dok³adnie z tego miejsca, w którym pojawi³ siê b³±d. Nie ma tu zauwa¿alnej straty prêdko¶ci. <A NAME=2.2.1.6>2.2.1.6. MS Video1</A> Jest bardzo stary i bardzo z³y kodek Microsoftu. W przesz³o¶ci by³ on dekodowany z kodekiem Win32 <CODE>msvidc32.dll</CODE>, teraz mamy w³asn± implementacjê open-source wykonan± przez <A HREF="mailto:melanson@pcisys.net">Mike'a Melansona</A>). <A NAME=2.2.1.7>2.2.1.7. Cinepak CVID</A> Najlepszym sposobem, aby ogl±daæ obrazy Cinepak za pomoc± MPlayera jest u¿ycie kodeka XAnim <CODE>vid_cvid.xa</CODE>, poniewa¿ obs³uguje on wyj¶cia YV12, YUY2, w przeciwieñstwie do kodeka Win32, który wspiera wy³±cznie RGB. <A NAME=2.2.2>2.2.2. Kodeki dŒwiêku</A> Najwa¿niejsze kodeki dŒwiêku, to: <UL> <LI>MPEG layer 2 oraz layer 3 (MP3) audio(w³asny kod, z optymalizacj± MMX/SSE/3DNow!)</LI> <LI>MPEG layer 1 audio(w³asny kod, z libavcodec)</LI> <LI>AC3 Dolby audio (w³asny kod, z optymalizacj± SSE/3DNow!)</LI> <LI>Ogg Vorbis kodek audio (w³asna biblioteka)</LI> <LI>Voxware audio (u¿ycie DirectShow DLL)</LI> <LI>alaw, msgsm, pcm i inne proste stare formaty dŒwiêkowe</LI> </UL> <A NAME=2.2.2.1>2.2.2.1. Programowe dekodowanie AC3</A> Domy¶lny dekoder, u¿ywany do plików z dŒwiêkiem AC3. Dekoder AC3 mo¿e tworzyæ mieszanki wyj¶ciowego dŒwiêku dla 2, 4 lub 6 g³o¶ników. Skonfigurowany dla 6 g³o¶ników, dekoder ten dostarcza oddzielne wyj¶cia dla wszystkich kana³ów AC3 do sterownika karty dŒwiêkowej, umo¿liwiaj±c do¶wiadczenie wra¿enia pe³nego "dŒwiêku otaczaj±cego", bez wymagania od zewnêtrznego dekodera AC3 u¿ycia kodeka hwac3. U¿yj opcji <CODE>-channels</CODE>, aby wybraæ ilo¶æ kana³ów wyj¶ciowych. U¿yj opcji <CODE>-channels 2</CODE> dla stereo downmix. Dla czterokana³owego downmix (wyj¶cia lewo-przód, prawo-przód, lewo-ty³, prawo-ty³), u¿yj opcji <CODE>-channels 4</CODE>. W tym przypadku jakikolwiek centralny kana³ bêdzie miksowany odpowiednio do przednich kana³ów. Ostatecznie, "-channels 6" bêdzie wyprowadza³o wszystkie kana³y AC3 tak, jak s± zakodowane - w kolejno¶ci lewy, prawy, lewy-tylny, prawy-tylny, centralny oraz LFE. Domy¶lna liczba kana³ów wyj¶ciowych wynosi 2. Aby korzystaæ z wiêcej ni¿ dwóch kana³ów wyj¶ciowych, musisz u¿yæ OSS, i posiadaæ sterownik dla karty dŒwiêkowej, który obs³uguje odpowiedni± liczbê kana³ów wyj¶ciowych przez SNDCTL_DSP_CHANNELS ioctl. Na przyk³ad wersja sterownika emu10k1 (u¿ywanego z kartami SB Live), nowsza ni¿ z sierpnia 2001, powinna byæ odpowiednia. Miksowanie na wyj¶ciu wiêcej ni¿ dwóch kana³ów powinno byæ traktowane jako eksperymentalne. <A NAME=2.2.2.2>2.2.2.2. Sprzêtowe dekodowanie AC3</A> Potrzebna ci bêdzie karta dŒwiêkowa, zdolna do obs³ugi AC3, z cyfrowym wyj¶ciem (SP/DIF). Sterownik karty dŒwiêkowej musi obs³ugiwaæ format AFMT_AC3 (tak, jak to jest w SB Live!). Po³±cz swój dekoder AC3 do wyj¶cia SP/DIF oraz u¿yj opcji '-ac hwac3'. To mo¿e zadzia³aæ, b±dŒ nie (status eksperymentalny - najprawdopodobniej nie zadzia³a). <A NAME=2.2.2.3>2.2.2.3. Obs³uga libmad</A> <A HREF="http://mad.sourceforge.net">libmad</A> jest wieloplatformow± bibliotek± dekodowania dŒwiêku MPEG. Je¶li nie wiesz dlaczego to jest dobre, prawdopodobnie nie potrzebujesz tego. Aby w³±czyæ obs³ugê, skompiluj Œród³a z opcj± <CODE>--enable-mad</CODE>. <A NAME=2.2.2.4>2.2.2.4. DŒwiêk VIVO</A> Kodek dŒwiêku stosowany do plików VIVO zale¿y od tego, czy jest to plik VIVO/1.0, czy VIVO/2.0. Pliki VIVO/1.0 zawieraj± dŒwiêk g.723, za¶ pliki VIVO/2.0 maj± Vivo Siren. Obecnie ¿aden z nich nie jest wspierany, ale mo¿esz ¶ci±gn±æ kodek g.723 z <A HREF="http://www.mplayerhq.hu/MPlayer/samples/drivers32/vivog723.acm">tej strony</A>, a nastêpnie skopiowaæ go do katalogu <CODE>/usr/lib/win32</CODE> lub innego odpowiedniego. <A NAME=2.2.3>2.2.3. Importowanie kodeków Win32</A> <A NAME=2.2.3.1>2.2.3.1. Kodeki VFW</A> VfW (Video for Windows), jest to stare Video API dla Windows. Jego kodeki maj± rozszerzenia .DLL lub (rzadziej) .DRV. Je¶li MPlayer nie dzia³a z twoim AVI:     <CODE>UNKNOWN video codec: HFYU (0x55594648)</CODE> To oznacza, ¿e twój AVI jest zakodowany za pomoc± kodeka, który ma HFYU fourcc (HFYU = kodek HuffYUV, DIV3 = DivX Low Motion, itd....). Teraz, gdy ju¿ to wiemy, bêdziemy musieli dowiedzieæ siê, któr± bibliotekê DLL z Windows za³adowaæ, aby móc odtworzyæ ten plik. W naszym przypadku system.ini zawiera to (oraz wiele innych):     <CODE>VIDC.HFYU=huffyuv.dll</CODE> Tak wiêc bêdziemy potrzebowaæ pliku huffyuv.dll. Zauwa¿, ¿e kodeki dŒwiêku s± wyró¿nione za pomoc± prefiksu MSACM:     <CODE>msacm.l3acm=L3codeca.acm</CODE> To jest kodek MP3. Maj±c ju¿ wszystkie potrzebne informacje (fourcc, plik z kodekiem, próbka AVI), wy¶lij ¿±danie wsparcia dla twojego kodeka mailem i za³aduj te pliki przez FTP:     <CODE>ftp://ftp.mplayerhq.hu/MPlayer/incoming/[nazwa_kodeka]/</CODE> <A NAME=2.2.3.2>2.2.3.2. Kodeki DirectShow</A> DirectShow to najnowsze Video API, które jest nawet gorsze, ni¿ jego poprzednik. Sprawy siê bardziej komplikuj±, odk±d: <UL> <LI>system.ini nie zawiera potrzebnych informacji, a w zamian za to jest przechowywany w rejestrze :( <LI>bêdzie potrzebny nam GUID kodeka. </UL> Wiêc znajdŒmy ten przeklêty rejestr ... <UL> <LI>Uruchom 'regedit'. <LI>Wci¶nij ctrl-f, odznacz pierwsze dwie opcje i zaznacz trzeci±. Wpisz fourcc kodeka (np.: TM20). <LI>Powinno siê pokazaæ pole ze ¶cie¿k± i nazw± pliku (np. : C:\WINDOWS\SYSTEM\TM20DEC.AX). <LI>Skoro mamy ju¿ plik, potrzebne nam jeszcze GUID. Spróbuj jeszcze raz poszukaæ, ale tym razem nazwy kodeka, nie fourcc. Jego nazwê mo¿na odczytaæ w File/Properties/Advanced, podczas odtwarzania tego pliku przez Media Player. Je¶li siê nie da, to pech ;) Spróbuj zgadn±æ (np. szukaj: TrueMotion). <LI>Je¶li znalaz³e¶ (w rejestrze), powinno byæ tam pole FriendlyName oraz pole CLSID. Zapisz, ¿e 16 bajtów CLSID, to potrzebne nam GUID. </UL> UWAGA:Poszukuj±c plików, staraj siê w³±czyæ wszystkie pola wyboru ... Mo¿esz dostaæ wiele nieprzydatnych odpowiedzi, ale byæ mo¿e dostaniesz te w³a¶ciwe przy okazji ... UWAGA: W razie niepowodzenia zrzuæ wszystko na M$. Maj±c ju¿ wszystkie potrzebne informacje (fourcc, GUID, plik z kodekiem, próbka AVI), wy¶lij zg³oszenie wsparcia dla swojego kodeka mailem, i prze¶lij te pliki na adres FTP: ftp://ftp.mplayerhq.hu/MPlayer/incoming/[nazwa_kodeka]/ </BODY> </HTML> --- NEW FILE --- <HTML> <BODY BGCOLOR=WHITE> <CENTER>MPlayer - Movie Player for LINUX (C) 2000-2001 Arpad Gereoffy (A'rpi/ESP-team) <A HREF="http://www.mplayerhq.hu">http://www.mplayerhq.hu</A> <A HREF="../documentation.html">[ Angielski ]</A> <A HREF="../Hungarian/documentation.html">[ Wêgierski ]</A> <A HREF="../German/documentation.html">[ Niemiecki ]</A> <A HREF="../French/documentation.html">[ Francuski ]</A> [ Polski ] </CENTER> <HR> Spis tre¶ci <HR> [...1595 lines suppressed...] </UL> No sound at all: <UL> <LI>your file uses an unsupported codec Workaround: read the documentation and help us adding support for it</LI> </UL> Video-out problems: First note: options -fs -vm and -zoom are just recommendations, not (yet) supported by all drivers. So it isn't a bug if it doesn't work. Only a few driver supports scaling/zooming, don't expect this from x11 or dga. OSD/sub flickering: - x11 driver: sorry, it can't be fixed now - xv driver: use -double option </BODY> </HTML> --- NEW FILE --- <HTML> <BODY BGCOLOR=white> <A NAME=2.4>2.4. Encoding with MEncoder</A> <A NAME=2.4.1>Overview MEncoder (MPlayer's Movie Encoder) is a simple movie encoder, designed to encode MPlayer-playable movies (AVI/DVD/VCD/VOB/MPG/MOV/VIV/NET) to other MPlayer-playable formats (see below). Currently it's in beta stage, and encodes only to DivX4 (1 or 2 passes) video, PCM/MP3/VBRMP3 audio. Also has stream copying abilities. In the future, there will be cropping, resizing filters, and other interesting stuff. <A NAME=2.4.2>Compiling <UL> <LI>read MPlayer's compilation instructions, it contains info about how to install libdvdread for DVD support, etc.</LI> <LI>download the newest DivX4linux libs from <A HREF="http://avifile.sourceforge.net/download.htm">avifile.sourceforge.net</A>, and have them PROPERLY installed. This is needed for DivX4 (1/2 pass) encoding. And since this is mandatory (now), MEncoder is Linux-only.</LI> <LI>download and compile libmp3lame (from lame 3.89beta or lame CVS). WARNING : DO NOT COMPILE LAME WITH GCC 2.96 ! It won't work properly ! This is needed for CBR/VBR MP3 audio encoding ability. Note that a single <CODE>lame</CODE> binary isn't sufficient. BTW: the less optimization you use for lame, the better the quality will be. You can test quality by running <CODE>make test</CODE> after lame's compiling process is over. The resulting number should be less than 30. Don't panic if it's 400 or so, you shouldn't heard any audible quality decrease. Oh, and if your compiler doesn't even run <CODE>make test</CODE> ... Well, delete that GCC 2.96.</LI> <LI>use <CODE>./configure</CODE> with optional parameters as usual (use <CODE>--enable-tv</CODE> to include V4L tuner grabbing code), and type : <CODE>make mencoder</CODE> , then <CODE>make install</CODE>.</LI> </UL> You are ready. As you probably know, other encoding tools need the avifile library installed. MEncoder doesn't need it at all. <A NAME=2.4.3>MEncoder features : <UL> <LI>encoding from the wide range of fileformats and decoders of MPlayer</LI> <LI>encoding from V4L compatible TV tuners</LI> <LI>encoding/multiplexing to interleaved AVI files with proper index</LI> <LI>1 or 2 pass DivX4 video</LI> <LI>VBR MP3 audio</LI> <LI>PCM audio</LI> <LI>stream copying (CBR audio only)</LI> <LI>input A/V synchronizing (PTS-based, can be disabled with -mc 0 option)</LI> <LI>FPS correction with <CODE>-ofps</CODE> option (useful when encoding 29.97fps VOB to 24fps AVI)</LI> <LI>movie rescaling</LI> </UL> Planned features : <UL> <LI>using audio from separate file (AC3, MP3, OGG)</LI> <LI>VBR audio stream copy</LI> <LI>even wider variety of available en/decoding formats/codecs (creating VOB files with DivX4/Indeo5/VIVO streams :)</LI> </UL> <A NAME=2.4.3.1>Encoding 2-pass DivX4 The name comes from the fact that this method encodes the file twice. The first encoding (dubbed pass) creates some temporary files with a size of few megabytes (do not delete them yet). In the second pass, the output file is created, using the bitrate data from the temporary file. The resulting file will have much better image quality. If this is the first time you heard about this, you should consult some guides available on the Net. This example shows how to encode a DVD to a 2-pass DivX4 AVI. Just two commands are needed : <CODE>    mencoder -dvd 2 -ovc divx4 -oac mp3lame -divx4opts br=1100 -o movie.avi -pass 1     mencoder -dvd 2 -ovc divx4 -oac mp3lame -divx4opts br=1100 -o movie.avi -pass 2</CODE> <A NAME=2.4.3.2>Rescaling movies Often the need to resize movie images' size emerges. Its reasons can be many, examples are decreasing output file size, encoding SVCDs to DivX. Ripped DVDs are mostly rescaled, for example a 4:3 DVD should be 640x480, especially when you want it to fit to 1 CD, and have good quality at the same time. SVCDs have 480x480 size, and their header contains the aspect ratio the player should use (Ex.: 480x480 + 4:3 = 640x480). However when encoding to AVI (DivX) files, you have be aware that AVI headers don't store this value. Thus, the only solution is rescaling. The output size is specified with the <CODE>-x</CODE>, and <CODE>-y</CODE> options. Furthermore, there are 3 rescaling filters in MEncoder, 0 : fast 1 : bilinear, 2 : bilinear, bicubic (best quality). They can be specified with the <CODE>-sws</CODE> option. If not specified, MEncoder will use 0 : fast bilinear. Rescaling is very simple : <CODE>    mencoder sample-svcd.mpg -divx4opts br=1300 -x 640 -y 480 -sws 2 -o output.avi</CODE> <A NAME=2.4.3.3>Stream copying MEncoder can handle input streams in two ways : encode or copy them. This section is about copying. <UL> <LI>Video stream (option <CODE>-ovc copy</CODE>) : nice stuff can be done :) Like, putting (not converting!) FLI or VIVO or MPEG1 video into an AVI file ! Of course only MPlayer can play such files :) And it probably has no real life value at all. Rationally : video stream copying can be useful for example when only the audio stream has to be encoded (like, uncompressed PCM to MP3).</LI> <LI>Audio stream (option <CODE>-oac copy</CODE>) : straightforward.</LI> </UL> <A NAME=2.4.4>Syntax   <CODE>mencoder [options] [input file] [options] ... <A NAME=2.4.5>Available options NOTE : for all available options, read the manpage ! <TABLE BORDER=0> <TR> <TD>  </TD> <TD> -o filename</TD> <TD>  </TD> <TD> specify output filename </TD> </TR> <TR> <TD>  </TD> <TD> -x width in pixels</TD> <TD>  </TD> <TD> rescale output video to given pixels width </TD> </TR> <TR> <TD>  </TD> <TD> -y height in pixels</TD> <TD>  </TD> <TD> rescale output video to given pixels height </TD> </TR> <TR> <TD>  </TD> <TD> -sws 0-2</TD> <TD>  </TD> <TD> type of scaling method   0 - fast bilinear   1 - bilinear   2 - bicubic (best quality) </TD> </TR> <TR> <TD>  </TD> <TD> -ovc codecname</TD> <TD>  </TD> <TD> Encode with the given codec (codec names are from codecs.conf). Examples:   help - get list of available codecs   copy - no encoding, just copy the stream (only from AVI/ASF now)   divx4 - encode to DivX4 </TD> </TR> <TR> <TD>  </TD> <TD> -oac codecname</TD> <TD>  </TD> <TD> Encode with the given codec (codec names are from codecs.conf). Examples:   help - get list of available codecs   copy - no encoding, just copy the stream (only from AVI/ASF now)   pcm - encode to uncompressed PCM   mp3lame - encode to MP3 (using Lame) </TD> </TR> <TR> <TD>  </TD> <TD> -divx4opts</TD> <TD>  </TD> <TD> If encoding to DivX4, you can specify its parameters here, like:   <CODE>-divx4opts br=1800:deinterlace:key=250</CODE> Common options: (for full list, check the manpage!)   help - get help   br=XXX - specify bitrate in kbit <4-16000> or bit <16001-24000000>   q=XXXX - quality (1-fastest, 5-best - default 5) </TD> </TR> <TR> <TD>  </TD> <TD> -lameopts</TD> <TD>  </TD> <TD> If encoding to MP3 with libmp3lame, you can specify its parameters here, like:   <CODE>-lameopts q=3</CODE>   <CODE>-lameopts br=192:cbr</CODE> Common options: (for full list, check the manpage!)   help - get help   cbr - select CBR MP3 (default is VBR)   br=XXX - specify bitrate in kbit <0-1024> (this is for CBR only!)   q=XXXX - quality (0-highest, 9-fastest - default 0) (this is for VBR only!) </TD> </TR> </TABLE> <A NAME=2.4.6>Examples Using MEncoder is the easiest thing on Earth. See the following : Encoding from DVD, title 2 : <CODE>    mencoder -dvd 2 -o title2.avi</CODE> Encoding from DVD, title 2, with rescaling : <CODE>    mencoder -dvd 2 -x 640 -y 480 -sws 2 -o title2.avi</CODE> Encoding from HTTP : <CODE>    mencoder http://mplayer.hq/example.avi -o example.avi</CODE> Encoding from a pipe : <CODE>    rar p test-SVCD.rar | mencoder -divx4opts br=800 -ofps 24 -pass 1 -- -</CODE> Encoding multiple *.vob files : <CODE>    cat *.vob | mencoder <options> -</CODE> Encoding from tuner (for tuner options <A HREF="documentation.html#2.5">see the TV input section !</A>) : <CODE>    mencoder -tv on:driver=v4l:width=640:height=480 <options></CODE> For all available options, check the MEncoder man page ! </BODY> </HTML> --- NEW FILE --- <HTML> <BODY BGCOLOR=white> <A NAME=5>5. FAQ section</A> <TABLE BORDER=0 WIDTH=100% ALIGN=left> <TD COLSPAN=3><A NAME=5.1>5.1 Compilation</A> </TD><TR><TD COLSPAN=3> </TD><TR> <TD>  </TD><TD VALIGN=top>Q:</TD><TD WIDTH=100%> configure ends with this text, and MPlayer won't compile ! <CODE>Your gcc does not support even i386 for '-march' and '-mcpu'.</CODE> </TD><TR><TD></TD><TD VALIGN=top>A:</TD><TD> Your gcc isn't installed correctly, check <CODE>config.log</CODE> file for details. </TD><TR><TD COLSPAN=3> </TD><TR> <TD>  </TD><TD VALIGN=top>Q:</TD><TD WIDTH=100%> What does "No such file or directory" means ? </TD><TR><TD></TD><TD VALIGN=top>A:</TD><TD> Probably there is no such file or directory. </TD><TR><TD COLSPAN=3> </TD><TR> <TD>  </TD><TD VALIGN=top>Q:</TD><TD WIDTH=100%> What's the problem with gcc 2.96 ? </TD><TR><TD></TD><TD VALIGN=top>A:</TD><TD> To be short: DO NOT USE gcc 2.96 !!! Check <A HREF="gcc-2.96-3.0.html">this</A> and <A HREF="users_against_developers.html">this</A> texts! If you still really really want to do so, be sure to use the latest release. </TD><TR><TD COLSPAN=3> </TD><TR> <TD></TD><TD VALIGN=top>Q:</TD><TD WIDTH=100%> Great, I have gcc 3.0.1 from RedHat/Mandrake, then I'm fine--! </TD><TR><TD></TD><TD VALIGN=top>A:</TD><TD> No, since there have been/are issues with those compilers. Use 2.95.x series for reliability (not <A HREF="gcc-2.96-3.0.html">2.96</A>). Use the latest gcc 3.0.x (starting at 3.0.2) if you want to use a 3.0.x version. </TD><TR><TD COLSPAN=3> </TD><TR> <TD></TD><TD VALIGN=top>Q:</TD><TD WIDTH=100%> I tried to compile MPlayer, but I got this output: <PRE> In file included from /usr/include/g++-v3/bits/std_cwchar.h:42, from /usr/include/g++-v3/bits/fpos.h:40, from /usr/include/g++-v3/bits/char_traits.h:40, from /usr/include/g++-v3/bits/std_string.h:41, from /usr/include/g++-v3/string:31, from libwin32.h:36, from DS_AudioDecoder.h:4, from DS_AudioDec.cpp:5: /usr/include/wchar.h: In function Long long int wcstoq(const wchar_t*, wchar_t**, int)': /usr/include/wchar.h:514: cannot convert `const wchar_t* __restrict' to `const </PRE> </TD><TR><TD></TD><TD VALIGN=top>A:</TD><TD> Upgrade your glibc to the newest. On Mandrake, use 2.2.4-8mdk . </TD><TR><TD COLSPAN=3> </TD><TR> <TD></TD><TD VALIGN=top>Q:</TD><TD WIDTH=100%> ...gcc 2.96... (yes, some people are STILL flaming about their gcc 2.96!!) </TD><TR><TD></TD><TD VALIGN=top>A:</TD><TD> But we has idegs (the word 'ideg' is described further in the FAQ). And our idegcounters overflow again and again. Unfortunately MPlayer is out of our control. It's used by lamers, Linux users who can't even use windows, and never tried to compile a kernel. They installed (with default options) Mandrake or RedHat or Suse, and without RTFM'ing they send messages saying 'it doesn't work! help me! please! i'm new to the linux! help! oh! help me!'. We can't stop them, but at least we try to force them RTFM and to read fuckin' messages of ./configure and mplayer. And you clever guys come and flame us with gcc 2.96 and binary packages. Instead of helping users or making patches to help solve problems. Half of our spare/free time is spent by answering silly mails here and making newer tricks and checks to configure to avoid such mails. And there is a balance. On one hand are you, clever guys, saying we are very bad because we don't like buggy gcc 2.96, and at the other hand there are the 'new to linux' guys who are showing us gcc 2.96 is buggy. Conclusion: we can't be good. Half of people always will say we are bad. Maybe we should close the project, make it closed source, commercial, and provide install support for it. then we could leave current work, so development could go faster, and we earn lots of money with it and buy a big house, etc etc. Do you really want it? It seems. Arpi (a mail on the mplayer-users list) </TD><TR><TD COLSPAN=3> </TD><TR> <TD></TD><TD VALIGN=top>Q:</TD><TD WIDTH=100%> Where can I find information about gcc 2.96 bugs ? </TD><TR><TD></TD><TD VALIGN=top>A:</TD><TD> In <A HREF="gcc-2.96-3.0.html">this</A> documentation. And <A HREF="users_against_developers.html">this</A> documentation describes why RedHat released 2.96 and other interesting things. </TD><TR><TD COLSPAN=3> </TD><TR> <TD></TD><TD VALIGN=top>Q:</TD><TD WIDTH=100%> SDL output doesn't work or compile. Problem is .... </TD><TR><TD></TD><TD VALIGN=top>A:</TD><TD> It is tested with newest SDL (probably runs on 1.1.7+). It does NOT work with any previous version, so don't ask. </TD><TR><TD COLSPAN=3> </TD><TR> <TD></TD><TD VALIGN=top>Q:</TD><TD WIDTH=100%> I am still having trouble compiling with SDL support. gcc says something about "undefined reference to `SDL_EnableKeyRepeat'" What's now? </TD><TR><TD></TD><TD VALIGN=top>A:</TD><TD> Where did you install the SDL library? If you installed in /usr/local (the default) then edit the top level config.mak and add "-L/usr/local/lib " after "X_LIBS=" Now type make. You're done! </TD><TR><TD COLSPAN=3> </TD><TR> <TD></TD><TD VALIGN=top>Q:</TD><TD WIDTH=100%> It doesn't compile, and it misses uint64_t inttypes.h and similar things... </TD><TR><TD></TD><TD VALIGN=top>A:</TD><TD> copy etc/inttypes.h to MPlayer directory (cp etc/inttypes.h .) try again... </TD><TR><TD COLSPAN=3> </TD><TR> <TD></TD><TD VALIGN=top>Q:</TD><TD WIDTH=100%> I have Pentium III but ./configure doesn't detect SSE </TD><TR><TD></TD><TD VALIGN=top>A:</TD><TD> Only kernel versions 2.4.x supports SSE (or try latest 2.2.19 or newer, but be prepared for problems) </TD><TR><TD COLSPAN=3> </TD><TR> <TD></TD><TD VALIGN=top>Q:</TD><TD WIDTH=100%> I have G200/G400, how to compile/use mga_vid driver? </TD><TR><TD></TD><TD VALIGN=top>A:</TD><TD> Read all this documentation. </TD><TR><TD COLSPAN=3> </TD><TR> <TD></TD><TD VALIGN=top>Q:</TD><TD WIDTH=100%> Are there rpm/deb/... packages of MPlayer? </TD><TR><TD></TD><TD VALIGN=top>A:</TD><TD> You can make a .deb package for yourself, check section <A HREF="documentation.html#6.1">6.1</A>. It's _STRONGLY_ discouraged to use precompiled packages of MPlayer, since it (currently) _highly_ depends on compile-time options and optimizations! Precompiled packages are COMPLETELY unsupported by the MPlayer team! </TD><TR><TD COLSPAN=3> </TD><TR> <TD></TD><TD VALIGN=top>Q:</TD><TD WIDTH=100%> During 'make', MPlayer complains about X11 libraries. I don't understand, I DO have X installed!? </TD><TR><TD></TD><TD VALIGN=top>A:</TD><TD> ...but you don't have the X development package installed. Or not correctly. It's called XFree86-devel* under RedHat, and xlib6g-dev* under Debian. Also check if the /usr/X11 symlink exists (this can be a problem on Mandrake systems). It can be created with the     <CODE>$ ln -sf /usr/X11R6 /usr/X11</CODE> command. Also check the /usr/include/X11 link :     <CODE>$ ln -sf /usr/X11R6/include/X11 /usr/include/X11</CODE> Your distribution may differ from the Linux Filesystem Standard. </TD><TR><TD COLSPAN=3> </TD><TR> <TD></TD><TD VALIGN=top>Q:</TD><TD WIDTH=100%> What about DGA driver? I can't find it!!! </TD><TR><TD></TD><TD VALIGN=top>A:</TD><TD> ./configure autodetects your DGA driver. If -vo help doesn't show DGA, then there's a problem with your X installation. Try ./configure --enable-dga (and RTFM) Alternatively, try SDL's DGA driver with '-vo sdl:dga' options. </TD><TR><TD COLSPAN=3> </TD><TR> <TD></TD><TD VALIGN=top>Q:</TD><TD WIDTH=100%> I can't compile SVGAlib.. I'm using 2.3/2.4 kernel. </TD><TR><TD></TD><TD VALIGN=top>A:</TD><TD> You have to edit SVGAlib's Makefile.cfg and comment "BACKGROUND = y" out. </TD><TR><TD COLSPAN=3> </TD><TR> <TD></TD><TD VALIGN=top>Q:</TD><TD WIDTH=100%> I compiled MPlayer with libdvdcss/libdivxdecore support, but when I try to start it, it says: <CODE>> error while loading shared libraries: lib*.so.0: cannot load shared object file: No such file or directory</CODE> I checked up on the file and it IS there in /usr/local/lib. </TD><TR><TD></TD><TD VALIGN=top>A:</TD><TD> What are you doing on Linux? Can't you install a library? Why do we get these questions? It's not MPlayer specific at all! Add /usr/local/lib to /etc/ld.so.conf and run ldconfig . Or install it to /usr/lib , because if you can't solve the /usr/local problem, you are careless enough to do such things. </TD><TR><TD COLSPAN=3> </TD><TR> <TD></TD><TD VALIGN=top>Q:</TD><TD WIDTH=100%> MPlayer doesn't seem to find my libcss. What am I doing wrong ? </TD><TR><TD></TD><TD VALIGN=top>A:</TD><TD> It's normal. MPlayer no longer depends on libcss to play a DVD. You have to install libdvdread and libdvdcss. Check for DVD Playback part <A HREF="cd-dvd.html">here</A>. libcss is to be used for example when you want to play encrypted VOB files from hard disk (not for general users). </TD><TR><TD COLSPAN=3> </TD><TR> <TD></TD><TD VALIGN=top>Q:</TD><TD WIDTH=100%> Hmm, strange. When loading the mga_vid.o kernel module, I found this in the logs: <CODE>Warning: loading mga_vid.o will taint the kernel: no license</CODE> </TD><TR><TD></TD><TD VALIGN=top>A:</TD><TD> The latest kernels modules needs require a flag indicating its license (mainly to avoid kernel hackers' debugging closed sources drivers). Upgrade your kernel and your modutils and MPlayer. </TD><TR><TD COLSPAN=3> </TD><TR> <TD></TD><TD VALIGN=top>Q:</TD><TD WIDTH=100%> When compiling MEncoder, it segfaults at linking !!! </TD><TR><TD></TD><TD VALIGN=top>A:</TD><TD> Dunno, upgrading binutils should help (2.11.92.* or newer should be good). Not our fault, do NOT report! </TD><TR><TD COLSPAN=3> </TD><TR> <TD></TD><TD VALIGN=top>Q:</TD><TD WIDTH=100%> I'd like to compile MPlayer on Minix ! </TD><TR><TD></TD><TD VALIGN=top>A:</TD><TD> Me too. </TD><TR><TD COLSPAN=3> </TD><TR> <TD COLSPAN=3><A NAME=5.2>5.2. General questions</A> </TD><TR><TD COLSPAN=3> </TD><TR> <TD></TD><TD VALIGN=top>Q:</TD><TD WIDTH=100%> What about DVD playing ? </TD><TR><TD></TD><TD VALIGN=top>A:</TD><TD> Read the CD/DVD section in <A HREF="cd-dvd.html">this page</A>. </TD><TR><TD COLSPAN=3> </TD><TR> <TD></TD><TD VALIGN=top>Q:</TD><TD WIDTH=100%> -xy or -fs option doesn't work with x11 driver (-vo x11) </TD><TR><TD></TD><TD VALIGN=top>A:</TD><TD> It does, but you have to explicitly specify software scaling (it's SLOW!) with the <CODE>-zoom</CODE> option. You better use XF86VidMode support: you must specify the -vm and the -fs switch, and you're done. Make sure you have the right Modelines in your XF86Config file, and try if the DGA driver (and SDL's DGA driver, see RTFM) works for you. It's much faster. If SDL's DGA works too, use that, it'll be EVEN faster! </TD><TR><TD COLSPAN=3> </TD><TR> <TD></TD><TD VALIGN=top>Q:</TD><TD WIDTH=100%> What is the meaning of numbers in the status line? </TD><TR><TD></TD><TD VALIGN=top>A:</TD><TD> See: <CODE>A: 2.1 V: 2.2 A-V: -0.167 ct: 0.042 57 41% 0% 2.6% 0 4</CODE> <UL> <LI>A: audio position in seconds <LI>V: video position in seconds <LI>A-V: audio-video difference in seconds (delay) <LI>ct: total A-V sync correction done <LI>frames played (counting from last seek) <LI>video codec cpu usage in percent (for mpeg it includes video_out too!) <LI>video_out cpu usage for avi, 0 for mpg (see above) <LI>audio codec cpu usage in percent <LI>frames needed to drop to maintain A-V sync <LI>current level of image postprocessing (when using -autoq) </UL> Most of them are for debug purposes, and will be removed soon. </TD><TR><TD COLSPAN=3> </TD><TR> <TD></TD><TD VALIGN=top>Q:</TD><TD WIDTH=100%> What if I don't want them to appear? </TD><TR><TD></TD><TD VALIGN=top>A:</TD><TD> Then you use the -quiet option, and read the manpage. </TD><TR><TD COLSPAN=3> </TD><TR> <TD></TD><TD VALIGN=top>Q:</TD><TD WIDTH=100%> Why is video_out cpu usage zero (0%) for mpeg files? </TD><TR><TD></TD><TD VALIGN=top>A:</TD><TD> It's not zero, but it's built in into codec, so can't be measured separated. You should try to play the file using -vo null and then -vo ... and check the difference to see video_out speed... </TD><TR><TD COLSPAN=3> </TD><TR> <TD></TD><TD VALIGN=top>Q:</TD><TD WIDTH=100%> What's XMMP? (is it XMMS or XMPS but mispelled?) </TD><TR><TD></TD><TD VALIGN=top>A:</TD><TD> It's a new project, see http://frozenproductions.com for details </TD><TR><TD COLSPAN=3> </TD><TR> <TD></TD><TD VALIGN=top>Q:</TD><TD WIDTH=100%> There are error messages about file not found /usr/lib/win32/.... </TD><TR><TD></TD><TD VALIGN=top>A:</TD><TD> Download <A HREF="ftp://ftp.mplayerhq.hu/MPlayer/releases/w32codec.zip">w32codec.zip</A> from *our* FTP (avifile's codec package has different DLL set). Install it. </TD><TR><TD COLSPAN=3> </TD><TR> <TD></TD><TD VALIGN=top>Q:</TD><TD WIDTH=100%> Are there any mailing lists on MPlayer? </TD><TR><TD></TD><TD VALIGN=top>A:</TD><TD> Yes! See RTFM on how to subscribe them! </TD><TR><TD COLSPAN=3> </TD><TR> <TD></TD><TD VALIGN=top>Q:</TD><TD WIDTH=100%> I've found a nasty bug when I tried to play my favourite video!! Who should I inform? </TD><TR><TD></TD><TD VALIGN=top>A:</TD><TD> See Appendix <A HREF="bugreports.html">C</A>. </TD><TR><TD COLSPAN=3> </TD><TR> <TD></TD><TD VALIGN=top>Q:</TD><TD WIDTH=100%> I have problems playing files with ... codec. Can I use'em? </TD><TR><TD></TD><TD VALIGN=top>A:</TD><TD> Check <A HREF="http://www.mplayerhq.hu/DOCS/codecs-status.html">http://www.mplayerhq.hu/DOCS/codecs-status.html</A>, if it doesn't contain your codec, read <A HREF="codecs.html#2.1.3">section 2.1.3</A>, and contact us. </TD><TR><TD COLSPAN=3> </TD><TR> <TD></TD><TD VALIGN=top>Q:</TD><TD WIDTH=100%> Umm, what is "IdegCounter"? </TD><TR><TD></TD><TD VALIGN=top>A:</TD><TD> A mixture of a hungarian and an english word. In english, "Ideg" means "nerve", and is pronounced as something like "ydaegh" . It was first used to measure the nervousness of A'rpi, after some (umm) "mystic" disappearance of CVS code ;) </TD><TR><TD COLSPAN=3> </TD><TR> <TD></TD><TD VALIGN=top>Q:</TD><TD WIDTH=100%> And what is "Faszom(C)ounter" ? </TD><TR><TD></TD><TD VALIGN=top>A:</TD><TD> "Fasz" is a hungarian word you don't want to know, the others are in connection with the pervert minds of the MPlayer developers. </TD><TR><TD COLSPAN=3> </TD><TR> <TD></TD><TD VALIGN=top>Q:</TD><TD WIDTH=100%> LIRC doesn't work, because ... </TD><TR><TD></TD><TD VALIGN=top>A:</TD><TD> Are you sure you use "mplayer_lirc" instead of "mplayer"? </TD><TR><TD COLSPAN=3> </TD><TR> <TD></TD><TD VALIGN=top>Q:</TD><TD WIDTH=100%> Subtitles are very nice, the most beautiful I've ever seen, but they slow down the playing! I know it's unlikely... </TD><TR><TD></TD><TD VALIGN=top>A:</TD><TD> After running ./configure , edit config.h and replace <CODE>#undef FAST_OSD</CODE> with <CODE>#define FAST_OSD</CODE>. Then recompile. </TD><TR><TD COLSPAN=3> </TD><TR> <TD></TD><TD VALIGN=top>Q:</TD><TD WIDTH=100%> The OSD is flickering! </TD><TR><TD></TD><TD VALIGN=top>A:</TD><TD> You use a vo driver with single buffering (x11,xv). With xv, use -double option. </TD><TR><TD COLSPAN=3> </TD><TR> <TD></TD><TD VALIGN=top>Q:</TD><TD WIDTH=100%> What exactly is this libavcodec? </TD><TR><TD></TD><TD VALIGN=top>A:</TD><TD> See the <A HREF="codecs.html#2.1.2.2">2.1.2.2 section</A>. </TD><TR><TD COLSPAN=3> </TD><TR> <TD></TD><TD VALIGN=top>Q:</TD><TD WIDTH=100%> But configure tells me "Checking for libavcodec ... no"! </TD><TR><TD></TD><TD VALIGN=top>A:</TD><TD> You need to get libavcodec from FFmpeg's CVS. Read the instructions in the <A HREF="codecs.html#2.1.2.2">ffmpeg section</A>. </TD><TR><TD COLSPAN=3> </TD><TR> <TD></TD><TD VALIGN=top>Q:</TD><TD WIDTH=100%> The GUI isn't usable with icewm, because some panel are over the movie!! </TD><TR><TD></TD><TD VALIGN=top>A:</TD><TD> Known, icewm is shit and dictatoric. Unsolvable. In detail: icewm sucks because its taskbar overrides GUI's window resize queries. If it asks for resize to 800x600, then it resizes window to 800x(600-taskbar_size). It's bad. Very bad. In short: shit. </TD><TR><TD COLSPAN=3> </TD><TR> <TD></TD><TD VALIGN=top>Q:</TD><TD WIDTH=100%> I can't access the GUI menu. I press right click, but I can't access any menu items ! </TD><TR><TD></TD><TD VALIGN=top>A:</TD><TD> Are you using FVWM ? Try the following : Start -> Settings -> Configuration -> Base Configuration Set "Use Applications position hints" to Yes. </TD><TR><TD COLSPAN=3> </TD><TR> <TD COLSPAN=3> <A NAME=5.3>5.3. File playing problems</A> </TD><TR><TD COLSPAN=3> </TD><TR> <TD></TD><TD VALIGN=top>Q:</TD><TD WIDTH=100%> ...... works with avifile/aviplay while doesn't with MPlayer. </TD><TR><TD></TD><TD VALIGN=top>A:</TD><TD> MPlayer != avifile The only common thing between these players is the Win32 DLL loader. The codecs (dll) sets, syncronization, demultiplexing etc is totaly different and shouldn't be compared. If something works with aviplay it doesn't mean that MPlayer should do it and vice versa. </TD><TR><TD COLSPAN=3> </TD><TR> <TD></TD><TD VALIGN=top>Q:</TD><TD WIDTH=100%> Audio goes out of sync playing .avi file. </TD><TR><TD></TD><TD VALIGN=top>A:</TD><TD> Try with -bps or -nobps option if still bad, send me (upload to ftp) that file, I'll check. </TD><TR><TD COLSPAN=3> </TD><TR> <TD></TD><TD VALIGN=top>Q:</TD><TD WIDTH=100%> Indeo 3.x/4.x movies are viewed upside-down!!!? </TD><TR><TD></TD><TD VALIGN=top>A:</TD><TD> It's a known bug (really it's a bug/limitation of the DLL codec) Try if your vo driver supports the -flip switch. </TD><TR><TD COLSPAN=3> </TD><TR> <TD></TD><TD VALIGN=top>Q:</TD><TD WIDTH=100%> Indeo 3.x,4.x video doesn't work at 32bpp resolutions (16,24 bpp are ok). </TD><TR><TD></TD><TD VALIGN=top>A:</TD><TD> It's a known bug (really it's a bug/limitation of the DLL codec). </TD><TR><TD COLSPAN=3> </TD><TR> <TD></TD><TD VALIGN=top>Q:</TD><TD WIDTH=100%> MPlayer exits with something error when using l3codeca.acm. </TD><TR><TD></TD><TD VALIGN=top>A:</TD><TD> Check 'ldd /usr/local/bin/mplayer' output. If it contains     <CODE>libc.so.6 => /lib/libc.so.6 (0x4???????)</CODE> where "?" is any number then it's ok, the error is not here. If it is:     <CODE>libc.so.6 => /lib/libc.so.6 (0x00??????)</CODE> then there is problem with your kernel/libc. Maybe you are using some security patches (for example Solar Designer's OpenWall patch) which forces loading libraries to very low addresses. Because l3codeca.acm is a non-relocatable DLL, it must be loaded to 0x00400000, we can't change this. You should use non-patched kernel, or use MPlayer's -afm 1 option to disable using l3codeca.acm. </TD><TR><TD COLSPAN=3> </TD><TR> <TD></TD><TD VALIGN=top>Q:</TD><TD WIDTH=100%> My computer plays M$ DivX AVIs with resolutions ~ 640x300 and stereo mp3 sound too slow. When I use -nosound switch, everything is ok (but quiet). </TD><TR><TD></TD><TD VALIGN=top>A:</TD><TD> Ok son, your machine is too slow. RTFM or anything. </TD><TR><TD COLSPAN=3> </TD><TR> <TD></TD><TD VALIGN=top>Q:</TD><TD WIDTH=100%> MPlayer dies with "MPlayer interrupted by signal 4 in module: decode_video". </TD><TR><TD></TD><TD VALIGN=top>A:</TD><TD> Try running MPlayer on the machine you compiled on. Or recompile. Don't use MPlayer on different CPU than it was compiled on. </TD><TR><TD COLSPAN=3> </TD><TR> <TD></TD><TD VALIGN=top>Q:</TD><TD WIDTH=100%> I have problems with [your window manager] and fullscreen xv/xmga/sdl/x11 modes.. </TD><TR><TD></TD><TD VALIGN=top>A:</TD><TD> Use the -fsmode switch. See example.conf or manpage. </TD><TR><TD COLSPAN=3> </TD><TR> <TD></TD><TD VALIGN=top>Q:</TD><TD WIDTH=100%> But it works with avifile! </TD><TR><TD></TD><TD VALIGN=top>A:</TD><TD> So what? </TD><TR><TD COLSPAN=3> </TD><TR> <TD></TD><TD VALIGN=top>Q:</TD><TD WIDTH=100%> Then avifile is better! </TD><TR><TD></TD><TD VALIGN=top>A:</TD><TD> Then use avifile, it has nice GUI and nice C++ code :) </TD><TR><TD COLSPAN=3> </TD><TR> <TD></TD><TD VALIGN=top>Q:</TD><TD WIDTH=100%> I got this playing mpeg files: Can't find codec for video format 0x10000001! </TD><TR><TD></TD><TD VALIGN=top>A:</TD><TD> You have old version of codecs.conf at ~/.mplayer/. Upgrade it from etc/ OR you have the <CODE>vc=</CODE> option or similar, in your config file(s). </TD><TR><TD COLSPAN=3> </TD><TR> <TD></TD><TD VALIGN=top>Q:</TD><TD WIDTH=100%> After starting mplayer under KDE(1/2) I just get a black screen and nothing happens, after about one minute the video starts playing. </TD><TR><TD></TD><TD VALIGN=top>A:</TD><TD> The KDE arts sound daemon is blocking the sound device, either wait the time until video starts or you disable the arts-daemon in kontrollcenter. If you want to use arts sound, specify audio output via SDL (ao=sdl), and make sure your SDL can handle arts sound. Yet another option is to start mplayer with artsdsp. </TD><TR><TD COLSPAN=3> </TD><TR> <TD></TD><TD VALIGN=top>Q:</TD><TD WIDTH=100%> I have an AVI that plays with grey screen with -vc odivx, and green with -vc divx4 . </TD><TR><TD></TD><TD VALIGN=top>A:</TD><TD> It's not a DivX file, but an M$ MPEG4v3 . Update your codecs.conf. </TD><TR><TD COLSPAN=3> </TD><TR> <TD></TD><TD VALIGN=top>Q:</TD><TD WIDTH=100%> There this movie is, and when I play it I get video-audio desync and/or MPlayer crashes with the following: <CODE>DEMUXER: Too many (945 in 8390980 bytes) video packets in the buffer!</CODE> </TD><TR><TD></TD><TD VALIGN=top>A:</TD><TD> This can have multiple reasons. <LI>your CPU and/or video card and/or bus is too SLOW. MPlayer displays a message if this is the case. (and the dropped frames counter is going up fast)</LI> <LI>if it is an AVI, maybe it has shit interleaving. Try the -ni option.</LI> <LI>your sound driver is shit, or you use ALSA 0.5 with -ao oss. See the <A HREF="sound.html">soundcards section</A>.</LI> <LI>the AVI has shit header, try with the -nobps option, and/or -mc 0 .</LI> </TD><TR><TD COLSPAN=3> </TD><TR> <TD></TD><TD VALIGN=top>Q:</TD><TD WIDTH=100%> I have an MJPEG file which works with other players but displays only black image in MPlayer. </TD><TR><TD></TD><TD VALIGN=top>A:</TD><TD> Disable the Windows DLL in <CODE>codecs.conf</CODE>, or use <CODE>-vc ffmjpeg</CODE> option (you have to compile MPlayer with libavcodec). </TD><TR><TD COLSPAN=3> </TD><TR> <TD></TD><TD VALIGN=top>Q:</TD><TD WIDTH=100%> When I try to grab from my tuner, it works, but colors are strange. It's ok with other applications. </TD><TR><TD></TD><TD VALIGN=top>A:</TD><TD> Your card probably misreports its colorspace capacity. Try with YUY2 instead of default YV12 (see TV input documentation). </TD><TR><TD COLSPAN=3> </TD><TR> <TD></TD><TD VALIGN=top>Q:</TD><TD WIDTH=100%> When I try to start playing, I get this message, but playing is good : <CODE>Linux RTC init: ioctl (rtc_pie_on): Permission denied</CODE> </TD><TR><TD></TD><TD VALIGN=top>A:</TD><TD> See the <A HREF="documentation.html#1.3">Installation section</A>. The part about new sync code. </TD><TR><TD COLSPAN=3> </TD><TR> <TD></TD><TD VALIGN=top>Q:</TD><TD WIDTH=100%> I have A/V sync problems. Some of my AVIs play fine, but some play with double speed ! </TD><TR><TD></TD><TD VALIGN=top>A:</TD><TD> You have buggy soundcard/driver. Most likely it's fixed at 44100Hz, and you try to play a file which has 22050Hz audio. Try the <CODE>-ao sdl</CODE> driver. </TD><TR><TD COLSPAN=3> </TD><TR> <TD></TD><TD VALIGN=top>Q:</TD><TD WIDTH=100%> All the WMV (or other..) files I play gives green/gray window and there is only sound! It prints: <CODE>Detected video codec: [null] drv:0 (NULL codec (no decoding))</CODE> </TD><TR><TD></TD><TD VALIGN=top>A:</TD><TD> Update your <CODE>codecs.conf</CODE> </TD><TR><TD COLSPAN=3> </TD><TR> <TD></TD><TD VALIGN=top>Q:</TD><TD WIDTH=100%> I'm using the GUI. During startup, MPlayer prints : <PRE><CODE>Gtk-WARNING **: This process is currently running setuid or setgid. This is not a supported use of GTK+. You must create a helper program instead. For further details, see...</CODE></PRE> </TD><TR><TD></TD><TD VALIGN=top>A:</TD><TD> You can't use GTK in a suid-root binary, as pointed out in the GUI section. </TD><TR><TD COLSPAN=3> </TD><TR> <TD COLSPAN=3> <A NAME=5.4>5.4. Video/audio driver problems (vo/ao)</A> </TD><TR><TD COLSPAN=3> </TD><TR> <TD></TD><TD VALIGN=top>Q:</TD><TD WIDTH=100%> Ok, -vo help shows DGA driver, but it is babbling about permissions! Help me! </TD><TR><TD></TD><TD VALIGN=top>A:</TD><TD> It works only if running as root! It's a DGA limitation. You should become to root (su -), and try again. Another solution is making mplayer SUID root, but its NOT RECOMMENDED!     <CODE>chown root /usr/local/bin/mplayer</CODE>     <CODE>chmod 750 /usr/local/bin/mplayer</CODE>     <CODE>chmod +s /usr/local/bin/mplayer</CODE> !!!! BUT STAY TUNED !!!! This is a *BIG* security risk! *NEVER* do this on a server or on a computer can be accessed by more people than only you because they can gain root privilegies through suid root mplayer!!! !!!! SO YOU HAVE BEEN WARNED ... !!!! </TD><TR><TD COLSPAN=3> </TD><TR> <TD></TD><TD VALIGN=top>Q:</TD><TD WIDTH=100%> When using Xvideo, my Voodoo 3/Banshee says: <CODE>X Error of failed request: BadAccess (attempt to access private resource denied)   Major opcode of failed request: 147 (MIT-SHM)   Minor opcode of failed request: 1 (X_ShmAttach)   Serial number of failed request: 26   Current serial number in output stream:27</CODE> </TD><TR><TD></TD><TD VALIGN=top>A:</TD><TD> Your driver is old, update it. Either download (at least) DRI version 0.6 from <A HREF="http://dri.sourceforge.net">http://dri.sourceforge.net</A>, or use the DRI cvs. </TD><TR><TD COLSPAN=3> </TD><TR> <TD></TD><TD VALIGN=top>Q:</TD><TD WIDTH=100%> When using Xvideo, I can't play DivX avis with my Voodoo 3/Banshee! It says: ... <CODE>Xvideo image format: 0x32315659 (YV12) planar Xvideo image format: 0x30323449 (I420) planar </CODE> ... </TD><TR><TD></TD><TD VALIGN=top>A1:</TD><TD> See the previous answer. </TD><TR><TD></TD><TD VALIGN=top>A2:</TD><TD> Since 0.18pre4 we support libavcodec from the ffmpeg package. It contains a C language DivX and OpenDivX decoder. The DivX decoder uses YV12 format for output, thus it should work for you. Compile in libavcodec support. </TD><TR><TD COLSPAN=3> </TD><TR> <TD></TD><TD VALIGN=top>Q:</TD><TD WIDTH=100%> OpenGL (-vo gl) output doesn't work (hangup/black window/X11 errors/...). </TD><TR><TD></TD><TD VALIGN=top>A:</TD><TD> Your opengl driver doesn't support dynamic texture changes (glTexSubImage) It's known not to work with nVidia's binary shit. It's known to work with Utah-GLX/DRI and Matrox G400 card. Also with DRI and Radeon card. It won't work with DRI others than these. it will not work with 3DFX cards because the 256x256 texture size limit. </TD><TR><TD COLSPAN=3> </TD><TR> <TD></TD><TD VALIGN=top>Q:</TD><TD WIDTH=100%> I have an nVidia TNT/TNT2 card, and I have a band with strange colours, right under the movie! Whose fault is this? </TD><TR><TD></TD><TD VALIGN=top>A:</TD><TD> It's the nVidia X driver's. These bugs are ONLY with the TNT/TNT2 cards, and we can't do anything about it, it's not our bug. UPDATE : it's fixed in newest drivers, at last.. </TD><TR><TD COLSPAN=3> </TD><TR> <TD></TD><TD VALIGN=top>Q:</TD><TD WIDTH=100%> I have an nVidia XYZ card, and when I click on the GUI's diplay window to toggle displaying the GUI panel, a black square appears where I clicked. I have the newest driver. </TD><TR><TD></TD><TD VALIGN=top>A:</TD><TD> Yes, nvidia corrected a previous bug (above), and implemented a new one. Let's congratule them. </TD><TR><TD COLSPAN=3> </TD><TR> <TD></TD><TD VALIGN=top>Q:</TD><TD WIDTH=100%> When I use the GUI with SDL video output, a second video window is created. </TD><TR><TD></TD><TD VALIGN=top>A:</TD><TD> Known, don't use SDL for GUI yet. </TD><TR><TD COLSPAN=3> </TD><TR> <TD COLSPAN=3> <A NAME=5.5>5.5. Feature requests</A> </TD><TR><TD COLSPAN=3> </TD><TR> <TD></TD><TD VALIGN=top>Q:</TD><TD WIDTH=100%> Is there a hint on how to watch RealMedia movies in MPlayer? </TD><TR><TD></TD><TD VALIGN=top>A:</TD><TD> There's no way to do it. Therefore this format deserves to die in flames. Theoretically you can reverse engineer Real codecs built for Linux (they are available as .so files), but in practice that's really difficult, even if you know how the compiler used by Real is making assembler code. </TD><TR><TD COLSPAN=3> </TD><TR> <TD></TD><TD VALIGN=top>Q:</TD><TD WIDTH=100%> When will be <your favourite video feature> (like subtitle placement) implemented? </TD><TR><TD></TD><TD VALIGN=top>A:</TD><TD> Wait for libvo2. </TD><TR><TD COLSPAN=3> </TD><TR> <TD></TD><TD VALIGN=top>Q:</TD><TD WIDTH=100%> I want to play MP3 files with MPlayer ! </TD><TR><TD></TD><TD VALIGN=top>A:</TD><TD> This feature is not planned. There are much better players (mpg123, 3pm, xmms) for this task, use them. BTW, MPlayer stands for Movie Player. </TD><TR><TD COLSPAN=3> </TD><TR> <TD></TD><TD VALIGN=top>Q:</TD><TD WIDTH=100%> I'd like to seek +/- 1 frames, instead of 10 seconds. </TD><TR><TD></TD><TD VALIGN=top>A:</TD><TD> This won't be done. It was, but then it fucked up A/V sync. Feel free to implement it, and send a patch. Don't ask for it. </TD><TR><TD COLSPAN=3> </TD><TR> <TD></TD><TD VALIGN=top>Q:</TD><TD WIDTH=100%> Where is the Windows version ? </TD><TR><TD></TD><TD VALIGN=top>A:</TD><TD> It's not released, and won't be. Look around the windows scene (opensource ASF parsers, opensource ASF encoders, etc) and you'll know why. We don't want to go to jail. </TD><TR><TD COLSPAN=3> </TD><TR> <TD></TD><TD VALIGN=top>Q:</TD><TD WIDTH=100%> What card you may suggest me to buy?</td> </TD><TR><TD></TD><TD VALIGN=top>A0:</TD><TD> It's for your opinion only but our issues are: </TD><TR><TD></TD><TD VALIGN=top>A1:</TD><TD> Speed: This parameter can be computed very easy: a) which movies do you plan to watch: - MPEG1: 320x200@32=256000 so you need only 256*25fps=6.4Mb/sec bandwidth (This format can be played in real-time on any PC since P-100 + S3Virge) - MPEG4: 640x480@32=1228800 you need videobandwidth 1.2*25fps=30Mb/sec To watch such movie in real-time you need enough power PC: (Celeron-450+DIMM based video card) - MPEG2 (aka DVD or SDTV): 1024x768@32=3145728 you need videobandwidth 3*30fps=90Mb/sec In extremal cases (if your video card supports IDCT decoding) this can be played on the same PC as for MPEG4 - HDTV (HighData TeleVision): 2000x2000@32=16000000 i.e. videobandwidth = 16*30fps=480Mb/sec (This means also that you need at least 32Mb of video memory to watch this stream: 16Mb for RGB area and 16Mb for YUV area) b) Bandwidth of PCI slot is: 33Mhz*32bit=132Mb/sec And PCI2.1 has 66MHz*32bit=265Mb/sec that is far enough for any movie playback (except HDTV streams which really require AGP bus). c) What memory type should be installed on video card: SIMM - avoid that DIMM - good if your video card has 128-bit memory access. DDR - is far enough for all types. Note: By DGA comparision - there is no any visible difference between video cards which have installed the same type of video memory. Resume: If you have enough power CPU (Celeron-450 or K6-2-500) it would be enough to buy any video card which has at least 8Mb of DIMM or DDR memory. </TD><TR><TD></TD><TD VALIGN=top>A2:</TD><TD> Quality: This question was investigated in depth at: <a href="http://www.anandtech.com">http://www.anadtech.com</a> AnandTech - Video Card Roundup - DVD Quality, Features & Performance (October 2000) </TD><TR><TD></TD><TD VALIGN=top>A3:</TD><TD> WORKING features under Linux: If you are win32 user then probably you have support (from driver and DirectX8 side) for any feature which was introduced in your chip. But for linux users: Currently I know only several vendors which have more or less advanced support under Linux:   <table BORDER COLS=5 WIDTH="100%" NOSAVE > <tr> <td> </td> <td> <center>Matrox</center> </td> <td> <center>ATI</center> </td> <td> <center>NVidia</center> </td> <td> <center>S4 Savage</center> </td> </tr> <tr> <td>Driver's provider</td> <td>enthusiasts</td> <td>enthusiasts</td> <td>OEM + enthusiasts</td> <td>enthusiasts</td> </tr> <tr> <td>Driver's quality</td> <td>Best(X11,kernel)</td> <td>Best(X11,GATOS,kernel)</td> <td>Buggy(X11 only)</td> <td>Best(X11 only)</td> </tr> <tr> <td>VIDEO OVERLAY</td> <td></td> <td></td> <td></td> <td></td> </tr> <tr> <td>BES and YV2RGB</td> <td>YES</td> <td>YES</td> <td>YES</td> <td>YES</td> </tr> <tr> <td>scaling filters</td> <td>N/A</td> <td>YES</td> <td>N/A</td> <td>N/A</td> </tr> <tr> <td>adaptive deinterlace</td> <td>NO</td> <td>YES</td> <td>N/A</td> <td>N/A</td> </tr> <tr> <td>Video equalizer (hue, contrast, saturation, color correction)</td> <td>N/A</td> <td>PARTLY (under devel)</td> <td>N/A</td> <td>N/A</td> </tr> <tr> <td>Alpha blending, color and video keys</td> <td>PARTLY</td> <td>PARTLY (under devel)</td> <td>N/A</td> <td>N/A</td> </tr> <tr> <td>Video capture</td> <td>N/A</td> <td>YES(GATOS)</td> <td>N/A</td> <td>N/A</td> </tr> <tr> <td>TV-out</td> <td>YES</td> <td>YES</td> <td>N/A</td> <td>N/A</td> </tr> </table> Well - it's very rude observing of video card. Indeed we should pay our attention for models of video card: For example if MatroxG400(G450) drivers support TV-out then G550 has no such support. Other sample: Adaptive deinterlacing exists only since Rage128 chip and isn't present on Mach64+ ones. Same as 3D features are far different from Mach64 to Radeon2 8500 with trueform possibilities. ANYWAY - MPLAYER'S TEAM DOESN'T ACCEPT ANY CLAIMS IF YOU AFTER READING OF THIS MATERIAL WILL BUY CARD WHICH IS UNSUCCESSFUL FOR YOU!!! THIS MATERIAL IS ONLY OUR VISION. Q: If PCI slot is far enough for most types of movies then why S3 Virge is too slow for them? A: Due to its SIMM memory. </TD><TR><TD COLSPAN=3> </TD><TR> <TD COLSPAN=3> <A NAME=5.6>5.6. Encoding</A> </TD><TR><TD COLSPAN=3> </TD><TR> <TD></TD><TD VALIGN=top>Q:</TD><TD WIDTH=100%> How can I encode ? </TD><TR><TD></TD><TD VALIGN=top>A:</TD><TD> Check <A HREF="encoding.html">this documentation</A>. </TD><TR><TD COLSPAN=3> </TD><TR> </TABLE> </BODY> </HTML> --- NEW FILE --- <HTML> <BODY BGCOLOR=WHITE> <A NAME=2.1>2.1. Supported formats</A> MPlayer can read/play from the following devices/formats: <UL> <LI> <A HREF="#2.1.1.1">VCD</A> (Video CD) directly from CD-ROM or from CDRwin's .bin image file <LI> <A HREF="#2.1.1.1">DVD</A>, directly from your DVD disk, using libdvdread for decryption <LI> <A HREF="#2.1.1.1">MPEG 1/2</A> System Stream (PS/PES/VOB) and Elementary Stream (ES) file formats <LI> <A HREF="#2.1.1.2">RIFF AVI</A> file format <LI> <A HREF="#2.1.1.3">ASF/WMV</A> 1.0 file format <LI> <A HREF="#2.1.1.4">QT/MOV</A> file format with (un)compressed headers <LI> <A HREF="#2.1.1.5">VIVO</A> format (.viv files) <LI> supports <A HREF="documentation.html#3.3">reading from stdin</A>, or network via HTTP </UL> Note: about realmedia (.ra/.rm) support read the FAQ! It's important to clarify a popular mistake. When people see a file with .AVI extension, they instantly declare that isn't an MPEG file. That's not true. At least not entirely. If you tell them that such a file can contain MPEG1 video, they laugh at you. Feel free to kick their dumbass faces, then tell them to RTFM. You see, a codec isn't equal to a file format. Video codecs are: MPEG1, MPEG2, DivX, Indeo5, 3ivx. Video formats are: MPG, AVI, ASF. In theory, you can happily put an OpenDivX video and MP3 audio into a .MPG format file. Though most players won't play it, since they expect MPEG1 video and MP2 audio (.MPG doesn't have the necessary fields to describe its video and audio streams, like .AVI does). Or put MPEG1 video to an .AVI. For example <A HREF="http://ffmpeg.sourceforge.net">ffmpeg</A> can create these files. Audio codecs and formats are basically the same terms. <A NAME=2.1.1>2.1.1. Video formats</A> <A NAME=2.1.1.1>2.1.1.1. MPEG files</A> <LI>MPG : this is the most basic form of MPEG file formats. Contains MPEG1 video, and MP2 (MPEG-1 layer 2) audio, or rarely MP1.</LI> <LI>DAT : this is the very same format as MPG, just different extension. Used on Video CDs. Due to the nature VCDs are created and Linux is designed, the DAT files can't be played nor copied from VCDs. You have to use the <CODE>-vcd</CODE> option to play the VideoCD.</LI> <LI>VOB : this is the MPEG file format on DVDs. The same as MPG, plus capability to contain subtitles, or non-MPEG (AC3) audio. Contains encoded MPEG2 video, and usually AC3 audio, but MP2 is allowed too. Read the <A HREF="cd-dvd.html#4.2">DVD section</A> !</LI> In MPEG files, series of frames are grouped together, and are independent from the other groups. What this means is you can cut/join an MPEG file with standard file-tools (like dd, cut), and it remains completely functional. One important feature for MPGs is that they have a field to describe the aspect ratio of the video stream within. For example SVCDs have 480x480 resolution video, and in the header that field is set to 4:3, so it's played at 640x480. AVI files don't have this field, so one has to rescale it during encoding. <A NAME=2.1.1.2>2.1.1.2. AVI files</A> Designed by Micro$oft, the AVI (Audio Video Interleaved) is a widespread multipurpose format, currently used mostly for DivX and DivX4 videos. Has many known drawbacks, and inabilities (for example in streaming). Has support for one video stream, and 99 audio streams. Can be as big as 2Gb. There exists an extension for it to be bigger, called OpenDMS. M$ currently strongly discourages its use and propagates ASF/WMV. Not if anybody cares. NOTE : DV cameras can create two types of AVI format, one is the usual and playable, the other is neither. There are two kinds of AVI files: <UL> <LI>Interleaved : audio and video content is interleaved. This is the standard usage. Recommended and mostly used. Some tools create interleaved AVIs with bad sync. MPlayer detects these as interleaved, and this climaxes in loss of A/V sync, probably at seeking. These files should be played as non-interleaved (with the <CODE>-ni</CODE> option).</LI> <LI>Non-interleaved : bad. First come the whole video stream, then the whole audio stream, thus needs a lot of seeking. It's very bad when playing from network or CDROM.</LI> </UL> MPlayer supports 2 kind of timing for AVI files: <UL> <LI>bps-based : it is based on bitrate/samplerate of video/audio stream. This method is used by most players, including avifile and windows media player. Files with broken headers, and files created with VBR audio but not VBR-compliant encoder will result in A/V desync with this method (mostly at seeking).</LI> <LI>interleaving-based : it doesn't use bitrate value of the header, instead it uses the relative position of interleaved audio and video chunks. Makes some badly encoded file with VBR audio playable.</LI> </UL> Any audio and video codec is allowed, but note that VBR audio isn't well supported by most of the players. The file format makes it possible to use VBR audio, but most players expect CBR audio, thus they fail with VBR. VBR is unusual, and Microsoft's AVI specs only describe CBR audio. I also note, that most AVI encoders/multiplexers create bad files if using VBR audio. Only 2 exception (known by me): NaNDub and <A HREF="encoding.html">MEncoder</A>. <A NAME=2.1.1.3>2.1.1.3. ASF/WMV files</A> ASF (active streaming format) comes from Microsoft. They developed two variants of ASF, v1.0 and v2.0. v1.0 is used by their media tools (windows media player and windows media encoder) and is very secret. v2.0 is published and patented :). Of course they differ, there is no compatibility at all (it's just another legal game). MPlayer supports only v1.0, as nobody has ever seen v2.0 files :) . Note, that .ASF files nowdays come with the extension .WMA or .WMV. <A NAME=2.1.1.4>2.1.1.4. QuickTime/MOV files</A> These are from Macintosh. Usually have extensions of .QT or .MOV . Note that since the MPEG4 Group chose QuickTime as the recommended file format for MPEG4, their .MOV files come with .MPG or .MP4 extension (interesting that in these files the video stream is a real .MPG file. With the <CODE>-dumpvideo</CODE> option you can even extract it.). Codecs: any codecs allowed, both CBR and VBR. Note: most new mov files use Sorenson video and QDesign Music audio. These formats are completely secret, and only Apple's quicktime player is able to play these files (on win/mac only). <A NAME=2.1.1.5>2.1.1.5. VIV files</A> MPlayer happily demuxes VIVO file formats. The format's big disadvantage is that it has no index block, nor fixed packetsize or sync bytes, and most files lack even keyframes, so forget seeking! VIVO/1.0 files' video codec is standard h.263 . The VIVO/2.0 files' video codec is a modified, nonstandard h.263 . Audio is the same, it may be g.723 (standard), or Vivo Siren . See the <A HREF=codecs.html#2.2.1.4>VIVO video codec</A> and <A HREF=codecs.html#2.2.2.4>VIVO audio codec</A> sections for installation instructions. <A NAME=2.1.2>2.1.2. Audio formats</A> Currently MPlayer is still a Movie and not a Media player, thus the pure audio formats (for example MP3, WAV, audio ASF) are unplayable. Use <A HREF="http://www.xmms.org">xmms</A>, <A HREF="http://www.mpg123.de">mpg123</A> or whatever. </BODY> </HTML> --- NEW FILE --- <HTML> <BODY BGCOLOR=WHITE> Question: What is GCC 2.96 ? I can't find it at GNU site. Answer: Read the <A HREF="http://gcc.gnu.org/gcc-2.96.html">official answer from GNU GCC team.</A> Question: What is the problem with GCC 2.96 ? And with 3.x ? Answer: And for the people, who periodically asks what are the exact problems with gcc 2.96, my answer: we don't know exactly. There were various problems and new problems / bugs come up periodically. It is not a single bug/problem. We just see various bugreports, mostly gcc internal bugs, compiler syntax errors in source or bad code compiled. They all are solved using different version of gcc. I understand that gcc 2.96 has different default optimization flags and they conflicts with our inline asm code, but we can't fix them, and we really don't want to fix them as they work with other compilers or gcc versions, and the fix may cause speed loss. I think that the gcc 2.96 should be fixed to be option-compatible with other releases, but redhat guys refused to do it. If someone interested - ask Eugene K., avifile author, he has a long mailing with them, because they had the same problems with avifile. Finally he changed avifile source to workaround gcc 2.96 bugs... We simply has no interest and time to do it. Ah, and about the pipe-in-comment bug: it wasn't really our bug. I've talked one of gcc maintainers, and he told me that gcc 2.96 and 3.x supports intel asm syntax, and it caused the pipe bug. But it is a bug, because gcc silently, without any warning, ignored the whole asm block! Other gcc 3.x problems comes from broken libstdc++ or glibc header (std_*.h) installation. They are not our fault. MPlayer compiles and works well with gcc 3.x versions. Only 2.96 is broken, but it depends on many environment elements, including gcc 2.96 release number, enabled mplayer features, etc. If it works for you using gcc 2.96, it doesn't mean it will work for everyone. Answer 2: Also read <A HREF="users_against_developers.html">this</A> text !!! Question: No! You are wrong! Everything works with gcc 2.96 but MPlayer Answer: No. You are wrong! Several projects (mainly which source contains high optimized inline asm code) had problems with gcc 2.96. For example: avifile, MESA / DRI, Wine, ffmpeg, lame. But other projects already workarounded gcc bugs (changed code which triggered compiler bugs) so they work for now. Question: No! You are wrong! Everything works with gcc 2.96 including MPlayer Answer: Good. Be happy. But you must know, it depends on many environment elements, including gcc 2.96 release number, enabled mplayer features, etc. If it works for you using gcc 2.96, it doesn't mean it will work for everyone! It only means that you are lucky, until you find a problem. But don't forget the No.1 rule of gcc 2.96 users: NEVER REPORT BUGS OR PROBLEMS IF YOU ARE USING GCC 2.96 Question: Ok. Understood. But I want to give it a try... how to compile with gcc 2.96? Answer: Really? Are you sure? Ok. You know... here is it: ./configure --disable-gcc-checking Question: No! I don't agree with you, because ... Answer: It doesn't matter. Keep your commets for yourself. We're not interested in gcc 2.96 stories. </BODY> </HTML> --- NEW FILE --- .\" MEncoder (C) 2000-2001 Arpad Gereoffy <arpi(a)esp-team.scene.hu> .\" This manpage was/is done by Gabucino .\" .TH MEncoder .SH NAME mencoder \- Movie Encoder for Linux .SH SYNOPSIS .B mencoder .RB [ \-vcd\ <track\ number> ] .RB [ \-dvd\ <titleid> ] .RB [ \-chapter\ <chapterid> ] .RB [ \-dvdangle\ <angleid> ] .RB [ \-dvdkey\ <key> ] .RB [ \-nobps ] .RB [ \-aid\ <id> ] .RB [ \-vid\ <id> ] .RB [ \-pp\ <quality> ] .RB [ \-vc\ <video\ codec\ name> ] .RB [ \-ac\ <audio\ codec\ name> ] .RB [ \-vfm\ <video\ codec\ family> ] .RB [ \-afm\ <audio\ codec\ family> ] .RB [ \-include\ <configfile> ] .RB [ \-mc\ seconds/5f ] .RB [ \-v ] .RB [ \-mp3file\ <filename> ] .RB [ \-ac3file\ <filename> ] .RB [ \-ovc\ <video\ codec\ name> ] .RB [ \-oac\ <audio\ codec\ name> ] .RB [ \-divx4opts\ <codec\ options> ] .RB [ \-lameopts\ <codec\ options> ] .RB [ \-pass\ <1/2> ] .RB [ \-passlogfile\ <filename> ] .RB [ \-ofps\ <fps> ] .RB [ \-o\ <filename> ] .RB [ \-frames\ <number> ] .RB [ \-x\ <rescale\ width> ] .RB [ \-y\ <rescale\ height> ] .RB [ \-sws\ <0-2> ] .I - or file or device .PP .SH DESCRIPTION .I mencoder MEncoder (MPlayer's Movie Encoder) is a simple movie encoder, designed to encode MPlayer-playable movies (AVI/DVD/VCD/VOB/MPG/MOV/VIV/NET) to other MPlayer-playable formats (see below). Currently it's in beta stage, and encodes only to DivX4 (1 or 2 passes) video, PCM/MP3/VBRMP3 audio. Also has stream copying abilities. In the future, there will be cropping, resizing filters, and other interesting stuff. .LP .SH "GENERAL OPTIONS" .TP .I NOTE Every "flag" option has "noflag" pair, e.g. -flag opposite is -noflag .TP .I NOTE CHECK THE HTML DOCUMENTATION TOO ! .TP .B \-vcd <track number> Encode the specified VCD track. .TP .B \-dvd <title number> Encode the specified DVD title. .TP .B \-chapter <chapter id> Use with -dvd option (see above). Start encoding at the specified chapter. .TP .B \-dvdangle <angle id> Use with -dvd option (see above), and if the DVD disc has multiple angles. It will encode the angle specified here. .TP .B \-dvdkey <key> Used to decrypt CSS-encrypted streams on hard disk (with given CSS decrypt key). .TP .B \-nobps Used only for AVIs. Doesn't use the bps value in the AVI header, instead calculates it. .TP .B \-aid <audio stream id> If the source media contains multiple audio streams (for example DVDs), encode the specified one. .TP .B \-vid <video stream id> If the source media contains multiple video streams, encode the specified one. .TP .B \-pp <value> Apply a postprocess filter to enhance image quality. (values TODO) .TP .B \-vc <codec name> Use specified codec (according to codecs.conf) for decoding input video stream. .TP .B \-ac <codec name> Use specified codec (according to codecs.conf) for decoding input audio stream. .TP .B \-vfm <video codec family> Force decoding by using a specific codec FAMILY, and FALLBACK to default if failed. For examples see MPlayer manpage. .TP .B \-afm <audio codec family> Force decoding by using a specific codec FAMILY, and FALLBACK to default if failed. For examples see MPlayer manpage. .TP .B \-include specify config file to be parsed after the default .TP .B \-mc\ seconds/5frame maximum sync correction per 5 frames (in seconds). Use -mc 0 to disable input A/V sync. .TP .B \-v Increase verbosity. .TP .B \-ovc <codecname> Encode with the given codec (codec names are from codecs.conf). Examples: -ovc help get help -ovc copy no encoding, just streamcopy -ovc divx4 encode to DivX4 .TP .B \-oac <codecname> Encode with the given codec (codec names are from codecs.conf). Examples: -oac help get help -oac copy no encoding, just streamcopy -oac pcm encode to uncompressed PCM -oac mp3lame encode to MP3 (using Lame) .TP .B \-divx4opts If encoding to DivX4, you can specify its parameters here, like: -divx4opts br=1800:deinterlace:key=250 Available options: help get help br=XXX specify bitrate in kbit <4-16000> or bit <16001-24000000> key=XXX maximum keyframe interval (in frames) deinterlace enable deinterlacing (don't use, DivX4 is buggy!) q=XXXX quality (1-fastest, 5-best) min_quant=XXX minimum quantizer (0-32) max_quant=XXX maximum quantizer (0-32) rc_period=XXX rate control period rc_reaction_period=XXX rate control reaction period rc_reaction_ratio=XXX rate control reaction ratio .TP .B \-lameopts If encoding to MP3 with libmp3lame, you can specify its parameters here, like: -lameopts br=192 Available options: help get help br=XXX specify bitrate in kbit <0-1024> (only for CBR) q=XXX Quality (0-highest, 9-fastest) (for VBR) vbr=XXX variable bitrate method 0=cbr 1=mt 2=rh(default) 3=abr 4=mtrh cbr constant bitrate mode=XXX 0=stereo 1=joint-stereo 2=dualchannel 3=mono (default: auto) padding=XXX 0=no 1=all 2=adjust ratio=XXX compression ratio <1-100> .TP .B \-pass <1/2> With this you can encode 2pass DivX4 files. First encode with -pass 1, then with the same parameters, encode with -pass 2. .TP .B \-passlogfile <filename> When encoding in 2pass mode, MEncoder dumps first pass' informations to the given file instead of the default divx2pass.log . .TP .B \-ofps <fps> The output file will have different frame/sec than the source. .TP .B \-o <filename> Outputs to the given filename, instead of the default 'test.avi' . .TP .B \-frames <number> Encode only given number of frames. .TP .B \-x <rescale width> Rescale output movie to given pixels wide. .TP .B \-y <rescale height> Rescale output movie to given pixels tall. .TP .B \-sws (0-2> Type of scaling method 0 fast bilinear 1 bilinear 2 bicubic (best quality) .SH FILES AND DIRECTORIES .IP .SH "EXAMPLES" .B Encoding DVD title #2 mencoder -dvd 2 -o title2.avi .TP .B Encoding from HTTP mencoder http://mplayer.hq/example.avi -o example.avi .TP .B Encoding from a pipe rar p test-SVCD.rar | mencoder -divx4opts br=800 -ofps 24 -pass 1 -- - .TP .B Encoding multiple *.vob files cat *.vob | mencoder <options> - .IP .SH BUGS Probably. Check the documentation. Bugreports should be addressed to the MPlayer-users mailing list (mplayer-users(a)mplayerhq.hu) ! If you want to submit a bugreport (which we love to receive!), please double-check the bugreports.html, and tell us all that we need to know to identify your problem. .LP .SH AUTHORS Check documentation ! MPlayer is (C) 2000-2001 .I Arpad Gereoffy <arpi(a)thot.banki.hu> This manpage is written and maintained by .I Gabucino . .LP .SH STANDARD DISCLAIMER Use only at your own risk! There may be errors and inaccuracies that could be damaging to your system or your eye. Proceed with caution, and although this is highly unlikely, the author doesn't take any responsibility for that! .\" end of file --- NEW FILE --- .\" MPlayer (C) 2000-2001 Arpad Gereoffy <arpi(a)esp-team.scene.hu> .\" This manpage was/is done by Gabucino .\" .TH MPlayer .SH NAME mplayer \- Movie Player for Linux .SH SYNOPSIS .B mplayer .RB [ \-gui ] .RB [ \-v ] .RB [ \-quiet ] .RB [ \-vo\ <driver>[:<device>] ] .RB [ \-ao\ <driver>[:<device>] ] .RB [ \-vcd\ track\ number ] .RB [ \-sb\ byte\ position ] .RB [ \-nosound ] .RB [ \-abs\ bytes ] .RB [ \-delay\ secs ] .RB [ \-nobps ] .RB [ \-aid\ id ] .RB [ \-vid\ id ] .RB [ \-fps\ rate ] .RB [ \-mc\ seconds/5f ] .RB [ \-fs ] .RB [ \-vm ] .RB [ \-zoom ] .RB [ \-x\ x ] .RB [ \-y\ y ] .RB [ \-xy\ factor ] .RB [ \-pp\ quality ] .RB [ \-include\ configfile ] .RB [ \-lircconf\ configfile ] .RB [ \-ffactor\ number ] .RB [ \-sub\ file ] .RB [ \-subfps\ rate ] .RB [ \-subdelay\ sec ] .RB [ \-z\ <0-8> ] .RB [ \-idx ] .RB [ \-forceidx ] .RB [ \-nodshow ] .RB [ \-noxv ] .RB [ \-forcexv ] .RB [ \-ss\ time ] .RB [ \-dumpaudio ] .RB [ \-dumpvideo ] .RB [ \-dumpstream ] .RB [ \-noframedrop ] .RB [ \-framedrop ] .RB [ \-nodouble ] .RB [ \-double ] .RB [ \-stereo\ mode ] .RB [ \-channels\ n ] .RB [ \-srate\ Hz ] .RB [ \-osdlevel\ level ] .RB [ \-config\ file ] .RB [ \-display\ name ] .RB [ \-unicode ] .RB [ \-utf8 ] .RB [ \-fsmode\ mode ] .RB [ \-vc\ video\ codec\ name ] .RB [ \-ac\ audio\ codec\ name ] .RB [ \-vfm\ video\ codec\ family ] .RB [ \-afm\ audio\ codec\ family ] .RB [ \-frames\ number ] .RB [ \-autoq\ quality ] .RB [ \-fb\ device ] .RB [ \-fbmode\ modename ] .RB [ \-fbmodeconfig\ filename ] .RB [ \-benchmark ] .RB [ \-dvd\ titleid ] .RB [ \-chapter\ chapterid ] .RB [ \-dvdangle\ angleid ] .RB [ \-dvdkey\ key ] .RB [ \-skin\ skin ] .RB [ \-aspect\ ratio ] .RB [ \-monitoraspect\ ratio ] .RB [ \-subcp\ codepage ] .RB [ \-dumpmpsub ] .RB [ \-screenw\ pixels ] .RB [ \-screenh\ pixels ] .RB [ \-cache\ kbytes ] .RB [ \-bpp\ depth ] .RB [ \-flip ] .RB [ \-playlist\ <filename> ] .RB [ \-slave ] .I - or file or device .PP .SH DESCRIPTION .I mplayer MPlayer is a movie player for LINUX (runs on many other Unices, and non-x86 CPUs, see section 6). It plays most MPEG, AVI and ASF/WMV files, supported by many native and Win32 DLL codecs. You can watch VideoCD, SVCD, DVD and even DivX movies too (and you don't need the avifile library at all!). The another big feature of mplayer is the wide range of supported output drivers. It works with X11, Xv, DGA, OpenGL, SVGAlib, fbdev, AAlib, but you can use SDL (and this way all drivers of SDL) and some lowlevel card-specific drivers (for Matrox, 3Dfx and Radeon) too! Most of them supports software or hardware scaling, so you can enjoy movies in fullscreen. And what about the nice big antialiased shaded subtitles (7 supported types!!!) with european/ISO 8859-1,2 (hungarian, english, czech, etc), cyrillic, korean fonts, and OSD? .LP .SH "GENERAL OPTIONS" .TP .I NOTE Every "flag" option has "noflag" pair, e.g. -fs opposite is -nofs .TP .B \-gui start MPlayer with the GUI mode. You have to compile it in, for details see the documentation. .TP .B \-dvd\ titleid tell MPlayer which movies (marked with titleid) to play. For example sometimes '1' are trailers, and '2' is the real movie. .TP .B \-sid\ id Turns on DVD subtitle displaying. Also, you MUST specify a number which corresponds to a DVD subtitle language (1-...). For the list of available subtitles, use with the -v switch and look at the output. (EXPERIMENTAL) .TP .B \-chapter\ chapterid specify which chapter to start playing at. Examples can be found below. .TP .B \-dvdangle\ angleid some DVD discs contain scenes that can be viewed from multiple angles. Here you can tell MPlayer which angles to use. Examples can be found below. .TP .B \-vo\ <driver>[:<device>] select video output driver and optinaly device. "device" is valid with SDL and GGI too, it means sub-driver then (for example: -vo sdl:aalib). you can get the list of available drivers executing .I mplayer -vo help .TP .B \-ao\ <driver>[:<device>] select audio output driver and optinaly device. "device" is valid with SDL too, it means sub-driver then (for example: -vo sdl:esd). If using OSS, you can specify which sound device to use like this : -ao oss:/dev/dsp1 (replaces the old -dsp option) you can get the list of available drivers executing .I mplayer -ao help .TP .B \-vcd\ track play video cd track from device instead of plain file .TP .B \-nosound don't play sound .TP .B \-fs fullscreen playing (centers movie, and makes black bands around it) .TP .B \-vm try to change to a different video mode. dga2, x11 (XF86VidMode) and sdl output drivers support it. .TP .B \-zoom use software scaling, where available (use with -nofs). svga, x11, vesa output drivers support it. .TP .B \-flip flip image (useful for example for old Indeo codecs). Supported only(?) by the 'sdl' and 'x11' outputs. .TP .B \-x\ x scale image to x width [if driver suppports!] .TP .B \-y\ y scale image to y height .TP .B \-xy\ factor scale image by <factor> .TP .B \-pp\ quality apply postprocess filter on decoded image. You need a STRONG CPU in order to use this! The supported formats and settings are: MPEG 1/2 0 (none), TODO OpenDivX 0 (none), TODO DivX4 0 (none), TODO DivX 0 (none), TODO -pp 0x20000 TODO .TP .B \-autoq\ quality dynamically changes the level of postprocess, depending on spare CPU time available. Uses the same value ranges as -pp . The number you specify will be the maximum level used. Usually you can use some big number. You don't have to (and don't) use together with -pp ! .TP .B \-ffactor\ number resample alphamap of the font. Can be: 0 plain white fonts 0.75 very narrow black outline [default] 1 narrow black outline 10 bold black outline .TP .B \-sub\ file use/display this subtitle file .TP .B \-subfps\ rate specify frame/sec rate of subtitle file (ONLY for frame-based SUB files, i.e. NOT MicroDVD format!) (default: the same as the movie) .TP .B \-subdelay\ sec delays subtitles by <sec> seconds. Can be negative. .TP .B \-osdlevel\ level specifies which mode the OSD should start in (0 : none, 1 : seek, 2: seek+timer) (default = 2) .TP .B \-lircconf\ configfile specifies a configfile for LIRC (see http://www.lirc.org) if you don't like the default ~/.lircrc .TP .B \-v enable verbose output (more -v means more verbose) .TP .B \-quiet display less output, status messages. .TP .B \-benchmark used in combination with -nosound and -vo null for benchmarking. .TP .B \-skin skin directory load skin from this directory (WITHOUT path name!). For example '-skin fittyfene' tries these : /usr/local/share/mplayer/Skin/fittyfene ~/.mplayer/Skin/fittyfene .TP .B \-aspect ratio set aspect ratio of movies. It's autodetected on MPEG files, and can't be autodetected on AVI files. Examples: -aspect 4:3 or -aspect 1.3333 -aspect 16:9 or -aspect 1.7777 (has -noaspect pair) .TP .B \-monitoraspect ratio set aspect ratio of your screen. Examples: -monitoraspect 4:3 or 1.3333 -monitoraspect 16:9 or 1.7777 .TP .B \-playlist <file> play files according to this filelist (1 file/row). .TP .B \-slave This option switches on slave mode. This is intended for use of MPlayer as a backend to other programs. Instead of intercepting keyboard events, MPlayer will read simplistic command lines from its stdin. See section .B SLAVE MODE PROTOCOL for the syntax. .IP .SH "ADVANCED OPTIONS" .TP .I NOTE These options can help you solve your particular problem.. Also, see the documentation ! .TP .B \-vc <name> force usage of a specific video codec, according to its name in codecs.conf, for example : -vc divx use VFW DivX codec -vc divxds use DirectShow DivX codec -vc ffdivx use libavcodec's DivX codec -vc ffmpeg12 use libavcodec's MPEG1/2 codec -vc divx4 use ProjectMayo's DivX codec See -vc help for FULL list ! .TP .B \-ac <name> force usage of a specific audio codec, according to its name in codecs.conf, for example : -ac mp3 use libmp3 MP3 codec -ac mp3acm use l3codeca.acm MP3 codec -ac ac3 use AC3 codec -ac hwac3 enable Hardware AC3 passthrough (see documentation) -ac vorbis use libvorbis -ac ffmp3 use ffmpeg's MP3 decoder (SLOW) See -ac help for FULL list ! .TP .B \-vfm <1-12> force usage of a specific codec FAMILY, and FALLBACK to default if failed. For example: -vfm 2 use VFW (Win32) codecs -vfm 3 use OpenDivX/DivX4 codec (YV12) (same as -vc odivx but fallback) -vfm 4 use DirectShow (Win32) codecs -vfm 5 use libavcodec codecs -vfm 7 use DivX4 codec (YUY2) (same as -vc divx4 but fallback) -vfm 10 use XAnim codecs See -vc help for FULL list ! NOTE : if libdivxdecore support was compiled in, then type 3 and 7 now contains just the same DivX4 codec, but different APIs to reach it. For difference between them and when to use which, check the DivX4 section in the documentation. .TP .B \-afm <1-12> force usage of a specific audio format. For example: -afm 1 use libmp3 (mp2/mp3, but not mp1) -afm 2 suppose raw PCM audio -afm 3 use libac3 -afm 4 use a matching Win32 codec -afm 5 use aLaw/uLaw driver -afm 10 use libvorbis -afm 11 use ffmpeg's MP3 decoder (even mp1) See -ac help for FULL list ! .TP .B \-sb\ position seek to byte position .TP .B \-ss\ time seek to given time position. For example : -ss 56 -ss 01:10:00 .TP .B \-bpp\ depth use different color depth than autodetect. Not all -vo drivers support it (fbdev, dga2, svga, vesa). .TP .B \-abs\ bytes sound card audio buffer size (in bytes, default: measuring) .TP .B \-delay\ secs audio delay in seconds (may be +/- float value) .TP .B \-nobps don't use avg. byte/sec value for A-V sync (AVI) .TP .B \-aid\ id select audio channel [MPG: 0-31 AVI: 1-99 ASF: 0-127 VOB: 128-...] .TP .B \-vid\ id select video channel [MPG: 0-15 AVI: -- ] .TP .B \-fps\ value force frame rate (if value is wrong in the header) .TP .B \-mc\ seconds/5frame maximum sync correction per 5 frames (in seconds) .TP .B \-ni force usage of non-interleaved AVI parser .TP .B \-include configfile specify config file to be parsed after the default .TP .B \-z\ <0-8> specifies compression level for PNG output 0 : no compression 8 : max compression .TP .B \-idx rebuilds INDEX of the AVI. Useful with broken downloads, or badly created AVIs. .TP .B \-forceidx force rebuilding of INDEX. Useful for testing, or AVIs with bad indexes. .TP .B \-nodshow disables usage of DirectShow video codecs .TP .B \-noxv disable XVideo hardware acceleration (with SDL only!) .TP .B \-forcexv force using XVideo (SDL!) .TP .B \-dumpaudio writes audio stream of the file to ./stream.dump (mostly usable with mpeg/ac3) .TP .B \-dumpstream dumps the file to ./stream.dump . Useful for example when ripping from DVD. .TP .B \-noframedrop no frame dropping : every frame is played, audio and video may be out of sync (default) .TP .B \-framedrop frame dropping : decode all frames, video may skip .TP .B \-nodouble disable doublebuffering (default). Currently this is only honoured by the Xv and the DGA driver. With the DGA driver this also disables OSD support but yields some speed gain. .TP .B \-double enable doublebuffering. Currently this is only honoured by the Xv and the DGA driver. .TP .B \-dvdkey key key to decrypt stream encrypted with CSS. For example : -dvdkey F169072699 (this is NOT for DVD playing! For DVD use the -dvd option!) .TP .B \-stereo mode select type of MP2/MP3 stereo output. Stereo 0 Left channel 1 Right channel 2 .TP .B \-channels n select number of audio output channels to be used Stereo 2 Surround 4 Full 5.1 6 Currently this option is only honoured for AC3 audio. .TP .B \-srate Hz specifies Hz to playback audio on. Has effect on playback speed! .TP .B \-config configfile specifies where to search for config file .TP .B \-display name specify the hostname and display number of the X server you want to display on. For example : -display xtest.localdomain:0 .TP .B \-unicode tells MPlayer to handle the subtitle file as UNICODE. Contrary: -nounicode .TP .B \-utf8 tells MPlayer to handle the subtitle file as UTF8. .TP .B \-fsmode\ mode This option workarounds some problems when using specific windowmanagers and fullscreen mode. If you experience fullscreen problems, try changing this value between 0 and 7. -fsmode 0 new method -fsmode 1 ICCCWM patch (for KDE2/icewm) -fsmode 2 old method -fsmode 3 ICCCWM patch plus Motif method .TP .B \-frames\ number MPlayer plays <number> frames, then quits. .TP .B \-fb\ device Specifies the framebuffer device to use. By default it uses /dev/fb0 . Only valid for the fbdev driver. .TP .B \-fbmode\ modename Change videomode to the one that is labelled as <modename> in /etc/fb.modes . Only valid for the fbdev driver. .TP .I NOTE VESA framebuffer doesn't support mode changing. .TP .B \-fbmodeconfig\ filename Use this config file instead of the default /etc/fb.modes . Only valid for the fbdev driver. .TP .B \-subcp\ codepage If your system supports iconv(3), you can use this option to specify codepage of the subtitle. Examples: -subcp latin2 -subcp cp1250 .TP .B \-dumpmpsub Convert the given subtitle (specified with the -sub switch) to MPlayer's subtitle format, MPsub. Dumps a dump.mpsub file to current directory. .TP .B \-screenw\ pixels If you use an output driver which can't know the resolution of the screen (mga/fbdev/x11 and/or TVout) this is where you can specify the horizontal resolution. .TP .B \-screenh\ pixels If you use an output driver which can't know the resolution of the screen (mga/fbdev/x11 and/or TVout) this is where you can specify the vertical resolution. .TP .B \-cache\ kbytes This option specifies how much memory to use when precaching a file/URL . Especially useful on slow media. Default is off. .IP .SH "ALPHA/BETA CODE" .TP .I NOTE These are included in this manpage just for completeness! These may or may NOT work! If you don't know what are these, you DON'T need these! In either case, double-check the documentation ! .TP .B \-br\ rate used with '-vo odivx' . Specifies the bitrate to encode OpenDivx at (in bits! e.g: 780000). .TP .I NOTE You CAN'T encode sound, only video right now! Don't ask for it, it's on the TODO list. .TP .B \-encode\ file used with '-vo odivx' . Specifies the output OpenDivX file. Won't overwrite. .TP .B \-dumpvideo dump video stream to ./stream.dump (only with MPEG-PS) (not very usable) .IP .SH KEYBOARD CONTROL .TP .I NOTE These keys may/may not work, depending on your video output driver. .TP <- or -> seek backward/forward 10 seconds up or down seek backward/forward 1 minute pgup/pgdown seek backward/forward 10 minutes p or SPACE pause movie (press any key) q or ESC stop playing and quit program + or - adjust audio delay by +/- 0.1 second / or * decrease/increase volume o toggle OSD: none / seek / seek+timer m toggle using master/pcm volume z or x adjust subtitle delay by +/- 0.1 second (the following keys are valid only when using DirectShow DivX codec, or the DivX4 codec with -vc divx4) 1 or 2 adjust contrast 3 or 4 adjust brightness 5 or 6 adjust hue 7 or 8 adjust saturation .IP .SH SLAVE MODE PROTOCOL If the -slave switch is given, playback is controlled by a line-based protocol with the following tokens: .TP stop pause playback play resume playback seek <NUM> continue at second NUM skip <NUM> skip NUM seconds (may be negative) quit exit mplayer .IP .SH FILES AND DIRECTORIES .TP .I CONFIG FILES Settings are stored system-wide in the /etc/mplayer.conf file, and per-user in $HOME/.mplayer/config. The directory $HOME/.mplayer and the 'config' are created if doesn't exist. .TP .I FONTS Fonts are searched in $HOME/.mplayer/font. There must be a font.desc file, and files with .RAW extension. .TP .I SUBTITLE FILES MPlayer currently supports 9 subtitle formats : MicroDVD, SubRip, unnamed, SAMI (smi), vplayer, RealMedia RT, ssa (Sub Station Alpha), AQT, and our own: MPsub. Sub files are searched in this priority : (for example /mnt/cdrom/movie.avi) /mnt/cdrom/movie.sub (utf/UTF/sub/SUB/srt/SRT/smi/SMI/rt/RT/txt/TXT/ssa/SSA) $HOME/.mplayer/sub/movie.sub (utf/UTF/sub/SUB/srt/SRT/smi/SMI/rt/RT/txt/TXT/ssa/SSA) $HOME/.mplayer/default.sub .IP .SH "EXAMPLES" .B Quickstart DVD playing mplayer -dvd 1 .TP .B Multiangle DVD playing mplayer -dvd 1 -dvdangle 2 .TP .B Playing from a different DVD device mplayer -dvd 1 /dev/dvd2 .TP .B Stream from HTTP mplayer http://mplayer.hq/example.avi .TP .B Convert subtitle to MPsub (to ./dump.mpsub) mplayer dummy.avi -sub source.sub -dumpmpsub .LP .SH BUGS Probably. Check the documentation. Bugreports should be addressed to the MPlayer-users mailing list (mplayer-users(a)mplayerhq.hu) ! If you want to submit a bugreport (which we love to receive!), please double-check the bugreports.html, and tell us all that we need to know to identify your problem. .LP .SH AUTHORS Check documentation ! MPlayer is (C) 2000-2001 .I Arpad Gereoffy <arpi(a)thot.banki.hu> This manpage is written and maintained by .I Gabucino . .LP .SH STANDARD DISCLAIMER Use only at your own risk! There may be errors and inaccuracies that could be damaging to your system or your eye. Proceed with caution, and although this is highly unlikely, the author doesn't take any responsibility for that! .\" end of file --- NEW FILE --- <html> <head> <meta http-equiv=Content-Type content="text/html; charset=iso-8859-1"> <title>MPlayer skin format</title> <style type="text/css"> em.note {color: green} em.warn {color: red} </style> </head> <body bgcolor=white text=black> <h1 align="center">MPlayer skin format</h1> <hr> <h2>Contents</h2> <ul type=disc> <li><a href="#intro">1 Introduction</a></li> <li><a href="#overview">2 Overview</a></li> <ul type=circle> <li><a href="#dirs">2.1 Directories</a></li> <li><a href="#images">2.2 Images</a></li> <li><a href="#parts">2.3 Parts of a skin</a></li> <li><a href="#files">2.4 Files</a></li> </ul> <li><a href="#skin">3 The <code>skin</code> file</a></li> <ul type=circle> <li><a href="#mainwin">3.1 Main window</a></li> <li><a href="#subwindow">3.2 Subwindow</a></li> <li><a href="#skinmenu">3.3 Skin menu</a></li> </ul> <li><a href="#fonts">4 Fonts</a></li> <ul type=circle> <li><a href="#symbols">4.1 Symbols</a></li> </ul> <li><a href="#guimsg">Appendix A: GUI messages</a></li> </ul> <hr> <div align=center> Last modified: Sep 10, 2001 </div> <hr> <h2><a name="intro">1 Introduction</a></h2> The purpose of this document is to describe the MPlayer skin format. The information contained here might be wrong, for a) it is not me who wrote the GUI, b) the GUI is not finished, c) I might be wrong. So do not be surprised if something does not work as described here. Thanks to Zoltán Ponekker for his help. András Mohari <mayday(a)freemail.hu> <h2><a name="overview">2 Overview</a></h2> It does not really have anything to do with the skin format, but you should know that MPlayer has no builtin skin, so at least one skin must be installed in order to be able to use the GUI. <h3><a name="dirs">2.1 Directories</a></h3> The directories searched for skins are (in order): <pre> /usr/local/share/mplayer/Skin/ ~/.mplayer/Skin/ </pre> Note that the first path may vary according to the way MPlayer was configured (see the <code>--datadir</code> argument of the <code>configure</code> script). Every skin is installed into its own directory under one of the directories listed above, for example: <pre> /usr/local/share/mplayer/Skin/default/ </pre> <h3><a name="images">2.2 Image formats</a></h3> Images must be truecolor (24 or 32 bpp) and can be in BMP, PNG and TGA format (note that TGA images must be uncompressed). The preferred format is PNG as it compresses very well. In the main window (see below) you can use images with `transparency': regions filled with the color #FF00FF (magenta) are fully transparent when viewed by MPlayer. This means that you can even have shaped windows if your X server has the XShape extension. <h3><a name="parts">2.3 Parts of a skin</a></h3> Skins are quite free-format (unlike the fixed-format skins of Winamp/XMMS, for example), so it is up to you to create something great. Currently there are three windows to be decorated: the <a href="#mainwin">main window</a>, the <a href="#subwindow">subwindow</a> and the <a href="#skinmenu">skin menu</a> (which can be activated by a right click). <ul> <li> The main window is where you can control MPlayer. The background of the window is an image. Various items can (and must) be placed in the window: buttons, potmeters (sliders, if you like it better) and labels. For every item, you must specify its position and size. A button has three states (pressed, released, disabled), so its image must be divided into three parts vertically. See the <a href="#main.button">button</a> item for details. A potmeter (mainly used for the seek bar and volume/balance control) can have any number of phases by dividing its image into different parts below each other. See <a href="#main.hpotmeter">hpotmeter</a> and <a href="#main.potmeter">potmeter</a> for details. Labels are a bit special: the characters needed to draw them are taken from an image file, and the characters in the image are described by a <a href="#fonts">font description file</a>. The latter is a plain text file which specifies the x,y position and size of each character in the image. (So the image file and its font description file form a font together.) See <a href="#main.dlabel">dlabel</a> and <a href="#main.slabel">slabel</a> for details. Note: all images can have full transparency as described in the section about <a href="#images">image formats</a>. </li> <li> The subwindow is where the movie appears. It can display a specified image if there is no movie loaded (it is quite boring to have an empty window :-)) Note: transparency is not allowed here. </li> <li> The skin menu is just a way to control MPlayer by means of menu entries. Two images are required for the menu: one of them is the base image that shows the menu in its normal state, the other one is used to display the selected entries. When you pop up the menu, the first image is shown. If you move the mouse over the menu entries, the currently selected entry is copied from the second image over the menu entry below the mouse pointer. (So the second image is never shown in whole.) A menu entry is defined by its position and size in the image (see the section about the <a href="#skinmenu">skin menu</a> for details). </li> </ul> There is an important thing not mentioned yet: for buttons, potmeters and menu entries to work, MPlayer must know what to do if they are clicked. This is done by <a href="#guimsg">messages</a> (events). For these items you must define the messages to be genereated when they are clicked. <h3><a name="files">2.4 Files</a></h3> You need the following files to build a skin. <ul> <li> The configuration file named <a href="#skin">skin</a> tells MPlayer how to put different parts of the skin together and what to do if you click somewhere in the window. </li> <li>The background image for the main window.</li> <li>Images for the items in the main window (including one or more font description files needed to draw labels).</li> <li>The image to be displayed in the subwindow (optional).</li> <li>Two images for the skin menu (they are needed only if you want to create a menu). </ul> With the exception of the skin configuration file, you can name the other files whatever you want (but note that font description files must have .fnt extension). <h2><a name="skin">3 The <code>skin</code> file</a></h2> As mentioned above, this is the skin configuration file. It is line oriented; comment lines start with a '<code>;</code>' character at the beginning of the line (only spaces and tabs are allowed before the '<code>;</code>'). The file is made up of sections. Each section describes the skin for an application and has the following form: <table border=1 width="100%"><tr bgcolor=silver><td><pre> section = section name . . . end </pre></td></tr></table> Currently there is only one application, so you need only one section: its name is movieplayer. Within this section each window is described by a block in the following form: <table border=1 width="100%"><tr bgcolor=silver><td><pre> window = window name . . . end </pre></tr></td></table> where window name can be one of these strings: <ul> <li>main - for the main window</li> <li>sub - for the subwindow</li> <li>menu - for the skin menu</li> </ul> (The sub and menu block is optional---you do not need to create a menu or to decorate the subwindow.) Within a window block, you can define each item for the window by a line in this form: <blockquote> <pre> item = parameter </pre> </blockquote> where item is a string that identifies the type of the GUI item, parameter is a numeric or textual value (or a list of values separated by commas). Putting the above together, the whole file looks something like this: <table border=1 width="100%"><tr bgcolor=silver><td><pre> section = movieplayer window = main ; ... items for main window ... end window = sub ; ... items for subwindow ... end window = menu ; ... items for skin menu ... end end </pre></tr></td></table> Finally some words about specifying images for the various items. The name of an image file must be given without leading directories--- images are searched in the directory of the skins. You may (but you need not) specify the file's extension. If the file doesn't exist, MPlayer tries to load the file <filename>.<ext>, where tga, TGA, bmp, BMP, png and PNG is tried for <ext> (in this order). The first matching file will be used. <table border=1 cellpadding=5 width="100%"><tr bgcolor="#ffffcc"><td> Here is an example to make this clear. Suppose that you have an image called main.png that you use for the main window: <blockquote> <pre> base = main, -1, -1 </pre> </blockquote> MPlayer tries to load main, main.tga, main.TGA, main.bmp etc, so main.png will be found. If (by accident) you wrote <blockquote> <pre> base = main.bmp, -1, -1 </pre> </blockquote> then main.bmp, main.bmp.tga, main.bmp.TGA, main.bmp.bmp would be searched and MPlayer would finally give up because there is no main.bmp in the directory, but main.png. </td></tr></table> <h3><a name="mainwin">3.1 Main window</a></h3> Below you can see the list of items that can be used in the '<code>window = main</code>' . . . '<code>end</code>' block. <dl> <dt><a name="main.base"> base = image, x, y </a></dt> <dd> Lets you specify the background image to be used for the main window. The window will appear at the given x,y position on the screen (0,0 is the top left corner). You can specify -1 for center and -2 for right (x) and bottom (y). The window will be as large as the image. Warning: transparent regions in the image (colored #FF00FF) appear black on X servers without the XShape extension. </dd> </dl> <dl> <dt><a name="main.button"> button = image, x, y, width, height, message</a></dt> <dd> Place a button of width * height size at the x,y position. The specified message is generated when the button is clicked. The image given by image must have three parts below each other (according to the possible states of the button), like this: <div align=center><table><tr><td><pre> +------------+ | pressed | +------------+ | released | +------------+ | disabled | +------------+ </pre></td></tr></table></div> </dd> </dl> <dl> <dt><a name="main.decoration"> decoration = enable|disable </a></dt> <dd> Enable or disable window manager decoration of the main window. Default is disable. </dd> </dl> <dl> <dt> <a name="main.hpotmeter"> hpotmeter = butt, bw,bh, phases, numphases, default, x, y, w, h, msg </a> </dt> <dd> Place a horizontal potmeter of w * h size at the x,y position. The image can be divided into different parts for the different phases of the potmeter (for example, you can have a pot for volume control that turns from green to red while its value changes from the minimum to the maximum.) hpotmeter can have a button that can be dragged horizontally. The parameters are: <ul> <li>butt - the image to be used for the button (must have three parts below each other, like in case of <a href="#main.button">button</a>)</li> <li>bw, bh - size of the button</li> <li>phases - The image to be used for the different phases of the hpotmeter. The image must be divided into numphases parts vertically (see below). A special value of <kbd>NULL</kbd> can be used if you want no such image. </li> <li>numphases - number of phases stored in the phases image</li> <li>default - default value for hpotmeter (in the range 0 to 100)</li> <li>x, y - position for the hpotmeter</li> <li>w, h - width and height of the hpotmeter</li> <li>msg - the message to be generated when the value of hpotmeter is changed</li> </ul> The image used for the different phases must look something like this: <div align=center><table border=0><tr><td><pre> +------------+ | phase #1 | +------------+ | phase #2 | +------------+ ... +------------+ | phase #n | +------------+ </pre></td></tr></table></div> Note: there will be a vpotmeter item too, but is it not implemented yet. </dd> </dl> <dl> <dt><a name="main.potmeter"> potmeter = phases, numphases, default, x, y, w, h, msg </a></dt> <dd> A potmeter without a button. (I guess it is ment to be turned round, but it reacts to horizontal dragging only.) For the description of the parameters see <a href="#main.hpotmeter">hpotmeter</a>. phases can be <code>NULL</code>, but its quite useless, since you can not see where the potmeter is set. </dd> </dl> <dl> <dt><a name="main.font"> font = fontfile, fontid </a></dt> <dd> Defines a font. fontfile is the name of a font description file with <code>.fnt</code> extension (no need to specify the extension here). fontid is used to refer to the font (see <a href="#main.dlabel">dlabel</a> and <a href="#main.slabel">slabel</a>). Up to 25 fonts can be defined. </dd> </dl> <dl> <dt><a name="main.dlabel"> dlabel = x, y, length, align, fontid, "text" </a></dt> <dd> Place a dynamic label at the x,y position. The label is called dynamic because its text is refreshed periodically. The maximum length of the label is given by length (its height is the height of a character). If the text to be displayed is wider than that, then it will be scrolled, otherwise it is aligned within the specified space by the value of the align parameter: 0 is for right, 1 is for center, 2 is for left. The text to be displayed is given by text: it must be written between double quotes (<code>"</code>) (but the <code>"</code> cannot be part of the text). The label is displayed using the font identified by fontid. You can use the following variables in the text. <div align=center> <table valign=top border=1> <tr align=center><th>Variable</th><th align=left>Meaning</th></tr> <tr><td align=center><kbd>$1</kbd></td> <td>play time in hh:mm:ss format</td></tr> <tr><td align=center><kbd>$2</kbd></td> <td>play time in mmmm:ss format</td></tr> <tr><td align=center><kbd>$3</kbd></td> <td>play time in hh format (hours)</td></tr> <tr><td align=center><kbd>$4</kbd></td> <td>play time in mm format (minutes)</td></tr> <tr><td align=center><kbd>$5</kbd></td> <td>play time in ss format (seconds)</td></tr> <tr><td align=center><kbd>$6</kbd></td> <td>movie's length in hh:mm:ss format</td></tr> <tr><td align=center><kbd>$7</kbd></td> <td>movie's length in mmmm:ss format</td></tr> <tr><td align=center><kbd>$8</kbd></td> <td>play time in h:mm:ss format</td></tr> <tr><td align=center><kbd>$v</kbd></td> <td>volume in xxx.xx% format</td></tr> <tr><td align=center><kbd>$V</kbd></td> <td>volume in xxx.x format</td></tr> <tr><td align=center><kbd>$b</kbd></td> <td>balance in xxx.xx% format</td></tr> <tr><td align=center><kbd>$B</kbd></td> <td>balance in xxx.x format</td></tr> <tr><td align=center><kbd>$$</kbd></td> <td>the <kbd>$</kbd> character</td></tr> <tr><td align=center><kbd>$a</kbd></td> <td>a character according to the audio type (none: <code>n</code>, mono: <code>m</code>, stereo: <code>t</code>)</td></tr> <tr><td align=center><kbd>$t</kbd></td> <td>track number (in playlist)</td></tr> <tr><td align=center><kbd>$o</kbd></td> <td>filename</td></tr> <tr><td align=center><kbd>$f</kbd></td> <td>filename in lower case</td></tr> <tr><td align=center><kbd>$F</kbd></td> <td>filename in upper case</td></tr> <tr><td align=center><kbd>$T</kbd></td> <td>a character according to the stream type (file: <code>f</code>, video CD: <code>v</code>, DVD: <code>d</code>, URL: <code>u</code>) </td></tr> <tr><td align=center><kbd>$p</kbd></td> <td>the "p" character (if a movie is playing and the font has the "p" character) </td></tr> <tr><td align=center><kbd>$s</kbd></td> <td>the "s" character (if the movie is stopped and the font has the "s" character) </td></tr> <tr><td align=center><kbd>$e</kbd></td> <td>the "e" character (if playback is paused and the font has the "e" character) </td></tr> </table></div> Note: The <kbd>$a</kbd>, <kbd>$T</kbd>, <kbd>$p</kbd>, <kbd>$s</kbd> and <kbd>$e</kbd> variables all return characters that should be displayed as special symbols (for example, "e" is for the pause symbol that usually looks something like <code>||</code>). You should have a font for normal characters and a different font for symbols. See the section about <a href="#symbols">symbols</a> for more information. </dd> </dl> <dl> <dt><a name="main.slabel"> slabel = x, y, fontid, text </a></dt> <dd> Place a static label at the x,y position. text is displayed using the font identified by fontid. The text is just a raw string ($x variables do not work) that must be enclosed between double quotes (the <code>"</code> cannot be part of the text). The label is displayed using the font identified by fontid. </dd> </dl> <h3><a name="subwindow">3.2 Subwindow</a></h3> The following items can be used in the '<code>window = sub</code>' . . . '<code>end</code>' block. <dl> <dt><a name="sub.base"> base = image, x, y, width, height </a></dt> <dd> The image to be displayed in the window. The window will appear at the given x,y position on the screen (0,0 is the top left corner). You can specify -1 for center and -2 for right (x) and bottom (y). The window will be as large as the image. width and height gives the size of the window; they are optional (if they are missing, the window is the same size as the image). </dd> </dl> <dl> <dt><a name="sub.background"> background = r, g, b </a></dt> <dd> Lets you set the background color. It is useful if the image is smaller than the window. r, g and b specifies the red, green and blue component of the color (each of them is a decimal number from 0 to 255). </dd> </dl> <h3><a name="skinmenu">3.3 Skin menu</a></h3> As mentioned earlier, the menu is displayed using two images. Normal menu entries are taken from the image specified by the base item, while the currently selected entry is taken from the image specified by the selected item. You must define the position and size of each menu entry by the menu item. These are the items that can be used in the '<code>window = menu</code>' . . . '<code>end</code>' block. <dl> <dt><a name="menu.base"> base = image </a></dt> <dd> The image for normal menu entries. </dl> </dd> <dl> <dt><a name="menu.selected"> selected = image </a></dt> <dd> The image showing the menu with all entries selected. </dd> </dl> <dl> <dt><a name="menu.menu"> menu = x, y, width, height, message </a></dt> <dd> Defines the x,y position and the size of a menu entry in the images. message is the message to be generated when the mouse button is released over the entry. </dd> </dl> <h2><a name="fonts">4 Fonts</a></h2> As mentioned in the section about the parts of a skin, a font is defined by an image and a description file. You can place the characters anywhere in the image, but make sure that their position and size is given in the description file exactly. The font description file (with .fnt extension) can have comment lines starting with '<code>;</code>'. The file must have a line in the form <blockquote> <pre> image = image </pre> </blockquote> where image is the name of the image file to be used for the font (you do not have to specify the extension). The above line is followed by character definition lines of the form: <blockquote> <pre> "char" = x, y, w, h </pre> </blockquote> Here x and y specifies the position of the char character in the image (0,0 is the upper left corner). w and h is the width and height of the character (in pixels, of course). Here is an example that defines the A, B, C characters using font.png. <table width="100%" border=1><tr bgcolor=silver><td><pre> ; can be "font" instead of "font.png" image = font.png ; Three characters are enough for demonstration only. :-) "A" = 0,0, 7,13 "B" = 7,0, 7,13 "C" = 14,0, 7,13 </pre></td></tr></table> <h3><a name="symbols">4.1 Symbols</a></h3> Some characters have special meanings when returned by some of the variables used in <a href="#main.dlabel">dlabel</a>; these characters are meant to be displayed as symbols. (For example, in case of a DVD stream, you could display a nice DVD logo instead of the character 'd'.) The following table lists all the characters that can be used to display symbols (and thus require a different font). <div align=center> <table> <tr><th align=center>Character</th><th align=left>Symbol</th></tr> <tr><td align=center><kbd>p</kbd></td> <td align=left>play</td></tr> <tr><td align=center><kbd>s</kbd></td> <td align=left>stop</td></tr> <tr><td align=center><kbd>e</kbd></td> <td align=left>pause</td></tr> <tr><td align=center><kbd>n</kbd></td> <td align=left>no sound</td></tr> <tr><td align=center><kbd>m</kbd></td> <td align=left>mono sound</td></tr> <tr><td align=center><kbd>t</kbd></td> <td align=left>stereo sound</td></tr> <tr><td align=center><kbd>f</kbd></td> <td align=left>stream is a file</td></tr> <tr><td align=center><kbd>v</kbd></td> <td align=left>stream is a video CD</td></tr> <tr><td align=center><kbd>d</kbd></td> <td align=left>stream is a DVD</td></tr> <tr><td align=center><kbd>u</kbd></td> <td align=left>stream is a URL</td></tr> </table> </div> Note: currently only 'p', 's', 'e', 'n', 'm' and 't' is used. <h2><a name="guimsg">Appendix A: GUI messages</a></h2> These are the messages that can be generated by buttons, potmeters and menu entries. Note: some of the messages might not work as expected (or not work at all). As you know, the GUI is under development. Playback control: <blockquote> <dl> <dt>evNext <dd>Jump to next track in the playlist. <dt>evPause <dd>Pause playing. <dt>evPauseSwitchToPlay <dd>Forms a switch together with evPlaySwitchToPause. They can be used to have a common play/pause button. Both messages should be assigned to buttons displayed at the very same position in the window. This message pauses playing and the image for the evPlaySwitchToPause button is displayed (to indicate that the button can be pressed to continue playing). <dt>evPlay <dd>Start playing. <dt>evPlaySwitchToPause <dd>The opposite of evPauseSwitchToPlay. This message starts playing and the image for the evPauseSwitchToPlay button is displayed (to indicate that the button can be pressed to pause playing). <dt>evPrev <dd>Jump to previous track in the playlist. <dt>evStop <dd>Stop playing. </dl> </blockquote> Seeking in the stream: <blockquote> <dl> <dt>evBackward10sec <dt>evBackward1min <dt>evBackward10min <dd>Seek backward 10 seconds / 1 minute / 10 minutes. <dt>evForward10sec <dt>evForward1min <dt>evForward10min <dd>Seek forward 10 seconds / 1 minute / 10 minutes. <dt>evSetMoviePosition <dd>Seek to position (can be used by a potmeter; the relative value (0-100%) of the potmeter is used). </dl> </blockquote> Video control: <blockquote> <dl> <dt>evDoubleSize <dd>Set the movie window to double size. <dt>evFullScreen <dd>Switch fullscreen mode on/off. <dt>evNormalSize <dd>Set the movie window to its normal size. </dl> </blockquote> Audio control: <blockquote> <dl> <dt>evDecAudioBufDelay <dd>Decrease audio buffer delay. <dt>evDecBalance <dd>Decrease balance. <dt>evDecVolume <dd>Decrease volume. <dt>evIncAudioBufDelay <dd>Increase audio buffer delay. <dt>evIncBalance <dd>Increase balance. <dt>evIncVolume <dd>Increase volume. <dt>evMute <dd>Mute/unmute the sound. <dt>evSetBalance <dd>Set balance (can be used by a potmeter; the relative value (0-100%) of the potmeter is used). <dt>evSetVolume <dd>Set volume (can be used by a potmeter; the relative value (0-100%) of the potmeter is used). </dl> </blockquote> Miscellaneous: <blockquote> <dl> <dt>evAbout <dd>Open the about window. <dt>evEqualeaser <dd>Turn the equalizer on/off. <dt>evExit <dd>Quit from the program. <dt>evIconify <dd>Iconify the window. <dt>evLoad <dd>Load a file (by opening a file browser window, where you can choose a file). <dt>evLoadPlay <dd>Does the same as evLoad, but it automatically starts playing after the file is loaded. <dt>evNone <dd>Empty message, it has no effect. (Except maybe in CVS versions. :-)) <dt>evPlayList <dd>Open/close the playlist window. <dt>evPreferences <dd>Open the preferences window. <dt>evSkinBrowser <dd>Open the skin browser window. </dl> </blockquote> </body> </html> --- NEW FILE --- <HTML> <BODY BGCOLOR=white> <A NAME=2.3.2>2.3.2. Audio output devices</A> MPlayer's audio interface is called libao2. It currently contains these drivers : <TABLE BORDER=0> <TD COLSPAN=4>General:</TD> <TR><TD>  </TD><TD VALIGN=top>oss</TD><TD>  </TD><TD>OSS (ioctl) driver</TD></TR> <TR><TD></TD><TD VALIGN=top>sdl</TD><TD></TD><TD>SDL driver (supports up/downsampling, ESD, ARTS etc)</TD></TR> <TR><TD></TD><TD VALIGN=top>nas</TD><TD></TD><TD>NAS (Network Audio System) driver</TD></TR> <TR><TD></TD><TD VALIGN=top>alsa5</TD><TD></TD><TD>native ALSA 0.5 driver</TD></TR> <TR><TD></TD><TD VALIGN=top>alsa9</TD><TD></TD><TD>native ALSA 0.9 driver (works, but has problems -> use OSS)</TD></TR> <TR><TD></TD><TD VALIGN=top>sun</TD><TD></TD><TD>SUN audio driver (/dev/audio) for BSD and Solaris8 users</TD></TR> </TABLE> The fact is, Linux soundcard drivers are usually shit, and always as incompatible as they can be. It MAY take a while to find your optimal settings. <UL> <LI>if you have OSS as driver, first try with -ao oss (this is the default). If you experience glitches, halts or anything out of the ordinary, have a look at -ao sdl (NOTE: of course you'll have to have a new SDL library and its devel pair installed). It helps in a lot of cases (it also supports ESD, ARTS, and up/downsampling. /esd is GNOME's, arts is KDE's sound daemon/).</LI> <LI>if you have ALSA version 0.5, then you ALMOST always have to use -ao alsa5 , since 0.5 has buggy OSS emulation code, and will crash MPlayer with a message like this: <UL> <CODE>DEMUXER: Too many (945 in 8390980 bytes) video packets in the buffer!</CODE></UL> </LI> <LI>if you have ALSA version 0.9, use -ao oss or -ao sdl as you wish. You can also use -ao alsa9 as it works now, however it has many problems (losing sync, disappearing audio, etc).</LI> </UL> On Solaris/FreeBSD systems, use the SUN audio driver with the -ao sun option, otherwise you'll have no video, nor audio playing. <A NAME=2.3.2.1>2.3.2.1. Soundcard experiences, recommendations</A> <TABLE BORDER=0 WIDTH=100%> <TD COLSPAN=3>VIA onboard chipset (via82cxxx) 48Khz only</TD><TR> <TD></TD><TD>Driver:</TD><TD> from <A HREF="http://sourceforge.net/project/showfiles.php?group_id=3242&release_id=59602">here</A></TD><TR> <TD COLSPAN=3>Aureal Vortex 2</TD><TR> <TD>    </TD><TD>OSS:</TD><TD>no driver</TD><TR> <TD></TD><TD>OSS/Pro:</TD><TD>OK</TD><TR> <TD></TD><TD>ALSA:</TD><TD>no driver</TD><TR> <TD></TD><TD>Max kHz:</TD><TD>48</TD><TR> <TD></TD><TD>Driver:</TD><TD><A HREF="http://aureal.sourceforge.net">aureal.sourceforge.net</A></TD><TR> <TD></TD><TD>Driver2:</TD><TD> from <A HREF="http://makacs.poliod.hu/~pontscho/aureal/au88xx-1.1.3.tar.bz2">here</A> (buffer size increased to 32k)</TD><TR> <TD COLSPAN=3>GUS PnP</TD><TR> <TD></TD><TD>OSS:</TD><TD>no driver</TD><TR> <TD></TD><TD>OSS/Pro:</TD><TD>OK</TD><TR> <TD></TD><TD>ALSA:</TD><TD>OK</TD><TR> <TD></TD><TD>Max kHz:</TD><TD>48</TD><TR> <TD COLSPAN=3>SB Live!</TD><TR> <TD></TD><TD>OSS:</TD><TD>OK</TD><TR> <TD></TD><TD>ALSA:</TD><TD>(?)</TD><TR> <TD></TD><TD>Max kHz:</TD><TD>48</TD><TR> <TD COLSPAN=3>SB AWE 64</TD><TR> <TD></TD><TD>OSS:</TD><TD>max 44kHz</TD><TR> <TD></TD><TD>ALSA:</TD><TD>48kHz sounds shit</TD><TR> <TD></TD><TD>Max kHz:</TD><TD>48</TD><TR> <TD COLSPAN=3>Gravis UltraSound ACE</TD><TR> <TD></TD><TD>OSS:</TD><TD>max 44Khz. not OK</TD><TR> <TD></TD><TD>ALSA:</TD><TD>OK</TD><TR> <TD></TD><TD>Max kHz:</TD><TD>48</TD><TR> <TD COLSPAN=3>Gravis UltraSound MAX</TD><TR> <TD></TD><TD>OSS:</TD><TD>OK</TD><TR> <TD></TD><TD>ALSA:</TD><TD>OK (?)</TD><TR> <TD></TD><TD>Max kHz:</TD><TD>48</TD><TR> <TD COLSPAN=3>ESS 688</TD><TR> <TD></TD><TD>OSS:</TD><TD>OK</TD><TR> <TD></TD><TD>ALSA:</TD><TD>OK (?)</TD><TR> <TD></TD><TD>Max kHz:</TD><TD>48</TD><TR> <TD COLSPAN=3>C-Media cards (which ones?)</TD><TR> <TD></TD><TD>OSS:</TD><TD>not OK (hissing) (?)</TD><TR> <TD></TD><TD>ALSA:</TD><TD>OK (?)</TD><TR> <TD></TD><TD>Max kHz:</TD><TD>?</TD><TR> <TD COLSPAN=3>Yamaha cards (*ymf*)</TD><TR> <TD></TD><TD>OSS:</TD><TD>not OK (?) (maybe -ao sdl)</TD><TR> <TD></TD><TD>ALSA:</TD><TD>OK only with ALSA 0.5 with OSS emulation AND -ao sdl (!) (?)</TD><TR> <TD></TD><TD>Max kHz:</TD><TD>?</TD><TR> <TD COLSPAN=3>Cards with envy24 chips (like Terratec EWS88MT)</TD><TR> <TD></TD><TD>OSS:</TD><TD>?</TD><TR> <TD></TD><TD>OSS/Pro:</TD><TD>OK</TD><TR> <TD></TD><TD>ALSA:</TD><TD>?</TD><TR> <TD></TD><TD>Max kHz:</TD><TD>?</TD><TR> <TD COLSPAN=3>PC Speaker or DAC</TD><TR> <TD></TD><TD>OSS:</TD><TD>OK (use the SDL driver : -ao sdl)</TD><TR> <TD></TD><TD>ALSA:</TD><TD>no driver</TD><TR> <TD></TD><TD>Max kHz:</TD><TD>the driver emulates 44.1 maybe more</TD><TR> <TD></TD><TD>Driver:</TD><TD><A HREF="ftp://ftp.infradead.org/pub/pcsp">ftp://ftp.infradead.org/pub/pcsp</A></TD><TR> </TABLE> <UL> <LI>on Linux, use at least kernel 2.4 if possible, 2.2 isn't tested <LI>if sound clicks when playing from CD-ROM, turn on IRQ unmasking ! for example "hdparm -u1 /dev/cdrom" (see "man hdparm" !!!) This is recommended anyways... (for XMMS, etc...) Read section <A HREF="cd-dvd.html#4.1">4.1</A>. <LI>don't use your soundcard by other application ( for ex. XMMS ) ! if you use ESD, start MPlayer with the '-vo sdl:esd' option ! <LI>Please tell us how MPlayer and your soundcard(s) worked together! </UL> </BODY> </HTML> --- NEW FILE --- <HTML> <BODY BGCOLOR=white> In medias res There are two major topic which always causes huge dispute and flame on the <A HREF="http://www.MPlayerHQ.hu/cgi-bin/htsearch">mplayer-users</A> mailing list. Number one is of course the topic of the GCC 2.96 series Also read <A HREF="gcc-2.96-3.0.html">this</A> text !!! The background : there were/are the GCC 2.95 series. The best of them was 2.95.3 . Please note the style of the version numbering. This is how the GCC team numbers their compilers. The 2.95 series are good. We never ever saw anything that was miscompiled because of the 2.95's faultiness. The action : RedHat started to include a GCC version of 2.96 with their distributions. Note the version numbering. This should be the GCC team's versioning. They patched the CVS version of GCC (something between 2.95 and 3.0) They patched it very deep, and used this version in the distrib because 3.0 wasn't out at time, and they wanted IA64 support ASAP (business reasons). Oh, and GCC 2.95 miscompiles bash on the s390 architecture (there is no RedHat distribution for s390..) . The facts : MPlayer's compile process needs the <CODE>--disable-gcc-checking</CODE> to proceed upon detecting a GCC version of 2.96 (apparently it needs this option on egcs too. It's because we don't test MPlayer on egcs. Pardon us, but we rather develop MPlayer). If you know MPlayer, you should know that it has great speed. It achieves this by having overoptimized MMX/SSE/3DNow/etc codes, fastmemcpy, and lots of other features. MPlayer contained MMX/3DNow instructions in a syntax that all Linux compilers accept it... except RedHat's GCC (it's more standard compliant). It simply skips them. It doesn't give errors. It doesn't give warnings. And, there is Lame. With gcc 2.96, its quality check (<CODE>make test</CODE> after compiling) doesn't even run !!! But hey, it compiles bash on s390 and IA64. The statements : most developers around the world begun having bad feelings about RedHat's GCC 2.96 , and told their RedHat users to compile with other compiler than 2.96 . RedHat users' disappointment slowly went into anger. What was all good for, apart from giving headaches to developers, putting oil on anti-RedHat flame, confusing users? The answer, I do not know. Present age, present time : RedHat says that GCC 2.96-85 and above is fixed, and works properly. Note the versioning. They should have started with something like this. What about GCC 2.96.85 ? It doesn't matter now. I don't search, but I still see bugs with 2.96 . It doesn't matter now, hopefully now RedHat will forget about 2.96 and turn towards 3.0. Towards a deep patched 3.0... What I don't understand is why are we hated by RedHat users for putting warning messages, and stay-away documents in MPlayer . Why are we called "brain damaged", "total asshole", "childish" by RedHat users, on our mailing list, and even on the redhat-devel . They even considered forking MPlayer for themselves. RedHat users. Why? It's RedHat that made the compiler, why do you have to hate us? Are you that fellow RedHat worshippers? Please stop it. We don't hold a grudge against users, doesn't matter how loud you advertise its contrary. Please go flame Linus Torvalds, the DRI developers (oh, now I know why there were laid off by VA!), the Wine, avifile. Even if we are arrogant, are we not the same as the previously listed ones? Why do we have to suffer from your unrightful wrath? I'm closing this topic. Think over it please. I (Gabucino) personally begun with <A HREF="http://www.redhat.com">RedHat</A>, then used Mandrake (sorry I don't know their URL), now I have <A HREF="http://www.linuxfromscratch.com">LFS</A>. Never held a grudge against RedHat or RedHat users, and I still don't. Hate is only comfortable. It won't bring you anywhere. Binary distribution of MPlayer Tons of users asked us about this. For example Debian users tend to say: Oh, I can <CODE>apt-get install avifile</CODE>, why should I compile MPlayer ? While this may sound reasonable, the problem lies a bit deeper than those-fuckin-MPlayer-developers-hate-gcc-2.96-and-RedHat-and-Debian. Reasons: Law MPlayer describes the sourcecode. It contains several files with incompatible licenses especially on the redistribution clauses. As source files, they are allowed to coexist in a same project. Therefore, NEITHER BINARIES NOR BINARY PACKAGES OF MPlayer ARE ALLOWED TO EXIST SINCE SUCH OBJECTS BREAK LICENSES. PEOPLE WHO DISTRIBUTE SUCH BINARY PACKAGES ARE DOING ILLEGAL ACTIVITIES. So if you know somebody who maintains a binary package then forward her/him this text and (ask him to) contact us. What (s)he is doing is illegal and IT IS NO LONGER MPlayer, but his/her mplayer. If it breaks, it is his/her fault. Don't come and cry on the MPlayer mailing lists, you will most likely be blacklisted. For example that french guy called Christian Marillat who denied our request, and is still distributing binary Debian packages of MPlayer, despite the fact that there was at least one user who downloaded it and failed (of course compiling from source helped him). And there is Guillaume Rousse, who is doing the same, but making RPMs for Mandrake. Do not support criminals! Reasons: Technical <UL> <LI>MPlayer's speed (MMX, SSE, fastmemcpy, etc) optimizations are determined during compilation. Thus a compiled binary contains very processor-specific code. An MPlayer binary compiled for K6 will die on Pentiums and vice versa. This has to be workarounded by runtime detection, which is not an easy thing to do becase it causes massive speed decrease. If you don't believe (it was explained in details 10000 times on mplayer-users, search the archive), solve it and send us a patch. Someone begun work on it, but disappeared since then.</LI> <LI>MPlayer's video/audio system is not plugin based. It is compiled into the binary, thus making the binary depend on various libraries (the GUI depends on GTK, DivX4 depends on libdivxdecore, SDL depends on libSDL, every SDL release contains an unique bug that has to be workarounded during compiletime, X11 output compiles differently for X3 and X4, etc). You may say: yes, let's make 30 versions of downloadable binaries! We won't. We will make these stuff pluggable in the future.</LI> </UL> </HTML> --- NEW FILE --- <HTML> <BODY BGCOLOR=white> <A NAME=2.3.1>2.3.1. Video output devices</A> <TABLE BORDER=0> <TD COLSPAN=4>General:</TD><TR> <TD>  </TD><TD VALIGN=top><A HREF=#2.3.1.13>x11</A></TD><TD>  </TD><TD>X11 with optional SHM extension</TD><TR> <TD></TD><TD VALIGN=top><A HREF=#2.3.1.2>xv</A></TD><TD></TD><TD>X11 using overlays with the Xvideo extension (hardware YUV & scaling)</TD><TR> [...966 lines suppressed...] mode which is detected automatically and in this case you'll get comparable with -vo dga and -vo fbdev drivers speed. Only thing you need to do - have TV connector plugged in before booting your PC since video BIOS initializes itself only once during POST procedure. For detail see <a href="video.html#2.3.1.12">VESA</a> sections of this documentation. <A NAME=2.3.1.A.3>2.3.1.A.3. Voodoo 3</A> Check <A HREF="http://www.iki.fi/too/tvout-voodoo3-3000-xfree">this URL</A>. </BODY> </HTML>

1 0

None
by None 11 Sep '25

11 Sep '25

(Publication # 22007 Rev: D Number 243192 Issue Date: August 1999 (pages 21 and below): If possible, use unsigned integer types over signed integer types. The unsigned types convey to the compiler that data cannot be negative, which allows some optimizations not possible with signed and potentially negative data. > > _______________________________________________ > Mplayer-cvslog mailing list > Mplayer-cvslog(a)mplayerhq.hu > http://mplayerhq.hu/mailman/listinfo/mplayer-cvslog > Best regards! Nick

1 0

None
by None 11 Sep '25

11 Sep '25

Simply it should be a good habit, imho ;) > Michael > _______________________________________________ > Mplayer-cvslog mailing list > Mplayer-cvslog(a)mplayerhq.hu > http://mplayerhq.hu/mailman/listinfo/mplayer-cvslog > Best regards! Nick

1 0