January 2006 - MPlayer-DOCS - lists.mplayerhq.hu

CVS: main/DOCS/man/en mplayer.1,1.1195,1.1196
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-serv2138/DOCS/man/en Modified Files: mplayer.1 Log Message: small wording/spelling/syntax fixes Index: mplayer.1 =================================================================== RCS file: /cvsroot/mplayer/main/DOCS/man/en/mplayer.1,v retrieving revision 1.1195 retrieving revision 1.1196 diff -u -r1.1195 -r1.1196 --- mplayer.1 3 Jan 2006 13:07:54 -0000 1.1195 +++ mplayer.1 3 Jan 2006 14:23:03 -0000 1.1196 @@ -517,7 +517,7 @@ Control verbosity directly for each module. The 'all' module changes the verbosity of all the modules not explicitly specified on the command line. -See '-msglevel help' for a list of all modules. +See '\-msglevel help' for a list of all modules. .br .I NOTE: Messages printed before the command line is loaded cannot be controlled. @@ -3468,7 +3468,7 @@ .RE .RSs .IPs bitexact -Only use bit exact algorithms on all steps of the decoding (for codec testing). +Only use bit-exact algorithms in all decoding steps (for codec testing). .IPs bug=<value> Manually work around encoder bugs. .RSss

1 0

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/man/en mplayer.1,1.1194,1.1195
by syncmail＠mplayerhq.hu 03 Jan '06

03 Jan '06

CVS change done by Guillaume Poirier CVS Update of /cvsroot/mplayer/main/DOCS/man/en In directory mail:/var2/tmp/cvs-serv29706/DOCS/man/en Modified Files: mplayer.1 Log Message: add bitexact's lavd flag desc. Index: mplayer.1 =================================================================== RCS file: /cvsroot/mplayer/main/DOCS/man/en/mplayer.1,v retrieving revision 1.1194 retrieving revision 1.1195 diff -u -r1.1194 -r1.1195 --- mplayer.1 30 Dec 2005 05:15:26 -0000 1.1194 +++ mplayer.1 3 Jan 2006 13:07:54 -0000 1.1195 @@ -3467,6 +3467,8 @@ Available options are: .RE .RSs +.IPs bitexact +Only use bit exact algorithms on all steps of the decoding (for codec testing). .IPs bug=<value> Manually work around encoder bugs. .RSss

2 1

CVS: homepage/src projects.src.en,1.196,1.197
by syncmail＠mplayerhq.hu 03 Jan '06

03 Jan '06

CVS change done by Diego Biurrun CVS Update of /cvsroot/mplayer/homepage/src In directory mail:/var2/tmp/cvs-serv13461/src Modified Files: projects.src.en Log Message: Slackware build scripts link update Index: projects.src.en =================================================================== RCS file: /cvsroot/mplayer/homepage/src/projects.src.en,v retrieving revision 1.196 retrieving revision 1.197 diff -u -r1.196 -r1.197 --- projects.src.en 27 Dec 2005 14:41:54 -0000 1.196 +++ projects.src.en 3 Jan 2006 02:13:19 -0000 1.197 @@ -42,7 +42,7 @@ Gentoo ebuilds</li> <li><a href="http://plf.zarb.org/">Mandrake</a><br> urpmi packages by the Penguin Liberation Front</li> - <li><a href="http://www.faleiros.eti.br/SlackBuild/">Slackware</a><br> + <li><a href="http://faleiros.eti.br/?q=SlackBuild/mplayer">Slackware</a><br> Slackware build script by Herbert Alexander Faleiros</li> <li><a href="http://packman.links2linux.org/?action=128">SUSE</a><br> packages for several SUSE versions by Henne Vogelsang</li>

1 0

suggestions for main/docs/xml/en/encoding-guide.xml
by compn 02 Jan '06

02 Jan '06

sorry i missed the first couple threads on this, i think its a well written guide and just needs a bit more polishing. > <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 like size, quality, streamability, usability and popularity as well as... (popularity meaning that even if x264 is the greatest current codec, not everyone has the h264 decoding library installed, just like it took a while for everyone to get divx3 and then to get xvid...) > which widely depend on personal taste and technical constraints. > </para> > <itemizedlist> > <listitem><para> > <emphasis role="bold">Compression efficiency</emphasis>: > It is quite easy to understand that newer-generation codecs are made > to yield better picture quality than previous generations. how about just 'most newer-generation codecs are made to increase quality and compression' > Therefore, you cannot go wrong therefor, the authors of this guide, and many other people (doom9, others?) suggest you use an mpeg-4 avc codec like... > <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> > when 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.) imo, that blog post is horribly inefficient at telling the average user the differences between mp4 asp and mp4 avc... the user does not care about the framework of the codec. either a guide showing the difference should be linked to or this part removed. or maybe 'advanced codec developers maybe interested in reading michael ni's opinion on why mpeg4 asp codecs suck' > 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. bleeding edge? do non-native english people know this word? how about 'newest technology' ? > </para> > <para> > What is more, beginning to use a new codec requires that you spend some > time becoming familiar with its 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 is why they tend to yield the best quality quality per > encoding time ratio. > 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 does not mean you should not experiment double negative. -(which does not mean you should not experiment +(you should still try the other options which are mentioned in other sections > 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> err, where does using threads affect picture quality? this needs to be rephrased... and where did you get those statistics? 40-60% speedup using what? an smp box? if so, say so.. > > <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> hmm, this makes little sense unless you were around during those divx3 days... how about: Back when the majority of people were using divx3 and newer codecs started emerging, some people chose to stick with divx3. they might have been afraid of change. this meant that they lost out on better quality codecs and got stuck with old divx3 bugs. this is also happening today with libavcodec and xvid vs the newer codecs like x264. > <para> > Make your own judgment, and do not always listen to what some people will > tell you to do or think: The best codec is the one you master the best, doesnt this then invalidate the guide? :) how about something like: Make your own judgement, do not take advice from people who swear by one codec. take a few sample clips from raw sources and compare different encoding options/codecs to find one that suits you 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>

3 2