MeGUI - x264/XviD/lavc/Snow encoder with MP4/MKV/AVI output & audio

[odyn1982]

I only run x264CLIReader.exe and in megui folder I don't see any log.

[Doom9]

I only run x264CLIReader.exe and in megui folder I don't see any log.

No.. I mean when you run MeGUI again and encode an x264 job. Since we know that we can get the stderr output on your box I think even in the absence of a status update while encoding.. since you get the last one you get the contents of the log.. and I have debug code that adds every received line to the log and send it attached to each status update.. since we get the last one we get the accumulated lines that I was able to read..

[Doom9]

I've identified and fixed the audio bug. It doesn't happen if you switch between audio tracks and if a profile is selected, so this is why I never catched it.

I am VERY curious about your MeGUI logfile... can hardly wait.

[odyn1982]

I run new job with x264.exe and my log is as always (x264CLIReader.exe is in megui folder) but I had to close status window myself (no progress bar):

Next job job1 is a video job. encoder commandline:
"E:\DIVX\PROGRAMY\x264\megui\x264.exe" --bitrate 700 --no-b-adapt --subme 4 --analyse p8x8,b8x8,i4x4 --progress --no-psnr --output "E:\DIVX\PROGRAMY\x264\megui\output.mp4" "E:\DIVX\PROGRAMY\x264\megui\input.avs"
successfully set up video encoder and callbacks for job job1

Maybe I did something wrong because my english isn't as good as yours (maybe I don't understood your last post in 100%

[Doom9]

but I had to close status window myself

Oh yeah.. I won't see anything on your setup But it'll be interesting to see the result of x264clireader on machines where the status window closes itself after encoding.

[absinthe]

Well, I get squat.



-abs

[Doom9]

Well, I get squat.

I'm afraid to say then you're never gonna get a progress bar for x264 encoding unless somebody else figures something out I'm apparently unable to. As a last thing could you please run x264 in commandline mode and append ">2 output.txt" and tell me what your output.txt contains after encoding?
And what windows version are you using... non NT based versions apparently are unaware of stderr.. at least when it comes to redirecting in the commandline.. perhaps that also applies to reading from stderr as well.

@Pasqui: I hope you can run the x264clireader as well and report back, also let me know about your windows version.

[Pasqui]

Using MeGUI 0.1.9.9 on WinXP I still get no status bar.
The log window shows:
Next job job1 is a video job. encoder commandline:
"F:\Program Files\x264\x264.exe" --bitrate 700 --ref 3 --bframes 2 --weightb --analyse p8x8,b8x8,i4x4,p4x4,i8x8 --8x8dct --progress --no-psnr --output "H:\MATRIX_RELOADED_DISC_1\VIDEO_TS\video.mp4" "H:\MATRIX_RELOADED_DISC_1\VIDEO_TS\Matrix2.avs"
successfully set up video encoder and callbacks for job job1

x264.exe processes the frame (CPU at 99%) then drops down to 0% (I guess the compression is over). But Status window stays open and x264 process is still displayed in the task manager.

[absinthe]

The command line

"C:\Documents and Settings\abs\Desktop\AV Tools\MencoderGUI\codecs\x264.exe" --bitrate 700 --no-b-adapt --subme 4 --analyse p8x8,b8x8,i4x4 --progress --no-psnr --output "C:\Documents and Settings\abs\Desktop\AV Tools\MencoderGUI\codecs\output.mp4" "C:\Documents and Settings\abs\Desktop\AV Tools\MencoderGUI\codecs\input.avs" >2 output.txt

produces a file simply called "2" . But it's empty.

If I remove the "2" from the command line (i.e. > output.txt), then I do get an output.txt, and it's still empty.

I just use plain ole Win XP (SP1) with an Athlon processor.

Thanks for tryin', tho!

-abs

[Doom9]

@pasqui: what about the x264cliencoder I posted in this thread.. could you run it and let me know the results please?

@absinthe: urgh.. it should be 2> output.txt, not >2 output.txt. Sorry about that.

[absinthe]

Originally Posted by Doom9

urgh.. it should be 2> output.txt, not >2 output.txt. Sorry about that.

Well, that simply produces no file at all.

Odd.

-abs

[Pasqui]

@Doom9
Here is the result of x264CLIReader:

