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

[odyn1982]

I don't understand this command "> output.txt".
I use Net 1.1 and mencoder works with megui.

[berrinam]

I don't understand this command "> output.txt".
If you are using MeGUI v.0.1.9.7 then go to
video codec config -> more -> custom commandline options
and add "> output.txt"

This will pipe all output from x264.exe to output.txt, and you can check this file to see what problems may have arisen.

[odyn1982]

It's strange, when I want add new custom options it doesn't work. I have one idea why: long time ago I've installed net 2.0 and then I returned to 1.1. I think that I should format my winxp but I don't have time :D

[JoeBG]

OK Doom9, proof the problem is here. VDubMod doesn't open my avs either.

VDubMod message

So far:
Programs that won't open: MeGUI, VDubMod
Programs that open: NeroRecode, all players, x264 cli encoder (i did some tests manually inputing on x264 and it worked)

So, if someone could help me, where do I get a YV12 decoder? :( Thanks a lot.

Just install Xvid and everything will work.

[berrinam]

It's strange, when I want add new custom options it doesn't work.

Yes, it's a bug in MeGUI. Anyway, to get it to work, you need to enter the custom options, then go to the Main tab and press ok.

[JoeBG]

A new version is out.

A word of warning: due to the format of xvid zones (they have no end frame but end just before the start of the next zone (and if there's none at the end of the video), so do not use the intro credits feature with xvid just yet (if you do, you'll end up encoding the entire video at the credits quantizer because the zone will extend from the first frame till the last (or till the end credits start, but since the end credits extend till the end and use the same quantizer it comes down to the same)).

Once the zone feature has been thoroughly tested I will add it to the remaining codecs and in the process take care of the special zone format used in XviD.

@ doom9

One question to Xvid and lavc zones: In the moment, only the second pass in both codecs are getting zones in the commandline. There are no zones in first pass. How is it possible for the encoder to reach the final size? To my opinion, there have to be zones in the first pass too :confused:

[odyn1982]

I always do like you said and nothing works :confused:
but I can use jeryll's x264CLI GUI or .bat files without problems :D

[kurt]

I made some more tests about the encoding speed and MeGUI seems to be slower than encoding via commandline on my machine:

avs-skript with 161frames: # PLUGINS
LoadPlugin("C:\PROGRA~1\GORDIA~1\DGMPGDec\DGDecode.dll")
#LoadPlugin("C:\PROGRA~1\GORDIA~1\AviSynthPlugins\decomb.dll")
#LoadPlugin("C:\PROGRA~1\GORDIA~1\AviSynthPlugins\KernelDeInt.dll")
LoadPlugin("C:\PROGRA~1\GORDIA~1\AviSynthPlugins\UnDot.dll")
# SOURCE
mpeg2source("C:\Movies [C]\test\test.d2v")
# TRIM
trim(68490,68651)
# CROPPING
crop(8,72,704,432)
# DENOISING: choose one combination (or none)
Undot()
- MeGUI with mencoder (mplayer2005.06.09.P4.): 121seconds --->1,33fps
- only mencoder (mplayer2005.06.09.P4.): 28seconds ---> 5,75fps
commandline: "C:\Rippen\mencoder\mencoder.exe" "C:\Movies [C]\test\yyyy.avs" -ovc x264 -x264encopts bitrate=1500:bframes=3:b_adapt:b_pyramid:weight_b:4x4mv:i4x4:i8x8 -o "C:\Movies [C]\test\test1.264" -of rawvideo
---> Progress display works fine in both
_____________

- MeGUI with x264.exe: 118seconds ---> 1,36fps
- only x264.exe: 29s ---> 5,55fps
commandline: "C:\Rippen\x264\x264.exe" --bitrate 1500 --bframes 3 --b-pyramid --weightb --analyse p8x8,b8x8,i4x4,p4x4,i8x8 --progress --no-psnr --output "C:\Movies [C]\test\teat1.mp4" "C:\Movies [C]\test\yyyy.avs"
--> but it's strange... sometimes (2of6 attempts) MeGUI needs ~1minute...here (http://img159.echo.cx/my.php?image=28uz.jpg) is the cpu-management.
--> no progress display neither in MeGUI nor in commandline...
I would post the output.txt but i can't it handle too...

Edit:
same avs encoded with x246cligui 0.1.5b needs 34seconds --> 4,73fps
--bitrate 1500 --bframe 3 --weightb --b-pyramid --8x8dct --analyse i4x4,p4x4,p8x8,b8x8,i8x8, --qpmin 10 --qpmax 51 --progress -o "C:\Dokumente und Einstellungen\evil.bert\Desktop\testx264cligui1.mp4" "C:\Movies [C]\test\yyyy.avs"

[Doom9]

One question to Xvid and lavc zones:And there I thought people were only using MeGUI for x264. I'm not getting much feedback on the whole zone thing actually, but it was a whole lot of work and quite nifty if you start using it.. I really want it to be properly tested before propagating it through everything else. Are you refering to auto-mode or video-only mode? The reason I'm asking is that job generation is completely independent in the two modes (well, almost.. I try to put everything used at least twice into separate methods but there's a lot of additional logic in auto mode).

I don't understand this command " > output.txt".Add this to the commandline you're running in dos. It means you won't see anything anymore, but everything is written to output.txt in the current directory.

[scorpdt]

Hi Doom9 .... thanks for the wonderful application .... a nice revamp btw.

The audio borked again in 0.1.9.7 and I include the error message below.

aDesired size of this automated encoding series: 10240000 bytes
Next job job1-1 is an audio job. besweet commandline:
"D:\A264\BeSweet.exe" -core( -input "D:\DEVDASSUB_SCN\BlackAVS\1 MPA T01 DELAY -32ms.mpa" -output "D:\DEVDASSUB_SCN\BlackAVS\123.mp4" -logfile "besweet.log" ) -bsn( -2ch -vbr_streaming -codecquality_high -aacprofile_he ) -ota( -d -32 -g max )
successfully set up audio encoder and callbacks for job job1-1
Exception when trying to update status while a job is running. Text: '2222' is not a valid value for 'value'. 'value' should be between 'minimum' and 'maximum'. stacktrace: at System.Windows.Forms.Control.MarshaledInvoke(Control caller, Delegate method, Object[] args, Boolean synchronous)
at System.Windows.Forms.Control.Invoke(Delegate method, Object[] args)
at MeGUI.MeGUI.UpdateGUIStatus(StatusUpdate su)

I have the sample of the audio file which you can access http://scorpio1.homeip.net:6970/images/audio.rar

Running the besweet (v1.5b30) from command line works fine with no error.
The video encoding only (i.e. without Audio) is working ok .... no problem encountered so far.

Cheers!
Scorpio

[JoeBG]

And there I thought people were only using MeGUI for x264. I'm not getting much feedback on the whole zone thing actually, but it was a whole lot of work and quite nifty if you start using it.. I really want it to be properly tested before propagating it through everything else. Are you refering to auto-mode or video-only mode? The reason I'm asking is that job generation is completely independent in the two modes (well, almost.. I try to put everything used at least twice into separate methods but there's a lot of additional logic in auto mode).


It´s video only and I loaded my usual test Avisynthskript for a testclip.
Zones in x264 are ok, but I´m wondering why there are only zones in the second pass in xvid and lavc. I´m just wondering if this could be correct?

By the way: It makes no sense for me to use x264 when I have a target bitrate (1/3 DVD) of 1800 :) for a 90 minute Film :D

[Doom9]

but I´m wondering why there are only zones in the second pass in xvid and lavc. I´m just wondering if this could be correct?That's a bug allright.

Phew, I really have my plate full today, haven't I? I'm really glad berrinam is around and has already solved many of the issues reported.

[Pasqui]

@Doom9
I have the same problem as odyn1982: the progress window is not updated whereas the x264.exe process is displayed in the task manager.
using the following command:
H:\>"F:\Program Files\x264\x264.exe" --pass 1 --bitrate 611 --stats "2pass.log"
--bframes 2 --subme 2 --weightb --analyse i4x4,p4x4,i8x8 --progress --no-psnr --
output NUL "H:\MATRIX_RELOADED_DISC_1\VIDEO_TS\Matrix2.avs" >output.txt

I get an empty output.txt !
But in the command window, I get the following info:

avis [info]: 640x272 @ 25.00 fps (198950 frames)
x264 [info]: using cpu capabilities MMX MMXEXT SSE 3DNow!
encoded frames: 597/198950 (0.3%), 20.72 fps

Regards,

Pasqui.

[Doom9]

@pasqui: thank you.. so x264.exe acts as I expect it to. There are a few bugs in the x264 commandline generation that will cause the progress bar to fail. I hope to catch them all in the version I'm about to release.

[LigH]

Instead of ">" (stout redirection), try "2>" (sterr redirection) - I did not check it, but it may be worth a try.

[Doom9]

@JoeBG: Please explain how you are encoding when you only get zones in the second pass. Below you'll find my log output for an automated 2 pass encoding session using the lavc codec:

Next job job9-1 is a video job. encoder commandline:
"mencoder.exe" "D:\DVDs\DVDVolume\VIDEO_TS\re-trailer.avs" -ovc lavc -o NUL: -passlogfile "2pass.log" -lavcopts vpass=1:vbitrate=800:turbo:vmax_b_frames=2:vqdiff=2:vrc_override=1,182,20/3214,3598,20
successfully set up video encoder and callbacks for job job9-1
----------------------------------------------------------------------------------------------------------

Log for job job9-1


----------------------------------------------------------------------------------------------------------
job job9-1 has been processed. This job is linked to the next job: job9-2
Next job job9-2 is a video job. encoder commandline:
"mencoder.exe" "D:\DVDs\DVDVolume\VIDEO_TS\re-trailer.avs" -ovc lavc -passlogfile "2pass.log" -lavcopts vpass=2:vbitrate=800:vmax_b_frames=2:vqdiff=2:vrc_override=1,182,20/3214,3598,20 -o "D:\DVDs\DVDVolume\VIDEO_TS\test.avi" -of avi -ffourcc MP4V
successfully set up video encoder and callbacks for job job9-2


As you can see, the zones are in both passes. I did this by loading an AviSynth script, set intro and credits in the preview window that popped up, selected the lavc codec, set output type to avi, pressed config to configure codec, set encoding mode to automated 2 pass, enabled turbo, pressed OK, pressed Queue, started encoding.
I just debugged xvid job creation (exactly same scenario) with the same results (obviously without intro). However, I found a bug in the commandline generation (you didn't post yours.. it's essential information to me)

@kurt: something is seriously wrong with your PC. MeGUI should never use 50% cpu time.. it uses hardly any CPU time on my box.

Instead of ">" (stout redirection), try "2>" (sterr redirection) - I did not check it, but it may be worth a try.Good thinking.. that'll tell me what comes out in stderr (which is what I'm reading in order to write the status updates)

[Pasqui]

@LigH & Doom9
using this command line
"F:\Program Files\x264\x264.exe" --pass 1 --bitrate 611 --stats "2pass.log" --bframes 2 --subme 2 --weightb --analyse i4x4,p4x4,i8x8 --progress --no-psnr --output NUL "H:\MATRIX_RELOADED_DISC_1\VIDEO_TS\Matrix2.avs" é> output.txt

I get nothing in the command window and the following is redirected to output.txt:
avis [info]: 640x272 @ 25.00 fps (198950 frames)
x264 [info]: using cpu capabilities MMX MMXEXT SSE 3DNow!
encoded frames: 199/198950 (0.1%), 21.12 fps
encoded frames: 398/198950 (0.2%), 20.71 fps

[Doom9]

to those that do not have a progress bar: does the status window disappear once encoding is done? if so I can put debug code into the log and you can post it here after encoding. doing that would require virtually no additional effort and hopefully help me trace the problems (if they're not caused by incorrect commandlines.. I found at least 3 bugs that cause this problem already)

[Doom9]

@scorpdt: does audio encoding work if you're not using auto-mode? obviously it's easier for me to just test that. Actually, never mind I tested it.. but it would've been useful to know just in case so I start looking at the right place. The less time I spend trying to reproduce the problem, the more I can spend to quickly resolve outstanding issues and add additional features ;)

[kurt]

to those that do not have a progress bar: does the status window disappear once encoding is done?
jep, it disappear when the job is finished ...

about my machine: will try to change the priority of MeGUI in windows and see if it helps...

[Doom9]

@scorpdt: actually, you're report isn't quite correct ;) Audio encoding does in fact work. But using your source, BeSweet doesn't act like it normally does. Besweet writes progress reports to the commandline.

Normally such output looks like this:

[00:00:00:000] Initializing...
[00:00:00:000] -- Initializing...

[00:00:00:032] | Maximum Gain Found : 128.7dB
[00:00:00:064] | Maximum Gain Found : 122.1dB
....
transcoding ...
[00:00:00:640] transcoding ...
[00:00:00:672] transcoding

In order to compute the percentage, I use the last "Gain found" line as the audio length, then compare the value in a transcoding line with that value. Now here's a snippet of how audio encoding looks using your source file:


[00:00:00:000] Initializing...
[00:00:00:000] -- Initializing...

[00:00:00:072] | Maximum Gain Found : 0.0dB
[00:00:00:072] |

[00:00:00:040] Asserting negative delay..

[00:00:00:064] transcoding ...
[00:00:00:088] transcoding ...

As you can see, there is no gain finding for reasons beyond me. I tried without the delay but that seems to have no influence. I've also used the exact same settings for both files. And since we don't have an audio format mismatch (encoding a 2.0 source to 5.1 will give weird timestamps).. it's BeSweet's doing. I basically have to capitulate here.. only DSPGuru can tell why BeSweet reacts like that. But, in order to still allow you to encode, I have added a sanity check to my percentage finding algorithm.. if it gets a value that is too large (like in your case), I'll simply set it back to the maximum allowed value.. 100%. It'll look like it is done right away, but I'm afraid there's really not much more I can do.

[Doom9]

@everyone with the no progress problem: in the build I'm about to release I have added some code that will add every line I'm reading from x264.exe's stderr to the log. This means huge logs and I'm sorry for that. If you don't have the problem and everything else works fine, just flush the logs.. if you have the problem, pick the simplest scenario where it happens (direct mp4 output, no auto mode, default x264 settings (that means you do not load your default profile!!) and attach the log to a post here).

@kurt: I just checked the task manager when I'm encoding.. MeGUI uses 0% CPU, rarely 1 or 2%... basically x264.exe eats up all the cpu time which is how it should be. And that's with x264.exe running at low priority (MeGUI runs at normal priority by default).

[Maximus_G]

@Maximus_G: your description sounds like you're not doing things right. I don't know what you're doing.. you're refering to some ominous button that I do not know for starters, and the process of auto encoding works like that on my box: configure video, configure audio, press auto-encode...
OK, odyn1982 has posted the pictures - the same for me.

Are you going to fix the missing "--8x8dct" parameter?

[Rash]

@Rash

didn't you notice the other MeGUI topic where I mentioned how to change the decoder, there are various other topics about this as well

http://forum.doom9.org/showthread.php?t=88452&page=1&pp=20&highlight=avsedit
Thanks a lot Stax!

Alright! I'm sorry! I promise next time I will look for before asking in the topic. I just thought it was somehow related to my problem! :)

Now it worked! ;) No problem at all. I even saw the progress bar (though I think MeGUI was reporting the encoding fps incorrectly, it was saying about 1400fps! oh, I wish! :D). Thank you all very much for the support!

[scorpdt]

Doom9, thanks for looking into the problem reported on the audio. Sorry for insufficient information provided on my part (actually I did test out audio only encode but somehow miss that out in my report) :)

