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

[Doom9]

MeGUI is the most comprehensive GUI based ISO MPEG-4 solution.

Input: AviSynth scripts (AVS), AVI, D2V, VOB/TS/MPG/PVA
Output: MP4, MKV, AVI

Video Codecs: x264, XviD, Libavcodec MPEG-4, Snow
Audio Codecs: AAC (Nero, Faac), MP3

Download the latest build (http://www.sf.net/projects/megui)

Required tools:
Microsoft .NET Runtime 2.0 (http://www.microsoft.com/downloads/details.aspx?FamilyID=0856eacb-4362-4b0d-8edd-aab15c5e04f5&DisplayLang=en)

Avisynth 2.55 (http://www.doom9.org/Soft21/SupportUtils/AviSynth_255.exe) for video frameserving. Beta versions are NOT!!! supported

A YV12 VfW codec. If you have a recent XviD version installed, that will suffice. If you don't get any preview when opening an AviSynth script, install the Helix YV12 codec (http://forum.doom9.org/showthread.php?s=&threadid=56972)

For x264 encoding:
x264 CLI (http://forum.doom9.org/showthread.php?t=89979) alternatively you can use mencoder

For XviD, lavc, Snow and x264 encoding (alternative to x264 CLI)
latest version of mencoder (http://www.aziendeassociate.it/cd.asp?dir=/mplayer) (it's part of the mplayer package, pick the version that best matches your CPU

For audio encoding
besweet 1.5b31 (http://www.doom9.org/Soft21/Audio/BeSweetv1.5b31.zip)

For MP4 muxing
latest version of mp4box (http://www.aziendeassociate.it/cd.asp?dir=/gpac/dev) (version 0.4.0 or later)

For MKV muxing
latest version of mkvtoolnix (http://www.bunkus.org/videotools/mkvtoolnix/downloads.html) You need the full installer!

To create DGIndex projects:
DGMPGDec 1.41 or higher (http://neuron2.net/dgmpgdec/dgmpgdec.html)

To create AviSynth scripts: copy dgdecode.dll (see DGIndex download) to your AviSynth plugins directory (c:\program files\avisynth\plugins or wherever you have installed it to). For IVTC and deinterlacing, you'll also have to copy Decomb (http://www.doom9.org/Soft21/Filters/decomb521.zip) to your AviSynth plugin directory.


If you are only interested in the x264 part of MeGUI, check out MeGUI x264 edition (http://forum.doom9.org/showthread.php?t=98032). If you are only interested in the snow part of MeGUI, check out MeGUI Snow edition (http://forum.doom9.org/showthread.php?t=98033)


There are 4 threads dedicated to MeGUI
This one is for general discussion
Feature request thread (http://forum.doom9.org/showthread.php?t=105162) to make feature requests
Bug report thread (http://forum.doom9.org/showthread.php?t=105160) to make bug reports
Developer thread (http://forum.doom9.org/showthread.php?t=95863)For those who wish to participate in the project

In addition, to get a headstart at configuring x264, check out Sharktooth's MeGUI x264 profiles (http://forum.doom9.org/showthread.php?t=101813)

[LigH]

BeSweet 1.5b30 is out; not really the perfect place here, but at least loosely related. ;)

[North2Polaris]

Looks like 0.193a is in the zip file, not 0.194

[Doom9]

Looks like 0.193a is in the zip file, not 0.194Urhg.. try again now.

[North2Polaris]

Urhg.. thanks! :)

[Doom9]

bump.. new version is out.

[kurt]

NIce, Doom9 - that was really fast :)

but is it a bug that there is no more mp4 output but only raw&avi in x264 encoding? or have i missed s.th. ?

[Doom9]

but is it a bug that there is no more mp4 output but only raw&avi in x264 encoding? or have i missed s.th. ?The latter. Have you actually tried encoding? I am currently encoding using a stock 0.1.9.5 right from the zip I posted.
I suppose you set the x264 to mencoder and are only looking at the input tab, not actually encoding. mencoder cannot (well, it can but it's mp4 output is almost unusable, ask bond for details) write mp4 output so I make it write raw, then mux that into an mp4 after encoding. I used to allow .mp4 output names directly in x264 mode and then rewriting the video filename for mencoder, but I think it's better that people realize right away that mencoder will write raw. If you look at the queue when you create mp4 output, you''ll see exactly what is done being done. You'll see 1/2 video jobs, the last one with raw output, and a mux job.

and btw, megui now fully defaults to using x264.exe (settings, it's the default codec and the default output is mp4). So you must've already changed something. Since most people seem to prefer x264.exe over mencoder you can now get started and only use the better updated x264.exe.. it already has some features that mencoder still cannot offer (like video SAR).

[kurt]

Sorry, my fault - i was a ltitle bit irritated by the output path *.264 when clicking on File Type: MP4 :rolleyes:
i just noticed that by myself that mp4 output follows as a muxing process after the avc encoding and i would have edited my post above but my old machine took to much time for encoding :p

[Doom9]

I might go back on how it was previously done and have a tooltip on the filetype selection that tells you that if your encoder is mencoder, you'll get an additional mux job.

[kurt]

ok, i think it's clear for me now... :)
i made some tests without mencoder and latest x264cli but its really slow on my machine; 160frames need 2,5 minutes (in two pass, Subpixel Ref. 5, and all other "high profile" options on, 3bframes, target bitrat 1500...) while x264 Vfw only need ~50sec with exact the same options (but avi output)... any ideas why it's so much slower?
[I'll do some more tests with longer clips....]

in settings of MeGUI i can't save the default priority to NORMAL, it has to be changed while the encoding process...and autostart queue seems to be always activated...

[Doom9]

in settings of MeGUI i can't save the default priority to NORMAL, it has to be changed while the encoding process...and autostart queue seems to be always activated...Hmm.. they are saved properly but both not taken into account. I'll fix that in the next release.

I have no idea about your encoding speed.. but I'm quite sure the commandline encoder is on par speed-wise, and MeGUI's overhead is minimal.

[Doom9]

any ideas why it's so much slower? Actually, one of the bugs you reported could just explain that. Unless you change priority manually, megui will yield priority to other apps you have running.. I suppose your VirtualDub is running at normal priority. And if you're using the PC while encoding.. low priority will always be slower.. by how much depends on how much cpu time your "other tasks" require.

[kurt]

i changed it immediately at the beginning of 1st pass (and then on 2nd pass too) of the encoding to NORMAL ... VDM is set on idle process priority ... i did both encodings under the same circumstances (there were no other "big" tasks)... I'll check the speed again when you release the next build :)

[Doom9]

Well, if you close MeGUI, you'll find all the jobs as xml files in the jobs subdirectory. Open the job in question using notepad, and in it you'll find a line like this:

<Commandline>"mencoder.exe" "D:\DVDs\DVDVolume\VIDEO_TS\re-trailer.avs" -ovc x264 -x264encopts bitrate=700:subq=4:i4x4 -o "D:\DVDs\DVDVolume\VIDEO_TS\test.264" -of rawvideo </Commandline>

Copy everything in between <Commandline> and </Commandline>, then open a dos prompt and go to your MeGUI directory, paste that commandline, put "start /low " before it (so it'll look like this:

start /low "mencoder.exe" "D:\DVDs\DVDVolume\VIDEO_TS\re-trailer.avs" -ovc x264 -x264encopts bitrate=700:subq=4:i4x4 -o "D:\DVDs\DVDVolume\VIDEO_TS\test.264" -of rawvideo

) and see what you get. I'm sure speed will be roughly the same.

[kurt]

) and see what you get. I'm sure speed will be roughly the same.
you are right, speed is similar and very low ...

[Doom9]

you are right, speed is similar and very low ...thus we have taken MeGUI out of the equation :) This asks for a continuance in another thread. Basically I'd triple check of my parameters are really okay as I've never heard or noticed that the commandline versions would be significantly slower than the VfW at the same settings, but since the VfW does not permit all the options the commandline encoders do, it's easy to get non matching parameters.

[Rash]

Doom9, I think I need some help. :) I'm trying to open my AVS script on MeGUI but it returns the folowing error:

The file D:\Home\Rash\Development\Movie\p-logo\logo.avs cannot be opened. Please make sure it's a valid AviSynth script and that AviSynth is properly installed. You can check the validity of your script and AviSynth installation by opening the file in your favourite media player. Error message for your reference: AVIStreamGetFrameOpen failed
So I checked my script on MPC and Nero ShowTime and they open it correctly. I have AviSynth 2.5.5 installed.

Thank you very much! ;)

My very simple script (it is a test video I have)

LoadPlugin("D:\Home\Rash\Programs\MeGUI\DGIndex\DGDecode.dll")
mpeg2source("D:\Home\Rash\Development\Movie\p-logo\logo-new.d2v")

[Doom9]

Could you cut of a snippet of your test video, make sure the problem still ocurrs with that snippet, then upload it someplace where I can get it to have a look?

[Rash]

OK, I will try to do it. My video is a 13MB .vob.

I did some more tests. I tested the folowing avs script

LoadPlugin("")
Which AviSynth, obviously, return as a video error message. [here] (http://img286.echo.cx/img286/1402/avserror9zk.png) MeGUI returns me the exact same error above.

I have also tried opening other videos I have using the DirectShowSource(). That is OK on MeGUI. Then I tried opening other .vob files I had (through d2v) and couldn't open none of them, but they all work on the media players alright. So I guess this is not a specific problem with my test vob, is it? But if you still want a snippet I'll do it.

I guess there is something in my computer working against it. I have WinDVD 7, Nero ShowTime (I have no choice, it comes with NeroRecode) and ffdshow installed. Maybe there is an incompatibility somewhere. MeGUI doesn't add anything to the registry, does it? If it does maybe I could delete it and try again. I tried deleting the settings.xml but it didn't work. Oh, and one more thing, I can't create a d2v file from an ifo either. If you want, I can send you the error log. But somehow I think the problems are related.

[JoeBG]

@ doom9

The new look is very sexy ;) Is this the last layout? :)

[Doom9]

Is this the last layout?Not really.. with zones coming (I'm currently testing the most evil scenarios and try to make it crash), the x264 config dialog will look differently, so do the settings. Then as you can see from the development forum, there will be new dialogs in the future, along with a restructured dgindex project creator, a chapter creator, etc. And of course the codec dialog screens can be changed at any time (new features, make things more userfriendly, etc... but this is the same with VfW codecs).

I know why you're asking though and I'd say it's safe to start with the guide now. The big changes have been done. If you use the latest release you should be okay.

[Doom9]

If it's 13MB, could you just upload the entire thing or are you on a 56k connection? Either way with a working sample (that crashes on your box) or the entire thing I'll try my best to figure out what's causing this. It seems to happen on rare occasion on other's people's PCs but most users seem to never encounter this. Perhaps the tools that can read this script don't use AVIFile but DirectShow (media players), or custom readers (VDub I think).

Just a thought, do you have a YV12 codec installed? I suppose you do but perhaps it's only registered for DShow?

[Doom9]

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.

[Rash]

Fine Doom9, I just don't have a place to upload it right now. I could open a ftp on my PC for you to download. Unfortunately I have problems with time. :( So now it is 17:30 here. By midnight I'll have to shut down my computer, so we have about 6 hours to do it, right?

Check your PM Inbox.

[Doom9]

I got the file. Created a dgindex project from it (using version 1.2.1 final), then loaded the d2v into megui's avisynth script creator (I'm afraid the dgindex project creator requies DVD Decrypter ripped input for now) which created a script for me and auto-loaded that script. Everything worked out just fine. So it's not so much the code as AVIFile failing on your PC. What kind of YV12 decoder do you have installed (open your AviSynth script in Graphedit)?

BTW, here's my script:
mpeg2source("D:\test.d2v")
LanczosResize(640,352)

dgindex.dll is located directly in the MeGUI directory (but that should only be required for the avisynth script creator) and in my avisynth autoload plugin directory.

[Rash]

Oh, so I copied DGdecode.dll to MeGUI's directory and successfully created an avs! :D

But the error loading the AVS is still the same. I'm not sure about the YV12 decoder you asked me. Graphedit only shows 3 boxes. The avs one, linked to ffdshow MPEG-4 Video Decoder then linked to VMR Video Renderer.

Well, ffdshow wan't supposed to be there, am I right? I use it because I check "Uncompressed" on ffdshow Codecs options. I like ffdshow's processing so I use it with all videos.

I'll disable ffdshow and see what happens. Thanks a lot for your help Doom. ;)

[Maximus_G]

That's strange, but... how do you manage to "Autoencode" with x264.exe? Coz when i create the jobs using this button, press "start", a progress window opens... and nothing happens! x264.exe is present in the process list, it seems to work, but there's no progress seen, and the process doesn't stop, though i'm waiting long enough. At the same time - if i copy the command-line from MeGUI log window, and start it from the command-line window - it works well... I just don't get it.

[Doom9]

@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, configure output, configure output size, press queue. Then depending on your settings (from the settings dialog, Control-S in the main gui), encoding either starts (autoqueue and no other job is currently running), or it doesn't.

The log is auto-saved.. what do you get after the commandline? And what happens if you close MeGUI, re-open it, double click on the job that is in processing state, then press start? And is x264.exe running when you do that (check in the task manager) .And what is your setup (audio tracks, output format).. all those things are crucial to know. I have personally tested auto-mode with x264.exe (and mencoder) using no, 1 mp4 or 1 ac3 audio track input (so with and without audio encoding and muxing), and with and without using additional subtitle streams, chapters and assigning track languages. The only possible problem I ran into is mp4box not wanting to complete its job due to incorrect subtitle or chapter files.. but that is signalled as an error in the log and it only affects the muxing step, not the encoding one.

@Rash: when I open the avs described above (from your source), I also have 3 boxed, but I have the Moonlight Color Space converter in the middle. Obviously this stems from me having the Moonlight AVC encoder installed so I'll check on a PC where I don't have it installed (but ffdshow is on all my PCs) and see what I get.

[Doom9]

@Rash: Alright, I finally managed to properly play an AviSynth script on my work PC. Rendering the script in Graphedit yields the following Graph, which I believe to be the standard (it rings a bell seeing it.. unlike the Moonlight one, this one looks very familiar).

AviSynth Video -> AVI Decompressor -> Color Space Converter -> Video Renderer. Both filters in the middle are standard Windows filters, filename is quartz.dll. I guess they'll also do the decoding in MeGUI.

I also tried setting ffdshow to not decode AviSynth (no change), then enable support for all supported raw output (no change), changing it to decode raw YV12 (now I have the same graph as you have), but in all cases MeGUI still opened the video.

[thed33p]

I did a quick encode with MeGUI 0.1.9.6 and it's working like a charm! 3 zones together with cropping - no problem.

Audio wasn't encoded but I'm sure that was something I overlooked. (will post if it wasn't :) )

Thanks Doom9, Berrinam, xtknight (hope I didn't miss anyone)

[kurt]

if using x246.exe and not mecoder, is it normal that there is no progressing in the status window while encoding? (jobs always finished fine later). With mencoder there is a progressing display...

[thed33p]

I used X264 and the status window worked just fine....

[Doom9]

the new version is out.
@Rash: I'll try stax' code to open video in the next release.. perhaps that'll change anything for you. But the problem isn't so much my fault as a generic incompatibility with that method and some part of your setup.

if using x246.exe and not mecoder, is it normal that there is no progressing in the status window while encoding?I would've never released it if I didn't have a progress bar.. the first x264 supporting version already had one and x264.exe is one feature I test in each release.

[Doom9]

by the way, there are two things I forgot:

0.1.9.6 also has a context menu in the video player allowing you to go to the intro end, credits start, and zone start/end (if applicable). And thanks to xtknight for helping out with the mp4 muxer progress bar.. he created a working muxer where I could take certain ideas from to finally get it working.

[Ariakis]

if using x246.exe and not mecoder, is it normal that there is no progressing in the status window while encoding? (jobs always finished fine later). With mencoder there is a progressing display...

I got the same problem, and I believe I know the problem... here's my job log:


Next job job1-1 is a video job. encoder commandline:
"C:\Program Files\x264\x264.exe" --pass 1 --bitrate 256 --stats "2pass.log" --keyint 300 --min-keyint 30 --ref 2 --bframes 2 --b-pyramid --subme 3 --weightb --analyse i4x4,p4x4,i8x8 --qpmin 1 --qpstep 50:--progress --no-psnr --output NUL "C:\Joe\VOB\Damien Rice\Damien Rice.avs"


I think what breaks it is: --qpstep 50:--progress
Any idea why this is happening?

Edit:
Also, on this pass I had specified a --cqm "flat" flag in the Custom Commandline Options, and it didn't show up. Is this being process correctly?

Edit2:
Okay, after further testing: for me, specifying a different quantizer delta messes up the commandline, as shown above. Also, when that bug isn't in effect, MeGUI still seems to ignore the additional custom commandline options. (This is all with 0.1.9.7)

[lazyn00b]

Using MeGUI 0.1.9.7, I can't get the Adaptive B-frames setting to stay enabled in the config dialog. For example, if I set B-frames to 2 and click on Adaptive, then hit OK, then hit Config again, the Adaptive box is cleared! I'm not sure if I'm doing something wrong or if this is a bug. Also, creating a new profile from within the config dialog will cause the Adaptive setting to be instantly cleared as well.

[falcon2000eg]

if using x246.exe and not mecoder, is it normal that there is no progressing in the status window while encoding? (jobs always finished fine later). With mencoder there is a progressing display...

Same problem with me


Edit2:
Okay, after further testing: for me, specifying a different quantizer delta messes up the commandline, as shown above. Also, when that bug isn't in effect, MeGUI still seems to ignore the additional custom commandline options. (This is all with 0.1.9.7)

that is it

[odyn1982]

I've got the same problem: no progress in the status window while encoding with x264.exe.

[Maximus_G]

@Maximus_G: your description sounds like you're not doing things right.
OK, i'll make a thorough description later.
For now, i've found a nasty thingy.
If you set "I8x8" in the "Macroblock options", the "Adaptive DCT" checkbox is checked automatically, because it's required to use with the i8x8. BUT MeGUI doesn't add the "-8" ("--8x8dct") parameter to the command-line. So, i8x8 isn't used at all. Which can be seen in the x264 encoding statistics.

And - I've got the same problem: no progress in the status window while encoding with x264.exe.

[Rash]

@Rash: I'll try stax' code to open video in the next release.. perhaps that'll change anything for you. But the problem isn't so much my fault as a generic incompatibility with that method and some part of your setup.
That's definately true. It also seems our graphs are a bit different. So here are some screens.

This one here is the error message itself. I was doing some tests today and that's what I realised: on MeGUI version 0.1.9.5 this message is displayed twice. That is, I try to open the video, the error pops up. I click OK and the error pops up again. I click OK and MeGUI's "VideoPlayer" window pops up blank (no video). Now with MeGUI versions 0.1.9.6 and 0.1.9.7 the error message pops up only once (so I press OK only once and the blank "VideoPlayer" window appears). This is all the time, I mean, it didn't happen only once but all the times I tried loading the avs in my tests (about 7 times). 0.1.9.5 twice, 0.1.9.6/7, once. Maybe you changed the way the errors are handled? Don't know, but something is different. ;)

» http://img12.echo.cx/img12/8136/errormsg9dc.png

Now this is a screenshot from my Graphedit. The first one is with ffdshow and its info while the video is playing. The other one is the same with "User Overlay Mixer" disabled on "Output" on ffdshow. Unfortunately none of them works. But hey! There is no AVI Decompressor as you stated! :eek:

» http://img12.echo.cx/img12/9540/graphedit5ul.png
» http://img104.echo.cx/img104/3434/graphedit21jm.png

[LigH]

One reason of no progress might be that x264 immediately exits due to some requirements not met. For example, I had strange reactions of the .NET x264CLIgui, trying to encode a video which was not macroblock aligned:
...
avis [info]: 640x360 @ 25.00 fps (400 frames)
x264 [error]: width % 16 != 0 or height % 16 != 0 (640x360)
x264_encoder_open failed
Maybe here the reason is similarly simple...

[Rash]

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

VDubMod message
[!] Couldn't locate decompressor for format 'YV12' (unknown).
VirtualDub requires a Video for Windows (VFW) compatible codec to
decompress video. DirectShow codecs, such as those used by Windows Media
Player, are not suitable. Only 'Direct stream copy' is available for this
video.
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.

[absinthe]

Ok, so then it's not just me with no progress bar in 0.1.9.7 :).

I'm finally able to encode using just about any options I want. My only darn problem is speed. I plan to build a new box when dual core AMDs become available retail. For now, my 1.4 Ghz Athlon takes about 10x clip length to encode per pass :(.

This little GUI is getting better and better, doom!

-abs

[stax76]

@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

[LigH]

It is always wise to use the board search engine and insert very typical words out of the error message there. In your case, for example, search for "locate decompressor YV12".

Such an important topic as YV12 video even got its own FAQ thread, didn't you know?!

[Doom9]

Maybe you changed the way the errors are handled?Yes I have. I changed the constructor of the preview a bit, and some other stuff that could relate to this. Because the video player is used so often I have not yet changed the way it is opened.. I plan to have an additional method that loads the video and that returns false if the video cannot loaded.. if that happens, the player will not be shown anymore.. I'm sure this will help in certain confusing scenarios where people think the video is okay even if they get an empty player. I will also change the error message to point people to opening the video in VDub as this seems to be the read test.. you can encode if it plays via DirectShow, getting the length and such will even work if I cannot get any frames, but only if you can properly open it via vfw will the video preview work.

x264_encoder_open failedfailed should be recognized as an error and be reported back in the queue

@Ariakis: thank you for your reports.. just the level of details and work on your part that I need. Reports like this make it easy for me to get right started with the bugfixing :)

@lazyn00b: I'll check this out tonight.

@odyn1982: can you check posts by other people on this issue and confirm that it is the same options that are causing this problem? I can explain why it happens based on the commandline Ariakis has posted.. since --progress is not separated by the previous option, it is not taken into account.. and without --progress x264.exe doesn't send progress reports to the commandline and hence I have nothing for my own progress reports.

[MeteorRain]

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.
have you installed xvid vfw? it should work for yv12.

[odyn1982]

My job always looks like this:
Next job job1 is a video job. encoder commandline:
"x264.exe" --bitrate 700 --ref 5 --bframes 3 --b-pyramid --subme 6 --weightb --analyse p8x8,b8x8,i4x4,p4x4,i8x8 --me umh --progress --no-psnr --output "E:\DIVX\FILMY\TRAILERS\HP2\Test\new.mp4" "E:\DIVX\FILMY\TRAILERS\HP2\Test\TEST5.avs"
successfully set up video encoder and callbacks for job job1

Then I press "start", a progress window opens... and nothing happens! x264.exe is present in the process list, it seems to work, but there's no progress seen.
http://img297.echo.cx/img297/273/megui7ay.th.jpg (http://img297.echo.cx/my.php?image=megui7ay.jpg)
But if I copy the command-line from MeGUI log window, and start it from the command-line window - it works well... :confused:
http://img297.echo.cx/img297/2920/x264fromcommandpromt2bf.th.jpg (http://img297.echo.cx/my.php?image=x264fromcommandpromt2bf.jpg)

[Doom9]

@odyn1982: does it work if you use default settings? it's THE thing to try.. naturally I cannot test every settings and in my tests I normally use the defaults (less time to set everything up). And could you add "> output.txt" to your commandline, run it again, and attach output.txt here?

Also, which version of .NET are you using? 2.0 is currently not supported (it may work.. if so, good for you, but if it doesn't, don't ask me to fix it.. I'll support 2.0 once it has become final).

[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.

[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.

http://www.imageark.net/image.php?id=119609

-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.txtproduces 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]

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:
http://img68.echo.cx/img68/7012/image16lv.th.jpg (http://img68.echo.cx/my.php?image=image16lv.jpg)

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.php?attachmentid=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]

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 !! :eek: Cool! :D

So, I still get the fps reported incorrectly. Here is a screenshot (http://img63.echo.cx/my.php?image=megui1qd.png) 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]

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.

[kurt]

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.

with mencoder there are no problems at all - progress window works and closes after the job is finished...
here's the logfile for MeGui 0.2.0.0 with x264.exe after aborting by hand...
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.
i see your point, and it's sad that we are apperantly in minority ...
about handling a debugger: i don't know anything about it :D

Edit: in the meantime i uninstalled (completely) and reinstalled .net framwork 1.1 ... but the problems exist like before....

[Doom9]

I've compiled a list with all the info collected on the progress window. Please help fill the blanks

odyn1982:

status updates: no
x264 pw closes: no
x264 process still present after encoding: no
other pw closes: yes
status updates non x264.exe: yes
x264clireader works: yes
redirect stderr works: yes
progress in cli: yes
.net version: 1.1
ever had .net 2.0 installed: yes
windows version: winxp pro (sp0)

kurt

status updates: no
x264 pw closes: yes (not in 0.2.0.0)
x264 process still present after encoding: no
other pw closes: yes
status updates non x264.exe: yes
x264clireader works: no
redirect stderr works: no
progress in cli: no
.net version: 1.1sp1
ever had .net 2.0 installed: no
windows version: winxp sp2 home

pasqui

status updates: no
x264 pw closes: no
x264 process still present after encoding: yes
other pw closes: yes
status updates non x264.exe: yes
x264clireader works: yes
redirect stderr works: yes
progress in cli: yes
.net version: 1.1
ever had .net 2.0 installed: no
windows version: WinXP Pro

maximum_g

status updates: no
x264 pw closes: no
x264 process still present after encoding:
other pw closes: yes
status updates non x264.exe: yes
x264clireader works:
redirect stderr works:
progress in cli:
.net version:
ever had .net 2.0 installed:
windows version:

absinthe

status updates: no
x264 pw closes: yes (not in 0.2.0.0)
x264 process still present after encoding: no (yes in 0.2.0.0)
other pw closes yes
x264clireader works: no
redirect stderr works: no
progress in cli: no
.net version: 1.1
ever had .net 2.0 installed: no
windows version: winxp sp1 pro


explanation: pw = progress window
x264 process still present after encoding refers to encoding using MeGUI.. check the task manager.
redirect stderr works: <your x264.exe commandline> 2> stderr.txt gives you a file where you can see the progress reports
progress in cli: running x264.exe from the commandline with the --progress option set shows the encoding progress.

[kurt]

update:

kurt

status updates: no
x264 pw closes: yes (not in 0.2.0.0)
x264 process still present after encoding:no
other pw closes: yes
status updates non x264.exe: yes
x264clireader works: no
redirect stderr works: no
progress in cli: no
.net version: 1.1sp1
ever had .net 2.0 installed: no
windows version: winxp sp2 home

[absinthe]

absinthe

status updates: no
x264 pw closes: yes (not in 0.2.0.0)
x264 process still present after encoding: no (yes in 0.2.0.0)
other pw closes yes
x264clireader works: no
redirect stderr works: no
progress in cli: NO
.net version: 1.1
ever had .net 2.0 installed: nope
windows version: winxp sp1 Pro

-abs

[MeteorRain]

maybe still a bug:
when you reencode an automated 2pass job (by double click them to change the done state to waiting), after you press start and the 1st-pass job done, the 2nd-pass job don't run while the text of the 'stop' button is still 'stop' (while the time nothing is encoding)
and when you press 'stop', the 2nd-pass job encodes, and if more jobs are waiting, they will be encoding one by one, as usual.

[odyn1982]

.net version: 1.1
ever had .net 2.0 installed: yes
windows version: winxp sp2 pro pl

This is my log from DebugView:

00000000 0.00000000 [1428] Creation of mvCore
00000001 0.00006062 [1428] mvCore own adresse : 139723904
00000002 0.00945902 [1428] Destruction of mvCore
00000003 0.00954954 [1428] mvCore own adresse : 139723904
00000004 0.00959452 [1428] ME : 0.0 %
00000005 0.00966827 [1428] LUMA & VAR : 0.0 %
00000006 0.00970794 [1428] COMPENSATION : 0.0 %
00000007 0.07860552 [1428] INTERPOLATION : 0.0 %
00000008 0.13055765 [1428] Overiding iDCT With: 7
00000009 0.19646547 [1428] TffdshowBase::Constructor
00000010 0.20408851 [1428] TffdshowDecVideo::Constructor
00000011 0.37787456 [1428] TffdshowDecVideo::Destructor
00000012 82.40028607 [1428] Creation of mvCore
00000013 82.40121161 [1428] mvCore own adresse : 139986048
00000014 82.40868965 [1428] Destruction of mvCore
00000015 82.40874748 [1428] mvCore own adresse : 139986048
00000016 82.40878575 [1428] ME : 0.0 %
00000017 82.40883129 [1428] LUMA & VAR : 0.0 %
00000018 82.40886817 [1428] COMPENSATION : 0.0 %
00000019 82.43259800 [1428] INTERPOLATION : 0.0 %
00000020 82.50061977 [1428] Overiding iDCT With: 7
00000021 82.53524400 [1428] TffdshowBase::Constructor
00000022 82.53739484 [1428] TffdshowDecVideo::Constructor
00000023 82.54489300 [1428] TffdshowDecVideo::Destructor
00000024 109.15470737 [1428] Creation of mvCore
00000025 109.15476855 [1428] mvCore own adresse : 139265152
00000026 109.16283410 [1428] Destruction of mvCore
00000027 109.16288746 [1428] mvCore own adresse : 139265152
00000028 109.16293104 [1428] ME : 0.0 %
00000029 109.16297099 [1428] LUMA & VAR : 0.0 %
00000030 109.16300871 [1428] COMPENSATION : 0.0 %
00000031 109.16304558 [1428] INTERPOLATION : 0.0 %
00000032 109.23131851 [1428] Overiding iDCT With: 7
00000033 109.29078193 [1428] TffdshowBase::Constructor
00000034 109.29288024 [1428] TffdshowDecVideo::Constructor
00000035 109.30095864 [1428] TffdshowDecVideo::Destructor
00000036 109.46945380 [4024] Creation of mvCore
00000037 109.47750873 [4024] mvCore own adresse : 21103744
00000038 109.47756153 [4024] Destruction of mvCore
00000039 109.47760875 [4024] mvCore own adresse : 21103744
00000040 109.47764674 [4024] ME : 0.0 %
00000041 109.47768278 [4024] LUMA & VAR : 0.0 %
00000042 109.47771910 [4024] COMPENSATION : 0.0 %
00000043 109.51280316 [4024] INTERPOLATION : 0.0 %
00000044 109.55027245 [4024] Overiding iDCT With: 7

00-11 - open avisynth script
12-23 - add to queue
24-44 - started job

[Doom9]

@odyn1982: could you fill out the remaining blanks.. and could you run a .net ide to debug (dbgview seems to show x264.exe working) where things go wrong? I do have some lingering suspcions but taking shots out in the dark takes a lot of time. I'd really like to know what is going on. Obiously, if x264.exe is run on the commandline and doesn't produce any progress info.. that ends the whole status update issue and I just have to ensure that the "job done" message comes back. But where those updates are available, it should be possible to get a working progress report during encoding.

[odyn1982]

I run x264.exe from commandline and get only:

00000000 0.00000000 [2536] Creation of mvCore
00000001 0.00006425 [2536] mvCore own adresse : 21103744
00000002 0.00902405 [2536] Destruction of mvCore
00000003 0.00907769 [2536] mvCore own adresse : 21103744
00000004 0.00911959 [2536] ME : 0.0 %
00000005 0.00915591 [2536] LUMA & VAR : 0.0 %
00000006 0.00919083 [2536] COMPENSATION : 0.0 %
00000007 0.00922575 [2536] INTERPOLATION : 0.0 %
00000008 0.08026830 [2536] Overiding iDCT With: 7

Net v1.1.4322.585

[Doom9]

hmm.. I just realized debugview also works with managed languages, too. So rather than dumping stuff in the log I'll start adding Trace commands in the next build so people can simply run dbgview and have it listen to the output of my app. Still if anybody affected has the VS IDE that would also help immensely.. I can guide you through the steps setting everything up and running the software.

[Doom9]

@absinthe, kurt: since you're not getting any progress reports from x264.exe even when launching it in the commandline with the --progress parameter, you might want to report that in the x264 development thread: http://forum.doom9.org/showthread.php?t=80910 as the problem is clearly somewhere in between your computer and x264.

[namchik]

Doom9,
I also get only this progress window:
http://images.people.overclockers.ru/31682.png
Then I abort the job and get this logfile:
Next job job1 is a video job. encoder commandline:
"x264.exe" --bitrate 700 --subme 4 --analyse p8x8,b8x8,i4x4 --progress --no-psnr --output "D:\MeGUI\1111.mp4" "D:\MeGUI\qwe.avs"
successfully set up video encoder and callbacks for job job1
When I copy the "x264.exe" --bitrate 700 --subme 4 --analyse p8x8,b8x8,i4x4 --progress --no-psnr --output "D:\MeGUI\1111.mp4" "D:\MeGUI\qwe.avs" from log to CMD, encoding goes normally:
http://images.people.overclockers.ru/31681.png
This happens only with x264cli... mencoder works fine.

[absinthe]

@absinthe, kurt: since you're not getting any progress reports from x264.exe even when launching it in the commandline with the --progress parameter, you might want to report that in the x264 development thread.
Done.

-abs

[falcon2000eg]

There is no problem with the progress bar it only take its time to update so i got my first info after 5 minutes sometimes it could take 10min then it updates every 3-4 minutes one, realy i do not care as long as it give me the correct fps and remaining time,so i think it is somthing about the priority of the threads, the cpu usage for x264 is 100%.I tried and made the priority of megui high even realtime but nothing happend, there is no problem with mencoder.So any one have aproblem abot the progerssbar take your time and see Anyway here is my log file

Now the real problem is I can not encode in raw format when use x264.exe beacuse megui always set file extension in the command line to mp4 not 264 as it must be.

Sorry for my realy horrible english.

[Doom9]

@namchik: since you don't get any progress reports running x264.exe manually it is also an issue for the x264 development thread. Hopefully that one can be sorted out along with the problems certain people have that seem to be my doing (x264.exe gives progress reports but MeGUI doesn't).

falcon2000eg makes an interesting point. Actually I have noted this too.. unlike mencoder, x264.exe only writes a progress report after a certain number of frames have been encoded. So far I have found no rule as to which interval is used (it seems to fluctuate). Perhaps this might also be the reason why certain people don't get any progress reports on the commandline. Looking at the log you posted, you get the first progress report after only 191 frames.. and since I wait for 10 progress reports.. you know the time it takes for an update. I might do this differently in the future though, comparing the frame number of two reports and if the distance is more than 10 (the value used for mencoder which makes a report for every frame it encodes) then fire a status update immediately. I normally get status updates in MeGUI in intervals that vary between 50 and several hundred frames.

[namchik]

Doom9,
Do you mean this progress report: ?
http://images.people.overclockers.ru/31691.png
I have this during manual encoding with x264.exe

[xtknight]

OK when I run x264clireader I get this:

C:\tools\megui>x264CLIReader.exe
12:18:11 PMStarted x264.exe and the stdout and stderr readers
12:18:11 PM line received: avis [error]: unsupported input format (DIB )
12:18:11 PM line received: could not open input file 'input.avs'
12:18:11 PMx264.exe has quit. Exiting now

So stderr works??

Windows XP SP2 (Windows NT 5.1.2600.0) - .NET v1.1.4322.573

[Doom9]

So stderr works??Yup.. you're not one of the unlucky fews..

Do you mean this progress report: ?Yup, I meant that. I'll add a load of trace commands in the next version and have you all run debugview while encoding.. unless somebody who knows C# comes around and has that same problem within the next few hours.

[Pasqui]

@Doom9
Here is my updated info
status updates: no
x264 pw closes: no
x264 process still present after encoding: yes
other pw closes: yes (just tested with Besweet)
status updates non x264.exe: yes (just tested with Besweet)
x264clireader works: yes
redirect stderr works: yes
progress in cli: yes
.net version: 1.1 French runtime
ever had .net 2.0 installed: no
windows version: WinXP Pro French

[Doom9]

when you reencode an automated 2pass job (by double click them to change the done state to waiting), after you press start and the 1st-pass job done, the 2nd-pass job don't run while the text of the 'stop' button is still 'stop' (while the time nothing is encoding)I cannot reproduce that. I set up an automated twopass job, encoded it, changed both jobs back to waiting and encoded.. both jobs are being redone that way.

[savior]

using the .2 release of the gui, all up to date software required for it. worked for the first movie i encoded, but now it hangs on the 2nd pass, while it says processing in the window i checked task manager and x264 isnt running, this is in auto mode 2 pass. i aborted then reloaded the avs and tried again, same issue. unzipped main files again on main and 2nd comp, hangs on both comps. gonna del everything from the gui folder and try again. if needed i have the log avail.

thanks doom9 for this great program :)

[Doom9]

I need more than just the log.. I need every step you took after starting MeGUI. And .. please do try with the default settings. You're using x264 so that's default, if you configure the codec, just set the mode to auto 2 pass and do not change anything else (you can do that later.. it's important to start with a common ground that I know works and approach the problem step by step from there). Logs will also be immensely helpful.. they show commandlines which can help pinpoint a commandline generation problem (there are so many options I simply cannot test everything).

[Doom9]

thanks.. just in time for the new release.

[Doom9]

Alright, the next version is out.

Please check out this post about tracing what goes on while encoding with x264.exe if you have any problems with the status reports: http://forum.doom9.org/showthread.php?p=678129#post678129. It won't help kurt and absinthe who seem to have a deeper problem that needs to be solved on their PC or in x264.exe, but I hope I can get things working for the rest.

Note that the XviD zones word of advice still applies.. in XviD a zone goes from its start frame until the next zone.. if there's no such zone, the zone will extend till the last frame of the video. This is exactly how things work in the XviD VfW. However, if there's a need and audience for it, I could add additional logic for XviD zones that would automatically insert 100% weight zones in between your configured zones (if necessary, if the end frame of zone x is n, and the start frame of zone x+1 is n+1, then obviously nothing would have to be done). Let me know.

[savior]

here is the log

logfile (http://home.comcast.net/~slapp_happy/megui.txt)

and also a screenshot of the issue, you can see the time 2nd pass started and current time of screenshot, x264 not shown in task manager during 2nd pass.

this encode was done after deleting folder and starting with fresh megui and files.

there was also a issue with mencoder for x264 but thatl be another post.

screenshot (http://home.comcast.net/~slapp_happy/megui.jpg)

[Rash]

@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.
The fps fluctuate a lot. From 1010 to 2300 fps. I did the test but using the new release 0.2.0.1, so you removed the fps reporting thing. Nevertheless I am 99% sure this is indeed a locale problem. The decimal separator here is comma and not a dot. ;)

[Doom9]

you still owe me a step by step explanation on how I can reproduce the problem. See the guidelines here. If I can't reproduce the problem and it's a report from one person... well, put yourself into my position. One time is no time. If something is seriously wrong, there will be multiple people reporting it and/or you can guide me through the steps to be taken to reproduce the problem. But please let's use the official MeGUI thread for further discussion (I'll move these posts).. this one is really for the developers.

[Doom9]

so you removed the fps reportingNo, please explain. And run DebugView while encoding (see here: http://forum.doom9.org/showthread.php?t=96415). That log will give me all the lines I'm reading and how I'm translating them into FPS reports.

[savior]

sorry about that doom9.

all files extracted into single dir. no config needed for megui only to make sure x264.exe is used and not mencoder.
dgdecode.dll renamed and put into avisynth filter dir.

1: d2v creator used, .d2v saved and audio extracted.
2:avisynth script creator, set res, and saved script.
3:script loaded, set output for video, loaded audio, set audio output and configed.
4:autoencode selected, set for default of 1 cd overhead is left alone.
5: clicked queue selected start.

everything was left default other than to check that x264.exe was selected as h264 encoder.

[Doom9]

@savior: is there an easier scenario? can you reproduce it without auto-encode? steps 1/2 are irrelevant here so I can discard them.. but having to worry about auto-encoding that increases complexity by a considerable amount (and if it only happens there, that also helps to rule out certain things.. then there's the question if it only happens with audio encoding configured, if you configure a pre-existing audio mp4, or if it also happens in auto mode without any audio at all (you can still use the auto mode then.. in that case you just get the video at your desired size)). And I really do need to see that DebugView output.. I have a feeling that all those issues are due to some internal exception that is being catched but that aborts the whole commandline reading in the encoder.

[Rash]

OK Doom9, here it goes. Both the Debug Viewer and the MeGUI logs. What I meant was that this new version of MeGUI doesn't produce that huge log anymore.

Anyway, I believe the language encoding problem is causing this. Just a cosmetic problem. MeGUI is working perfectly here now. ;)

Can I ask just one question? Since I haven't found any information this... What does that MP4 overhead option on the "AutoEncode" window does?

[Doom9]

@Rash: Thank you for the attachment. Unfortunately I've only added the important trace line in the 0.2.0.1a version. I've just noted that Brazilian Portuguese uses the comma as decimal separator, and since odyn reported that the 0.2.0.1a fixes all problems for him with regards to the progress bar, perhaps you could give it a try as well and let me know if it works out for you: http://forum.doom9.org/showthread.php?t=96415

What does that MP4 overhead option on the "AutoEncode" window does?It sets the overhead assumption for the bitrate calculation. While lower than other containers, MP4 still does have an overhead per video frame that has to be taken into account. You can set that in the GUI. It'll be set to 10.4 bytes/frame when you use b-frames, and 4.3 bytes/frame when you do not use b-frames (so you can see that b-frames incurr a significant container overhead.. but compared to AVI's 24 bytes/frame for video only (and a lot more with VBR audio).. it's still low).

I have exposed that setting, and am writing muxing statistics for each mp4 muxed to a file mp4stats.txt in your MeGUI directory.. hopeing that enough people will send me that file (it's not really happening right now I'm afraid) so that I can gather enough statistics to make better assumptions about the overhead.. it seems 10.4 works out pretty well at least for x264 with b-frames, but I'm not so sure about the rest. Seems some time I also have to go over the whole statistics reporting again because it's not really up to the scenarios that are now possible (e.g. mp4 muxing with a video-only mp4.. that scenario wasn't foreseen when I started the muxer and it only was introduced when I started supporting x264.exe).

[Rash]

I was going to attach the logs here, but since it is 100% now with 0.2.0.1a (including a coma in the fps :D) I won't give you anymore trouble.

But I couldn't find a mp4stats.txt in my MeGUI folder, otherwise I would send it to you. Is that because I'm doing a video only encode?

[Doom9]

Is that because I'm doing a video only encode?Indeed.. it is only written when you're muxing something into an mp4.. either using auto-mode or using the muxer manually.

[Doom9]

alright, the next version is out.

A word of advice: I haven't tested what will happen if you have an mp3 job configured and try to launch auto-mode.. it might explode your PC.. realistically seen if I did all the preparation right it shouldn't allow you to launch auto-mode, but you never know. Either way MP3 in MP4 will not be a supported configuration.

Please let me know if you need another other lame options for casual mp3 encoding but note that I'm not going to support every option. I have no plans to create a BeLight clone.. I don't think that would be useful in the MeGUI context, plus I consider it unethical to write a clone of an existing program just because I can, and bring nothing of my own to the table.

[Rash]

Doom9, if I may make a suggestion, you could do only LAME --preset options. For example:

--preset medium
--preset standard
--preset extreme

Or let the user type the switch he prefers himself. Afterall the LAME presets are supposed to make the best possible quality. I don't know, just a suggestion. I won't use MP3 anyway. ;)

And thank you for the new version.

[Doom9]

well.. I added the options I think I might ever use.. those are the ones that are highly likely to stay ;)

[savior]

here is the debugview log
debug log (http://home.comcast.net/~slapp_happy/megui.log)

was set up for auto 2pass, and to mux previously encoded audio.

was you needing another other type of log file??

[Doom9]

I think I got it from here. Looking at your log I see that the video bitrate is 0. Looking a bit further I see that the bitrate was set to 0 because the framerate of your video appears to be 0. Looking at the debugview log, x264.exe reports the same framerate. So, clearly something is wrong with your video. If you open the script again.. do you get a proper view preview window where you can actually see your video?

Also, set the second pass back to waiting, and start again while leaving Debugview running.. I guess it'll catch an x264.exe error. Apparently a bitrate of 0 works for the first pass but I'm confident it won't work for the second pass.. x264.exe will abort with an error message that I seem not to catch as such. If you get nothing interesting in the debugview, could you also try to run your second pass commandline from dos mode and append "> output.txt" at the end of the commandline, then post output.txt here.

[savior]

set back to waiting and started second pass. nothing happened as you stated.

2nd log (http://home.comcast.net/~slapp_happy/megui2.log)

trying 2nd pass in dos mode to see what happens.

loaded avs again and preview comes up perfect.

noticed this in the log

Desired size of this automated encoding series: 734003200 bytes
Encoded audio file is present: C:\BASKBALL\VIDEO_TS\baseketa.mp4 has a size of 46925530 bytes.
adjusting desired size. New desired size = 687077670 bytes
No audio encoding. Calculating desired video bitrate directly.
Setting video bitrate for the video jobs to 0 kbit/s
Desired size of this automated encoding series: 734003200 bytes
Encoded audio file is present: C:\BASKBALL\VIDEO_TS\baseketa.mp4 has a size of 46925530 bytes.
adjusting desired size. New desired size = 687077670 bytes
No audio encoding. Calculating desired video bitrate directly.
Setting video bitrate for the video jobs to 0 kbit/s
Next job job1-1 is a video job. encoder commandline:
"x264.exe" --pass 1 --bitrate 0 --stats "2pass.log" --subme 4 --analyse p8x8,b8x8,i4x4 --progress --no-psnr --output NUL "C:\BASKBALL\VIDEO_TS\baseket.avs"
successfully set up video encoder and callbacks for job job1-1

----------------------------------------------------------------------------------------------------------

Log for job job1-1

avis [info]: 640x352 @ 0.00 fps (148305 frames)
x264 [info]: using cpu capabilities MMX MMXEXT SSE 3DNow!
x264 [info]: slice I:594 Avg QP:47.95 Avg size: 130
x264 [info]: slice P:147711 Avg QP:51.00 Avg size: 17
x264 [info]: slice I Avg I4x4:0.1% I8x8:0.0% I16x16:99.9%
x264 [info]: slice P Avg I4x4:0.0% I8x8:0.0% I16x16:0.0% P:0.0% P8x8:0.0% PSKIP:100.0%
x264 [info]: kb/s:0.0

Actual bitrate after encoding without container overhead: 0.00

----------------------------------------------------------------------------------------------------------
job job1-1 has been processed. This job is linked to the next job: job1-2
Next job job1-2 is a video job. encoder commandline:
"x264.exe" --pass 2 --bitrate 0 --stats "2pass.log" --subme 4 --analyse p8x8,b8x8,i4x4 --progress --no-psnr --output "C:\BASKBALL\VIDEO_TS\baseketv.mp4" "C:\BASKBALL\VIDEO_TS\baseket.avs"
successfully set up video encoder and callbacks for job job1-2
----------------------------------------------------------------------------------------------------------

so unable to process 2nd pass due to these para.

[savior]

ok this is confusing, when loading .avs in virtualdub or mpc, virtualdub closes and mpc crashes. so maybe something with mpeg2dec.dll im using??

but it loads in megui , weird heh.

and that was just the renamed dgdecode.dll from the dmpgdec zip file.

[LigH]

Immediately closing or crashing applications... one possible reason is that you may have placed an AviSynth 2.0x plugin into the auto-load folder of AviSynth 2.5x. Does the "version()" script work well?

Furthermore, I see no reason to rename DGDecode.dll to MPEG2Dec.dll - and I hope you know that d2v project files must always be generated with the same DGIndex.exe that was bundled together with the DGDecode.dll used to open it.

[savior]

it is the dgindex.exe and dgdecode.dll from the dgmpgdec140rc3.zip file i have. it was renamed due to just with avisynth only installed the preview window would not load in megui. i had to manually load the plugin each time for a video. so yes the .dll being used was packaged with the dgindex im using. also the version() does work when loaded into mpc. avisnyth 2.55.

[bond]

i wasnt able to set the paths for mp4box and mencoder in the settings

mencoder.exe and mp4box.exe is simply not displayed to be existing the folder (altough they are of course)

[Doom9]

mencoder.exe and mp4box.exe is simply not displayed to be existing the folder (altough they are of course)The directory filter was set to besweet.exe and mp4.exe respectively.. naturallly mencoder.exe and mp4box.exe don't fall under that filter. Wait a few minutes for 0.2.0.2a

[bond]

i also noticed that you offer mp4, aac to aac, mp3 encoding via besweet

note that besweet doesnt offer aac decoding so you cant use it for reencoding aac (in mp4 or not)

[Doom9]

i also noticed that you offer mp4, aac to aac, mp3 encoding via besweetNot so much offering as not removing the open filter.. there are tons of caveats when switching between audio output formats.. I doubt I can deal with every possible scenario. Just imagine somebody accessing the audio codec dropdown, selecting mp3 output by mistaken.. and boom.. his configured mp4 input is gone, even though he only selected mp3 by mistake. So, in addition to remove the input filter (that I can do), I'd have to kick out his configured mp4 input.. if he goes back to AAC mode.. the previously loaded mp4 is still gone and will have to be reloaded.. not really ideal, is it?
In auto-mode, since the input is an mp4... it'll be muxed.. the rest of the config won't matter. In the future with AVI output, isInputAVIMuxable() will return false on that stream.. so the stream will be discarded because it wasn't configured properly.

If you have a solution that covers every!! scenario that you think is better than mine, please let me know.

[Doom9]

Alright, the latest build discards mp4/aac input of the first configured track. The second track doesn't really apply because it will never be used (mencoder only supports 1 audio track in mp3).

[bond]

you didnt seem to understand what i mean:

besweet cant decode aac audio so of course also the aac->aac conversion will not work
therefore you cant allow aac/mp4 input in the audio input tab independantly of the output format


edit: btw would be nice if the logs could be moved to a seperate log folder, cause they can get a lot and fill the main folder quickly

[Doom9]

you didnt seem to understand what i mean:Hmm.. you wrote it differently the first time, but you did point out a problem in mp3 mode. Now in mp3 mode as you can see mp4 output is no longer possible.

And as far as mp4 input goes.. did you notice that it's not possible to select an output file when you select an mp4 input? It's also not possible to start encoding with an .aac/.mp4 loaded as audio input. In auto-mode, if your audio input it set to an aac/mp4 file, it will be muxed in the mux step.. no audio encoding will be done. Audio encoding to mp4 is only done if the input is a non aac/mp4 file and the output is an aac/mp4 file.

If that doesn't work as it should please file a bugreport but at least I know it used to work exactly how I want it. I found it rather cumbersome to have to configure audio tracks in a separate window, hence I also allow audio input files that will only be muxed, not encoded, as well as those that will be encoded and muxed (and those that will only be encoded in audio only mode.. pressing queue in the audio groupbox will create just an audio job independent of any other thing you may have configured).

edit: btw would be nice if the logs could be moved to a seperate log folder, cause they can get a lot and fill the main folder quicklyOkay, I'll move them to a logs/ subfolder in the MeinGUI folder in the next release (not the one I'm about to release).

[Doom9]

I have a conceptual question, for bond, and everybody else:

Does it make sense that you can configure audio streams to be muxed in the main GUI or should this only be possible in the muxing window?

Right now, you can select .aac/.mp4 audio tracks in the main GUI, then when you press AutoEncode, you configure the final output name, split size, etc. And if you check "Add subtitles & chapters" before pressing GO, you can configure the name of the audio tracks you'll get (be it tracks that will be muxed, or tracks that will be encoded and then muxed), and add additional streams.

To permit configuration of both audio tracks that will be encoded and those that will only be muxed in the main window, I had to go through considerable hoops. Now with the addition of AVI output in auto encoding mode, it might get worse, and conceptually I'm not sure it makes a lot of sense to configure audio tracks that are to be muxed, not encoded, in the main GUI which is clearly meant for setting up jobs that are to be encoded.

Thus, what would you think about the following:

In the main GUI in the audio section, you configure audio jobs that are to be encoded. Then if you go into auto-mode, the checkbox you can check to give audio tracks a language, as well as adding subtitle tracks and chapters, will lead you to the mux configuration window where you can not only add a language descriptor to existing audio tracks (those that you set up for encoding in the main GUI), but you'll also be able to add additional existing audio tracks (.aac/.mp4 files for mp4 output).

And in case of AVI output, the additional window will just allow you to specify pre-existing MP3/AC3 audio tracks.

Or simply put: everything that you're going to encode is set up in the main window, everything that you're going to mux is set up in an additional window from within the auto-encode window (and of course the muxing functionality will also be available separately from the tools menu.. the mp4 muxer is already available from that menu today).

I think that way would be cleaner insofar that encoding and muxing are clearly separated. Considering all the work already put into this, it might not really make my life easier at this point, but from a coding point of view at least it would still be a more easy to understand workflow.

[bond]

Hmm.. you wrote it differently the first time, but you did point out a problem in mp3 mode. Now in mp3 mode as you can see mp4 output is no longer possible.
i also noticed that you offer mp4, aac to aac, mp3 encoding via besweeti didnt only talk about mp3 encoding, but about aac encoding too

And as far as mp4 input goes.. did you notice that it's not possible to select an output file when you select an mp4 input? It's also not possible to start encoding with an .aac/.mp4 loaded as audio input. In auto-mode, if your audio input it set to an aac/mp4 file, it will be muxed in the mux step.. no audio encoding will be done. Audio encoding to mp4 is only done if the input is a non aac/mp4 file and the output is an aac/mp4 file.ah that makes sense and is a great thing

it might be good to disable the config tab too in that case, cause this made me think megui wants to reencode the aac

about the autoencode muxing, its working fine


about the new avc profile setting feature:
- great that you offer this!
- setting custom macroblocks allows using high profile mb even with main and baseline profile
- cqm seems to always be disabled, even when high profile is set
- a feature request: also being able to set the levels (automatically together with the vbv values of the levels) would make the profile/level support complete

one issue i noticed:
when clicking on the config tab megui isnt displayed in the windows taskbar at the bottom of the screen anymore
when closing the config tab it appears again
is that a normal behaviour? it makes switching between megui and eg writing a thread on doom9 (or reading a guide) slightly (!) more difficult

[cheburashka]

@Doom9
I like x264cliGUI 1st pass speedup section. It make 2-3 pass configuration more flexible. It would be nice to have similar options in MeGUI interface.

[Doom9]

I like x264cliGUI 1st pass speedup section. It make 2-3 pass configuration more flexible.Could you outline this a bit? In fact you already have turbo mode in MeGUI which disables certain options (only during the first pass).. notably it lowers subq, number of reference frames and certain mb options.

@bond: thanks for the feedback on the profiles. Do you have a link about the levels? I took your sticky for that feature but I didn't find anything about buffers (I looked.. I figured buffers most come into play at some point).

is that a normal behaviour?Yup.. I ended up having about 5 windows on top of each other in certain configurations and that simply was too much for me so I started hiding forms.. basically the main GUI is inacessible when you are in a configuration dialog. But, if you know a more userfriendly way.. you can show/hide any form, show or not show it in the taskbar, dynamically set minimize/maximize buttons on form.. you name it. Just tell me how I can make it better.

it might be good to disable the config tab too in that case, cause this made me think megui wants to reencode the aacYou mean the config button, right? I guess I could do that but I see the following problem: say a user wants to configure/create/edit an audio profile.. now in order to do that he/she first needs to load an encodeable audio file.. as a counterexample you can configure codecs in both GordianKnot or VirtualDub even if no encodable video source is loaded.. I guess moving the non-encodable audio input selection into a place where it becomes more apparent that they're only being muxed will improve the "straightforwardness". I'll await some more feedback before changing anything though.

[bond]

@bond: thanks for the feedback on the profiles. Do you have a link about the levels? I took your sticky for that feature but I didn't find anything about buffers (I looked.. I figured buffers most come into play at some point).
you would need to have a look at the specs (which i link to in the sticky), i dont know anything about the different vbv settings so i dont think i can be much help here

Yup.. I ended up having about 5 windows on top of each other in certain configurations and that simply was too much for me so I started hiding forms.. basically the main GUI is inacessible when you are in a configuration dialog. But, if you know a more userfriendly way.. you can show/hide any form, show or not show it in the taskbar, dynamically set minimize/maximize buttons on form.. you name it. Just tell me how I can make it better.
always display the main gui in the taskbar and the others not

You mean the config button, right? I guess I could do that but I see the following problem: say a user wants to configure/create/edit an audio profile.. now in order to do that he/she first needs to load an encodeable audio file.. as a counterexample you can configure codecs in both GordianKnot or VirtualDub even if no encodable video source is loaded.. I guess moving the non-encodable audio input selection into a place where it becomes more apparent that they're only being muxed will improve the "straightforwardness". I'll await some more feedback before changing anything though.
maybe you should move the audio muxing to the autoencode tab? after all you can also mux mp3 audio to .mp4 with mp4box, so it might make sense to seperate the reencodeaudio from the muxaudio inputs

or you allow an own switch in the config tab which lets people choose between "mux" and "encode" (encode also offering the codec settings)

[Pasqui]

@Doom9
So far the only problem I have with MeGUI (now taht x264 progress bar works) is the suggest resolution checkbox in AviSynth sript generator panel. Each time I check it I get the following error:
System.FormatException: Le format de la chaîne d'entrée est incorrect.
at System.Number.ParseDouble(String s, NumberStyles style, NumberFormatInfo info)
at System.Double.Parse(String s, NumberStyles style, IFormatProvider provider)
at MeGUI.AviSynthWindow.suggestResolution_CheckedChanged(Object sender, EventArgs e)
at System.Windows.Forms.CheckBox.OnCheckedChanged(EventArgs e)
at System.Windows.Forms.CheckBox.set_CheckState(CheckState value)
at System.Windows.Forms.CheckBox.OnClick(EventArgs e)
at System.Windows.Forms.CheckBox.OnMouseUp(MouseEventArgs mevent)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ButtonBase.WndProc(Message& m)
at System.Windows.Forms.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
Is it a known issue ?

Regards

[cheburashka]

Could you outline this a bit? In fact you already have turbo mode in MeGUI which disables certain options (only during the first pass).. notably it lowers subq, number of reference frames and certain mb options.

This sections would allow you to manually adjust default "turbo" settings and to change me method as well.
See attached image:
http://forum.doom9.org/attachment.php?attachmentid=4220&stc=1

[savior]

doom9, after deleting the folder again, starting with your latest version and going back to dgindex 1.30 issue has been fixed. dunno if the fix was local or not but im glad its fixed. thank you for your time and your great program.

:)

job job1-1 has been processed. This job is linked to the next job: job1-2
this series of jobs starts with an audio job and is followed by regular twopass video jobs
The audio job is named job1-2 the first pass job1-2 and the second pass job1-3
The second pass job has a desired final output size of 734003200 bytes and video bitrate of 700 kbit/s
The audio file size is 113850023 bytes
calculateVideoBitrate(113850023, 734003200, 148299, 4.3, 23.976)
Setting the desired bitrate of the subsequent video jobs to 801 kbit/s
Next job job1-2 is a video job. encoder commandline:
"x264.exe" --pass 1 --bitrate 801 --stats "2pass.log" --analyse p8x8,b8x8,i4x4 --progress --no-psnr --output NUL "C:\BASKBALL\VIDEO_TS\base.avs"
successfully set up video encoder and callbacks for job job1-2

[Doom9]

Is it a known issue ?Well.. the AR uses a dot as decimal separator.. I suppose if you were to change the decimal separator in the language settings in the control panel it would work. I think this is the exact same issue as the progress bar, except that there's an ample amount of error catching done in the encoder (hence you just didn't get any status updates.. double parsing would bomb out and that was that) which isn't the case here.

This sections would allow you to manually adjust default "turbo" settings and to change me method as well.I see. Though I'm wondering if this is such a smart thing. Some of those changes might actually have a noticeable impact on the quality of the final product.

[cheburashka]

I see. Though I'm wondering if this is such a smart thing. Some of those changes might actually have a noticeable impact on the quality of the final product.

You may put this section in advanced tab, so only people who know what they do will change defaults.

[cheburashka]

Doom9,

You tool is getting more and more mature to be "all in one" frontend.
The only thing I miss is a compressibility test. After that it would be "new GK without VFW." :cool:

[Doom9]

well.. I'm a bit wary about that feature.. if you have aku backing you up that it's safe to use certain options in a first pass without visible quality degration, then I believe the turbo option should do all those things. There's a turbo option in libavcodec, xvid and the x264 vfw version.. it's all one checkbox, so I'd say it's kinda what people can be trusted to handle safely.. give them another 10 options on top of what's already there might just end up confusing people more and drive them to using another codec. And for those who know what they're doing, they're probably not looking for a tool that is as automatic as MeGUI has become.

As far as the compressibility check goes.. personally I find that a useless feature.. but if there's a demand and somebody can tell me what I'd have to do (I really don't have a clue what is done in such a check.. it's just something I never felt any particular need for knowing), perhaps I'll do it. Of course.. there's 4 different codecs, and I figure 3 different stats formats at least (libavcodec based encoders, xvid and x264).

[AMED]

Hi,

I gave MeGUI a go last night and found a couple of problems.

I have ripped the monster inc DVD using DVDDecrypter using IFO mode.
i have set all the locations for all the needed files in MeGUI and i'm using x264 for encoding, not mencoder

i open up MeGUI and start the d2v creator and load the first vob file from the ripped DVD. i get and error stating that it couln't find the stream information.txt
MeGUI is looking for the file named vts_13 - stream information.txt when i look in the folder where i ripped the disc the files are as below.
VTS_13_0.IFO
VTS_13_PGC_01 - Stream Information.txt
VTS_13_PGC_01_1.VOB
VTS_13_PGC_01_2.VOB
VTS_13_PGC_01_3.VOB
VTS_13_PGC_01_4.VOB
VTS_13_PGC_01_5.VOB
i click ok on the couldn't find dialogue box, demux all audio streams and build the d2v.

onto AVS.

i open up the AVS creator and load the d2v file i just made. i get an error saying that dgdecode.dll wasn't found.
System.DllNotFoundException: Unable to load DLL (dgdecode.dll).
at MeGUI.d2vReader.openMPEG2Source(String fileName)
at MeGUI.d2vReader.openD2V()
at MeGUI.VideoPlayer.loadVideo(String path, PREVIEWTYPE type)
at MeGUI.AviSynthWindow.openVideo(String videoInput)
at MeGUI.AviSynthWindow.openVideoButton_Click(Object sender, EventArgs e)
at System.Windows.Forms.Control.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ButtonBase.WndProc(Message& m)
at System.Windows.Forms.Button.WndProc(Message& m)
at System.Windows.Forms.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
i checked the directory where DGIndex.exe is and sure enough dgdecode.dll is there, so i copied dgdecode.dll into the same dir that MeGUI.exe is in and that fixed that problem. i save the AVS file after cropping the picture (using autocrop).

I load the AVS into the video part and specify the output name, and click autoencode.

a couple of encoding boxes pop up and then dissapear and the log shows this
Desired size of this automated encoding series: 734003200 bytes
No audio encoding. Calculating desired video bitrate directly.
Setting video bitrate for the video jobs to 587201 kbit/s
Next job job1-1 is a video job. encoder commandline:
"H:\Stored Files\Video\MeGUI-0.2.0.4\x264.exe" --pass 1 --bitrate 587201 --stats "2pass.log" --analyse p8x8,b8x8,i4x4,p4x4,i8x8 --8x8dct --progress --no-psnr --output NUL "G:\UNDEFINED\MeGUI.avs"
successfully set up video encoder and callbacks for job job1-1
----------------------------------------------------------------------------------------------------------

Log for job job1-1

avis [error]: unsupported input format (DIB )

----------------------------------------------------------------------------------------------------------
job job1-1 has been processed. This job is linked to the next job: job1-2
Next job job1-2 is a video job. encoder commandline:
"H:\Stored Files\Video\MeGUI-0.2.0.4\x264.exe" --pass 2 --bitrate 587201 --stats "2pass.log" --analyse p8x8,b8x8,i4x4,p4x4,i8x8 --8x8dct --progress --no-psnr --output "G:\UNDEFINED\Megui video.mp4" "G:\UNDEFINED\MeGUI.avs"
successfully set up video encoder and callbacks for job job1-2
----------------------------------------------------------------------------------------------------------

Log for job job1-2

avis [error]: unsupported input format (DIB )
could not open input file 'G:\UNDEFINED\MeGUI.avs'
desired video bitrate of this job: 587201 kbit/s - obtained video bitrate: 0 kbit/s
----------------------------------------------------------------------------------------------------------
job job1-2 has been processed. This job is linked to the next job: job1-3
Next job job1-3 is a mux job. mp4box commandline:
"H:\Stored Files\Video\MeGUI-0.2.0.4\MP4Box\MP4Box.exe" -add "G:\UNDEFINED\Megui video.mp4" -fps 24 -new "G:\UNDEFINED\Megui video-muxed.mp4"
successfully set up muxer and callbacks for job job1-3
----------------------------------------------------------------------------------------------------------

Log for job job1-3

Error setting job priority. Error message: Cannot process request because the process (2780) has exited. stacktrace: at System.Diagnostics.Process.GetProcessHandle(Int32 access, Boolean throwIfExited)
at System.Diagnostics.Process.GetProcessHandle(Int32 access)
at System.Diagnostics.Process.set_PriorityClass(ProcessPriorityClass value)
at MeGUI.MP4Muxer.encode()
----------------------------------------------------------------------------------------------------------


Hi had a feeling that there was something funky with the AVS file, so i used Gordianknot to create an avs to compare with the MeGUI one.
This is the MeGUI created AVS
mpeg2source("G:\UNDEFINED\monsters.d2v")
crop(10,0,-10,-2)
LanczosResize(640,480)

and the one from gordain knot (which works)
LoadPlugin("C:\PROGRA~1\GORDIA~1\DGMPGDec\DGDecode.dll")
LoadPlugin("C:\PROGRA~1\GORDIA~1\AviSynthPlugins\UnDot.dll")
mpeg2source("G:\UNDEFINED\monsters.d2v")
crop(10,0,700,572)
LanczosResize(640,480)
Undot()

sorry for such a long post.

[LigH]

"avis [error]: unsupported input format (DIB )"

Very strange: The FourCC "DIB " is one of the few valid for RGB24. But your script looks like it shall output YV12 because there is no colorspace conversion after MPEG2Source.

I wonder if it is possible that any kind of "forced colorspace conversion" kicks in between AviSynth and x264. But where, and how?!

[berrinam]

i checked the directory where DGIndex.exe is and sure enough dgdecode.dll is there, so i copied dgdecode.dll into the same dir that MeGUI.exe is in and that fixed that problem.
Not actually, it just made it disappear. You also need dgdecode.dll in your AviSynth plugins folder (normally, c:\program files\AviSynth 2.5\plugins), but it won't tell you about that error in any explicit way (ie, it will just fail quietly with the symptoms you have).

[AMED]

having dgdecode.dll in c:\program files\AviSynth 2.5\plugins and in the same folder as MeGUI.exe seems to have fixed all my problems.

[Doom9]

vts_13 - stream information.txtThat's the default setting.. you can have tons of ways of DVD Decrypter naming the output files.. just as AutoGK expects certain options checked, I do, too.

And as far as dgdecode goes.. somewhere in the readme it should say that the dll needs to be in the megui folder for the AviSynth creator, and in your autoload folder. I've often moved around scripts to machines that had the proper DLLs, but not at the proper place.. hence relying on auto-load where I don't have to worry about the location of the DLLs.

[AMED]

That's the default setting.. you can have tons of ways of DVD Decrypter naming the output files.. just as AutoGK expects certain options checked, I do, too.

And as far as dgdecode goes.. somewhere in the readme it should say that the dll needs to be in the megui folder for the AviSynth creator, and in your autoload folder. I've often moved around scripts to machines that had the proper DLLs, but not at the proper place.. hence relying on auto-load where I don't have to worry about the location of the DLLs.

couldn't you have it search for *stream information.txt in the folder of where the ripped files are?

[Di Abolico]

Hi! Great thanks to you, Doom9 and all who participated, for such a great tool!

Got a minor question that's not exactly on topic, but surely related to. The other day I did some dvd-rip encoding with MeGUI + mencoder to Xvid. There was great speed, no errors, and colors, totally messed up in resulting video. Checked avs script - it played ok in players like MPC and Light Alloy, however mplayer, just as mencoder (no wonder), produced wrong colors. After adding "ConvertToRGB32()" to avs script weird effect went away, but doesn't mencoder accept YV12-source material?

[Doom9]

couldn't you have it search for *stream information.txt in the folder of where the ripped files are?That wouldn't work if you have two VTS sets in the same directory.. but I see what I can do about the naming.. it would have to be VTSX (where the X matches the VOB you selected.. it needs to be the first one by the way as DGIndex expects to be given the first one and picks up subsequent ones automatically) + *Stream Information.txt.. I have to check if I can make a filter like that.

@Di Abolico: If you're using dgindex.. which version? mencoder can only handle true YV12.. DGIndex used a slightly different format until v1.2.1 that would lead to discolored results when used with mencoder.

[Di Abolico]

Doom9
Unbelievable! Yes, you were absolutely right! Upgrading DGIndex (the version had been, ashamed to say, 1.0.12) entirely solved the problem. Thank you kindly!

[stax76]

Of course.. there's 4 different codecs, and I figure 3 different stats formats at least (libavcodec based encoders, xvid and x264).

also don't forget everytime a change is made to the stats format it's a breaking change, mine is based on filesize, 40 lines (old and ugly) code, works regardless of the used codec and quite good for DivX and XviD. I wonder how do you find your bitrate without doing a compcheck?

[Doom9]

I wonder how do you find your bitrate without doing a compcheck?it's all based on the per frame overhead assumption. Fortunately the Nero AAC encoder takes MP4 overhead (or actually... "underhead" as the raw stream is bigger than the one packed into an MP4) into account so I really only have to worry about video and the values I'm using (the ones ateme gave me with their avc encoder) seem to work out reasonably well.

Either way, somebody first has to guide me through a compcheck for me to be able to figure out the amount of work and if I really want to do that. Of course, since it's open source, anybody can step in..

@cheburashka: I've started a discussion on turbo "features" in the official x264 thread.. if there are any changes that could be added to the current turbo mechanism, I prefer to implement all those, rather than risk that people either use settings that make things slower but not better, or break anything. In the end what I think mostly matters is that you get the best possible speed gain without degrading the end results.. anything else should be up to people setting up first and second pass (and 3rd for that matter.. I'm currently contemplating adding an automated 3 pass even though it's not something I'd ever use, but it's easy enough for regular encoding, just needs some additional intelligence in automated mode)

[superdump]

I've started a discussion on turbo "features" in the official x264 thread.
And I've replied. :)

[Doom9]

by the way.. here's another way you can help, without even needing to know how to code: since subtitles cannot be OCR'ed completely automatic in most cases, I have asked for VobSub subtitle import to mp4box (Nero style using private streams). I haven't gotten around to even encoding a sample stream though so if you have one ready, could you please attach it here: https://sourceforge.net/tracker/?func=detail&atid=571741&aid=1227952&group_id=84101

Having that feature in mp4box would mean I could also offer fully automated subtitle processing in MeGUI and get one step closer to the one click ideal.

[berrinam]

Is matroska output (eg for AC3+AVC) through mkvmerge a possible future for MeGUI, or do you plan to stick to the mp4 container?

[Doom9]

I'm not really a fan supporting 10 different containers.. each has its own sets of problems that need to be dealt with. For instance, Matroska cannot handle raw AVC so you'll either have to have two mux jobs (raw -> mp4, mp4 -> mkv), or restrict the encoder to x264.exe.. then there's bitrate calculation, yet another muxer to be supported, new muxing dialogues, new audio formats (ogg), new ways of transferring audio streams in between dialogs.. even adding avi is a pain in the ass even though I have a neat workaround in mind (you can mux audio during video encoding).

[Doom9]

I've already fixed all the issues bond mentioned (no level support yet) and the ultra-fast turbo, as well as all the other issues that have come up. In addition, I believe to have fixed another old muxing issue also related to commas.. I think I got them all now.

I really got myself into a mess with that AVI feature though.. I'm still not done with that :/ Should've stuck to MP4 output.

[Doom9]

Alright, with the new release out, a few notes:

mencoder freezes when muxing AC3. This is because it cannot get the properties of your audio file. unixfs wrote a patch for that which was turned down (http://forum.doom9.org/showthread.php?t=94787&page=1&pp=20).. I'm going to file a bug report hoping it'll be fixed fast.

Note that I have yet to adjust the load button to take care of the newly created muxjob type so don't try to load an AVI mux job.

mencoder can't split (right now) so AVI split sizes are ignored. I kept it in the hope that this will change some day.

And I hope that's it.

[bond]

avc cqm files have the extension .cfg, not .txt!

[Doom9]

avc cqm files have the extension .cfg, not .txt!alright, I'll adjust that. Not that it would matter since it's still an ASCII text file ;)

[Doom9]

the new version is out. enjoy

[buzzqw]

Hi !

some notes:

if in configuration of avc i choose ABR, and then on main window autoencode a job for 2 pass encoded is created
Would be better to use antoencode to determinate the bitrate for avc choiced configuration ?

or, is possible to integrate a mini bitrate calculator to calculate exactly the bitrate needed ?

in d2v creator if i stick "On close load file" after demuxing this option isn't fuctional

in avisynth script generator dgdecode.dll isn't loaded, so the script do not run (i haven't set a avisynthdir plugin in my registry for conflict between filter dll), could be useful to set path to filters dll in tools -> setting

in avisynth script generator after creating a project and avs script, after checking "On save close and load to be encoded", when i close the script isn't loaded, the preview yes, but not the "avisynth script" to be encoded

Thanks Doom9

BHH

(and sorry for my english)

[JoeBG]

the new version is out. enjoy

And it´s great, thanks a lot.

[Ishan]

@Doom9
Could you add a way to select the audio sample rate ? I'm trying to do a PSP compliant MPEG4 SP+LC AAC file but audio is always set @ 44.1 wich the PSP don't like.
It needs to be 24khz (thx Sony :| )

[Pasqui]

@Doom9
Thanks for this new version. It works great !
So far, I've found only two small issues:
- in D2V creator, the word "Français" is displayed as "Franais" as if extended charset was not supported
- in auto encode panel, when configuring the muxing, the avi extension is automatically added even if a MP4 file is muxed.

[bond]

It needs to be 24khz (thx Sony :| )
not only that
the .mp4 files which should play on the psp also need to have some extra info not defined by mpeg-4, so you will not be able to play the output from megui directly anyways, but need to remux the file again to make it psp-compatible (if such a tool exists)

[Doom9]

if in configuration of avc i choose ABR, and then on main window autoencode a job for 2 pass encoded is created
Would be better to use antoencode to determinate the bitrate for avc choiced configuration ?Have you tried running the jobs? The bitrate is automatically calculated and adjusted according to the effective audio size you get (in case you're doing audio encoding as well, not just audio muxing).

In order to reach the target size, two or three pass encoding is required. You can configure which one of the two is done in the settings, and override that in the codec configuration dialog (if the codec you're using it set to automated 2 or 3 pass that one is taken, anything else (except for CQ where I abort right away) leads to the number of passes configured in the settings. The bitrate you specify in the configuration is not used in auto-mode whatsoever, it is always overridden by the calculated one.

or, is possible to integrate a mini bitrate calculator to calculate exactly the bitrate needed ?Not needed, it is done automatically and I take care of all container overhead you'll get as well.

in avisynth script generator dgdecode.dll isn't loaded, so the script do not run (i haven't set a avisynthdir plugin in my registry for conflict between filter dll), could be useful to set path to filters dll in tools -> settingI have considered and discarded that back when creating the avisynth window. Why? I use 3 computers for development, and each of them has a different AviSynth configuration.. so when transfering my source material I neded up having to adjust AviSynth scripts because the plugin path was hardcoded. It it much easier for most users to have the script auto-load and not having to worry about absolutel paths. If you're not using plugin auto-loading, that means you know just fine what you're doing and are capable of adding the appropriate line by yourself, wouldn't you agree?

[Ishan]

Some of the psp video encoder (like pspvideo9) use ffmpeg for encoding, I assume they found out what to mux with the stream to make it works.
Gotta check that out.

[Doom9]

in avisynth script generator after creating a project and avs script, after checking "On save close and load to be encoded", when i close the script isn't loaded, the preview yes, but not the "avisynth script" to be encodedfixed in the new version

Could you add a way to select the audio sample rate ? I'm trying to do a PSP compliant MPEG4 SP+LC AAC file but audio is always set @ 44.1 wich the PSP don't like.
It needs to be 24khz (thx Sony :| )Eww, bad audio quality. Though the thing is.. you cannot use MeGUI for the PSP.. the MP4 files it creates are not compatible with the PSP since sony had the foresight to break the MP4 specs.. you need a special ffmpeg build to create MP4s that the PSP can handle (at least that's what all the FAQs say). So, if the MP4s MeGUI create will never be PSP compatible (please verify and report back), it obviously makes no sense to add downsampling.. it just gives people the idea that they could use the output for the PSP which is in fact misleading.

in auto encode panel, when configuring the muxing, the avi extension is automatically added even if a MP4 file is muxed.I cannot reproduce that.. please elaborate. When you set filetype to MP4, auto-encode will run in MP4 mode (so naturally the extension is mp4), when you set filetype to AVI, auto-encode will run in AVI mode, so naturally the extension is AVI.

[Doom9]

in d2v creator if i stick "On close load file" after demuxing this option isn't fuctionalI cannot confirm that.. works fine here. Three things happen when I activate that option: VOBInputWindow closes, in the main GUI I have audio input configured (AC3 file as input, mp4 as output... audio codec was previously set to AAC), and the avisynth creator window opens with the d2v project preselected and the preview window present. What are your demuxed audio files called? What exactly doesn't work (guide me through it step by step).

[Ishan]

ok, I checked out how they encode a compliant file.
It's just MPEG4 SP + LC AAC@24khz in mp4 container and they use the -title "mytitle" option of ffmpeg (wich I think makes it "compliant" to Sony mp4 format)

[Doom9]

- in D2V creator, the word "Français" is displayed as "Franais" as if extended charset was not supportedI've seen that.. not quite sure why that happens.. I thought StreamReader was capable of handling the default codepage. Turns out it seems to default to ASCII. I've now forced it to using the System's default codepage and special characters (I tried ~ and ç) are properly shown now.

[Doom9]

@Ishan: well, it's a special ffmpeg build. If you can manage PSP compliant files muxed with mp4box let me know and I might support it.. but unless I'm sure my output can be played I won't touch the featureset and mislead people into believing they can use MeGUI to create PSP content when in fact they cannot.

[Ishan]

Ok, I wasn't aware it was a special build ^^
My bad :)

[lesnick]

In meGUI 2.0.0.6 i can`t use 1st pass:
Next job job1-1 is a video job. encoder commandline:
"E:\My things\Prog\meGUI\tool\mencoder.exe" "" -ovc lavc -o NUL: -passlogfile "2pass.log" -lavcopts vpass=1:vbitrate=825:vqdiff=2
successfully set up video encoder and callbacks for job job1-1
----------------------------------------------------------------------------------------------------------

Log for job job1-1

File not found: ''
Failed to open
Cannot open file/device.

[Doom9]

In meGUI 2.0.0.6 i can`t use 1st pass:Quote obviously, there's no video input defined.. can you tell me how you created this job, starting from you starting up MeGUI?

[buzzqw]

Have you tried running the jobs? The bitrate is automatically calculated and adjusted according to the effective audio size you get (in case you're doing audio encoding as well, not just audio muxing).

i try to explayn better:
i want to do 1 pass (and only) abr encoding.

even if i choose abr in avc config, and use autoencode to determinate bit rate given a specified size (kb) , on automatic encoding windows on click on queue , a 2 pass job is created. I want 1 pass abr at bitrate calculated by autoencode

Not needed, it is done automatically and I take care of all container overhead you'll get as well.

but for 1 pass encode ?

not having to worry about absolutel paths. If you're not using plugin auto-loading, that means you know just fine what you're doing and are capable of adding the appropriate line by yourself, wouldn't you agree?

OK, i agree. Not happy but i agree


in d2v creator if i stick "On close load file" after demuxing this option isn't fuctional
What exactly doesn't work (guide me through it step by step).


start megui (great appz !!)
tool -> d2v creator
open a vob (just a vob laying around in hd, no ifo, vts info...)
choose d2v project output
click on prepare
after the run of dgindex, click "On close load files"
click on exit (X)

no project is loaded

hope that helps !

BHH

[Doom9]

no project is loadedWhat about the audio configuration.. what did you chose there? Is it a series of vobs or a single one?

but for 1 pass encode ?Not supported. 1 pass means CBR for lavc, snow and XviD, which is about the worst thing you can do, and ABR still means a non optimal bitrate distribution, and less accuracy hitting the target size. However, since the calculated bitrate is automatically shown, you can just go into the autoencode window, note the calculated video bitrate, get back to the main screen, plug the bitrate into the x264 config, and press Queue to just encode the video. One pass in auto mode is not supported for the reasons explained in this and my last reply. I know there's a lot of OPV this OPV that going on in this board and I see programmers spend an outrageous amount of time getting this thing to work for a scenario it's not meant for. So I have decided not become another one of these programmers.
The bitrate calculation even works if you configure an audio stream for encoding that you're going to mux later on.. but not knowing the size in advance, obviously the bitrate isn't as accurate as it could be.

[berrinam]

start megui (great appz !!)
tool -> d2v creator
open a vob (just a vob laying around in hd, no ifo, vts info...)
choose d2v project output
click on prepare
after the run of dgindex, click "On close load files"
click on exit (X)

no project is loaded

hope that helps !

BHH
Actually, that checkbox really means: once dgindex has closed, close d2vprojectcreator and open files in avisynth window. It isn't supposed to load files when the d2v project creator is closed.

[Doom9]

after the run of dgindex, click "On close load files"
click on exit (X)Urgh.. I completely missed that.. thanks berrinam. I guess I shouldn't just read diagonally.

[Doom9]

@amed: good news: the next version is able to handle your stream info files.

[Doom9]

so the new version is out now. The file is smaller because 0.2.0.6 was a debug build (my new PC crashed and ruined the Visual Studio installation so I simply put up the debug build that I already had)

A word about the automated threepass mode that I forgot to mention before: if you uncheck "Overwrite Stats File in 3rd pass", and do an automated 3 pass, you'll get video jobs of the following types:
3 pass 1st pass
3 pass 2nd pass
2 pass 2nd pass

Don't worry about that, it's just that 3 pass 3rd pass updates the stats file again, whereas 2 pass 2nd pass doesn't.. this has no influence at all on the resulting file but just keeps the stats file from the 2nd pass.

[Sharktooth]

bug 1: when loading custom matrices it searches for .txt files even even if .cfg files are selected in the dropdown list.
bug 2: the custom matrix editor parser needs to be fixed coz it erratically says "invalid quantizer..."
suggestion1: to avoid confusiom it's better you disable lossless option in modes other than CQ (i know it automatically switches to CQ...)
suggestion2: add "queue" button to AVI and MP4 muxers.
suggestion3: add "normalize volume" in the audio codec config

[Doom9]

bug 2: the custom matrix editor parser needs to be fixed coz it erratically says "invalid quantizer..."Please post a sample file that you loaded.. I used the intial 3 matrices posted in this forum for testing and they seem to be working just fine.

bug 1: when loading custom matrices it searches for .txt files even even if .cfg files are selected in the dropdown list.There are two instances.. it looks like the one in the quantizer editor works and the one in the x264 configuration dialog doesn't.

suggestion3: add "normalize volume" in the audio codec configI use hybridgain automatically (see commandline: -ota( -d 0 -g max )) isn't that even better than to give people the ability not to perform anything and end up flooding the audio forum with "my audio is too low" posts?

suggestion2: add "queue" button to AVI and MP4 muxers.The mux button really is a Queue button.. it queues the job.. it'll only be started if autostart is enabled in the settings. Should I rename the button?

[Sharktooth]

bug 2: it's my AVC HR matrix (find it in my sig. or in x264CLI rev.270B).
bug 1: right

suggestion 3: some ppl prefer to keep the original volume. maybe adding that option and have it enabled by default would fit.
suggestion 2: yes, less confusing.

[Doom9]

about the matrices

here's how a line of an 8x8 matrix looks in the reference format (jvt matrix):

6,10,13,16,18,23,25,27,

and here's one of your lines

6, 7, 8,10,12,14,16,18

You use a trailing comma at the end of each line for the 4x4 matrices (except for the last line), but none for the 8x8 matrices. So if you adapt your matrix to the standard format it'll work. The x264 parser might be more forgiving, MeGUI expects exactly the standard format.

suggestion1: to avoid confusiom it's better you disable lossless option in modes other than CQ (i know it automatically switches to CQ...)I'm not at all convinced.. the way it is now.. people realize that CQ mode is a must.. if they don't know that.. they come here asking "how do I use lossless mode" and we have to tell them "lossless mode is used when you set the quantizer to 0 so you have to use CQ mode and set the quantizer to 0". The way it is now, they select high profile, click on lossless mode, and that's that.

[Yama4050242]

newbie problem:
i encode the video through megui with a .mp4 output instead of .264, then how to set the fps, since my source is 29.9 progressive，but the output is 25 fps,thx

[Doom9]

@Yama4050242: please have a look at my generic problem reporting guidelines: http://forum.doom9.org/showthread.php?t=96137

As it is now I have to ask you a dozen questions to get an idea about what you're doing. I kindly ask that you do provide all that info without me having to ask for it. AS a general rule, if you tell people everything you do since the start of the program in question, it makes things much easier. For instance, MeGUI supports 4 codecs.. since you have an MP3 I know it's not Snow but that still leaves 3 other possibilities, plus two different encoders for x264. Then, there's a manual mode, a manual mode in which multiple jobs are generated, and an automated mode. That alone gives us 4 * 3 = 12 permutations not taking into account any settings you may have changed, or how you determine that the output has the wrong framerate. I also don't see a logfile.. for instance if there was a problem detecting the framerate, the log would possibly reflect upon that.

[Doom9]

Bugfix release for automated 2/3 pass encoding is out. Sorry for breaking things.. it worked when I tested it yesterday night.

@lesnick: this should take care of your problem.

[nightrhyme]

Sounds like a nice app. Decided to give it a try. Downloaded all the appropriate appz's (inluding 7z) only to find out I'm not able to unpack X264CLI_rev270B_mmx.7z (not supported archive) Why do people insist on using this futile compression tool :(

[Yama4050242]

ok, i c, detail, i am using megui(0206) with x264.exe(rev.207) as an encoder to encode my 29.9 fps progressive hd mv capture to .mp4 as an output with onli video, i guess it wouldnot change the framerate, but it did so(change to 25)

second pass log

job job1-1 has been processed. This job is linked to the next job: job1-2
Next job job1-2 is a video job. encoder commandline:
"xxxxxxxxx\x264.exe" --pass 2 --bitrate 2048 --stats "2pass.log" --ref 3 --bframes 3 --no-b-adapt --b-pyramid --subme 6 --weightb --analyse all --8x8dct --me esa --progress --no-psnr --output "xxxxxx\xxx.mp4" "xxxxxx\xxx.avs"
successfully set up video encoder and callbacks for job job1-2
----------------------------------------------------------------------------------------------------------

Log for job job1-2

avis [info]: 1024x576 @ 29.97 fps (5999 frames)
x264 [info]: using cpu capabilities MMX MMXEXT SSE SSE2 3DNow!
mp4 [info]: initial delay 200 (scale 2997)
x264 [info]: slice I:140 Avg QP:26.49 Avg size: 23127
x264 [info]: slice P:1739 Avg QP:27.72 Avg size: 13815
x264 [info]: slice B:4120 Avg QP:29.53 Avg size: 7105
x264 [info]: slice I Avg I4x4:9.2% I8x8:38.2% I16x16:52.6%
x264 [info]: slice P Avg I4x4:3.1% I8x8:23.3% I16x16:36.1% P:20.7% P8x8:1.2% PSKIP:15.5%
x264 [info]: slice B Avg I4x4:1.7% I8x8:9.6% I16x16:9.2% P:29.0% B:5.0% B8x8:2.1% DIRECT:4.4% BSKIP:38.8%
x264 [info]: 8x8 transform intra:41.2% inter:51.2%
x264 [info]: kb/s:2259.5

Actual bitrate after encoding without container overhead: 2259.70
desired video bitrate of this job: 2048 kbit/s - obtained video bitrate: 2262.50457221537 kbit/s


my avs did not apply any filter but just add the .d2v then return video


my question is how to tell the encoder"hi, dont change my framerate!!!"

[LigH]

@ nightrhyme:

http://sourceforge.net/projects/sevenzip

compresses tighter than almost any other tool - that's why! ;)
__

P.S.: Looks like the new .7z archives require at least 7-zip v4.2x (current version is 4.23). If it still doesn't decompress, you might have received an incomplete archive and should download again.

I was able to unpack it with version 4.20.

[Doom9]

@Yama4050242: now we're talking. There's no muxing going on so no error on my part and x264 properly detects the framerate. Question is.. how do you figure the framerate is wrong? If your player tells you so.. perhaps your player is wrong? Stranger things have happened. Or is the video effectively running too slow.. it's a 17 % difference so it would definitely be clearly visible. And you're not muxing this video only mp4 you got from megui? I'm asking because I know that mp4box uses 25fps when muxing anything unless you override the default framerate.

[Doom9]

you can also unpack 7zip files with a recent version of Winrar.. that's how I do it. Unfortunately I cannot control how other people redistribute software and those tools that come in 7zip format are changing very often (sometimes several times a day) I cannot have my own redistribution.. it would just cut into the time I spend developing and I'm convinced that that time is better spent developing and helping people rather than to download and repack x264 and mencoder builds.

[Yama4050242]

ffdshow tells me my video is 25 fps, i havent mux the video with audio yet, since i notice the .264 output can use the framerate configurator, but if the video input for the muxer is .mp4, i can not configurate it since it's grey

[Doom9]

ffdshow tells me my video is 25 fps,alright.. you didn't check if it actually ran at a wrong framerate, did you? I dare you to try. Chances are you'll find that ffdshow always reports 25 fps.. I just checked with a 23.976fps source (that is perfectly in synch with the audio that belongs to it)..

[Yama4050242]

i check using mpc Ctrl+g for the original file to find out where it is, then use mpc to play the encoded file, Ctrl+g and give the frame number i got in the original file, the pic is not the same. i just want to find out if my 2m video can beat the aveage 8m mpeg2 file, so i need the same pic to compare

[Yama4050242]

original frame 2966, 29.970

i checked my encoded video with both 2996, 25.000 and 2996, 29.970, the 2 are differ from the original one

[Doom9]

come on, please.. does the video run 17% slow or not? mux audio and see for yourself..

I have ample experience with the go to function to know not to trust it. Half the DS filters don't go to the right frame.. plus then there's the b-frame issue (they cause delays).. just read the damned codec comparison for my rant on this issue.. or ask somebody writing DS filters.. try bobololo from ateme for instance.. we've had discussions on this during the last codec comparison.

[Yama4050242]

no, the time is the same, not slow, maybe i try the .264 output.
is there a way to check the real framerate?
and if my source is 29.97 fps, then no matter what format i set to the output, it should be the same as source no matter how the decoder may play on it, am i right?

and how to play the .264 file, they should be playable right?

[Doom9]

you can't really play the raw streams. But here's my last attempt at trying to convince you that ffdshow is full of shit: plug in "--fps 29.97" into the Custom Command Line options in the More tab of the x264 codec configuration dialog.. that forces 29.97 output. It will not change anything because x264.exe uses the input fps as output fps.. but just so that you can sleep during the night. Or even better: try mp4box on the file.. here's the commandline: mp4box -info your-mp4.mp4. It'll tell you the properties of the streams.

Seriously though this is it for me. If you trust ffdshow over anything else, even common sense (muxing in audio, compare playlength and playback speed of source and encoded material), nobody will take you seriously around here.

[Ishan]

I can confirm ffdshow is often reporting false frame rate. I often get 25fps while the stream is in fact 23.976...

[Sharktooth]

Sounds like a nice app. Decided to give it a try. Downloaded all the appropriate appz's (inluding 7z) only to find out I'm not able to unpack X264CLI_rev270B_mmx.7z (not supported archive) Why do people insist on using this futile compression tool :(
Futile? It's the best compressor around... however if you watched the build changelog, you would have known i used 7zip 4.23 to compress the files...

[Sharktooth]

about the matrices

here's how a line of an 8x8 matrix looks in the reference format (jvt matrix):

6,10,13,16,18,23,25,27,

and here's one of your lines

6, 7, 8,10,12,14,16,18

You use a trailing comma at the end of each line for the 4x4 matrices (except for the last line), but none for the 8x8 matrices. So if you adapt your matrix to the standard format it'll work. The x264 parser might be more forgiving, MeGUI expects exactly the standard format.
I removed the trailing comma (it was a bug in my matrix editor) but i'll keep the alignment for better readability.
Hope it wont cause problems.

EDIT: ehr... megui still doesnt want to read it... :(

[Doom9]

I removed the trailing comma (it was a bug in my matrix editor) but i'll keep the alignment for better readability.Alignments won't cause problems, but I'm afraid you misunderstood.. your 8x8 matrix lack the trailing comma.. the default jvt matrix from the avc reference code has that trailing comma.. so my matrix editor looks for it and uses it as quantizer separator. Your 8x8 matrix looks as follows when read

1,2,3,4,5,6,7,8 9,10,11,12, 13, 14, 15, 16

then I separate the string by comma.. so these two lines turn into the following lines (quantizer separated by -)
1-2-3-4-5-6-7-8 9
10-11-12-13-14-15-16

and in the end I don't have all the 64 values as the value at the end of a line and the first of the subsequent value are combined.. and "8 9" cannot be parsed into an int directly. So quant = Int32.Parse("8 9"); throws an exception, which in turn leads to the "invalid quant" error message.

[Sharktooth]

...going to buy a pair of googles...

[Doom9]

I see that you've added the trailing comma. If you encounter any problem with my matrix editor please let me know.. I don't think it's a widely used feature and I may not have tested it enough.

[Sputnik776]

I'm trying to use MyGUI but I'm running into an error at a very basic level. I'm trying to open an avs file but get the AVIStreamGetFrameOpen failed error. The same avs file opens fine in both virtual dub 1.6.8 and wmp. Video file in question is using HFYU codec at 640x480. Script posted below.

# Created by AVSEdit
# Admin 6/14/2005
AVISource("c:\quake3sh.avi")

[berrinam]

Hello Sputnik776. Welcome to this forum.

I was able to reproduce your error after a bit of testing. While VirtualDub will not throw an error when opening an avs file without a YV12 decoder, VirtualDubMod will, and MeGUI will throw the AVIStreamGetFrameOpen error for the same reason. Try installing a YV12 decoder (ffdshow, and set Raw Video decoding to All supported in the VFW codec configuration; XviD should also work).

[Sharktooth]

I see that you've added the trailing comma. If you encounter any problem with my matrix editor please let me know.. I don't think it's a widely used feature and I may not have tested it enough.
will do ;)