F:\Program Files\x264>x264clireader
21:51:54Started x264.exe and the stdout and stderr readers
21:51:54 line received: avis [info]: 640x272 @ 25.00 fps (201 frames)
21:51:54 line received: x264 [info]: using cpu capabilities MMX MMXEXT SSE 3DNow
!
21:51:54 line received: mp4 [info]: initial delay 0 (scale 25)
21:51:54 line received: encoded frames: 1/201 (0.4%), 9.09 fps
21:51:55 line received: encoded frames: 2/201 (0.9%), 9.85 fps
21:51:55 line received: encoded frames: 3/201 (1.4%), 10.10 fps
21:51:55 line received: encoded frames: 4/201 (1.9%), 10.67 fps
21:51:55 line received: encoded frames: 5/201 (2.4%), 10.66 fps
21:51:55 line received: encoded frames: 6/201 (2.9%), 11.30 fps
21:51:55 line received: encoded frames: 7/201 (3.4%), 11.48 fps
21:51:55 line received: encoded frames: 8/201 (3.9%), 11.63 fps
...

Regards,

Pasqui.

[kurt]

here's my result:


I'm using windows XP Home SP2 on my P4 2ghz...
I think this post apply for me too ...

I'm afraid to say then you're never gonna get a progress bar for x264 encoding unless somebody else figures something out I'm apparently unable to.

edit: microsoft framework .net 1.1 + Hotfix (KB886903) + German Language Pack

[Doom9]

@pasqui: thanks. So we have two categories here:
1) status updates work but have no progress bar. This is due to the system's apparent inability to redirect stderr - both in cmd.exe and from within a .NET application.

2) status updates do not work (so there's no progress bar either, and the progress window has to be closed manually). However, stderr can be redirected and read from x264clireader (http://forum.doom9.org/attachment.ph...chmentid=4182). I think the next release will fix the problem for machines falling into that category as I've changed the way the x264.exe output is read to what I'm using in x264clireader.

Now if anybody else has the problem, please perform the tests to find out in which category you fall, and if it's the first one, let me know about your .NET runtime version and Windows version. And if you do not have a progress bar using mencoder, besweet or mp4box, let me know, too.

[Pasqui]

@Doom9
Still no luck using MeGUI 0.2.0.0
I get the same behavior as before: no update of status window and x264.exe still present in task manager. When I manually close the Status window, x264 process disappear.

[odyn1982]

Bad news: I still have a problem with status window, it doesn't close and I don't see any progress but x264.exe process is finished.

[absinthe]

Originally Posted by Doom9

So we have two categories here:
1) status updates work but have no progress bar. This is due to the system's apparent inability to redirect stderr - both in cmd.exe and from within a .NET application.

2) status updates do not work (so there's no progress bar either, and the progress window has to be closed manually). However, stderr can be redirected and read from x264clireader.

But . . . for me, status updates don't seem to work, thus I have no progress bar, but I do not have to close the progress window. It always closes just fine.

At least that's how it was in 0.1.9.9. Whoa! I just downloaded 0.2.0.0 and now, for the first time, the progress window does not close. This is definitely the first time this has happened. And it must be something in the new version as I'm doing the exact same little sample job I've been doing all day.

-abs

EDIT: Something definitely borked for me in 0.2.0.0. The progress window never closes, as I mentioned. A 1-pass job will output fine, tho. However, I can't do more than 1 pass at a time as the first will never "finish." So, interestingly, I rolled back to 0.1.9.9 and it works fine again (except no progress shown in the progress window). Could this be .NET weirdness?

-abs

[Rash]

Wow! Version 0.2.0.0 !! Cool!

So, I still get the fps reported incorrectly. Here is a screenshot from the the encoding window. Interesting, though, is that MeGUI still reports the encoding time correctly. I'm sure these are not spike fps, it stays about 1500fps all the time. Anyway, not a big problem. I believe you have more important things to do.

I have also attached my log. By looking at the log it seems there are no problems.

[kurt]

Originally Posted by absinthe

The progress window never closes, as I mentioned. A 1-pass job will output fine, tho. However, I can't do more than 1 pass at a time as the first will never "finish."
-abs

same problem here - more than one job is impossible for me too...

[Doom9]

If your progress window (it's called like that, let's all use the same terminology in the future to prevent confusion.. it's even called ProgressWindow in the code) doesn't close.. does it close when you're encoding using mencoder, audio encoding or mp4 muxing? I also need to see your logs from an x264.exe session.

@Rash: does the FPS fluctuate or does it always stay the same? And what is the decimal separator in your language settings in the control panel? Could you compare the percentage from the logfile (the one before the line "sending status update") with the percentage you get in the progress window? Could it be that in the window it's 100 times the value reported in the log? I suspect that your comma separator isn't a dot, so due to your locale 20.12fps is read and converted into 2012 fps. If you can confirm my suspicion I can force the locale to EN-us for the conversion and the problem will be gone.

Please tell me any of you guys can handle a debugger.. I'm going crazy here.. it works for most people and at some point I have to stop questioning and blaming myself.. we're only dealing with a handful of people here having this issue, compared to the number of downloads it's a miniscule percentage.