Log in

View Full Version : MeGUI - missing x264 progress reports


Doom9
26th June 2005, 01:30
Alright, version 0.2.0.1 contains some trace code that I hope will be helpful.

If you do not get any status updates in the progress window using x264.exe as encoder, but do get them when you run x264.exe on the commandline (using the --progress option), this is for you.

For starters you need to download DebugView here: http://www.sysinternals.com/Utilities/DebugView.html

Then set up everything for encoding, start DebugView and start encoding.

You should see a lot of lines flashing by in the DebugView window, looking something like this:

00000000 02:13:07 [3748] x264CLI encoder started. Entering stderr reading phase now
00000001 02:13:08 [3748]
00000002 02:13:08 [3748] Got a non empty line from x264.exe: avis [info]: 640x352 @ 25.00 fps (3598 frames)
00000003 02:13:08 [3748]
00000004 02:13:08 [3748] Got a non empty line from x264.exe: x264 [info]: using cpu capabilities MMX MMXEXT SSE SSE2 3DNow!
00000005 02:13:08 [3748]
00000006 02:13:08 [3748] Got a non empty line from x264.exe: mp4 [info]: initial delay 0 (scale 25)
00000007 02:13:08 [3748]
00000008 02:13:08 [3748] Got a non empty line from x264.exe: encoded frames: 4/3598 (0.1%), 36.70 fps

Once encoding is done, save the messages from DebugView to a file, and attach it here (don't post the contents, just attach it or upload it someplace else and post a link here).

namchik
26th June 2005, 06:08
Hi, Doom9
I tried to re-encode an xvid-source with MeGUI 0.2.0.1
Here's the log from Dbgview.exe (log1.txt)

Then I uninstalled ffdshow, tried again and got this log (log2.txt)

odyn1982
26th June 2005, 09:19
My debugview log file:
http://sr2.mytempdir.com/64060

Pasqui
26th June 2005, 10:07
@Doom9
Here is my log file

Doom9
26th June 2005, 11:01
Alright.. is that all you get from your entire encoding session? I see just 10 frames encoded in all three cases. How long is your source, and please encode till the end of it if you haven't (or let me know if you already have and the log you posted is all you got). I do smell the bacon already but I need to be sure if I should go down that road I'm currently considering.

odyn1982
26th June 2005, 11:59
I only got 10 frames encoded in the log but my script has 50 frames. With full 3213 frames I got the same log.

namchik
26th June 2005, 16:26
Doom9,
my source was about 500 frames. So encoding in 1 pass with default settings should take about 30-40 seconds... but it lasts forever and doesnt seem to stop... so I had to abort it manually.

Doom9
26th June 2005, 17:12
please try the attached 0.2.0.2 build (http://forum.doom9.org/attachment.php?attachmentid=4209). It contains more trace messages and I force the culture info to EN-US where the comma separator is a dot. That way parsing the FPS should not be a problem.

odyn1982
26th June 2005, 17:50
The problem with the progress window had disappeared and everything works now: I can see fps and the progress window closes after the job is finished. :D
Thank you Doom9 for your hard work and excellent program :thanks:

Doom9
26th June 2005, 19:22
Boy am I glad to hear that. Best news I've heard all week.. this little problem has been ruining my sleep all week.

Now hopefully it'll work out for the rest as well, and those with no x264 progress bar on the commandline can find a way to get those progress reports (and thus get them in MeGUI as well).

I've checked, Poland uses the comma as decimal separator.. x264.exe used a dot.. my locale uses a dot as well. Since I haven't really changed anything in the a release I guess it's that.. I'm only forcing a locale for the encoding thread so once that data leaves the encoder thread it is once again handled in your native locale.. I'm pretty sure that shouldn't cause any other problems.. and I guess you get your FPS indication in the GUI with a comma as decimal separator, don't you?

If it is that it also explains why it only ocurrs using x264.exe.. it's the only encoder that uses floating point progress reports.. all other programs either have none (BeSweet.. there I had to derive progress based on the length of the source), or use integers (mencoder, mp4box).

Pasqui
26th June 2005, 19:54
@Doom9
Everything is working fine now. Thanks ! :D

namchik
27th June 2005, 01:45
@Doom9
Now it's OK. Thanks.
Damn dot and comma :D