I'll try out other audio files. Thanks.

Scorpio

[Doom9]

So, does anybody have any feedback on the progress bar using x264.exe? Does it still not work for you. If it doesn't, please attach the contents of the log here.

though I think MeGUI was reporting the encoding fps incorrectly, it was saying about 1400fps! oh, I wish!Have you used 0.1.9.8 for that? if so please attach the log. If not, please try again with 0.1.9.8 (or the 0.1.9.9 I'm about to post) and then attach the log if the problem still happens.

[Doom9]

alright.. the new release is out. Now more fiddling with the custom commandline, now you have matrices built-in even though the editor isn't quite ready yet. Enjoy.

The debug code for the missing x264.exe progress bar is still in there. Please post your logs if you are still not getting a progress bar when using x264.exe.

[kurt]

new version isn't downloadable yet :)

[Doom9]

Now it is. You're one of the people who had problems with the status bar, haven't you? How did 0.1.9.8 work out for you?

[kurt]

yes, but with 0.1.9.8 the progress bar problem was still there...see at the attachement (logfile is a bit short, isn't it?!) ..

I'll try 0.1.9.9 later that day...

[Doom9]

logfile is a bit short, isn't it?!way too short. The progress window disappears though once encoding is finished, does it not? Could you try the 2> output.txt trick ligh mentioned and post the result of the operation as well? Your logfile tells me (assuming the progress window goes away once encoding is done) that MeGUI cannot read anything from the stderr of x264.exe.

@Pasqui, absinthe, odyn1982: How does this look for you... stdout versus the contents of the log in version 0.1.9.8 or above?

[LigH]

You can even combine both:

x264 -options... > output.txt 2> errors.txt

[kurt]

ok, i will try this out in the evening (when i'm back from university)...

[kurt]

problem with no progress bar (and disappearing status window after encoding) still extists in MeGUI 0.1.9.9 on my machine:

with MeGUI i tried > output.txt 2> errors.txt but no files were written...
when using x264 via commandline 2 empty files were written...
----> logfile is like the one above (still short, with commands: > output.txt 2> errors.txt)
"C:\MeGUI\x264.exe" --bitrate 700 --no-b-adapt --subme 4 --analyse p8x8,b8x8,i4x4 --progress --no-psnr --output "C:\Movies [C]\test\test.mp4" "C:\Movies [C]\test\yyyy.avs" > output.txt 2> errors.txt

with MeGUI and latest mencoder (21/06/2005) no files were written too (log is short )...
when using mencoder via commandline the attached files were written...
"C:\Rippen\mencoder\mencoder.exe" "C:\Movies [C]\test\yyyy.avs" -ovc x264 -x264encopts bitrate=700:subq=4:i4x4 -o "C:\Movies [C]\test\test.264" -of rawvideo > output.txt 2> errors.txt

[P.S: still problems with priorities of the new MeGUI (only 50% cpu), i will check my machine...]

Edit: pasted commandline

[odyn1982]

I tested versions 0.1.9.8-9 and problem with progress bar still exists, my status window doesn't close (but x264.exe finished job). No files were written with command "> output.txt"
My log:
Next job job1 is a video job. encoder commandline:
"E:\DIVX\PROGRAMY\x264\x264CLI\x264.exe" --bitrate 700 --no-b-adapt --subme 4 --analyse p8x8,i4x4 --progress --no-psnr --output "E:\test.mp4" "E:\TEST5.avs" > output.txt
successfully set up video encoder and callbacks for job job1
One question: i don't use bframes so why there is " --no-b-adapt "

[ckjnigel]

I'm a tyro at this and am chuffed that I can even use standard Gordian Knot. A complication for me is that I run GK under WinX64 but have to use MeGUI on the Win32 partition because that's where NET 1.1 is. Is there some way to use the movie.avs and sdtrk.ac3 files that GK produces for an XviD encode as inputs for MeGui? The .avs was recognized okay, but I couldn't figure out how to reencode and mux the AC3 into an Mp4
BTW, the Yu-Gi_Oh x264 I made with GK looks vastly better with Videolan player than via players using the latest ffdshow. Heck, with VLC the 500 mb file is scarcely distinguishable from DVD.

[absinthe]

Still no status progress with 1.9.9, but the encoding box does close and I believe it always did.

Using default settings (ABR/700 kbps),
"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 "D:\withintest.mp4" "D:\within_test.avs"produces the attached logfile.

I hope this hasn't been covered elsewhere, but does x264 have limitations on input colorspace? Sometimes my jobs last about 1 second and I get no output, or rather an empty file. Sometimes that only happens on the second pass. That was history, but the problem seemed solved when I started using the x264 CLI. It just now happened again though. I realized I'd had no problems with d2v files made from direct DVD rips, and realizing that the file I was just using was HuffyUV, I converted to YV12 via AviSynth and the problem went away.

Also, it seems in the last couple of versions that you can't output raw from MeGUI. Choosing RAW as output, the output field seems to default to a "*.mp4" file, which is the output I get.

-abs

[Doom9]

when using x264 via commandline 2 empty files were written...But that seems to indicate a generic incapability of your PC to have stdout or stderr redirected when using x264.exe. And there's really nothing I can do.. if you don't even get stdout redirected on the commandline, I'm not susprised that MeGUI can't do it either.. it tries as you do with the 2> errors.txt but since you don't get anything in that file, MeGUI won't get anything from its streamreader either.

The only thing I can still try is the paralell 3 thread stdout/stderr reading that I use for mp4box now.. when time permits (week-end probably) I'll make a separate dumb program that launches x264.exe and writes out any messages received from x264's stdout and stderr to the commandline. But I would not at all be surprised if that didn't work on your machine either. And that means I'd be at the end of my rope and your computer is just not compatible with my software, period.

Still no status progress with 1.9.9, but the encoding box does close and I believe it always did. Please post the megui logfile for that encoding session (you posted the stats file ;)) MeGUI logfiles are in the MeGUI directory and named like this: logfile-date-time.log.

[Doom9]

I tested versions 0.1.9.8-9 and problem with progress bar still exists, my status window doesn't close (but x264.exe finished job).So that is another problem then.. it means you get no status updates sent to the GUI.. so naturally there won't be any progress bar. I take it you never have a progess bar in audio encoding, muxing, and video encoding using another encoder (or codec) either, do you?

Can you try appending >2 errors.txt to your commandline and tell me what the file contains after encoding (try launching x264.exe from the commandline just in case).

but I couldn't figure out how to reencode and mux the AC3 into an Mp4How about loading it as audio input, press configure the configure the output, select an output name, press queue (and start if you disabled auto queue start)? That'll get you an mp4 ;) Or, configure audio, do not press queue, configure video, press auto-encode, select a desired filesize, and start encoding? If there's something that doesn't work, then let me know in the greatest possible amount of detail (spare me nothing.. I rather be flooded with data than having to ask back).

[Doom9]

One question: i don't use bframes so why there is " --no-b-adapt "Probably because b-adapt is the default and I didn't make this option conditional on b-frames being present.. the GUI is aware of that, the commandline generator isn't. Of course I can change that for future versions.

[Doom9]

problem with no progress bar (and disappearing status window after encoding)Does that mean "it disappears" or "it stays even when x264.exe has done its job"? stay = bad and it's another issue entirely than having a progress window that disappears after encoding, even if there are no status updates.. the disappearance tells me that there is no basic problem with sending status updates (the disappearance is triggered via the same kind of status updates as the progress updates), and thus the problem lies with reading the stderr from x264.exe.. if the progress window stays even when x264.exe is done, then there's a problem dispatching the status updates (as odyn1982 has).

[odyn1982]

No, I always have progress bar with mencoder and mp4box.

My x264cli.bat file:

@ECHO OFF
CLS

REM =======================================================
REM PLEASE EDIT THE PATHS TO THE NECESSARY APPLICATIONS
REM =======================================================
SET pathToX264CLI="E:\DIVX\PROGRAMY\x264\x264CLI\x264.exe"
SET pathToInput="E:\TEST5.avs"
SET pathToOutput="E:\TEST.mp4"
SET pathToStats="E:\TEST.log"
REM =======================================================
REM =======================================================
ECHO.
ECHO ============================================
ECHO CALLING x264 USING THE FOLLOWING COMMAND:
ECHO ============================================
ECHO x264.exe [--bframe 3 --b-pyramid --ref 5 --filter -2:-2 --qcomp 0.75 --ipratio 1.10 --pbratio 1.40 --analyse "all" --8x8dct --weightb --me "umh" --merange 16 --subme 5 --no-psnr]

%pathToX264CLI% --pass 1 --bitrate 900 --bframe 3 --b-pyramid --ref 3 --filter -2:-2 --direct temporal --stats %pathToStats% --qcomp 0.75 --ipratio 1.10 --pbratio 1.40 --analyse "none" --8x8dct --weightb --me "dia" --merange 16 --subme 3 --progress -o NUL %pathToInput% 2> output.txt
ECHO


Output.txt:

avis [info]: 576x240 @ 25.00 fps (51 frames)
x264 [info]: using cpu capabilities MMX MMXEXT SSE 3DNow!
encoded frames: 1/51 (1.9%), 7.14 fps
encoded frames: 2/51 (3.9%), 12.82 fps
encoded frames: 3/51 (5.8%), 17.54 fps
encoded frames: 4/51 (7.8%), 17.09 fps
encoded frames: 5/51 (9.8%), 16.03 fps
encoded frames: 6/51 (11.7%), 16.71 fps
encoded frames: 7/51 (13.7%), 16.63 fps
encoded frames: 8/51 (15.6%), 16.53 fps
encoded frames: 9/51 (17.6%), 16.48 fps
encoded frames: 10/51 (19.6%), 17.30 fps
encoded frames: 11/51 (21.5%), 17.19 fps
encoded frames: 12/51 (23.5%), 17.47 fps
encoded frames: 13/51 (25.4%), 17.33 fps
encoded frames: 14/51 (27.4%), 17.59 fps
encoded frames: 15/51 (29.4%), 17.46 fps
encoded frames: 16/51 (31.3%), 17.66 fps
encoded frames: 17/51 (33.3%), 17.56 fps
encoded frames: 18/51 (35.2%), 17.73 fps
encoded frames: 19/51 (37.2%), 17.38 fps
encoded frames: 20/51 (39.2%), 17.54 fps
encoded frames: 21/51 (41.1%), 17.46 fps
encoded frames: 22/51 (43.1%), 17.60 fps
encoded frames: 23/51 (45.0%), 17.53 fps
encoded frames: 24/51 (47.0%), 17.66 fps
encoded frames: 25/51 (49.0%), 17.99 fps
encoded frames: 26/51 (50.9%), 17.89 fps
encoded frames: 27/51 (52.9%), 18.19 fps
encoded frames: 28/51 (54.9%), 18.11 fps
encoded frames: 29/51 (56.8%), 18.38 fps
encoded frames: 30/51 (58.8%), 18.29 fps
encoded frames: 31/51 (60.7%), 18.55 fps
encoded frames: 32/51 (62.7%), 18.45 fps
encoded frames: 33/51 (64.7%), 18.53 fps
encoded frames: 34/51 (66.6%), 18.60 fps
encoded frames: 35/51 (68.6%), 18.67 fps
encoded frames: 36/51 (70.5%), 18.74 fps
encoded frames: 37/51 (72.5%), 18.95 fps
encoded frames: 38/51 (74.5%), 18.86 fps
encoded frames: 39/51 (76.4%), 18.77 fps
encoded frames: 40/51 (78.4%), 18.82 fps
encoded frames: 41/51 (80.3%), 18.75 fps
encoded frames: 42/51 (82.3%), 18.80 fps
encoded frames: 43/51 (84.3%), 18.73 fps
encoded frames: 44/51 (86.2%), 18.78 fps
encoded frames: 45/51 (88.2%), 18.83 fps
encoded frames: 46/51 (90.1%), 18.75 fps
encoded frames: 47/51 (92.1%), 18.80 fps
encoded frames: 48/51 (94.1%), 18.74 fps
encoded frames: 49/51 (96.0%), 18.78 fps
encoded frames: 50/51 (98.0%), 18.72 fps
encoded frames: 51/51 (100.0%), 18.65 fps
x264 [info]: slice I:1 Avg QP:23.00 Avg size: 11538 PSNR Mean Y:42.74 U:44.62 V:45.56 Avg:43.39 Global:43.39
x264 [info]: slice P:28 Avg QP:27.68 Avg size: 5814 PSNR Mean Y:37.79 U:42.03 V:42.15 Avg:38.79 Global:38.53
x264 [info]: slice B:22 Avg QP:30.77 Avg size: 2137 PSNR Mean Y:36.33 U:41.39 V:41.58 Avg:37.46 Global:37.30
x264 [info]: slice I Avg I4x4:51.5% I8x8:38.5% I16x16:10.0%
x264 [info]: slice P Avg I4x4:0.0% I8x8:0.0% I16x16:28.3% P:53.5% P8x8:0.0% PSKIP:18.2%
x264 [info]: slice B Avg I4x4:0.0% I8x8:0.0% I16x16:7.5% P:29.8% B:11.2% B8x8:0.0% DIRECT:6.1% BSKIP:45.4%
x264 [info]: 8x8 transform intra:3.6% inter:37.3%
x264 [info]: PSNR Mean Y:37.25 U:41.80 V:41.97 Avg:38.31 Global:38.01 kb/s:867.9

encoded 51 frames, 17.94 fps, 868.58 kb/s

[Doom9]

@odyn1982: at least you get stderr messages.. so that behavior is consistent.. we just need to figure out why you don't get any statusupdates sent in x264 mode. I'll dump all the lines I get from x264 into a logfile and write it to the HD automatically instead of using the log appending mechanism which relies on the status updates.

@kurt: do you have a progress bar during audio encoding? besweet also writes the processing output to stderr and only informational messages to stdout. mencoder and mp4box use stdout and only rarely stderr.

[odyn1982]

Next problem with audio configuration. Megui always uses this settings: -azid( -s stereo -c normal -L -3db ) -bsn( -2ch -cbr 128 ) -ota( -d 0 -g max )
but I wanted 5.1ch, VBR streaming, he profile with high quality.


Log for job job2

besweet: "E:\DIVX\PROGRAMY\AUDIO\BeSweetv1.5b30\BeSweet.exe" -core( -input "E:\DIVX\FILMY\TRAILERS\HP2\HII T03 2_0ch 192Kbps DELAY 0ms.ac3" -output "E:\DIVX\FILMY\TRAILERS\HP2\Test\audio.mp4" -logfile "besweet.log" ) -azid( -s stereo -c normal -L -3db ) -bsn( -2ch -cbr 128 ) -ota( -d 0 -g max )

BeSweet v1.5b30 by DSPguru.
--------------------------

[00:00:00:000] Initializing...
[00:00:00:000] -- Initializing...

[00:02:08:512] |

SR: 48000, Table idx: 6 - start 12, stop 8
SR: 48000, Table idx: 6 - start 12, stop 8
[00:02:08:512] Finalizing...
[00:02:08:512] Conversion Completed !

Visit DSPguru's Homepage at :
http://DSPguru.doom9.net/

The progress window disappears though once encoding is finished.

[kurt]

Does that mean "it disappears" or "it stays even when x264.exe has done its job"? stay = bad and it's another issue entirely than having a progress window that disappears after encoding, even if there are no status updates.. the disappearance tells me that there is no basic problem with sending status updates (the disappearance is triggered via the same kind of status updates as the progress updates), and thus the problem lies with reading the stderr from x264.exe.. if the progress window stays even when x264.exe is done, then there's a problem dispatching the status updates (as odyn1982 has).
status window disappears, when the job is done - so there is no fault....
only the progress bar fails...


@kurt: do you have a progress bar during audio encoding? besweet also writes the processing output to stderr and only informational messages to stdout. mencoder and mp4box use stdout and only rarely stderr.
yes, progress bar during audio encoding works! (and 99% cpu for besweet.exe by default - in contrast to x264.exe) ...

The only thing I can still try is the paralell 3 thread stdout/stderr reading that I use for mp4box now.. when time permits (week-end probably) I'll make a separate dumb program that launches x264.exe and writes out any messages received from x264's stdout and stderr to the commandline. But I would not at all be surprised if that didn't work on your machine either. And that means I'd be at the end of my rope and your computer is just not compatible with my software, period.
that doesn't sound good for my machine.... :( it's strange that besweet works properly but x264.exe doesn't...

[absinthe]

Please post the megui logfile for that encoding session (you posted the stats file ;)) MeGUI logfiles are in the MeGUI directory and named like this: logfile-date-time.log.Well, inexplicably, I don't get such a file in my MeGUI directory at any point. I'm definitely using 0.1.9.9.

