X264, problem with the second pass

[claudiobar]

Hi!
I'm having problems to encode in 2pass mode. Until R386 everything was going OK, but starting with R340, when the first pass is done, the codec shows me the message: "2nd pass has more frames than 1st pass (27878413 vs 4144)" -> numbers are an example.

I've got no way to fix it... any ideas? Anyone else w/the same problem?

Thanks!
Claudio

[akupenguin]

:search: It's not a bug.
... and how could it be "broken" for rev>=340 but ok for rev<386?

[claudiobar]

My mistake. I should have written "until rev. 336".
I've been searching in the forum and through google, but did'nt find anything of help.

Sorry about my english

[Sirber]

No need to be sorry, if we can read, no problem! :D

[Sharktooth]

for example: http://forum.doom9.org/showthread.php?t=102053&highlight=2nd+pass+frames+1st

However check your stats file.
Also, can you please change the title of your first post to something more appropriate? (x264 is not broken anyways!)

[greggerm]

Having had the same problem and reading the above linked thread, I see that adding the nicefps() (+ it's dll) into the avs may help the situation.

With that in mind, I am using the MeGUI one click encoding option - how can I set the oneclick mode to add such a line to the script automatically? I have attempted to edit the default avs profile .xml file, but it appears that it is not used or read during the oneclick function.

Is there a way, other than hand-editing the created avs, to have the niceftp() call placed into the oneclick generated script file?

[Doom9]

you don't need nicefps anymore.. the mp4 delay issue has been fixed

[greggerm]

Back to the drawing boards I guess - I had the 2nd pass error, but of course I dropped all the files in the trash. I'll have to re-run the job to get a log to see exactly what's going on again. Thanks for the input...
-Greg

[claudiobar]

Ok, I'll change the name of the thread then (can you tell me where is the option to do it? I'm a newbie here...)

[I've already figured it out :cool:]

So, if I open the stats file with the notepad... where should I add the nicefps() line?

[BTW; I'm using xmpeg, and can't see any avs file, only the stats one]

Thanks!

[bond]

you dont need nicefps()

tell us how many frames are shown in the stats file and whether that is the same number in your input source

[claudiobar]

The second pass is the wrong one. The message that the codec gives me says "2nd pass has more frames than 1st pass (241124224 vs 145022)" in this case.

[bond]

yes, still:

tell us how many frames are shown in the stats file and whether that is the same number in your input source

[claudiobar]

The number of frames in the stats file are: 145022. This is the same number shown in the input source.
The number of frames that the codec "sees" in the second pass is wrong, so much overestimated.

[claudiobar]

Any of you knows if the latest revision fixes this issue?

[bond]

what you are reporting is very strange

can you post the exact commandline you are using for both passes?

[claudiobar]

I'm using xmpeg (I'm some new to this, or perhaps too lazy...)
And the settings are almost the default ones, but anyways I've been messing around with them, with no change.

[bond]

I'm using xmpeg (I'm some new to this, or perhaps too lazy...)
And the settings are almost the default ones, but anyways I've been messing around with them, with no change.is xmpeg using the vfw version of x264 (outputting to .avi) or the commandline version (outputting to .mp4 or .mkv)?

i never tried xmpeg so i dont know if it borks things, you might want to tell the xmpeg devs about this

[claudiobar]

Outputs to avi.

Well, xmpeg is'nt even developing...
Anyways it works fine with xvid, divx, and previous versions of x264

[bond]

try megui