[MPlayer-dev-eng] [PATCH] "turbo" mode

[Loren Merritt]

On Mon, 20 Sep 2004, Guillaume POIRIER wrote:
> Le lun 20/09/2004 à 01:11, Loren Merritt a écrit :
>
>> So do the first pass with vpass=1, all subsequent passes with vpass=3.
>> You can't just run a 3rd pass after a normal 2nd pass, because the 2nd
>> pass didn't save the required data.
>
> Even with you patch?

Yes. I didn't modify the behavior of vpass=2, which is not compatible with
3 pass encoding.

> Do we both agree that the three runs that you do have first vpass set to
> 1 and all subsequent (2nd and 3rd) set to vpass=3?

Yes.

>> vpass=1,vqscale=2,mbd=2,trell,v4mv,precmp=0,cmp=0,subcmp=2,dia=-1,last_pred=1,vmax_b_frames=1
>> vpass=3,vbitrate=1200,mbd=2,trell,v4mv,precmp=0,cmp=2,subcmp=6,preme=2,dia=-1,predia=4,last_pred=3,mv0,cbp,qprd,lmin=1,lmax=4,vqmin=1,vqmax=6,vratetol=100000,vqcomp=0.6
>> vpass=3,vbitrate=1200,mbd=2,trell,v4mv,precmp=0,cmp=2,subcmp=6,preme=2,dia=3,predia=4,last_pred=3,mv0,cbp,qprd,lmin=1,lmax=4,vqmin=1,vqmax=6,vratetol=100000,vqcomp=0.6,qns=3
>
> So why did write the above? Just so that I could see the difference
> between all 3 passes?

Just to clarify what I have been using as turbo.

> Please have a look at what the (updated) vpass section of the manpage
> reads, just to be sure it's now correct.

Patch attached.

--Loren Merritt
-------------- next part --------------
Index: mplayer.1
===================================================================
RCS file: /cvsroot/mplayer/main/DOCS/man/en/mplayer.1,v
retrieving revision 1.727
diff -u -r1.727 mplayer.1
--- mplayer.1	20 Sep 2004 18:39:48 -0000	1.727
+++ mplayer.1	20 Sep 2004 19:15:20 -0000
@@ -5358,25 +5358,31 @@
 .PD 0
 .RSs
 .IPs 1
-first pass
+first pass (also see turbo)
 .IPs 2
 second pass
-.IPs 3 (also see turbo)
-Second and third pass of three pass encoding.
+.IPs 3
+Nth pass (second and third passes of three pass encoding)
+.RE
+.RS
 Here is how it works, and how to use it:
 .br
 The first pass (vpass=1) writes the stats file.
 You might want to deactivate some CPU-hungry options, like "turbo"
 mode does.
 .br
-The second pass (vpass=3, that is not a typo ;-) ) reads the stats file and
+In two pass mode, the second pass (vpass=2) reads the stats file and
 bases ratecontrol decisions on it.
-You can use all encoding options, except very CPU-hungry options like "qns",
 .br
-The third pass (vpass=3) does both.
-It first read the stats then overwrite them (You might want to backup
-divx2pass.log before doing this if there's any possibility that you'll
-have to cancel MEncoder).
+In three pass mode, the second pass (vpass=3, that is not a typo ;-) )
+does both: It first reads the stats, then overwrites them.
+(You might want to backup divx2pass.log before doing this if there is 
+any possibility that you'll have to cancel MEncoder).
+You can use all encoding options, except very CPU-hungry options like "qns".
+.br
+The third pass (vpass=3) is the same as the second pass, except that it has 
+the second pass's stats to work from.
+You can use all encoding options, including CPU-hungy ones.
 .RE
 .PD 1
 .sp 1