Log in

View Full Version : MeGUI reports incorrect FPS compared to the logs

graysky
27th August 2007, 21:44
I tested this with MeGUI v0.2.6.1001 and the old stable 1043 version. The FPS values in the GUI don't agree with the FPS values in the log files... can anyone else confirm?

http://img251.imageshack.us/img251/5681/errordd2.gif

The pic shows the GUI values for FPS compared to the ones from the log files... I color-coded the 3 runs here.
Kurtnoise
27th August 2007, 22:46
Just a guess : the fps values from the GUI are calculated with the StartTime / EndTime whereas the others are the values computed by the encoder. Not really a bug. Just two different ways to have these values. Furthermore, note that you can have some rounding...
graysky
27th August 2007, 22:52
Could be... I'd guess the encoder's method of calculation is more accurate... wonder if the GUI can read it directly from the output and simply redirect it to the field...
Kurtnoise
27th August 2007, 23:05
wonder if the GUI can read it directly from the output and simply redirect it to the field...
it could...but that will depend mainly on the encoders not the GUI itself. Not sure that all encoders available in meGUI compute this value.
Sharktooth
28th August 2007, 00:06
i think it's fine as it is since every encoder has a different output.
to read the FPS from the encoder output we should write a different stdout/stderr parser for every encoder (assuming it exposes the FPS value) and that's quite a waste of time.
graysky
29th August 2007, 20:31
@sharktooth - I agree with your point about supporting many different encoders, but I don't think accurately reporting them is a waste. If the internal fps calculator is off, why report anything?
Sharktooth
29th August 2007, 20:39
the internal calculator works perfectly. the difference is in the fact megui measures the time in a different way (including the time required to launch and close the encoder... etc).
graysky
29th August 2007, 21:21
ok... that makes sense. I didn't realize the clock didn't stop when doing non-encoding related events.
ACrowley
1st September 2007, 14:09
the internal calculator works perfectly. the difference is in the fact megui measures the time in a different way (including the time required to launch and close the encoder... etc).


Yes, fps calculater works perfect.

But generally the Timecalculation in newer builds not.
The Elapsed Time still goes to zero after 24h.

And Remaining Time still "jumps around".

Via x264.exe in cmd.exe, the Remaining Time is stable and mostly a fixed Time.

It all works with older megui Builds so far i can remeber.
Sharktooth
1st September 2007, 14:17
yes, it's a known bug.