Anyhow, just like kurt, my status window definitely closes when the job's done; there's just no progress bar movement (it's always 0%).

Also like kurt, audio progress works just fine. As it does with muxing.

-abs

[Doom9]

Okay guys.. here's a very simply .net cli program that reads both stdout and stderr from x264.exe. It expects x264.exe in the same directory, as well as an avisynth script called input.avs.

You obviously have to launch it from the commandline and it should show something like this:

D:\MeGUI\bin\Debug>x264CLIReader.exe
18:13:40Started x264.exe and the stdout and stderr readers
18:13:40 line received: avis [info]: 640x352 @ 25.00 fps (3598 frames)
18:13:40 line received: x264 [info]: using cpu capabilities MMX MMXEXT SSE SSE2
3DNow!
18:13:40 line received: mp4 [info]: initial delay 0 (scale 25)
18:13:40 line received: encoded frames: 4/3598 (0.1%), 36.70 fps
18:13:40 line received: encoded frames: 8/3598 (0.2%), 42.78 fps
18:13:40 line received: encoded frames: 11/3598 (0.3%), 47.01 fps
18:13:40 line received: encoded frames: 15/3598 (0.4%), 48.08 fps

Let me know what you get. Obviously this only applies to people not getting x264.exe status updates. If this fails I guess you'll have to settle for having no progress bar.

[odyn1982]

This is what I got:
http://img297.echo.cx/img297/3391/x264clireader3hl.th.jpg (http://img297.echo.cx/my.php?image=x264clireader3hl.jpg)

[Doom9]

@odyn1982: Could you explain which steps you took from starting MeGUI until encoding. I'm especially interested if there was an audio profile selected when you start MeGUI, if you changed the profile selection at any point in either window.

This is what I got:Excellent.. so I can read from stderr on your box after all. Now, what is the content of the MeGUI log after an x264 job?

[odyn1982]

No, I've never had any audio or video profile.
I choose my input and output file, then I configured audio options (5.1, vbr, he, high), clicked queue and finally start.