December 2005 - MPlayer-DOCS - lists.mplayerhq.hu

CVS: main/DOCS/man/en mplayer.1,1.1160,1.1161
by syncmail＠mplayerhq.hu 24 Dec '06

24 Dec '06

CVS change done by Diego Biurrun CVS Update of /cvsroot/mplayer/main/DOCS/man/en In directory mail:/var2/tmp/cvs-serv16416 Modified Files: mplayer.1 Log Message: misc fixes Index: mplayer.1 =================================================================== RCS file: /cvsroot/mplayer/main/DOCS/man/en/mplayer.1,v retrieving revision 1.1160 retrieving revision 1.1161 diff -u -r1.1160 -r1.1161 --- mplayer.1 22 Nov 2005 16:49:36 -0000 1.1160 +++ mplayer.1 23 Nov 2005 00:27:25 -0000 1.1161 @@ -301,7 +301,7 @@ Toggle displaying "forced subtitles". .IPs a\ \ \ \ Toggle subtitle alignment: top/\:middle/\:bottom. -.IPs "z and x" +.IPs "x and z" Adjust subtitle delay by +/\:- 0.1 seconds. .IPs "r and t" Move subtitles up/\:down. @@ -1961,9 +1961,12 @@ OSS audio output driver .PD 0 .RSs -.IPs dsp-device[:mixer-device[:mixer-channel]] -Sets the audio-output device (default: /dev/\:dsp), mixer device (default: -/dev/\:mixer) and mixer channel (default: pcm). +.IPs <dsp-device> +Sets the audio output device (default: /dev/\:dsp). +.IPs <mixer-device> +Sets the audio mixer device (default: /dev/\:mixer). +.IPs <mixer-channel> +Sets the audio mixer channel (default: pcm). .RE .PD 1 . @@ -2820,7 +2823,7 @@ has no effect, the size of the slices as provided by the decoder is used. .br If the decoder does not use slice rendering, the default is 16. -.REss +.RE .IPs (no)osd Enable or disable support for OSD rendering via OpenGL (default: enabled). This option is for testing; to disable the OSD use \-osdlevel 0 instead. @@ -2844,7 +2847,7 @@ .br 2: Use the GL_ARB_texture_non_power_of_two extension. In some cases only supported in software and thus very slow. -.REss +.RE .IPs (no)glfinish Call glFinish() before swapping buffers. Slower but in some cases more correct output (default: disabled).

4 8

CVS: main/DOCS/man/en mplayer.1,1.1167,1.1168
by syncmail＠mplayerhq.hu 03 Jan '06

03 Jan '06

