digitalFAQ.com Forums [Archives] - Mencoder: About mencoder speed

digitalFAQ.com Forums [Archives] (http://www.digitalfaq.com/archives/)

- Video Encoding and Conversion (http://www.digitalfaq.com/archives/encode/)

- - Mencoder: About mencoder speed (http://www.digitalfaq.com/archives/encode/9974-mencoder-mencoder-speed.html)

About mencoder speed

For all people that find the mencoder speed amazing, just look at that :

Code:

Pos:3719.3s 185968f (49%) 23fps Trem: 141min 1571mb A-V:0.000 [1741:0]

The process was started at 5:10pm localtime. It is now 7:20pm.

2h10 to process 1 hour of video, we are far from 23 fps as annouced on the screen.

So do NOT trust what it's written except "Trem" that is correct. I will need >5 hours to process the first pass of this movie (2h10 length). That is fast compared to any other encoders on my PC but not as much as mencoder try to make you think about.

EDIT : wait a minute !
185968 / 3719.3 = 50 :!:

I'm doing a 25 FPS source (clearly identified as 25fps in the first lines of the mencoder output), and I encode into 25 FPS.

:arrow: What is happenign there :?:

Phil,
Are you doing D2V :arrow: AVS :arrow: makeAVIS :arrow: MEncoder :?:
Or you are working with AVI :arrow: MEncoder :?:
Or maybe VOB :arrow: MEncoder :?:
Please post your command line so that I can try to recreate that.
I just hope you're working on a regular progressive PAL source otherwise I won't be able to assist you.
But since you're in PAL land maybe we're both in luck.
Cheers

PS-Mind you Phil, that MEncoder tells you how many FPS it is currently doing and not the average.
That is, you could be on an average 12FPS encoding but you could be, at a given point (due to almost no motion) be doing 23FPS.

Quote:

Originally Posted by rds_correia

Phil,Are you doing D2V :arrow: AVS :arrow: makeAVIS :arrow: MEncoder :?:

Okay, so let's resume : I'm currently doing a vob directly.

What is strange is that I encoded this same movie last week at a "normal" displayed speed of 13 fps. But I reinstalled all my PC yesterday and I'm currently doing my first encoding since that.
I was first very surprise to encode at this speed until I noticed that it was completly wrong. But I really don't know where is the problem...

:arrow: the only thing I changed is the post processing that I didn't use in my last week attempts.

Quote:

Please post your command line so that I can try to recreate that.
I just hope you're working on a regular progressive PAL source otherwise I won't be able to assist you.

The DVD is progressive, yes.

Code:

D:\Mes KVCD>"mencoder.exe" -of rawvideo -sws 9 -nosound -vf yuvcsp,pp=hb:100:100

/vb,crop=688:544:-1:-1,hqdn3d=1:1:2,expand=704:576 -ovc lavc -lavcopts vcodec=mp

eg2video:vrc_eq=tex:vmax_b_frames=2:preme=2:precmp=2:vstrict=-1:scplx_mask=0.3:v

qblur=0:mbqmin=1:vqmin=1:lmin=0.3:vpass=1:vrc_buf_size=1835:vbitrate=1740:vrc_ma

xrate=4500:aspect=1.7777:autoaspect=1:keyint=15:intra_matrix=8,9,12,22,26,27,29,

34,9,10,14,26,27,29,34,37,12,14,18,27,29,34,37,38,22,26,27,31,36,37,38,40,26,27,

29,36,39,38,40,48,27,29,34,37,38,40,48,58,29,34,37,38,40,48,58,69,34,37,38,40,48

,58,69,79:inter_matrix=16,18,20,22,24,26,28,30,18,20,22,24,26,28,30,32,20,22,24,

26,28,30,32,34,22,24,26,30,32,32,34,36,24,26,28,32,34,34,36,38,26,28,30,32,34,36

,38,40,28,30,32,34,36,38,42,42,30,32,34,36,38,40,42,44 -ofps 25.000 "E:\WE_WERE_

SOLDIERS\VIDEO_TS\VTS_01_1.VOB" -o "D:\Mes KVCD\We were soldiers.m2v"

Quote:

PS-Mind you Phil, that MEncoder tells you how many FPS it is currently doing and not the average.

I think about that but the number did'nt change a lot during these two hours. So whatever it is displayed (current or average) it is wrong.
Since the beguinign the Trem was correct : 270 min announced at first for a 2h10 movie.

Quote:

That is, you could be on an average 12FPS encoding but you could be, at a given point (due to almost no motion) be doing 23FPS.

That is also the purpose of that thread : I'm bored to see people telling how much fps they obtain with this encoder. If they just trust what is displayed, my current case proves that this is just bullcrap. I hope they are smarter than that.

Well in my case the fps is correct :P
2:03;22 movie pal 25 fps
thats 123:33 minutes
thats 7413 seconds
and 7413*25=185325 frames
Im encoding at 16 fps so that means it would take about 193:05 minutes per pass and thats correct. for the first pass I stil am in my second one but I don't think it's gonna be different.

Hi Phil,

well ... I always do see things how they "come out" and not how they are signed. In Fact almost every time the displayed FPS Speed encoding factor matches the time which is needed ... but it makes me not surprising that also "mencoder" can give confused "console text" outputs.

I also watched in here the "mencoder" drops frames thread and I only can say all my mencoder encodings are in sync with audio and all plays back ok.
Thats why many people do get confusing about "theoretics" but we always should see thinks in their "real" output ... and what comes out on the device where we see our final work is what counts.

I ONLY had crazy framedrops which mad audio out of sync in case of a telecined source (like NTSC Captures) encoded with mencoder ... but thats not the subject in here.

I often heared that after a "system reinstall" things getting weired ... like in the case when Rui had no probs using ffdshow Makeavis BEFORE he had to reinstall his system... after that we had a big "figuring out" time on skype phone.

Whats that build youre using of mencoder?

Do go to the official mplayer team compiled CVS build from may 18th
http://www.mplayerhq.hu/MPlayer/releases/win32-beta/

And see if there things getting solved.

To me it seems that "sasha" from mplayer team does configure the compiling a bit different ... maybe were doing something wrong when compiling .. I dont think so but .... lets do a comparison.

Quote: