Mencoder: Less Frames with Mencoder then TMPGEnc! - Page 2

incredible · #21 05-30-2004, 08:03 PM

@ EM

And ....

If we look into mencoders manual ... we can found nice parameters like ....

- idx
- force idx

(both source index related!)

BUT! this one should be your first choice to try out as FIRST in THIS case

:

- noskip

(avoids skipping of frames! during encoding)

Encoder Master · #22 05-31-2004, 08:58 AM

I can't see any sync problems because I only lost 7-10 Frames.

But you think if I insert in my Process.bat "- noskip" I haven't this problems?

I wanna test it.

incredible · #23 05-31-2004, 12:41 PM

Quote:

Originally Posted by Encoder Master

I can't see any sync problems because I only lost 7-10 Frames.

Thats more than a quarter second

In regular if you got a "recognisable" (and thats what were talking about in here) sync offset ybout a quarter second that you will notice DIRECTLY! I think on lipps based synchronity AND for shure on sudden sound impacts like shots, explosions, Door closing ... etc.

Encoder Master · #24 05-31-2004, 12:50 PM

I re-test it and try to upload a sample.

black prince · #25 05-31-2004, 02:59 PM

@rds_correia,

rds_correia wrote:

Quote:

I wouldn't think it has anything to do with FAT32 or NTFS, BP, but you could always try that as well.
Cheers

I encoded "Transporter" a 92 minute video using MEncoder which dropped
12 frames. I watched the entire movie and there were no sync problems.
You were right about dropped frames. I wanted to see if NTFS would
speed-up the fps encoding time. If anyone has noticed a difference
please post.

Thanx

-BP

rds_correia · #26 05-31-2004, 03:45 PM

Quote:

Originally Posted by black prince

I encoded "Transporter" a 92 minute video using MEncoder which dropped
12 frames. I watched the entire movie and there were no sync problems.
You were right about dropped frames. I wanted to see if NTFS would
speed-up the fps encoding time. If anyone has noticed a difference
please post.

Hi

Wait BP.
If it's telling you that it's skipping frames it's because it's really skipping frames.
We just have to find out why.
Please post as much info as you can gather.
The Mencoder build #, the command line used, the type of source used, which movie it is, the way you learnt it was skipping frames, etc.
I mean, we gotta try and recreate such problems on other PCs and not only your's.
Twelve skipped frames is a whole lotta frames.
That's nearly half the frames contained in a second of motion picture.
I mean, you can actually feel it during the whole movie.
C ya

Koekies · #27 06-01-2004, 02:47 PM

I was browsing through some files in an mplayerhq build and found this in mplayer subdir in the config file

Code:

vo=directx
#dr=yes  
double=yes
font=c:/windows/fonts/arial.ttf
ao=win32
autosync=100
framedrop=yes
quiet=yes

is this usefull information?

incredible · #28 06-01-2004, 05:31 PM

At least that is something we should focus on!

So do test by changing the parameter to "no" in the "framedrop" line.

EDIT: To me it seems (if thinking afterwards) that this argument only will be recognised by Mplayer, but not mencoder (says the manual) !??!? Welll ... we should test.

Encoder Master · #29 06-02-2004, 11:28 AM

Oh it seems that DialHot has the solution. There are in the First GOP some bad Frames which VDub doesn't read but for example in WMP the frames will be displayed.

Dialhot · #30 06-02-2004, 11:37 AM

FYI it's not the first time I loose frames by importing MPEG1 into Vdub.

A long time ago, I used to frameserve MPEG1 into Tmpgenc via Vdub (because at this moment the directshowsource support for MPEG1 was completly broken) : ONE THIRD of ;y encoding finished unsynch !

And there was no warning nor message anywhere in vdub giving the reason

I finally dropped this solution and I used a temporary avi in huffyuv donewith tmpgenc from the mpeg1 source.

I never notice such problem with mpeg2 but why not ?