CVS change done by Diego Biurrun CVS Update of /cvsroot/mplayer/main/DOCS/man/en In directory mail:/var2/tmp/cvs-serv694/DOCS/man/en Modified Files: mplayer.1 Log Message: preliminary environment variables section Index: mplayer.1 =================================================================== RCS file: /cvsroot/mplayer/main/DOCS/man/en/mplayer.1,v retrieving revision 1.1167 retrieving revision 1.1168 diff -u -r1.1167 -r1.1168 --- mplayer.1 7 Dec 2005 00:57:32 -0000 1.1167 +++ mplayer.1 7 Dec 2005 16:14:10 -0000 1.1168 @@ -9082,6 +9082,237 @@ . . .\" -------------------------------------------------------------------------- +.\" environment variables +.\" -------------------------------------------------------------------------- +. +.SH ENVIRONMENT VARIABLES +. +There are a number of environment variables that can be used to +control the behavior of MPlayer and MEncoder. +. +.TP +.B MPLAYER_HOME +Directory where MPlayer looks for user settings. +. +.SS libaf: +. +.TP +.B LADSPA_PATH +If LADSPA_PATH is set, it searches for the specified file. +If it is not set, you must supply a fully specified pathname. +FIXME: This is also mentioned in the ladspa section. +. +.SS libmpdvdkit2: +. +.TP +.B DVDCSS_CACHE +Specify a directory in which to store title key values. +This will speed up descrambling of DVDs which are in the cache. +The DVDCSS_CACHE directory is created if it does not exist, +and a subdirectory is created named after the DVD's title +or manufacturing date. +If DVDCSS_CACHE is not set or is empty, libdvdcss will use +the default value which is "${HOME}/.dvdcss/" under Unix and +"C:\Documents and Settings\$USER\Application Data\dvdcss\" under Win32. +The special value "off" disables caching. +. +.TP +.B DVDCSS_METHOD +Sets the authentication and decryption method that +libdvdcss will use to read scrambled discs. +Can be one of title, key or disc. +.PD 0 +.RSs +.IPs key\ \ +is the default method. +libdvdcss will use a set of calculated player keys to try and get the disc key. +This can fail if the drive does not recognize any of the player keys. +.IPs disc\ +is a fallback method when key has failed. +Instead of using player keys, libdvdcss will crack the disc key using +a brute force algorithm. +This process is CPU intensive and requires 64 MB of memory to store +temporary data. +.IPs title +is the fallback when all other methods have failed. +It does not rely on a key exchange with the DVD drive, but rather uses +a crypto attack to guess the title key. +On rare cases this may fail because there is not enough encrypted data +on the disc to perform a statistical attack, but in the other hand it +is the only way to decrypt a DVD stored on a hard disc, or a DVD with +the wrong region on an RPC2 drive. +.RE +.PD 1 +. +.TP +.B DVDCSS_RAW_DEVICE +Specify the raw device to use. +Exact usage will depend on your operating system, the Linux +utility to set up raw devices is raw(8) for instance. +Please note that on most operating systems, using a raw device +requires highly aligned buffers: Linux requires a 2048 bytes +alignment (which is the size of a DVD sector). +. +.TP +.B DVDCSS_VERBOSE +Sets the libdvdcss verbosity level. +.PD 0 +.RSs +.IPs 0 +Outputs no messages at all. +.IPs 1 +Outputs error messages to stderr. +.IPs 2 +Outputs error messages and debug messages to stderr. +.RE +.PD 1 +. +.TP +.B DVDREAD_NOKEYS +DVDREAD_NOKEYS is MPlayer specific, but currently unused. +In the file libmpdvdkit2/dvd_reader.c DVDREAD_NOKEYS is used +in the funcion initAllCSSKeys, but the only place where this +function is called is commented. +. +.TP +.B HOME +FIXME: Document this. +. +.SS libao2: +. +.TP +.B AO_SUN_DISABLE_SAMPLE_TIMING +FIXME: Document this. +. +.TP +.B AUDIODEV +FIXME: Document this. +. +.TP +.B AUDIOSERVER +Specifies the Network Audio System server to which the +nas audio output driver should connect and the transport +that should be used. +If unset DISPLAY is used instead. +The transport can be one of tcp and unix. +Syntax is tcp/somehost:someport, somehost:instancenumber +or [unix]:instancenumber. +.sp 1 +.RS +.I EXAMPLES: +.RE +.PD 0 +.RSs +.IPs AUDIOSERVER=somehost:0 +Connect to NAS server on somehost using default port and transport. +.IPs AUDIOSERVER=tcp/somehost:8000 +Connect to NAS server on somehost listening on TCP port 8000. +.IPs AUDIOSERVER=(unix)?:0 +Connect to NAS server instance 0 on localhost using unix domain sockets. +.RE +.PD 1 +. +.TP +.B DISPLAY +FIXME: Document this. +. +.SS vidix: +. +.TP +.B VIDIX_CRT +FIXME: Document this. +. +.SS osdep: +. +.TP +.B TERM +FIXME: Document this. +. +.SS libvo: +. +.TP +.B DISPLAY +FIXME: Document this. +. +.TP +.B FRAMEBUFFER +FIXME: Document this. +. +.TP +.B HOME +FIXME: Document this. +. +.SS libmpdemux: +. +.TP +.B HOME +FIXME: Document this. +. +.TP +.B HOMEPATH +FIXME: Document this. +. +.TP +.B http_proxy +FIXME: Document this. +. +.TP +.B LOGNAME +FIXME: Document this. +. +.TP +.B USERPROFILE +FIXME: Document this. +. +.SS libmpcodecs: +. +.TP +.B XANIM_MOD_DIR +FIXME: Document this. +. +.SS GUI: +. +.TP +.B CHARSET +FIXME: Document this. +. +.TP +.B DISPLAY +FIXME: Document this. +. +.TP +.B HOME +FIXME: Document this. +. +.SS libavformat: +. +.TP +.B AUDIO_FLIP_LEFT +FIXME: Document this. +. +.TP +.B BKTR_DEV +FIXME: Document this. +. +.TP +.B BKTR_FORMAT +FIXME: Document this. +. +.TP +.B BKTR_FREQUENCY +FIXME: Document this. +. +.TP +.B http_proxy +FIXME: Document this. +. +.TP +.B no_proxy +FIXME: Document this. +. +. +. +.\" -------------------------------------------------------------------------- .\" Files .\" -------------------------------------------------------------------------- .

2 1

CVS: main/DOCS/man/en mplayer.1,1.1162,1.1163
by syncmail＠mplayerhq.hu 03 Jan '06

03 Jan '06

CVS change done by Oded Shimon CVS Update of /cvsroot/mplayer/main/DOCS/man/en In directory mail:/var2/tmp/cvs-serv26621/DOCS/man/en Modified Files: mplayer.1 Log Message: new -msglevel option, constrols msg level for every msg module Index: mplayer.1 =================================================================== RCS file: /cvsroot/mplayer/main/DOCS/man/en/mplayer.1,v retrieving revision 1.1162 retrieving revision 1.1163 diff -u -r1.1162 -r1.1163 --- mplayer.1 5 Dec 2005 19:27:03 -0000 1.1162 +++ mplayer.1 6 Dec 2005 08:42:48 -0000 1.1163 @@ -511,6 +511,43 @@ Specify configuration file to be parsed after the default ones. . .TP +.B \-msglevel <all=<level>:module=<level>:...> +Control verbosity directly for each module. +The 'all' module changes the verbosity of all other modules not specified. +See '-msglevel help' for a list of all modules +.br +.I NOTE: +Messages printed before the command line is loaded cannot be controlled. +.br +Available levels: +.PD 0 +.RSs +.IPs -1 +Complete silence. +.IPs 0 +Fatal messages only. +.IPs 1 +Error messages. +.IPs 2 +Warning messages. +.IPs 3 +Short hints. +.IPs 4 +Information messages. +.IPs 5 +Status messages (those hidden by -quiet). +.IPs 6 +Verbose messages. +.IPs 7 +Debug level 2. +.IPs 8 +Debug level 3. +.IPs 9 +Debug level 4. +.RE +.PD 1 +. +.TP .B \-quiet\ Make console output less verbose; in particular, prevents the status line (i.e.\& A: 0.7 V: 0.6 A-V: 0.068 ...) from being displayed.

3 3

CVS: main/DOCS/xml/en tvinput.xml,1.14,1.15
by syncmail＠mplayerhq.hu 31 Dec '05

31 Dec '05

CVS change done by Guillaume Poirier CVS Update of /cvsroot/mplayer/main/DOCS/xml/en In directory mail:/var2/tmp/cvs-serv16051/DOCS/xml/en Modified Files: tvinput.xml Log Message: Add Rich's advice posted on the thread: Date: Dec 16, 2005 8:51 PM Subject: Re: [MPlayer-users] How to tell if the video input is interlaced or not? Index: tvinput.xml =================================================================== RCS file: /cvsroot/mplayer/main/DOCS/xml/en/tvinput.xml,v retrieving revision 1.14 retrieving revision 1.15 diff -u -r1.14 -r1.15 --- tvinput.xml 1 Sep 2005 23:53:57 -0000 1.14 +++ tvinput.xml 31 Dec 2005 19:16:14 -0000 1.15 @@ -54,9 +54,15 @@ <listitem> <para> -If you capture the video with the vertical resolution higher than half of -the full resolution (i.e. 288 for PAL or 240 for NTSC), make sure you turned -deinterlacing on. Otherwise you'll get a movie which is distorted during +If you capture the video with the vertical resolution higher than half +of the full resolution (i.e. 288 for PAL or 240 for NTSC), then the +'frames' you get will really be interleaved pairs of fields. +Depending on what you want to do with the video you may leave it in +this form, destructively deinterlace, or break the pairs apart into +individual fields. +</para> +<para> +Otherwise you'll get a movie which is distorted during fast-motion scenes and the bitrate controller will be probably even unable to retain the specified bitrate as the interlacing artifacts produce high amount of detail and thus consume lot of bandwidth. You can enable

1 0

CVS: main/DOCS/xml/en encoding-guide.xml,1.36,1.37
by syncmail＠mplayerhq.hu 31 Dec '05

31 Dec '05

CVS change done by Guillaume Poirier CVS Update of /cvsroot/mplayer/main/DOCS/xml/en In directory mail:/var2/tmp/cvs-serv20612/DOCS/xml/en Modified Files: encoding-guide.xml Log Message: New section: choosing the video codec for your encode: what to consider before picking it. Index: encoding-guide.xml =================================================================== RCS file: /cvsroot/mplayer/main/DOCS/xml/en/encoding-guide.xml,v retrieving revision 1.36 retrieving revision 1.37 diff -u -r1.36 -r1.37 --- encoding-guide.xml 6 Dec 2005 00:45:15 -0000 1.36 +++ encoding-guide.xml 27 Dec 2005 09:34:57 -0000 1.37 @@ -1350,6 +1350,111 @@ </para> </sect2> +<sect2 id="menc-feat-dvd-mpeg4-codec"> +<title>Choosing the video codec</title> + +<para> + Choosing the video codec to use depends on several factors, some of + which widely depend on personal taste and technical constraints. +</para> +<itemizedlist> + <listitem><para> + <emphasis role="bold">Compression efficiency</emphasis>: + It's quite easy to understand that newer-generation codecs are made + to yield better picture quality than previous generations. + Therefore, you cannot be wrong + <footnote id='fn-menc-feat-dvd-mpeg4-codec-cpu'> + <para>Be careful, however: decoding DVD-resolution MPEG-4 AVC videos + requires a fast machine (i.e. a Pentium 4 over 1.5Ghz or a Pentium M + over 1Ghz). + </para></footnote> + by choosing MPEG-4 AVC codecs like + <systemitem class="library">x264</systemitem> instead of MPEG-4 ASP codecs + such as <systemitem class="library">libavcodec</systemitem> MPEG-4 or + <systemitem class="library">XviD</systemitem>. + (To get a better grasp of what the fundamental differences between + MPEG-4 ASP and MPEG-4 AVC are, you would be well advised to read the entry + "<ulink url="http://guru.multimedia.cx/?p=10">15 reasons why MPEG4 sucks</ulink>" + from Michael Niedermayer's blog.) + Likewise, you should get better quality using MPEG-4 ASP instead + of MPEG-2 codecs. + </para> + <para> + However, newer codecs which are in heavy development can suffer from + bugs which have not yet been noticed and which can ruin an encode. + This is simply the tradeoff for using bleeding-edge technology. + </para> + <para> + What's more, beginning to use a new codec requires that you spend some + time becoming familiar with its available options, so that you know what + to adjust to achieve a desired picture quality. + </para></listitem> + + <listitem><para> + <emphasis role="bold">Hardware compatibility</emphasis>: + It usually takes a long time for standalone video players to begin to + include support for the latest video codecs. + As a result, most only support MPEG-2 and MPEG-4 ASP + (beware: usually, not all MPEG-4 ASP features are supported). + Please refer to the technical specs of your player (if they are available), + or Google around for more information. + </para></listitem> + + <listitem><para> + <emphasis role="bold">Best quality per encoding time</emphasis>: + Codecs that have been around for some time (such as + <systemitem class="library">libavcodec</systemitem> MPEG-4 and + <systemitem class="library">XviD</systemitem>) are usually heavily + optimized with all kinds of smart algorithms and SIMD assembly code. + That's why they tend to yield the best quality per fps. + However, they may have some very advanced options that, if enabled, + will make the encode really slow for marginal gains. + </para> + <para> + If you are after blazing speed you should stick around the default + settings of the video codec (which doesn't mean you should not experiment + with some of the options which are mentioned in other sections + of this guide). + </para> + <para> + You may also consider choosing a codec which can do multi-threaded + processing. + <systemitem class="library">libavcodec</systemitem> MPEG-4 does + allow that, resulting in small speed gains at the price of lower + picture quality. + <systemitem class="library">XviD</systemitem> has some experimental + patches available to boost encoding speed, by about 40-60% in typical + cases, with low picture degradation. + <systemitem class="library">x264</systemitem> also allows multi-threaded + encoding, which currently speeds-up encoding by 15-30% while lowering + PSNR by about 0.05dB. + </para></listitem> + + <listitem><para> + <emphasis role="bold">Personal taste</emphasis>: + This is where it gets almost irrational: For the same reason that some + hung on to DivX 3 for years when newer codecs were already doing wonders, + some folks will prefer <systemitem class="library">XviD</systemitem> + or <systemitem class="library">libavcodec</systemitem> MPEG-4 over + <systemitem class="library">x264</systemitem>. + </para> + <para> + Make your own judgment, and don't always listen to what some people will + tell you to do or think: The best codec is the one you master the best, + and the one that looks best to your eyes on your display + <footnote id='fn-menc-feat-dvd-mpeg4-codec-playback'> + <para>The same encode may not look the same on someone else's monitor or + when played back by a different decoder, so future-proof your encodes by + playing them back on different setups.</para></footnote>! + </para></listitem> +</itemizedlist> +<para> + Please refer to the section + <link linkend="menc-feat-selecting-codec">selecting codecs and container formats</link> + to get a list of supported codecs. +</para> +</sect2> + <sect2 id="menc-feat-dvd-mpeg4-audio"> <title>Audio</title>

5 11

CVS: main/DOCS/xml/en skin.xml,1.13,1.14
by syncmail＠mplayerhq.hu 31 Dec '05

31 Dec '05

CVS change done by Diego Biurrun CVS Update of /cvsroot/mplayer/main/DOCS/xml/en In directory mail:/var2/tmp/cvs-serv3512/en Modified Files: skin.xml Log Message: Guide on creating quality skins. Index: skin.xml =================================================================== RCS file: /cvsroot/mplayer/main/DOCS/xml/en/skin.xml,v retrieving revision 1.13 retrieving revision 1.14 diff -u -r1.13 -r1.14 --- skin.xml 10 Dec 2005 20:28:11 -0000 1.13 +++ skin.xml 31 Dec 2005 14:03:47 -0000 1.14 @@ -1103,4 +1103,54 @@ </sect1> +<sect1 id="skin-quality"> +<title>Creating quality skins</title> + +<para> +So you have read up on creating skins for the +<application>MPlayer</application> GUI, done your best with the +<application>Gimp</application> and wish to submit your skin to us? +Read on for some guidelines to avoid common mistakes and produce +a high quality skin. +</para> + +<para> +We want skins that we add to our repository to conform to certain +quality standards. There are also a number of things that you can do +to make our lives easier. +</para> + +<para> +As an example you can look at the <systemitem>Blue</systemitem> skin, +it satisfies all the criteria listed below since version 1.5. +</para> + +<itemizedlist> + <listitem><para>Each skin should come with a + <filename>README</filename> file that contains information about + you, the author, copyright and license notices and anything else + you wish to add. If you wish to have a changelog, this file is a + good place.</para></listitem> + + <listitem><para>There should be a file <filename>VERSION</filename> + with nothing more than the version number of the skin on a single + line (e.g. 1.0).</para></listitem> + + <listitem><para>Horizontal and vertical controls (sliders like volume + or position) should have the center of the knob properly centered on + the middle of the slider. It should be possible to move the knob to + both ends of the slider, but not past it.</para></listitem> + + <listitem><para>Skin elements should have the right sizes declared + in the skin file. If this is not the case you can click outside of + e.g. a button and still trigger it or click inside its area and not + trigger it.</para></listitem> + + <listitem><para>The <filename>skin</filename> file should be + prettyprinted and not contain tabs. Prettyprinted means that the + numbers should line up neatly in columns.</para></listitem> +</itemizedlist> + +</sect1> + </appendix>

1 0

CVS: main/DOCS/xml Makefile,1.24,1.25
by syncmail＠mplayerhq.hu 31 Dec '05

31 Dec '05

CVS change done by Diego Biurrun CVS Update of /cvsroot/mplayer/main/DOCS/xml In directory mail:/var2/tmp/cvs-serv19664 Modified Files: Makefile Log Message: Build incomplete Russian docs last. Index: Makefile =================================================================== RCS file: /cvsroot/mplayer/main/DOCS/xml/Makefile,v retrieving revision 1.24 retrieving revision 1.25 diff -u -r1.24 -r1.25 --- Makefile 15 Apr 2005 23:23:43 -0000 1.24 +++ Makefile 31 Dec 2005 14:01:19 -0000 1.25 @@ -1,7 +1,7 @@ # Makefile for generating the HTML documentation # List of subdirectories to be processed. -SUBDIRS = en es fr hu pl ru cs +SUBDIRS = en es fr hu pl cs ru # Generated chunked HTML files go here. HTML_CHUNKED = ../HTML

1 0

glossary or Table of Contents or Index for manual?
by compn 31 Dec '05

31 Dec '05

some users say that they cannot find what they want in the manual. i think this is because there are too many words that decsribe the same thing. <ekkaia> the problem with the manual is that you have to know what your doing ;P i propose a glossary or index or table of contents at the end of the manual which says: fast forward or seek or jump or skip or advance or goto: see -ss keep video window or stay or one window or continue: see -fixed-vo flashing screen or green pink screen see -colorkey because a user will only search for one or two words that he thinks would describe what he is looking for. this is inheritenly a problem with anyone who does searching. you get better results if you try different words. any thoughts? -compn

3 2

CVS: main/DOCS/xml/en codecs.xml,1.72,1.73
by syncmail＠mplayerhq.hu 31 Dec '05

31 Dec '05

CVS change done by Loren Merritt CVS Update of /cvsroot/mplayer/main/DOCS/xml/en In directory mail:/var2/tmp/cvs-serv19753/en Modified Files: codecs.xml Log Message: update x264 feature summary Index: codecs.xml =================================================================== RCS file: /cvsroot/mplayer/main/DOCS/xml/en/codecs.xml,v retrieving revision 1.72 retrieving revision 1.73 diff -u -r1.72 -r1.73 --- codecs.xml 1 Aug 2005 21:00:07 -0000 1.72 +++ codecs.xml 31 Dec 2005 00:41:35 -0000 1.73 @@ -539,26 +539,24 @@ <title>Encoder features</title> <listitem><para>CAVLC/CABAC</para></listitem> <listitem><para>Multi-references</para></listitem> - <listitem><para>Intra: all macroblock types (16x16 and 4x4 with + <listitem><para>Intra: all macroblock types (16x16, 8x8, and 4x4 with all predictions)</para></listitem> <listitem><para>Inter P: all partitions (from 16x16 down to 4x4)</para></listitem> <listitem><para>Inter B: partitions from 16x16 down to 8x8 (including SKIP/DIRECT)</para></listitem> <listitem><para>Ratecontrol: constant quantizer, constant bitrate, - or multipass ABR</para></listitem> + single or multipass ABR, optional VBV</para></listitem> <listitem><para>Scene cut detection</para></listitem> <listitem><para>Adaptive B-frame placement</para></listitem> <listitem><para>B-frames as references / arbitrary frame order</para></listitem> + <listitem><para>8x8 and 4x4 adaptive spatial transform</para></listitem> + <listitem><para>Lossless mode</para></listitem> + <listitem><para>Custom quantization matrices</para></listitem> + <listitem><para>Parallel encoding of multiple slices</para></listitem> </itemizedlist> -<itemizedlist> -<title>Encoder limitations</title> - <listitem><para>No real RD</para></listitem> -</itemizedlist> - - </sect4> <sect4 id="codec-h264-whatis">

1 0

CVS: main/DOCS/xml/en ports.xml,1.73,1.74
by syncmail＠mplayerhq.hu 30 Dec '05

30 Dec '05

CVS change done by Diego Biurrun CVS Update of /cvsroot/mplayer/main/DOCS/xml/en In directory mail:/var2/tmp/cvs-serv4051/DOCS/xml/en Modified Files: ports.xml Log Message: Mac OS update Index: ports.xml =================================================================== RCS file: /cvsroot/mplayer/main/DOCS/xml/en/ports.xml,v retrieving revision 1.73 retrieving revision 1.74 diff -u -r1.73 -r1.74 --- ports.xml 25 Dec 2005 17:34:10 -0000 1.73 +++ ports.xml 30 Dec 2005 21:40:39 -0000 1.74 @@ -568,15 +568,13 @@ <sect1 id="macos"> <title>Mac OS</title> <para> -<application>MPlayer</application> should compile out-of-the-box on -Mac OS X 10.2 and up. The preferred compiler is the Apple version of +<application>MPlayer</application> does not work on Mac OS versions before +10, but should compile out-of-the-box on Mac OS X 10.2 and up. +The preferred compiler is the Apple version of GCC 3.x or later. If you have Mac OS X 10.3.9 or later and QuickTime 7 you can use the macosx video output driver. </para> -<sect2 id="mplayerosx"> -<title>MPlayer OS X</title> - <para> You can get a native GUI for <application>MPlayer</application> together with precompiled <application>MPlayer</application> binaries for Mac OS X from the @@ -675,7 +673,6 @@ the old project for <application>Xcode</application> 1.x does not work anymore. </para> -</sect2> </sect1> <sect1 id="amiga">

1 0