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 ;)

[lesnick]

hello, i have the problems:
1) i cant use 1st pass cording x264 with mencoder: fps -1, time 0

Next job job4-1 is a video job. encoder commandline:
"E:\My things\Prog\meGUI\tool\mencoder.exe" "E:\vid\tg.avs" -ovc x264 -o NUL: -passlogfile "2pass.log" -x264encopts pass=1:bitrate=700:bframes=1:b_adapt:subq=1:no8x8mv:nob8x8mv:me=0
successfully set up video encoder and callbacks for job job4-1
----------------------------------------------------------------------------------------------------------
Log for job job4-1
----------------------------------------------------------------------------------------------------------
job job4-1 has been processed. This job is linked to the next job: job4-2
Next job job4-2 is a video job. encoder commandline:
"E:\My things\Prog\meGUI\tool\mencoder.exe" "E:\vid\tg.avs" -ovc x264 -passlogfile "2pass.log" -x264encopts pass=2:bitrate=700:bframes=1:b_adapt:i4x4 -o "E:\vid\gh\ged.264" -of rawvideo
successfully set up video encoder and callbacks for job job4-2
---------------------------------------------------------------------------------------------------------
Log for job job4-2
----------------------------------------------------------------------------------------------------------
The current job was aborted. Stopping queue mode

2) if i use B frames (when i don`t use b frames - all is O.K.) in AVC with mencoder i have file 0 kb:
Log for job job4-1
----------------------------------------------------------------------------------------------------------
job job4-1 has been processed. This job is linked to the next job: job4-2
Next job job4-2 is a video job. encoder commandline:
"E:\My things\Prog\meGUI\tool\mencoder.exe" "E:\vid\tg.avs" -ovc lavc -passlogfile "2pass.log" -lavcopts vpass=2:vbitrate=700:vmax_b_frames=2:vb_strategy=1:qpel:vqdiff=2:trell -o "E:\vid\gh\ged.m4v" -of rawvideo
successfully set up video encoder and callbacks for job job4-2
----------------------------------------------------------------------------------------------------------
Log for job job4-2

[mpeg4 @ 00A9C848]b_frame_strategy must be 0 on the second passCould not open codec.
FATAL: Cannot initialize video driver.
Cannot find codec matching selected -vo and video format 0x32315659.
desired video bitrate of this job: 700 kbit/s - obtained video bitrate: 0 kbit/s
----------------------------------------------------------------------------------------------------------
job job4-2 has been processed. This job is linked to the next job: job4-3
Next job job4-3 is a mux job. mp4box commandline:
"E:\My things\Prog\meGUI\tool\MP4Box.exe" -add "E:\vid\gh\ged.m4v" -fps 25 -new "E:\vid\gh\ged.mp4"
successfully set up muxer and callbacks for job job4-3
----------------------------------------------------------------------------------------------------------
Log for job job4-3

an exception ocurred when trying to read from stdout: Could not find file "E:\vid\gh\ged.mp4".
----------------------------------------------------------------------------------------------------------

[Doom9]

Let's start with number two: I see you're using the b-frame reduction mode, and the 2nd pass error message tells me all I need to know.
Looking at the mencoder manpage I found this:
vb_strategy=<0-1> (pass one only)It appears that I missed that one and add vb_strategy to first and second pass, causing your problem. I will fix this in the next version. For now just don't use the adaptive b-frame setting when using lavc.

As for your first problem, I had to consult the manpage again but I'm afraid that's my fault, too. The me=0 option is the culprit.. mencoder uses me=1-4

I guess the error message in both cases would be there, but doesn't have either the word error or anything else I identify as an error in it.. otherwise MeGUI should halt immediately and not start subsequent jobs.

[lesnick]

Sorry for oftop. Can you tell me, what you prefer: Mencoder or x264 for x264 cording, and why? And can you tell me where i can get x264CLI SSE/SSE2 ?

[Sharktooth]

x264 CLI (coz it's smaller and is usually more up to date - also, less code, less bugs...) and it already comes with SSE/SSE2. The MMX suffix is there to warn ppl it REQUIRES AT LEAST MMX to work.

[Doom9]

Mencoder or x264 for x264 cording, and why?It depends.. if you want AVI output, mencoder is clearly preferable. If you want mp4 output, x264 is more practical. Right now with the summer break this one doesn't matter much, but the reason I added support for another encoder in a mencoder GUI is because x264.exe is smaller and more up-to-date.. we're lucky to get one mencoder build a week, but the latest x264 compilations are out only hours after a new revision has been committed.

But I'm glad you're using mencoder.. you discovered two bugs.. not good for me but good for all the other users.

[lesnick]

Thanks for prompt replies. I shall wait the following release

[Doom9]

Alright, before I unleash the one click mode upon the world here's the list of caveats for the upcoming release:

You will need to create a profile for the audio and video codec you're going to use.

Set AR to Auto Detect in the one click window or make sure you select the proper one manually.

DVDs with MPEG audio might cause problems.. if you have one, please get me the stream info file. The same applies to LPCM tracks.

AVI output in the one click window has NOT!! been tested. Trying to use it might make your head explode.

The language selection seems to suffer from the fact that depending on where you bought a DVD, the language might be indicated using the native name (like Français), or the English name. Currently, MeGUI only supports English names. Whether or not it will be possible to support both is currently under investigation.

I moved around a LOT!! of tested code which inevitably might lead to problems. It is therefore crucial that those who try the one click mode and run into problem, try reproducing the problem using a "lesser" mode. So here's the how to for the various parts:

Opening a video source: start the dgindex project creator (control-d), and set it up just like you did set up the job in the one click window

DGIndex problem: same as above, try reproducing in the dgindex project creator window

DGIndex has run successfully but jobs are not properly created: try the AviSynth project creator (Control-A in the main gui). Open your d2v, check "autocrop", check "suggest resolution", check "on save close and load", then press save. This reproduces the steps that will be taken after running dgindex in the one click window.

Problem encoding/muxing: try using the auto mode using the same video and audio profile and the video/audio you got demuxed.

Since the code is the same, bugfixing will always be done first in the separate modules (easier scenarios).

[Doom9]

alright, the new release is out now.

[haubrija]

Ok... I'm laying myself out for ridicule... but I don't want anyone else to go through the same thing.

I set up my jobs doing an auto encode. Come back in the morning and my mp4 is way oversized. Plus it has no audio. I'm thinking what the hell?

Doom9... it might be a good idea to have megui perform a check so the user doesn't name both the video and audio output the same thing hence overwriting one of their jobs in the process. I realize this may be a little redundant and no one else may make my idiotic mistake...but just in case :)

btw love your tool. Keep up the good work.

[Doom9]

Doom9... it might be a good idea to have megui perform a check so the user doesn't name both the video and audio output the same thing hence overwriting one of their jobs in the process.Well, I could certainly do that.

As for the oversize I would need to see your logfile..

[leowai]

I set up my jobs doing an auto encode. Come back in the morning and my mp4 is way oversized.

I got the same problem. I used v0.2.0.8. Double checked that v0.2.0.9 also the same.

haubrija, you're more lucky than I am. I only realize this oversize problem on the process of 2nd pass. First pass takes me about 22hrs to complete on my P3 1GHz machine. :(

From the command line generated by MeGUI, I think MeGUI should replace the bitrate in the configuration panel (says 700 default) to what it calculated (says 626kps, with 128kps of AAC audio) in the AutoEncode mode.

It doesn't make sense since the audio size is already known, the "Automatic Encoding" dialog box also shows the required Avereage Bitrate to fit the target output size. Why the program doesn't allow to change the default 700 (in config panel) to the calculated bitrate? This option is remain in gray and unselectable. :(

This is a bug of MeGUI?

Thanks.

[Doom9]

It doesn't make sense since the audio size is already known, the "Automatic Encoding" dialog box also shows the required Avereage Bitrate to fit the target output size. Why the program doesn't allow to change the default 700 (in config panel) to the calculated bitrate? This option is remain in gray and unselectable. What do you mean by the config panel? There's no panel.. just dialogs. You can set any bitrate you want in a codec configuration dialog (this is the window you get when you press the config button in the main gui).. in auto-mode, this will be discarded... you cannot set a bitrate you are required to set a size and the bitrate is automatically calculated based on your configuration.. all that calculation info is actually part of the log (so where is it?). The way you're describing things, I'm wondering if you are using MeGUI correctly.. you get your jobs set up from the autoencode window, don't you? If you load one of those created jobs from the queue, you'll see that it has the bitrate that was calculated. It makes absolutely no sense to propagate a calculated bitrate to the codec configuration dialog.. once you enter the auto mode, you cannot reconfigure the codec and your last configured settings will be taken. The only way you can still change anything after clicking queue in the auto encode window is if you load a job from the queue, change something, and update the existing job.

A job has it's own configuration.. at the point you press queue, the currently active settings (minus bitrate in case of video in auto-encode or one click mode) will be plugged into that job. After it is in the queue, it has no reference whatsoever to what you see in the codec configuration dialog. You can change that all you want.. once a job is in the queue, you can only change it if you a) load it, b) modify it, c) update it. a & c require the appropriately named buttons in the queue tab.

Now if you're refering to the "Average Bitrate" textfield in the "Automatic Encoding" groupbox in the Automatic Encoding window... this is a bitrate preview and it does change if you change the file size. I'm quite confused why you think you need to specify a bitrate. You do not.. MeGUI is smart enough to calculate the bitrate for you, taking up to two audio tracks and up to 5 subtitle tracks automatically into account. And it has to be a hell of a coincidence if the average bitrate in the place I just mentioned is exactly 700 kbit/s. Try this: configure audio and video, go into one click mode, note the average bitrate shown. Then press cancel, press the X button to clear the audio, and go to the auto encode window again. Note that the average bitrate has changed.

[leowai]

Now if you're refering to the "Average Bitrate" textfield in the "Automatic Encoding" groupbox in the Automatic Encoding window... this is a bitrate preview and it does change if you change the file size.
Yes, I mean the Average Bitrate in "Automatic Encoding". I also noticed the change of video size and bitrate if an audio is included.
I'm quite confused why you think you need to specify a bitrate. You do not.. MeGUI is smart enough to calculate the bitrate for you, taking up to two audio tracks and up to 5 subtitle tracks automatically into account.
Yes, it does show the changes. However, when I double check with the command line in quequed jobs (3 pass), it shows the bitrate is equals to the one specified in the config dialog instead of the calculated one.

Following is my encoding steps:
1. Video: a. Set input AviSynth Script. (A movie windows shown).
b. Define the Video Output: AVC, MP4 and use "automated 3pass"
*If the bitrate is 800 here, I will get this in the command line!

2. Define Audio input and output @128kbps (assume no problems here).
3. Click on "AutoEncode", now I got the calculated is 626kbps (Video file size will be 593221KB). Assume no additional audio, subtitles and chapters to add. I click on "Queque" button.
4. Use text edit to open the corresponding job file *.xml. I found the command lines in jobs now specifying "--bitrate 800". This 800 is the bitrate in the config dialog rather than the calculated 626 (which takes audio size into account).

My problem is the MeGUI "AutoEncode" provide correct bitrate but when it generate the command line for jobs, it uses the bitrate in the config dialog! Wondering is this happen to you too, or it just happen to me only. :(

May be my steps in creating the jobs are incorrect.

And it has to be a hell of a coincidence if the average bitrate in the place I just mentioned is exactly 700 kbit/s. Try this: configure audio and video, go into one click mode, note the average bitrate shown. Then press cancel, press the X button to clear the audio, and go to the auto encode window again. Note that the average bitrate has changed.
"One Click Mode"="One Click Encoder" in the tools menu? If you refers to the "AutoEncode" button, see above.

Hope my explanation above is clear enough.

Thanks.

[Doom9]

Yes, it does show the changes. However, when I double check with the command line in quequed jobs (3 pass), it shows the bitrate is equals to the one specified in the config dialog instead of the calculated one.That is correct, if you are also encoding audio. Think about it for a second: when you're encoding audio, you do not know the audio size in advance... you can guess (which MeGUI does and shows you the results from that guess), but that guess is generally not very accurate, especially in VBR mode. So what happens is that the bitrate is left as configured in the configuration dialog, up until the point where all audio jobs have been completed. Then you'll see entries in the log in between the last audio and the first video job telling you the size of the audio stream(s) and which bitrate MeGUI recalculates for the video knowing how big your audio file(s) is/are. Sure I could add the calculated bitrate from the autoencode average bitrate field into all the jobs.. but what good will that do me if I have to recalculate the bitrate anyway? It's just an additional step that serves no purpose.

However, if you try without audio encoding, but do specify an audio track to be muxed, then you will immediately see in the log that MeGUI is calculating the video bitrate, and if you check the jobs, the bitrate will match the value the log tells you. If you're just muxing pre-existing audio files, MeGUI can calculate the video bitrate accurately right there. And if you combine the two scenarios (one pre-existing audio track, one to be encoded), you'll have a hybrid mode in which MeGUI reduces the desired size by the size of the pre-existing audio, and then recalculates again once your audio track to be encoded has been encoded.

So, once again.. if your output is oversized I need to see the log, plain and simple. You'll see MeGUI recalculating bitrates in there. The last version might lack some entries but you'll see the recalculation for sure as that's a part of the code I have not touched since the introduction of the 3 pass mode. And naturally I have checked that the bitrate recalculation works properly when I made those changes.

[leowai]

However, if you try without audio encoding, but do specify an audio track to be muxed, then you will immediately see in the log that MeGUI is calculating the video bitrate, and if you check the jobs, the bitrate will match the value the log tells you.
Yup. Check that if I mux the video with an existing audio, the command output to the jobs are correct. i.e. skip step 2 and add additional audio(s) at the end of step 3.

If you're just muxing pre-existing audio files, MeGUI can calculate the video bitrate accurately right there. And if you combine the two scenarios (one pre-existing audio track, one to be encoded), you'll have a hybrid mode in which MeGUI reduces the desired size by the size of the pre-existing audio, and then recalculates again once your audio track to be encoded has been encoded.
I see. This means the bitrate will be changed according to the output audio size. Just wondering, since job files are save after MeGUI closed, will MeGUI update the jobs when encoding if the jobs start after MeGUI is closed and re-open?

My senerio might be able to be explained. I've input an EXISTING audio as one of the encoding job. I then delete off the job later because only doing this I would notice the change of bitrate in Video to fit 1 CD correctly in the "AutoEncode" dialog. I simply thought that the shown bitrate in gray will be used in the encoding process. That is my first use of MeGUI and that's why I thought I was correct. Now I know I shouldn't do so :).

I've tried the encoding with auto3pass and it takes me 20hrs+ for a pass of 2hr DVD movie. I don't want to wait for another day and I think it might be good enough with a 2nd pass video. It is my mistake to remove the 3rd pass while the 2nd encoding is in process. I just thought that they are independent processes running in sequence. Not knowing that MeGUI is getting the jobs done in sequence with dependant of previous job in auto3pass.


I believe that is the cause where the video size is increased to an undesired size after I've remove the 3 pass from the encoding sequence.

Thanks for you well explanation about the details. Keep on the good job.

[berrinam]

it takes me 20hrs+ for a pass of 2hr DVD movieI'm not sure if you are aware, but the Turbo option in the x264 (if that's what you're using) settings will give a 3-5 times speed-up on the first pass with no noticeable quality loss.

[Doom9]

Just wondering, since job files are save after MeGUI closed, will MeGUI update the jobs when encoding if the jobs start after MeGUI is closed and re-open?It depends. As I said, the update is done when you have a series of jobs belonging together. If an audio job links to a video job, that's when the recalculation kicks in. The only time this isn't done is if audio encoding is manually aborted (but then if you redo it, it'll be done again switching from audio to the video job), or if there was an error in the audio job (same thing here, redoing the audio job will redo the calculation).

So, even if you stop encoding after audio encoding by pressing the stop button in the queue tab, the bitrate will still be updated.. but the next job won't be encoded.

So unless you manage to crash MeGUI just in the right moment, the recalculation will always be done.

With pre-existing audio, unless MeGUI crashes before adding the jobs to the queue, the bitrate will be in order.

I've input an EXISTING audio as one of the encoding job. I then delete off the job later because only doing this I would notice the change of bitrate in Video to fit 1 CD correctly in the "AutoEncode" dialog.Yes that is indeed your problem. Doing so you the knowledge about the audio stream away from MeGUI, and it no longer knew that it had to reduce the video bitrate prior to encoding the first pass. That is why there's a warning if you delete a single job of a series of jobs.. deleting one can cause undesired results.

What you should've done is just set up video, then check "add additional streams" and specify your audio stream in the mux window that pops up.. that way the size of the audio would've been taken into account and your video would've ended up having the size you wanted it to have.

[leowai]

I'm not sure if you are aware, but the Turbo option in the x264 (if that's what you're using) settings will give a 3-5 times speed-up on the first pass with no noticeable quality loss.
Thanks, heard that before but haven try on it yet.

Again, thanks doom9. I would try these out and let the machine runs for this coming weekends. I'll report again if the oversize problem presented. However, I don't think it will happen again. :)

[haubrija]

Doom9,

Just a point of clarification. I beleive it was oversized because it mp4box imported the video twice. It saw that they were the same name so it imported the video (named temp.mp4) and then what it thought was the audio but was actually the same file (temp.mp4). So I don't think the oversize was the fault of megui... just me.

[IgorC]

What version of xvid (1.0.3 or 1.1 beta 2) mplayer has?

[Doom9]

What version of xvid (1.0.3 or 1.1 beta 2) mplayer has?as far as I can tell from my limited experience with the mencoder source, you have to compile in the xvid sources to actually get xvid support. Thus it would be up to whomever compiles mencoder to include whichever version of the xvid sources he/she saw fit. I know it's devapi4 (so 1.x), but that's that.

[IgorC]

It would be great (at last for me) to see mplayer/MeGUI working with last Xvid 1.1 beta 2 Koepi's build.

[Doom9]

Xvid 1.1 beta 2 Koepi's build.that is a vfw build.. I'm not using vfw for encoding and I don't plan to ever change that. If you want vfw, look for tools automating avs2avi or the VfW codec (Gordian Knot, AutoGK, DVX, AVI.NET, etc).

MeGUI is a mencoder gui (hence the first two letters of the name).. it'll support what mencoder supports in terms of codecs.

[Doom9]

the new build for today is out. enjoy

[LigH]

I got a crash on exiting MeGUI 0.2.1.0a - I cleaned the directories for a fresh install of MeGUI and all required tools, created a few video profiles, and closed MeGUI. Here, .NET reported a failure not being able to access a file (unsupported path format). The reason must be: I used a colon in the profile description ("x264 HQ Auto3pass 16:9"). This would result in an invalid filename.

In case you still need a crash report, I saved it.

[Beave]

MeGUI is getting better and better. I like it. I'm still playing around with x264 and found your GUI very helpful.

A few suggestions from my side:

Could you add the output filename automaticly when opening an avs or an audio file? Like when I open mymovie.avs, the output box could already have the filename "mymovie-video.mp4" or something simmilar in the same directory. For autoencode it doesn't really matter how the immidiate files are called anyways.

I wouldn't mind seeing the commandlines in the mainwindow. Something like in the config windows, would be nice.

In the x264 config window when selecting automated 2-pass the shown commandline is a bit confusing. Could you maybe show both passes seperately on top of each other in the commandline?

The avsynth creator doesn't support resolutions higher than 720.

I would like to be able to define the noise-options with my favorite filters for avisynth myself somewhere.

I wouldn't mind seeing ProjectX support in MeGUI to fix the sync-issues in some of the TS files. Having this in the 1-click tool would be great, too.

Now something farfetched maybe, but I'll ask anyways:
When doing lots of testencodes with x264 with resolution up to 720p I noticed, that playback load depends on many parts. The more options you choose for x264 the higher the playback load (obviously!). The higher the bitrate, the higher the playback load. The more noisereduction filters in avisynth the lower the playback load. The last two things are hard to predict, but they change the playback performance quite a bit.
Maybe there is some way to guess or compute the expected playback performance?

Could you add a compressibility check with x264 to MeGUI? There is probably too little experience with this yet, but it would help to decide on the right options.

[superdump]

The higher the bitrate, the higher the playback load. The more noisereduction filters in avisynth the lower the playback load. The last two things are hard to predict, but they change the playback performance quite a bit.
Maybe there is some way to guess or compute the expected playback performance?
The higher the bitrate, the more data that has to be decoded, hence why it produces more load. Noise reduction filters make the video easy to encode, reducing the bitrate and so reducing playback load.

There is a standardised restriction on bitrate and other properties such that the video can be guaranteed to be playable on hardware capable of decoding this h.264 profile/level. I believe Doom9 is considering adding these profiles/levels to the gui.

[Doom9]

Could you add the output filename automaticly when opening an avs or an audio file?Yes, that would be no problem.

I wouldn't mind seeing the commandlines in the mainwindow. Something like in the config windows, would be nice.I don't see the point of that.. when you configure you can show the commandline and it won't change in the main window.. all that is added is input and output filenames..

In the x264 config window when selecting automated 2-pass the shown commandline is a bit confusing. Could you maybe show both passes seperately on top of each other in the commandline?Why is it confusing? You're configuring the second pass.. MeGUI does the rest when it's time. It's not like the first pass configuration is just out there.. it has to be generated manually and that code doesn't belong into the commandline generation.

The avsynth creator doesn't support resolutions higher than 720. Hmm.. I guess that is due to me setting a maximum for the updown control. I can change that in function of the video that is being opened.. I just wanted to prevent that people resize video to a size larger than the original.

I would like to be able to define the noise-options with my favorite filters for avisynth myself somewhere.And you can.. copy and paste them into the avisynth creator preview once you're done selecting from the available options in the GUI. I you want a full fledged AviSynth encoder, there are plenty of tools around for that and it just wouldn't be right copying other tools - I rather spend my time elsewhere.

I wouldn't mind seeing ProjectX support in MeGUI to fix the sync-issues in some of the TS files. Having this in the 1-click tool would be great, too.I have no idea what you mean by that.

Maybe there is some way to guess or compute the expected playback performance?I don't have a clue about that.. there's not even an attempt anywhere at such a thing.

Could you add a compressibility check with x264 to MeGUI? Asked and answered before. I don't know how a compcheck works so I need somebdy to lay it out for me. Give me the specs and I'll tell you if I can and will do it. But since it's not a feature I consider useful (I know it's in my guides but I have never personally used it for my own purposes, ever), all you can potentially expect from me in this matter is coding.. not the "figuring out how it works and specify the workflow" work. But bring it here and we'll see.

[haubrija]

Doom9,

I'm at work right now so I can't drop post a log, but I beleive I'm having a problem with the acc encoding. I want to encode to 5.1 aac but it seems to only be encoding in regular 2.0. I'm using mplayer for playback. In my audio options, I've been setting it for: 5.1, CBR 224, HE, leaving everything else default.

I have a soundstorm motherboard so I'd really love to get the 5.1 working. Is this a limitation of mplayer or a possible problem with megui. Thanks for any help.

[Doom9]

@haubrija: :logfile:

I believe Doom9 is considering adding these profiles/levels to the gui.those, yes, but that's for standalone players/hardware chips, not PCs.

[LigH]

To #275 ^:

Maybe this might help? http://www.codeproject.com/file/isvalidfilename.asp

[Beave]

I don't know how a compcheck works so I need somebdy to lay it out for me. Give me the specs and I'll tell you if I can and will do it. But since it's not a feature I consider useful (I know it's in my guides but I have never personally used it for my own purposes, ever), all you can potentially expect from me in this matter is coding.. not the "figuring out how it works and specify the workflow" work. But bring it here and we'll see.
OK, basicly it encodes a certain percentage of the video (usually 1-5%) with a fixed quant and generates the probable size for the whole movie. This way you can easily see how well compresseble it is when comparing to the final desired filesize.
I would suggest an extra window for that. There should be a box to put in the percentage for the comptest. A box for the desired filesize and for the bitrate (radio button style, so that only one can be selected). A config button to choose the x264 settings. Then you would take the input avs add a line to it (selectevery(300,15) for example, depending on the given percentage) and start the test.
Why is it confusing? You're configuring the second pass.. MeGUI does the rest when it's time. It's not like the first pass configuration is just out there.. it has to be generated manually and that code doesn't belong into the commandline generation.
When I select "turbo" it shows partly the settings of the second pass, but changes some settings to reflect the ones from the first pass.
I have no idea what you mean by that.
ProjectX is a software that takes input files like TS Transport Streams and demuxes them to .m2v and .ac3 or to another TS. While doing that it corrects errors to keep video and audio in sync.
I'd love to see a on click version for that. Taking a .ts file running it through ProjectX, then making a d2v file, then creating an avs with desired resolution and encoding it to .mp4. But maybe there isn't much demand for that?

[Beave]

The higher the bitrate, the more data that has to be decoded, hence why it produces more load. Noise reduction filters make the video easy to encode, reducing the bitrate and so reducing playback load.
When I encode a movie to a desired filesize the overall bitrate doesn't change. If the movie is more compressible the codec will just do a better job in compressing it. But how should that effect the playback performance? My guess is, it doesn't use that much "tricks" to encode so that playback doesn't need to decode all those "tricks". But shouldn't those "tricks" use the settings in the config? If I choose CABAC or 8x8dct or bframes playback should suffer, but not if the movie is less compressible. In that case it should only look worse, but use the same cpu load on playback.
Sorry for bringing this up in this thread. It only has slightly to do with MeGUI.

[Doom9]

When I select "turbo" it shows partly the settings of the second pass, but changes some settings to reflect the ones from the first pass.Which ones? I don't reacall turbo changing anything.. it shouldn't.

Don't you have a whole bunch of other things that need to be done with digital TV streams? Like cutting. That's definitely no job for MeGUI.. it's a video and audio encoding application.

[Beave]

I posted a screenshot. It shows different settings when selecting turbo in the commandline. Notice the subme=1 part. In the GUI there is number of reference frames = 3 selected.

[Doom9]

I posted a screenshot. okay.. I got it. This will actually happen in every codec that has turbo.. the problem is that in automated mode you have your second/third pass settings and the turbo flag that belongs to the first pass. When creating the jobs, the two are separated.. but that's only done when adding jobs to the queue. I'll remove the turbo flag for the commandline generation in the next version. if you set encoding mode to 2nd/3rd pass you'll see what you get in automated encoding mode (the two changes that are made when adding the job is setting the mode to second/third pass and removing the turbo flag)

[stax76]

To #275 ^:

Maybe this might help? http://www.codeproject.com/file/isvalidfilename.asp

thanks for the link, I just rewrote my routine based on this, in optimized basic it looks like this


Public Shared Function IsValidFileSystemName(ByVal name As String) As Boolean
For i As Integer = 0 To name.Length - 1
Dim charValue As Char = name.Chars(i)

Select Case charValue
Case """"c, "*"c, "/"c, ":"c, "<"c, ">"c, "?"c, "\"c, "|"c
Return False
End Select

If AscW(charValue) < 32 Then
Return False
End If
Next

Return True
End Function


translated to C# with Reflector:


public static bool IsValidFileSystemName(string name)
{
int num2 = name.Length - 1;
for (int num1 = 0; num1 <= num2; num1++)
{
char ch1 = name[num1];
char ch2 = ch1;
if (((((ch2 == '"') || (ch2 == '*')) || (ch2 == '/')) || ((ch2 == ':') || (ch2 == '<'))) || (((ch2 == '>') || (ch2 == '?')) || ((ch2 == '\\') || (ch2 == '|'))))
{
return false;
}
if (ch1 < ' ')
{
return false;
}
}
return true;
}


Microsoft has a internal method that don't follow this rules exactly, it throws an exception and can be seen with Reflector and accessed with Reflection:


GetType(System.IO.Path).InvokeMember("CheckInvalidPathChars", _
Reflection.BindingFlags.InvokeMethod Or _
Reflection.BindingFlags.NonPublic Or _
Reflection.BindingFlags.Static, _
Nothing, Nothing, New String() {"filename"})

[stax76]

Don't you have a whole bunch of other things that need to be done with digital TV streams? Like cutting. That's definitely no job for MeGUI.. it's a video and audio encoding application.


You've got a video preview and AviSynth script maker, these could be used to add cutting, it don't require much or sophisticated code I think. There was just a topic about a AC3 cutting tool that would be handy for this. Tools like ProjectX and Cuttermaran that are slow or don't support keys or lack features in general do the cutting job rather poor.

[berrinam]

Cutting can be done with the current apps that MeGUI requires -- video cutting is easy and frame-accurate with AviSynth (trim command), and BeSweet can cut audio, I believe.

[lesnick]

Help please - sometimes I need to recode very quickly, certainly I use mencoder for this purpose, prompt me, what options are desirable for the maximal speed. (though on mine celeron 1.7 it likely is ridiculous)

[LigH]

@ stax:

Great!

One of my most important problems with new programming languages being learned is: How is that function named, which will do what I want - and does it already exist at all, or do I have to write myself? Syntax can be learned in a snap, but the "word pool / vocabulary" is often sooooo different... you are lost without well referenced help.

[stax76]

Cutting can be done with the current apps that MeGUI requires -- video cutting is easy and frame-accurate with AviSynth (trim command)


I meant that our applications generate those Trim commands, I've done cutting in DVX with VirtualDub script and in AVSEdit with AviSynth Trim commands, in Stax Media Encoder both will be supported VirtualDub and AviSynth cutting.

@LigH

If you learn .NET I highly recommend to use Visual Studio 2005, the Express Beta Versions are free and work very well (until May 2006) and will be very cheap (50$) after that. They are designed for beginners. I use VS 2005 Express exclusively and many new features like generics extensively, there are tons of really cool new features though a beginner much likely struggles with the basics.

[Doom9]

Alright, so video cutting could be done easily.. and be analogue to zones. But what about audio? You cannot cut audio at an arbitrary position, it needs to be aligned with an audio frame or you'll get corrupt audio. And say we're using AC3 audio and incurr an almost 30ms delay (size of an audio frame) for each cut.. the audio would get way off base.

And I wasn't aware that besweet supported audio cutting.. I thought that was something for besplit.

I wrote my own filename code similar to the above, but it returns a string with a valid filename. I replace all invalid character by _<2 letter shortcut to the invalid char>_, so for instance * turns into _st_, < turns into _lt_, etc. I think it's reasonable to assume that users will not have a profile using such convention and another one using the invalid character so that there'll be two files named the same.

@lesnick: select 2 pass first pass, check turbo, check the commandline. Basically it's no MV options, subq 1, the lowest me method. But, if you use that for the second pass quality will be visibly degraded. Plus, perhaps you're using one of the other 3 codecs ;) <hint>it is important to tell us right when asking the question exactly what it is you want</hint>

[stax76]

Alright, so video cutting could be done easily.. and be analogue to zones. But what about audio? You cannot cut audio at an arbitrary position, it needs to be aligned with an audio frame or you'll get corrupt audio. And say we're using AC3 audio and incurr an almost 30ms delay (size of an audio frame) for each cut.. the audio would get way off base.

wave would be fine for my captures which AviSynth can Trim, other formats I have to investigate first

[lesnick]

meGUI 0.2.1.1 was crashed if push "config" for XVID
-----------------------------------------
See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.IndexOutOfRangeException: Index was outside the bounds of the array.
at MeGUI.CommandLineGenerator.generateXviDCommandline(String mencoderPath, xvidSettings xs, String input, String output)
at MeGUI.CommandLineGenerator.generateVideoCommandline(MeGUISettings settings, VideoCodecSettings vSettings, String input, String output)
at MeGUI.xvidConfigurationDialog.showCommandLine()
at MeGUI.xvidConfigurationDialog.dropDownBox_SelectedIndexChanged(Object sender, EventArgs e)
at System.Windows.Forms.ComboBox.OnSelectedIndexChanged(EventArgs e)
at System.Windows.Forms.ComboBox.set_SelectedIndex(Int32 value)
at MeGUI.xvidConfigurationDialog.set_CodecSettings(xvidSettings value)
at MeGUI.MeGUI.videoConfigButton_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)


************** Loaded Assemblies **************
mscorlib
Assembly Version: 1.0.5000.0
Win32 Version: 1.1.4322.573
CodeBase: file:///c:/windows/microsoft.net/framework/v1.1.4322/mscorlib.dll
----------------------------------------
MeGUI
Assembly Version: 1.0.2016.3771
Win32 Version: 1.0.2016.3771
CodeBase: file:///E:/My%20things/Prog/meGUI/MeGUI.exe
----------------------------------------
System.Windows.Forms
Assembly Version: 1.0.5000.0
Win32 Version: 1.1.4322.573
CodeBase: file:///c:/windows/assembly/gac/system.windows.forms/1.0.5000.0__b77a5c561934e089/system.windows.forms.dll
----------------------------------------
System
Assembly Version: 1.0.5000.0
Win32 Version: 1.1.4322.573
CodeBase: file:///c:/windows/assembly/gac/system/1.0.5000.0__b77a5c561934e089/system.dll
----------------------------------------
System.Drawing
Assembly Version: 1.0.5000.0
Win32 Version: 1.1.4322.573
CodeBase: file:///c:/windows/assembly/gac/system.drawing/1.0.5000.0__b03f5f7f11d50a3a/system.drawing.dll
----------------------------------------
System.Xml
Assembly Version: 1.0.5000.0
Win32 Version: 1.1.4322.573
CodeBase: file:///c:/windows/assembly/gac/system.xml/1.0.5000.0__b77a5c561934e089/system.xml.dll
----------------------------------------
bz6gxvzg
Assembly Version: 0.0.0.0
Win32 Version: 1.1.4322.573
CodeBase: file:///c:/windows/assembly/gac/system/1.0.5000.0__b77a5c561934e089/system.dll
----------------------------------------

************** JIT Debugging **************
To enable just in time (JIT) debugging, the config file for this
application or machine (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.

For example:

<configuration>
<system.windows.forms jitDebugging="true" />
</configuration>

When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the machine
rather than being handled by this dialog.
----------------------------------------------------

[Doom9]

wave would be fine for my captures which AviSynth can TrimBut the problem is that BeSweet doesn't read AviSynth scripts..

meGUI 0.2.1.1 was crashed if push "config" for XVIDWeird.. I don't recall changing anything since testing and it worked then but I can reproduce this now.

[Doom9]

OK, basicly it encodes a certain percentage of the video (usually 1-5%) with a fixed quant and generates the probable size for the whole movie. This way you can easily see how well compresseble it is when comparing to the final desired filesize.
I would suggest an extra window for that. There should be a box to put in the percentage for the comptest. A box for the desired filesize and for the bitrate (radio button style, so that only one can be selected). A config button to choose the x264 settings. Then you would take the input avs add a line to it (selectevery(300,15) for example, depending on the given percentage) and start the test.and then what? Using given settings I can predict how big the final movie is going to be.. but that's not what the comptest is about, is it? It's about picking the proper resolution given a certain target size.

[towerblocks]

meGUI 0.2.1.1 was crashed if push "config" for XVID
-----------------------------------------
See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.IndexOutOfRangeException: Index was outside the bounds of the array.
at MeGUI.CommandLineGenerator.generateXviDCommandline(String mencoderPath, xvidSettings xs, String input, String output)
at MeGUI.CommandLineGenerator.generateVideoCommandline(MeGUISettings settings, VideoCodecSettings vSettings, String input, String output)
at MeGUI.xvidConfigurationDialog.showCommandLine()
at MeGUI.xvidConfigurationDialog.dropDownBox_SelectedIndexChanged(Object sender, EventArgs e)
at System.Windows.Forms.ComboBox.OnSelectedIndexChanged(EventArgs e)
at System.Windows.Forms.ComboBox.set_SelectedIndex(Int32 value)
at MeGUI.xvidConfigurationDialog.set_CodecSettings(xvidSettings value)
at MeGUI.MeGUI.videoConfigButton_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)


************** Loaded Assemblies **************
mscorlib
Assembly Version: 1.0.5000.0
Win32 Version: 1.1.4322.573
CodeBase: file:///c:/windows/microsoft.net/framework/v1.1.4322/mscorlib.dll
----------------------------------------
MeGUI
Assembly Version: 1.0.2016.3771
Win32 Version: 1.0.2016.3771
CodeBase: file:///E:/My%20things/Prog/meGUI/MeGUI.exe
----------------------------------------
System.Windows.Forms
Assembly Version: 1.0.5000.0
Win32 Version: 1.1.4322.573
CodeBase: file:///c:/windows/assembly/gac/system.windows.forms/1.0.5000.0__b77a5c561934e089/system.windows.forms.dll
----------------------------------------
System
Assembly Version: 1.0.5000.0
Win32 Version: 1.1.4322.573
CodeBase: file:///c:/windows/assembly/gac/system/1.0.5000.0__b77a5c561934e089/system.dll
----------------------------------------
System.Drawing
Assembly Version: 1.0.5000.0
Win32 Version: 1.1.4322.573
CodeBase: file:///c:/windows/assembly/gac/system.drawing/1.0.5000.0__b03f5f7f11d50a3a/system.drawing.dll
----------------------------------------
System.Xml
Assembly Version: 1.0.5000.0
Win32 Version: 1.1.4322.573
CodeBase: file:///c:/windows/assembly/gac/system.xml/1.0.5000.0__b77a5c561934e089/system.xml.dll
----------------------------------------
bz6gxvzg
Assembly Version: 0.0.0.0
Win32 Version: 1.1.4322.573
CodeBase: file:///c:/windows/assembly/gac/system/1.0.5000.0__b77a5c561934e089/system.dll
----------------------------------------

************** JIT Debugging **************
To enable just in time (JIT) debugging, the config file for this
application or machine (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.

For example:

<configuration>
<system.windows.forms jitDebugging="true" />
</configuration>

When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the machine
rather than being handled by this dialog.
----------------------------------------------------


I get the same error,Using windows2000

[Doom9]

@towerblocks: lesnick already reported that bug and I confirmed it.. on the very same page nontheless.. please take a couple minutes to read posts since the last release for any issues that might already have been reported. Thank you.

[towerblocks]

@towerblocks: lesnick already reported that bug and I confirmed it.. on the very same page nontheless.. please take a couple minutes to read posts since the last release for any issues that might already have been reported. Thank you.

ok prob sorted thanks,But i've ran into another prob,it crashes on 2pass-1st pass,I hit the start button window appears then closes,It's probarbly
something i'm doing wrong here's the log.

Next job job3 is a video job. encoder commandline:
"C:\Megui.2.1.1\mencoder.exe" "C:\Documents and Settings\Administrator\Desktop\buf.avs" -ovc xvid -o NUL: -passlogfile "C:\Documents and Settings\Administrator\Desktop\Megui.2.1.1\logs\2pass.log" -xvidencopts pass=1:bitrate=963:max_key_interval=250:vhq=4:chroma_me:trellis:min_iquant=1:max_iquant=2:min_pquant=1:max_pquant=2:min_bquant=1:max_bquant=2:keyframe_boost=100:kfthreshold=1:kfreduction=20:chroma_opt:zones=1,q,1/60631,q,20
successfully set up video encoder and callbacks for job job3
----------------------------------------------------------------------------------------------------------

Log for job job3

Option xvidencopts: Unknown suboption zones

[LigH]

Your mencoder does not know the option "zones" - which version do you use?

[towerblocks]

Your mencoder does not know the option "zones" - which version do you use?

I've updated to the latest version,Works now thanks.

[parcival]

MeGUI seems great! I will use it as soon as I get back home!
It seems that it does all the things I am currently doing manually (DGIndex, 2-pass X.264, HE-AAC). I only hope it will support matroska container sometime since it is my favourite one, although it isn't really an issue since I can always do MP4->MKV easily with mkvmerge.

So :thanks: !

[Doom9]

the new release already supports matroska. If there will ever be matroska support in any other mode depends on a few things though.. whether it is possible to do all the operations mp4box does in one go (add various streams, assign language codecs, split), and if somebody can give me a good approximation of the container overhead for each codec type (in function of b-frames if that matters for matroska as well) and audio type (ac3, mp4, aac/mp4, and perhaps ogg as well).

[parcival]

You mean it supports Matroska as an input, right? Because from what I can tell only MP4 and AVI are supported as output.
MKVmerge is really a command line tool. The MKVmergeGUI is just an interface to create the command line for MKVmerge. So, the answer to your question is yes, it can create everything in one go, add streams, assign language, chapters, merging etc. MKVmergeGUI and MKVmerge are part of MKVtoolnix that has a lot more things in it than just what these two tools offer. All tools are command line so I believe that their integration to meGUI would be simple enough.
Before Matroska container I was using MP4. I made the switch to Matroska because back then it supported multiple audio and subtitle streams and it generally gave me less trouble with the players. Concerning container overhead I remember that it gave me smaller file sizes than MP4 for the same streams (I was using XviD and 5.1 HE-AAC, latter I switched to H.264). But you can find out more about this here:
http://www.matroska.org/technical/overhead/index.html

Besides the above the Matroska container is under the GPL, is free and it doesn’t have the legal limitations that MP4 tools might face in the future (or are already facing).

I have also a few notes for meGUI. I think, concerning the Avisynth script creation tool, that loading DGDecode.dll should be included by default in the beginning of the script (since it work always in pair with DGIndex). Its containing folder can be easily obtained since it is the same as DGIndex. Also, it would be a good feature to have the option to always include some specific script lines in the auto-created scripts. For example, I am always using Undot and Unfilter (www.trbarry.com) filters since they give me faster encodings with better quality. It would be good if there was a field where I could add these lines (or a way to point to a file containing them, for example filters.avs) and then they would be automatically added at the end of each auto-created script. Finally, the crop menu should have a preview just to give feedback of what you do.

Last, but not least, I couldn’t find a way through your tool to edit out parts of a movie that I do not want. For example, the titles feature is cool but sometimes you do not want titles at all, or you just want to encode a specific scene etc. It would be great if there was a movie edit screen just before opening-closing titles selection and similar to it, or even better similar to the VirtualDub edit abilities. I know that this can be done via the Avisynth script or the DGIndex but still there is no way to do it from inside meGUI and novice users might not know or think of how to workaround it.

Again, thanks for your great tool!

[LigH]

You mean it supports Matroska as an input, right?
No.

Doom9's MeGUI supports the fact, that the latest x264.exe revision is able to create H.264 video inside a Matroska container as output. So it supports ".mkv" as a valid file name extension for x264.exe - nothing else.

As input, it will still expect raw YV12 video.

[berrinam]

@parcival: A lot of what you ask for has already been asked for in this thread.
You mean it supports Matroska as an input, right? Because from what I can tell only MP4 and AVI are supported as output.Matrska is supported as output, not input, but only from AVC (x264).

All tools are command line so I believe that their integration to meGUI would be simple enough.To quote Doom9 from the MeGUI development thread, Well, human minds are very flexible. Code is not. It's a simple as that. Hinting that a certain feature would be easy, unless you actually know how the program in question works and having a clear idea of how to implement what you're asking for, is a little pretentious and not exactly how you want to motivate any programmer (it's like somebody telling you that the work you do all day could easily be done in half an hour, in other words you're slow an ineffective (and should thus be fired)).Matroska output will probably come somewhere in the future, but it is in no way simple.

Concerning container overhead I remember that it gave me smaller file sizes than MP4 for the same streams (I was using XviD and 5.1 HE-AAC, latter I switched to H.264).This is not true for H.264, I don't know about XviD.

Besides the above the Matroska container is under the GPL, is free and it doesn’t have the legal limitations that MP4 tools might face in the future (or are already facing).What legal limitations?

I think, concerning the Avisynth script creation tool, that loading DGDecode.dll should be included by default in the beginning of the script (since it work always in pair with DGIndex) Already been mentioned, and replied to, in this thread.

Also, it would be a good feature to have the option to always include some specific script lines in the auto-created scripts. For example, I am always using Undot and Unfilter (www.trbarry.com) filters since they give me faster encodings with better quality.Umm... not faster. This thread (http://forum.doom9.org/showthread.php?t=51181) has a comparison of speeds.

It would be good if there was a field where I could add these lines (or a way to point to a file containing them, for example filters.avs) and then they would be automatically added at the end of each auto-created script. Interesting idea, but I think it succumbs to the 80/20 rule.

Finally, the crop menu should have a preview just to give feedback of what you do.Huh? It already does.

Last, but not least, I couldn’t find a way through your tool to edit out parts of a movie that I do not want. Already suggested in this thread.

I know that this can be done via the Avisynth script or the DGIndex but still there is no way to do it from inside meGUI and novice users might not know or think of how to workaround it.What about audio cutting? That can't be done through AviSynth.

@edit: updated missing url link.

[Doom9]

Matrska is supported as output, not input, but only from AVC (x264).
In fact only using x264.exe.. mencoder won't work.

What legal limitations?Good question ;) Oh yeah, you have to pay patent fees for the MPEG-4 codecs as well if you use them commercially.. regardless of the container. Try selling videos online using XviD and Matroska.. Larry Horn will eventually get in touch with you just as he would (or an associate of his) if you put the video into the MP4 container.

[parcival]

Thanks for the quick replies.
I didn’t mean to offend anyone or his/her work. I know that programming is difficult since I am a programmer for more than twenty years. When I said that it looks "easy" to implement of course I didn’t mean in any way to pose myself as the super-programmer that finds anything easy. Many times things that I initially thought easy or simple as a programmer proved to be a real pain for me... Until you get down to the point of writing the code yourself you can never be sure. I only stated my personal opinion that it seems doable spending a reasonable amount of work. This was just an estimation that I shouldn’t have made and I am sorry if I offended anyone in any way.

Concerning the rest of the things I mentioned I am new to the thread and I didn’t have the time to look if they have been stated before. Again I am sorry for double posting.

My intention was to mention a few things that from my point of view would help improve an already great application. Of course the developer is free to do whatever he/she likes since it is his/her call and he/she is the ones spending precious time writing the code and developing a free application.

[berrinam]

@parcival: It's open-source and you are a programmer. Do you want to contribute?

[Doom9]

well.. if the assumption that mkvmerge behaves like mp4box, the muxing part itself is indeed not that complex.. but that's a big if. Getting mp4box to work was not as straightforward.. it took two attempts and the help of xtknight to get it done right. The rest won't be straightforward though.. it's not easy to handle different audio types that are are aren't valid for different containers, let the user switch output types and adjust input/output selections accordingly, calculate the bitrate differently taking into account the different overheads for different codec types and containers. MP4 is in fact in many ways a very straightforward container.. all I needed was 2 overhead values, be armed with the knowledge that the Nero AAC encoder takes MP4 container overhead into account, and that's it.

[parcival]

Yes, of course I want to contribute! That is why I also wrote such a long post in the first place. The problem is that I am working 10+ hours per day and I have little spare time left. In about two months though, I am planning a carrier change since I cannot handle so much work any longer. Then I will have a lot of time to work for the open source community, which is a dream I have for a very long time.
Till then all I have time for is a little bit of testing... :(

[Sputnik776]

Thanks to berrinam who pointed me to the vfw config when megui wouldn't load my script. That worked out perfect.

MeGui will load the .avs and preview the video as well as use mencoder to encode successfully.

However, when I change the encoder in the settings to be x264 it doesn't allow me to encode. Both the script and error are show below. I've installed both the cli and vfw v273 sharktooth builds from this forum category.

Any help would be greatly appriciated.

script:
# Created by AVSEdit
# Admin 6/14/2005
AVISource("c:\test.avi")
Video is HFYU codec at 30fps 640x480

error:
Next job job2 is a video job. encoder commandline:
"C:\Program Files\x264\x264.exe" --bitrate 700 --analyse p8x8,b8x8,i4x4 --progress --no-psnr --output "C:\test.mp4" "C:\test.avs"
successfully set up video encoder and callbacks for job job2
----------------------------------------------------------------------------------------------------------

Log for job job2

avis [error]: unsupported input format (DIB )
desired video bitrate of this job: 700 kbit/s - obtained video bitrate: 0 kbit/s
----------------------------------------------------------------------------------------------------------

[leowai]

Sputnik776,
I believe adding this at the end of your script will solve your problem.
ConvertToYV12()

Would it be nice for Sharktooth to include some information about using the AVS script as the input to x264 client in the x264 download page? I think it's useful for the newbies, since this question has been asked over and over again.

[Sputnik776]

Sorry for my noobish-ness... That did the trick leowai. Doing a fresh install on 2 different machines, both the vfw decoder change and this script addition were needed before things would work. I would imagine others like myself would benefit from that info being put in a faq or something.

Thanks for your patience.

[Doom9]

well, if I weren't so busy developing I'd have written an FAQ already. But you can't have both at the same time.

[Doom9]

alright, the bitrate calculator is done. enjoy

[roror]

is there a way to use ISOs in this tool, without using dvd decryptor to extract individual VOB files first?

[Doom9]

is there a way to use ISOs in this tool,No.. that would be adding a load of other potential issues that I really have no time for. That's stuff for a future Recode killer using x264 and xvid (which may or may not ever see the light of day).

[Rasi]

question:

why dont u offer the ability to use vorbis as audio?
xvid and ogg in an mkv container is quite common.... so it would make sense (at least for me ;))

[roror]

No.. that would be adding a load of other potential issues that I really have no time for. That's stuff for a future Recode killer using x264 and xvid (which may or may not ever see the light of day).
OK. Thanks.

[Doom9]

why dont u offer the ability to use vorbis as audio?Umm.. I guess you are not familiar with the changelog, are you? mkv output is video only directly from x264.exe (and only from that).. there's no muxing going on anywhere.. MeGUI cannot mux MKV so it has no way of muxing anything into an MKV. And it is after all an MPEG-4 tool.. not a Matroska tool.. you won't even find the word Matroska in the program's description.

[Beave]

Thanks for putting in the target filename when opening an avs file. Now to make it perfect I would have an additional request:
When I open the dialog box to choose another filename, I would like to see the current filename prewritten in that dialog as well. It would also be nice if in the main window the textfield could be writable so that I could change the filename directly.
These are merely some small suggestions. Your program is already great as it is.

I would love to use MEGui for XVID as well (all the important options are nicely put on one page), but I'm missing the option to choose a custom matrix there. Maybe it has been asked and aswered before, but I couldn't find it using search. My guess is that mencoder probably does not support it.

Could you add 1/6 DVD to the Automatic Encoding DropDownBox as well, please? That would be great.

[Doom9]

It would also be nice if in the main window the textfield could be writable so that I could change the filename directly. I have disabled that a long time ago because people used it to screw up the process.. putting extension that don't match the chosen output type, putting non existing paths, that kind of things.

I would like to see the current filename prewritten in that dialog as well.What good would that do? I mean if you're not happy with the filename you're getting automatically, you are likely to change everything, are you not?

My guess is that mencoder probably does not support it.
That is correct. All codec options mencoder supports are listed here: http://mplayerhq.hu/DOCS/man/en/mplayer.1.html#CODEC%20SPECIFIC%20ENCODING%20OPTIONS%20(MENCODER%20ONLY)

[leowai]

Doom9,
Could you make MeGUI updates (saves) the job once it is completed or done?

This is because if the OS crash (or restart) while MeGUI is still running, MeGUI will show all jobs are in waiting status after restarted. As a result, I think it's quite reasonable to update (save to disk) what ever job which has been just completed and so that important information could be retained even if MeGUI terminated unexpectedly.

It will be wonderful if the program can provide the pause and continue function when conversion is in process like Nero Recode has. This requires the support from the encoder client? If conversion is pausable, the long time conversion will be more flexible as sometimes you need more CPU resource to work on other things. This probably also able to let some hot running CPU rest for a while. :)

=========================================================
Lastly, I've a dream. I'm dreaming about the conversion in future could be stopped (and the conversion status are saved). You can do a restart or shutdown you machine. Then, the saved conversion will be able to continue from where it stopped just like we resume a halfway downloaded file from http. If this is workable, conversion of a DVD on low speed machine will never be a painful job. May be this requires the support of data segmentation/slices? x264 support slices, isn't it?
=========================================================

[mezzanine]

It will be wonderful if the program can provide the pause and continue function when conversion is in process like Nero Recode has.

It doesn't work on Recode, only thing that pauses is the progress bar.

[Doom9]

well.. depending on how the various encoders handle reading from stdout/stderr, a pause function would effectively be possible. I'm quite certain it will not work for mp4box, but it might work for the audio and video encoders. But should my tests show that it's indeed possible, I expect a couple cases of beer to implement this as it's a feature I really have no use for. And resuming will definitely not be possible.. that's not under my control.

Although, you're really not making a good case for this feature:
If conversion is pausable, the long time conversion will be more flexible as sometimes you need more CPU resource to work on other things. This probably also able to let some hot running CPU rest for a while.If your machine runs too hot, you need a better cooling solution, and with low priority, another application using more resources is no problem. I was playing HL2 and NFS while encoding for the codec comparison. While encoding was dog slow, it still worked.

Could you make MeGUI updates (saves) the job once it is completed or done?

This is because if the OS crash (or restart) while MeGUI is still running, MeGUI will show all jobs are in waiting status after restarted. As a result, I think it's quite reasonable to update (save to disk) what ever job which has been just completed and so that important information could be retained even if MeGUI terminated unexpectedly.That, too is a weak argument. If MeGUI is stable (which I think since I'm not having any open bug reports), if your PC crashes, it's normal that you lose information.. and machines really shouldn't crash at this day and age. If a stable machine crashes once a year that's one too many times, and anything above that should give you reason to worry.

[akupenguin]

That is correct. All codec options mencoder supports are listed here: http://mplayerhq.hu/DOCS/man/en/mplayer.1.html#CODEC%20SPECIFIC%20ENCODING%20OPTIONS%20(MENCODER%20ONLY) On that page I see:
quant_intra_matrix=<filename> Load a custom intra matrix file. You can build such a file with xvid4conf's matrix editor.
quant_inter_matrix=<filename> ...

[Doom9]

hmm.. that must be very new. Just last week I went over the manpage and implemented what there was to be implemented.

One thing though, since : is the option separator in mencoder, is using an absolutel windows path even possible (and does it require "s)?

I'm dreaming about the conversion in future could be stopped (and the conversion status are saved). You can do a restart or shutdown you machine. Then, the saved conversion will be able to continue from where it stopped just like we resume a halfway downloaded file from http. If this is workable, conversion of a DVD on low speed machine will never be a painful job. May be this requires the support of data segmentation/slices? x264 support slices, isn't it?Slices won't do you any good here.. they don't extend over the movie and you wouldn't know how big they are either. To resume encoding, you need to have all the encoder parameters at the time of the stop.. and no encoder offers even remotely that capability.

And slow PCs and video encoding just don't mix, and it never will. There will always be a newer format that requires even more computing power so you'll always have to upgrade.. or be content with lower quality compression at higher speeds. I'm sure MPEG-1 encoding is okay on your box ;)

[berrinam]

Well, x264 can be stopped and restarted later, using the --seek command.

[Doom9]

hmm.. well.. at first thought it would take quite a bit of work to get this done. Plus, how do you figure out where you have to seek to? It works if you limit the number of frames of the output and let it run till the end, but what do you do if the user aborted at some point, killing x264.exe rather than let it exit gracefully? Worst case, the stats file might end up in an inconsistent state. When I wrote the video encoder, I tested the abort functionality a couple times and ended up getting incomplete lines from the stdout/stderr.. if that happens to the statsfile as well, what will the encoder do?

[haubrija]

Searched for this but couldn''t find the answer...

What type of chapter file do you specify in DVD Decryptor to use in MeGui? There's about twenty different types and I tried a couple and they didn't work.

Thanks

[Doom9]

You need to use the Ogg chapter format.

[ookzDVD]

Can someone help me with the profile?
I really need a good one for XVID - 1 CD and X.264 - 1 CD. TIA.

[Doom9]

Well, good is a point of view question really. Here's what I use for high quality, but not insanely slow x264 encoding (starting with the megui default)
high profile
2 b-frames, adaptive
3 reference frames
RDO subpixel refinement
All macroblock options enabled
weighted prediction

And 2 threads if I would finally get my X2 back.

You may want to play with the alpha and beta deblocking values a little but that's really a personal thing.. some people prefer their video smooth, other prefer details and can live with a few blocks.

As far as XviD goes, I'm using the VfW defaults there as much as possible so there are less changes

Keyframe interval should be 10 times your framerate
leave number of b-frames at 2, motion search precision at 6, vhq mode at 1
enable vhq for b-frames, qpel
and default values for the rest

Keep in mind though.. that is my personal opinion and you'll find a lot of people who'll suggest something else.. it's up to you to decide what really works.

[Beave]

Doom9, if you get your X2 machine back, could you test how your x264/aac.mp4 settings would playback a 1280x720 HD movie? I just wonder how fast/new a computer I need to have a decently save cpu usage.

[ookzDVD]

@Doom9,

Thank you for the profile, I really apreciate that.

Btw,
I just forgot to tell you about the MeGUI,
Which Avisynth should be used ?
I used v2.55 and I got error while run "One Click",
when I read the "avs" manually, I think the script is missing the LoadPlugin command. :(

[berrinam]

@ookzDVD: Yes, Avisynth 2.55 is fine. I presume you mean the dgdecode.dll plugin? As said before, this needs to be put in the avisynth plugins directory.

[haubrija]

Doom9,

Found a small bug I beleive using 0.2.1.4. I set up my job to do AVC with AAC in an MP4. Click Autoencode for 1 cd. Now when I change the name of my muxed output, it changes the extension to avi even though I want mp4. I'm assuming this is in name only and the resulting file plays back fine in mplayer. Here's my log in case you need it.

----------------------------------------------------------------------------------------------------------
Next job job2-1 is an audio job. besweet commandline:
"C:\MP4 Encoding\BeSweetv1.5b29\besweet.exe" -core( -input "D:\c2 AC3 T01 2_0ch 192Kbps DELAY 0ms.ac3" -output "D:\audio.mp4" -logfile "besweet.log" ) -azid( -s dplii -c normal -L -3db ) -bsn( -2ch -cbr 160 -codecquality_high -aacprofile_he ) -ota( -d 0 -g max )
successfully set up audio encoder and callbacks for job job2-1
----------------------------------------------------------------------------------------------------------

Log for job job2-1

besweet: "C:\MP4 Encoding\BeSweetv1.5b29\besweet.exe" -core( -input "D:\c2 AC3 T01 2_0ch 192Kbps DELAY 0ms.ac3" -output "D:\audio.mp4" -logfile "besweet.log" ) -azid( -s dplii -c normal -L -3db ) -bsn( -2ch -cbr 160 -codecquality_high -aacprofile_he ) -ota( -d 0 -g max )

BeSweet v1.5b29 by DSPguru.
--------------------------

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

[00:51:54:720] |

SR: 48000, Table idx: 6 - start 12, stop 8
SR: 48000, Table idx: 6 - start 12, stop 8
[00:51:54:720] Finalizing...
[00:51:54:720] Conversion Completed !

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

----------------------------------------------------------------------------------------------------------
job job2-1 has been processed. This job is linked to the next job: job2-2
this series of jobs starts with an audio job and is followed by regular twopass video jobs
The audio job is named job2-2 the first pass job2-2 and the second pass job2-3
The second pass job has a desired final output size of 734003200 bytes and video bitrate of 6729 kbit/s
Third pass job found: job2-4
The audio file size is 62597955 bytes
Setting the desired bitrate of the subsequent video jobs to 1722 kbit/s
Next job job2-2 is a video job. encoder commandline:
"C:\MP4 Encoding\x264.exe" --pass 1 --bitrate 1722 --stats "2pass.log" --bframes 2 --no-b-adapt --b-pyramid --subme 1 --weightb --analyse none --me dia --progress --no-psnr --output NUL "D:\Carnivale.avs"
successfully set up video encoder and callbacks for job job2-2
----------------------------------------------------------------------------------------------------------

Log for job job2-2

avis [info]: 640x352 @ 23.98 fps (74680 frames)
x264 [info]: using cpu capabilities MMX MMXEXT SSE 3DNow!
x264 [info]: slice I:445 Avg QP:11.52 Avg size: 34379
x264 [info]: slice P:25109 Avg QP:12.57 Avg size: 14673
x264 [info]: slice B:49126 Avg QP:14.19 Avg size: 5740
x264 [info]: slice I Avg I4x4:71.6% I8x8:0.0% I16x16:28.4%
x264 [info]: slice P Avg I4x4:0.0% I8x8:0.0% I16x16:15.6% P:68.2% P8x8:0.0% PSKIP:16.2%
x264 [info]: slice B Avg I4x4:0.0% I8x8:0.0% I16x16:2.9% P:51.6% B:12.6% B8x8:0.0% DIRECT:16.9% BSKIP:16.1%
x264 [info]: kb/s:1709.8

Actual bitrate after encoding without container overhead: 21423.59

----------------------------------------------------------------------------------------------------------
job job2-2 has been processed. This job is linked to the next job: job2-3
Next job job2-3 is a video job. encoder commandline:
"C:\MP4 Encoding\x264.exe" --pass 3 --bitrate 1722 --stats "2pass.log" --ref 3 --bframes 2 --no-b-adapt --b-pyramid --subme 6 --weightb --analyse all --8x8dct --progress --no-psnr --output "D:\video.mp4" "D:\Carnivale.avs"
successfully set up video encoder and callbacks for job job2-3
----------------------------------------------------------------------------------------------------------

Log for job job2-3

avis [info]: 640x352 @ 23.98 fps (74680 frames)
x264 [info]: using cpu capabilities MMX MMXEXT SSE 3DNow!
mp4 [info]: initial delay 250 (scale 2997)
x264 [info]: slice I:445 Avg QP:11.58 Avg size: 32296
x264 [info]: slice P:25109 Avg QP:11.93 Avg size: 14553
x264 [info]: slice B:49126 Avg QP:13.79 Avg size: 5917
x264 [info]: slice I Avg I4x4:26.5% I8x8:46.3% I16x16:27.2%
x264 [info]: slice P Avg I4x4:5.2% I8x8:8.1% I16x16:3.6% P:53.0% P8x8:12.3% PSKIP:17.8%
x264 [info]: slice B Avg I4x4:1.7% I8x8:2.1% I16x16:1.0% P:27.4% B:15.9% B8x8:9.1% DIRECT:9.5% BSKIP:33.3%
x264 [info]: 8x8 transform intra:46.4% inter:26.1%
x264 [info]: kb/s:1722.1

Actual bitrate after encoding without container overhead: 21576.50
desired video bitrate of this job: 1722 kbit/s - obtained video bitrate: 1724.44663661746 kbit/s
----------------------------------------------------------------------------------------------------------
job job2-3 has been processed. This job is linked to the next job: job2-4
Next job job2-4 is a video job. encoder commandline:
"C:\MP4 Encoding\x264.exe" --pass 3 --bitrate 1722 --stats "2pass.log" --ref 3 --bframes 2 --no-b-adapt --b-pyramid --subme 6 --weightb --analyse all --8x8dct --progress --no-psnr --output "D:\video.mp4" "D:\Carnivale.avs"
successfully set up video encoder and callbacks for job job2-4
----------------------------------------------------------------------------------------------------------

Log for job job2-4

avis [info]: 640x352 @ 23.98 fps (74680 frames)
x264 [info]: using cpu capabilities MMX MMXEXT SSE 3DNow!
mp4 [info]: initial delay 250 (scale 2997)
x264 [info]: slice I:445 Avg QP:11.85 Avg size: 31471
x264 [info]: slice P:25109 Avg QP:12.01 Avg size: 14498
x264 [info]: slice B:49126 Avg QP:13.90 Avg size: 5955
x264 [info]: slice I Avg I4x4:25.6% I8x8:49.1% I16x16:25.3%
x264 [info]: slice P Avg I4x4:5.1% I8x8:8.2% I16x16:3.5% P:52.7% P8x8:12.2% PSKIP:18.3%
x264 [info]: slice B Avg I4x4:1.7% I8x8:2.0% I16x16:1.0% P:26.7% B:15.9% B8x8:9.7% DIRECT:8.9% BSKIP:34.2%
x264 [info]: 8x8 transform intra:46.7% inter:26.1%
x264 [info]: kb/s:1722.3

Actual bitrate after encoding without container overhead: 21579.57
desired video bitrate of this job: 1722 kbit/s - obtained video bitrate: 1724.69168238157 kbit/s
----------------------------------------------------------------------------------------------------------
job job2-4 has been processed. This job is linked to the next job: job2-5
Next job job2-5 is a mux job. mp4box commandline:
"C:\MP4 Encoding\mp4box.exe" -add "D:\video.mp4" -add "D:\audio.mp4";lang=eng -chap "D:\Carni2\VTS_01 - Chapter Information - OGG.txt" -fps 23.976 -new "D:\Outside Damascus.avi"
successfully set up muxer and callbacks for job job2-5
----------------------------------------------------------------------------------------------------------

Log for job job2-5

IsoMedia import - track ID 1 - Video (size 640 x 352)
IsoMedia import - track ID 1 - Audio (SR 48000 - 2 channels) - SBR AAC
IsoMedia import - track ID 2 - media type odsm sub-type MPEG
IsoMedia import - track ID 3 - media type sdsm sub-type MPEG
Saving Outside Damascus.avi: 0.500 secs Interleaving


Let me know if you need any more info.

[berrinam]

Yes, the file filter in AutoEncodeWindow.muxedOutputButton_Click is currently "MP4 Files (*.mp4)|*.avi"

[Doom9]

do you set the extension to avi (by selecting it from the dropdown or typing it) or was it changed automatically (and if so exactly at which point, what's the content of the file open dialogue when you press OK)?

[berrinam]

@Doom9: It's a bug, see my post just before yours.

[Doom9]

@Doom9: It's a bug, see my post just before yours.I saw that.. just trying to find out if something else is wrong or if it's merely a matter of the dialog filter.

[haubrija]

Doom9,

I didn't set it to .avi nor did i type it. It states "mp4 files" in the "save as" dialog box when you go to save but other .avi files I had in the same directory are visible when they should not be (as it should only be showing mp4 files).

[HookedOnTV]

I've got an encode that is acting posessed when it tries to mux at the end. Did a two pass xvid encode to mp4. It seems to have finished creating the m4v file successfully (no errors and sized as desired). When it tried muxing the m4v to mp4 the "video data" field that usually runs up through the file flashes between 0kb and 63316kb. A randomly named file with no extension is created in the root of the c: and just grows until there is no more free disk space (ate aroung 18gb). Abort the job and the file disappears. Tried doing a fresh mux job with the m4v file and the audio file with the same behavior. Was using 0.2.1.3, tried 0.2.1.4.

Going to try mp4box from the command line and see if it works.

[Doom9]

@HookedOnTV: That does sound more like an mp4box problem.. mp4box is writing that huge file (it's the way it works.. writes a temp file to the root of the target directory using a random name). Please let me know the results when you run mp4box with the same commandline manually.

[leowai]

Doom9,
I've some questions about the "--me" (ME Algo.) switch for x264 client in MeGUI.

1. MeGUI uses "--me dia" for 1st pass in turbo mode. Does this effect the accuracy if different ME algo. is used in the subsequence passes for automated 2passes and automated 3passes?

2. MeGUI seems to generate the command line as "--me" (without any ME algorithm specified) instead of "--me dia" if diamond (dia) ME algorithm is used.

For muti-passes: If turbo mode is selected, it's ok for the 1st pass (it shows "--me dia"), but I found this problem occurs in the command line of 2nd and 3rd pass (from the job list).

Is this a MeGUI bug?

[HookedOnTV]

Problems from the command line as well. When it does the "importing video" the counter goes all the way to 200/100 then starts over all the while building the temp file. An encoding job on an entirely different pc is doing the same thing. One pc has version 0.3.0.7 (Celtic Druid) and the other has 0.3.1 (Sharktooth) of mp4box.

[Doom9]

Does this effect the accuracy if different ME algo. is used in the subsequence passes for automated 2passes and automated 3passes?No, not noticeably. PSNR loss from using the full turbo settings (not only me.. a lot more is influenced by the turbo switch) is negligible.

MeGUI seems to generate the command line as "--me" (without any ME algorithm specified) instead of "--me dia" if diamond (dia) ME algorithm is used.
I'm afraid that's a bug

Problems from the command line as well.Then I'm afraid you need to open a thread in the container forum as it's not a MeGUI problem.

[HookedOnTV]

One last question before heading to the container area... is there a possibility the m4v is bad? I tried using mp4info on it and it says it can't open it. Is there a way to verify the file?

[leowai]

HookedOnTV,
Since you can't extract the information using mp4box, I afraid you did some non-standard ways to create such mp4 container with XviD codec.

I did mux x264 video (using native mp4 output) with HE-AAC (mp4), subtitles, chapters into 700MB mp4 without any problem.

As suggested by Doom9, you should to open a new thread, discribes the steps in details how your mp4 container with XviD codec is created.

[Negi]

Is there any way to make megui directly mux matroska?

Edit: HookedOnTV, if you update to mp4box 0.4x cvs versions, the no-extension file problem is gone.

[berrinam]

Matroska muxing in MeGUI should probably be coming very soon (I wrote most of the required code a few days ago). Anyway, it is based on mkvtoolnix, so why don't you just use the (better) gui for mkv muxing from them?

[Negi]

It's not so much that i can't use mkvmerge fine right now, it's just that it's less steps to have the muxing done directly in MeGui and less to worry about.

[Emp3r0r]

@Doom9: can you add avisynth (w/dgdecode.dll in plugins dir) to the list of required tools at beginning of thread? Also, xvid or ffdshow or something that supports yuv output colorspace is also required.

[Doom9]

@Emp3r0r: done. I also mentioned the remaining dll placement necessities. I should really write an FAQ one of these days.. but even I feel the summer time and rather do something else than writing or coding.

[sillKotscha]

Hi doom9,

here are just 2 observations I made on my pc...

under "tools" we have the option to create a *.d2v file. First input choice is a vob file and we can choose a *.mpg file as well. But if I load a *.mpg file, e.g. an edited, formerly DVB-T (*.pva) file MeGUI asks for the info file generated by DVD Decrypter. But for obvious reasons it won't be there ;)

Nevertheless I'm able to choose that *.mpg, choose the destination and DGIndex starts to work after "prepare" is pushed.
But after the d2v file is generated I can't close that window anymore to go back to the "main-settings" screen. All I can do is to kill the exe by using the taskmanager. All other tools/settings work flawless.

and a very strange behaviour concerning x264.exe:

I can do all the settings I want to and of course put the job(s) into queue manager. If I try to start the job list (e.g. automated 3pass) x264.exe starts each job just for a millisecond and closes itself. A 0 byte file is generated. That won't happen with MEncoder.
To circumvent that behaviour I've created a sub-folder and putted x264.exe in that folder (named tools with all other programs, BeSweet, MEncoder, etc.).
And now it works :) If x264.exe is back in the same folder as MeGUI.exe is, than it is again as described. Strange, hu?!

But as I told that has happend only on my machine. Maybe someone else made the same observation as me...

cheers Sill

P.S.: thanks for that very nice piece of work!! It is a pleasure to encode with it. Very nice surface, clean and easy to use. Just great!!

[Doom9]

Nevertheless I'm able to choose that *.mpg, choose the destination and DGIndex starts to work after "prepare" is pushed.
But after the d2v file is generated I can't close that window anymore to go back to the "main-settings" screen. All I can do is to kill the exe by using the taskmanager. All other tools/settings work flawless.
Do you have a short mpg with which I could reproduce that?

Strange, hu?!Well.. you got a log, don't you?

[sillKotscha]

Do you have a short mpg with which I could reproduce that?

sure, but not today... tomorrow I'll upload a file.

Well.. you got a log, don't you?

well, I do but I solved it using a little detour ;) for me that's no more a problem... for the coder - I'll uplaod the log as well.

Have a nice eve and thanks in advance.

Cheers Sill

[Slogra]

I can't get the aac encoding to work. I've put the aac.dll and aacenc.dll in the besweet folder, but it just skips the audio encoding all the time.
Aac.dll is used for stereo files and aacenc.dll for 5.1 files, is that correct?
I've tried stereo and 5.1 aacs but neither works. I downloaded aacenc from a p2p program cause i couldn't find it anywhere else, so that might be the problem.

[Doom9]

I downloaded aacenc from a p2p programI don't know if that is your problem but you've said the magical word that will ensure that nobody is allowed to help you.

[Slogra]

Oops, i thought that aac.dll was the nero encoder for stereo stuff and aacenc.dll some freeware pystel thingy that encodes to aac 5.1

[sillKotscha]

Do you have a short mpg with which I could reproduce that?

sure, but not today... tomorrow I'll upload a file.

ok, not really "tomorrow" but today... I hope it will help you.
I tried different edited pva-files (demuxed with projectx, cut and multiplexed (by mplex) with cuttermaran 1.65 (and versions below) - HCEnc working behind. All mpg files end up with the same problem... as described

... about the log.file - sorry, no current logfile available. Some kind of magic has happend ;) I tried to reproduce the problem to send you an up to date log with my mentioned problem - now I can't reproduce it... it just works, even with x264.exe in the same folder as MeGUI is. Don't mind - now I got a subfolder as I said and all is working one way or the other.

'nuff headache :)

Thanks in advance

Sill

P.S.: the *.mpg file (http://rapidshare.de/files/3291526/cut.mpg.html)

[Doom9]

the new version is out. Here are the release notes:

For starters let me say that this is the last time any software of mine will ever support multiple containers. It is a HUUUUUUGE headache to accomodate all possibilities. I love the simplicty of MP4.. MPEG-4 video, AAC audio, and thats' it. No huge multi-level if,then,else and switch statements, and a straightforward bitrate calculation (it was hard enough to get the darned window to work with one codec.. those who can read the code will surely appreciate the feeling).

I labelled this alpha because there's a lot of things untested. I never tested the one click window, never tested the new snow options and snow in mkv, and a bunch of other things. Hence, I left the old release up for download just in case.

The mkv bitrate calculation is ugly and may not be terribly accurate. I figure audio should be okay, but video poses a major problem as it requires the knowledge of how many I, P and B frames you get, BEFORE encoding your video. For more info on Matroska bitrate calculations, please refer to this thread: http://forum.doom9.org/showthread.php?t=96703&page=2. And if you have improvements (formulas, code), you're more than welcome.
Due to a completely unreasonable amount of work to get an accurate audio overhead fro Vorbis, the calculations for Vorbis might be way off track, and I'm extremely reluctant to support that audio codec at all. I rather focus on other interesting features like being able to re-open the status window, pause encoding (it might just work), better statistics, and I guess I can come up with some other features that help usability and don't cater to a minority audience.

[Beave]

I am fine with just MP4. You can use it for every input and the future support in hardware is more likely than mkv.
Did you give custom quant matrix in XVID another thought? Your tool is perfect for XVID/AAC5.1/MP4. Load the avs and the ac3, load the profile and press the GO Button.
Do you have any thoughts about fast first pass settings for xvid maybe?
I guess I will stick with xvid for a while, cause I get annoyed by the blockage in certain areas (especially blue) with x264 and playback performance is very demanding on high resolutions. XVID is still a great codec especially with custom matrices.

Small suggestion:
After pressing the Auto Encode Button, could you implement, that MEGui remembers the last size setting maybe?
STRG+V doesn't work there, only right click + Paste.
Could You add the possiblity to input the size in MB not in KB as well, maybe setting it up in the settings? I always have to use calc for it.

[Doom9]

Did you give custom quant matrix in XVID another thought?I recall asking a question about that and never getting an answer. How does it work with windows paths? (window has a : in it, and that's the option separator in mencoder, I know that this causes major issues for an x264 patch that is in the works to enable custom x264 quantizer matrices in mencoder)

If somebody cann tell me what turbo does in XviD I can see what of that can be done in MeGUI.. but naturally it would be better to make a mencoder patch. Or even better, turn enc_raw into an x264.exe equivalent.

Could You add the possiblity to input the size in MB not in KB as well, maybe setting it up in the settings? I always have to use calc for it.The autoencode window works without ugly code.. I'd like to keep it like that. The calculator was torture to write.. exactly the stuff programmers hate so much about GUIs.. there's so many interdependent GUI elements it drives you crazy. If you want to drive somebody away from software, give them a lot of pointers or such a GUI and your chances of succeeding are very high.

[Backwoods]

VirtualDub = 1-2fps

MeGUI = 3-4fps

Not sure why, but it happens. I like the simplicity of your program too.

Just one question, would it be possible to add delay with the muxing?

[Doom9]

Just one question, would it be possible to add delay with the muxing?Possible, yet, but desirable? I see a complete audio redesign versus the delay correction in BeSweet that is largely sufficient. And I'm not sure mencoder and mkvmerge support delays while muxing, I only know that mp4box does. Since when encoding audio it makes no sense not to correct the delay, it really only comes down to encode files where delay correction hasn't been done (and that's a case where I think people need to learn the hard way that they must do delay correction during audio encoding), and muxing files that you won't re-encode (AC3 mostly, and some MP2 audio from DVB transmissions).

[Backwoods]

I would prefer not to re-encode, that is why I asked.

[Doom9]

Release notes for 0.2.1.6:

pause works reliably for video and audio encoding and unreliably for muxing. The reason for this is that at some point, mp4box just doesn't care anymore if it's stdout and stderr is being read by MeGUI or not, and continues running anyway. There will be a stop eventually, but it's not like you can stop right where you are at any given position (the later you are in the muxing phase the more likely the pause will only activate when the muxed file has already been written).

I removed the alpha status due to lack of bugreports, but I haven't had time to do additional testing of the Matroska features.

[sillKotscha]

I removed the alpha status due to lack of bugreports

hmmm...

Nevertheless I'm able to choose that *.mpg, choose the destination and DGIndex starts to work after "prepare" is pushed.
But after the d2v file is generated I can't close that window anymore to go back to the "main-settings" screen. All I can do is to kill the exe by using the taskmanager.

;)

[North2Polaris]

Use the latest ffdshow version (built by Celtic Druid) for playing back x264: http://www.aziendeassociate.it/cd.asp?dir=/ffdshow
(Custom matrices are still not supported by ffdshow. Use Nero decoder if your encodes are made with CQMs
@doom9,

In MeGUI 0.2.1.4 under macroblock options, there are three options -- "all", "none", and "custom". If I set the option to "all" or "none" and then save the profile, when I reopen the profile the option is "custom". Is this correct?

Which option gives you a file that can be played using ffdshow? My latest encodes play only with the Nero decoder.

Thanks.

North

[Doom9]

If I set the option to "all" or "none" and then save the profile, when I reopen the profile the option is "custom". Is this correct?That sounds plausible. The profile is not something that is saved in a profile, only the checked/unchecked options are.

And I can play everything I create (plus not a megui issue).

[TheBashar]

Release notes for 0.2.1.6:
I removed the alpha status due to lack of bugreports, but I haven't had time to do additional testing of the Matroska features.

Hi Doom9. I'm not sure how to go about helping diagnose this, but since I upgraded from 0.2.1.3 to 0.2.1.6 a problem has cropped up. I've queued an automatic 2 pass job. I go to the queue tab and start the processing. The first pass job immediately completes (no error) even though it is impossible that it could have run.

Interestingly, the 2nd pass appears to work as it process for a bit before I abort it. Downgrading back to ...3 works without any trouble.

[Doom9]

I've queued an automatic 2 pass job. I go to the queue tab and start the processing. The first pass job immediately completes (no error) even though it is impossible that it could have run.Umm.. what does it say on the problem reporting guidelines? How can I possibly reproduce that? I'm no medium so I don't know what kind of job you set up (codec, settings, output type, etc etc etc etc etc etc etc.. I'm sure I can easily get up to a 5 digit permutation of options). standard avc 2 pass with default setting works, same with asp (that's the minimum test I run), so a statement like "automated encoding doesn't work" is simply false.

If I set the option to "all" or "none" and then save the profile, when I reopen the profile the option is "custom". Is this correct?It won't be like that in the next version.. stupid boring GUI code. The only good thing adding that had is that I discovered a bug in those options.

[berrinam]

I get faulty commandlines generated for turbo x264 passes with MeGUI. For any settings with x264, if I click turbo, the commandline generated has --me, but it is not followed by a me method, ie it is followed by whatever is the next option. This only happens with x264 turbo commandlines. I think this is what is causing the first passes that exit immediately.

Also, I don't know if it is just me, but pausing of x264 doesn't actually seem to pause. Instead, it just suspends status updates while x264 continues running in the background.

[parcival]

Now MeGUI supports Matroska! Great! Thanks!
Only the editing part is now missing. The problem seems to be with the AAC editing. Maybe the method I am currently using might give you an idea how to solve it.

1) I have the d2v file, the Avisynth script and the AC3 ready.
2) I open the Avisynth script with VirtualDubMod.
3) I add the AC3 stream.
4) I cut out the parts that I do not want.
5) I demux the AC3 stream. Only the parts that I want are demuxed.
6) I encode the demuxed AC3 to AAC.

So what I am proposing is edit the AC3 first and then encode the result instead of trying to go directly for the AAC.

I know it is an enormous amount of work and requires a few more MB for the job (for the demuxed AC3 - not a real issue though nowadays) but currently it seems the only solution.

What do you think?

[Doom9]

What do you think?/me has a headache just reading that.

[parcival]

/me has a headache just reading that.
Because I poorly explain it or because of the implications going this way? :)

[Doom9]

Because I poorly explain it or because of the implications going this way?The latter. You're not the first one to ask for something like that, but the implications are higher than the Himalayas. Give me a BeSweet that can handle AviSynth input, and ensure that AC3Source in AviSynth properly decodes AC3 with all channels and I'd consider it doable - I would even offer the cutting functionality (it's not a lot different from the zone creator). But without that, there's no way I'm ever going to do that.

[Sirber]

AC3Source downmix to stereo, not even sure about surround. I never been able to contact the author :(

[North2Polaris]

And I can play everything I create (plus not a megui issue).

Understood. Let me rephrase. What settings in MeGUI would constitute a "custom matrix"? This might help me with troubleshooting.

Would it be better to ask this question in a new thread? Thanks.

[parcival]

The latter. You're not the first one to ask for something like that, but the implications are higher than the Himalayas. Give me a BeSweet that can handle AviSynth input, and ensure that AC3Source in AviSynth properly decodes AC3 with all channels and I'd consider it doable - I would even offer the cutting functionality (it's not a lot different from the zone creator). But without that, there's no way I'm ever going to do that.
But that is why I made the suggestion. It is really a workaround for the limitations of BeSweet etc. The idea is to edit/cut the (5.1) AC3 before encoding it with BeSweet. I do it all the time and it works great.

From my point of view all you need are two things:
1) The cutting functionality that selects the parts you want.
2) A demuxing module for AC3 similar to the one VirtualDubMod has.

Then you just encode the demuxed AC3 to AAC with BeSweet (the whole demuxed AC3 file).

Maybe I do not understand completely what you are saying. Are you saying that what VirtualDubMod does (cutting/editing AC3) cannot be easily implemented to MeGUI?

Anyway, I know that what I am asking is a lot of work, so the case is closed for me. :D

[Doom9]

What settings in MeGUI would constitute a "custom matrix"? This might help me with troubleshooting. None. In tab 3 you have custom quantizer matrix groupbox.. in there you can load a custom quantizer matrix.. you either have one or don't.
Are you saying that what VirtualDubMod does (cutting/editing AC3) cannot be easily implemented to MeGUI?I'm saying I'm not going to automate VDubMod. If I start using any VfW capable encoding tool, I could just as easily have automated that from the getgo and use VfW codecs. I understand why you're asking but I'm not gonna do it, period.

[akupenguin]

Random comments (referring to 0.2.1.6):
(Disclaimer: I have not tried an MeGUI encode with all of these bugs, I am just looking at the generated commandlines.)

all:
The zones editor doesn't let you create a zone starting at frame 0 ("The video only starts at frame 1"). But frame 0 is the initial I-frame. (However, in x264 and IIRC also lavc, I-frames' quants are a function of the following P-frames, and not independently controllable. So a zone starting at 1 has the same effect as starting at 0.)
Typo: "WEIGTH" in the zones list.

x264:
x264cli expects zone weights to be factors, not percentages. (1.0 means no modification)
Quantization matrix: "None" and "Flat" are the same.
"Bitrate Variance" controls the same feature as lavc's "Filesize Tolerance". (though with different units)

lavc/ASP & Snow:
The default "Quantizer Blur" and "Quantizer Compression" show 0.0, and are ommitted from the commandline when left at that. MEncoder's default is 0.5 for both.
vrc_override treats a positive modifier as a quantizer, and negative as a bitrate weight (in percent). MeGUI writes positive for both (so all zones are CQ). e.g. "Start: 3, End: 42, Mode: WEIGHT, Modifier: 100" should be "vrc_override=3,42,-100".
"# Motion Predictors" is useful in ASP. It is supported but not useful in Snow. And it's predictors from neighboring blocks in the current frame, not prev.

lavc/ASP:
4MV should not require VHQ or RDO.

Snow:
commandline sets cmp=12 when "SAD" is selected. Should be cmp=0 (or omitted, since cmp=0 is Mencoder's default).

xvid:
As with x264, zones weights are factors, not percentages.
Since xvid zones have only start frames, any one not immediately followed by another zone should be paired with a "<endframe+1>,w,1".

[TheBashar]

Hi Doom9. I'm not sure how to go about helping diagnose this, but since I upgraded from 0.2.1.3 to 0.2.1.6 a problem has cropped up. I've queued an automatic 2 pass job. I go to the queue tab and start the processing. The first pass job immediately completes (no error) even though it is impossible that it could have run.

Interestingly, the 2nd pass appears to work as it process for a bit before I abort it. Downgrading back to ...3 works without any trouble.

More details. I was mistaken. Reverting to 0.2.1.3 did not fix the problem. The queue entries generated by 0.2.1.6 showed the same behaviour even when processed with 0.2.1.3. Creating new queue entries with 0.2.1.3 does not show the problem.

The problem exhibited itself when the configuration generated the following commandline for the first (turbo pass):
x264.exe --pass 2 --bitrate 1800 --stats 2pass.log --keyint 300 --bframes 2 --subme 1 --weightb --analyse none --me dia --progress --no-psnr --output ep-2b.mp4 ep-2b.avs

The 2pass (which wasn't the problem) has the commandline of:
x264.exe --pass 2 --bitrate 1800 --states 2pass.log --keyint 300 --bframes 2 --subme 6 --weightfb --analyse all --8x8dct --progress --no-psnr --output ep-2b.mp4 ep-2b.avs

[Doom9]

Also, I don't know if it is just me, but pausing of x264 doesn't actually seem to pause. Instead, it just suspends status updates while x264 continues running in the background.Actually.. give it some time. For some reason, x264 doesn't care that nobody reads its stdout anymore, until about 30 seconds later.. then it stops. The only way to make it stop right away would be to pause MeGUI and you can only do that if you're debugging and hit a breakpoint. And that also stops the GUI thread so the program becomes non responsive. The thread is suspended immediately, I don't see anything else I could do.

The queue entries generated by 0.2.1.6 showed the same behaviour even when processed with 0.2.1.3.Obviously they will since it's the commandlines. What is the difference between the 0.2.1.3 generated first pass commandline and the 0.2.1.6 one? For me, it is the most natural thing in the world to compare those two right at the beginning. Always blame the commandline first and the code later (obviously code generates the commandline but I rather know I have to modify the commandline generator class, than having to look elsewhere)

[lesnick]

I have problem with last version of MeGUI if i use "turdo" with x264, for example:
-------------------------------------------------------------------------
Next job job1-1 is a video job. encoder commandline:
"E:\My things\Prog\meGUI\tool\x264\x264.exe" --pass 1 --bitrate 700 --stats "2pass.log" --subme 1 --analyse none --qpstep 1 --me --progress --no-psnr --output NUL "D:\preview.avs"
successfully set up video encoder and callbacks for job job1-1
----------------------------------------------------------------------------------------------------------

Log for job job1-1

bad ME method `--progress'
---------------------------------------------------------------------------

[Sharktooth]

it lacks the ME method.
it should be "--me something" (i think dia for "turbo") in the command line.

[Doom9]

x264cli expects zone weights to be factors, not percentages. And what's the range? 0.01 to 1.0?

"Bitrate Variance" controls the same feature as lavc's "Filesize Tolerance". (though with different units)So you're saying I should rename one of the two? I stuck to the description in the manpages.

4MV should not require VHQ or RDO.I know, but the manpage suggests that it works better together. I guess I could relax that and use a tooltip instead.

Since xvid zones have only start frames, any one not immediately followed by another zone should be paired with a "<endframe+1>,w,1".I warn people about that in the release notes. I've refrained from doing that automatically since no XviD encoder does that.

[akupenguin]

And what's the range? 0.01 to 1.0?
x264 accepts anything in 0 < weight <= MAX_FLOAT.
But given the finite range of possible QPs, I expect the range that does actually does anything is around .02 to 50.

[Doom9]

geez.. 50 times the bitrate? mencoder has it limited to 100. in xvid it only goes up to 2. There goes my one zone to rule them all approach :/

[Doom9]

about weighted zones in lavc: in the manpage it states quality correction in %. So if I want 10% of the original bitrate, what would the value be? -10?, and consequently -100 to keep the original bitrate, -200 to double the original bitrate, etc?

[akupenguin]

So if I want 10% of the original bitrate, what would the value be? -10?, and consequently -100 to keep the original bitrate, -200 to double the original bitrate, etc? right

[Doom9]

"# Motion Predictors" is useful in ASP. It is supported but not useful in Snow. And it's predictors from neighboring blocks in the current frame, not prev.
from the mencoder manpage last_pred=<0-99>
amount of motion predictors from the previous frame
0
(default)
a
Will use 2a+1 x 2a+1 macroblock square of motion vector predictors from the previous frame.

p.s. perhaps you know that: xvid in mencoder now supports custom quantizer matrices, but mencoder uses : as option separator. Is there a workaround built-in for the fact that absolute paths on windows contain a : ?

[akupenguin]

I guess I misread the code. Lavc keeps a single buffer full of mvs. At any time during motion estimation, some of them have been updated to the current frame, and others still contain the previous frame's values. last_pred uses all neighbors without distinguishing between those states.

xvid in mencoder now supports custom quantizer matrices, but mencoder uses : as option separator. Is there a workaround built-in for the fact that absolute paths on windows contain a : ?
Some of the the suboption parsers have a workaround. The video encoders are not among them. They're waiting for a general option parser rewrite. I don't know if anyone is actually working on it or if it's just being discussed.

[Doom9]

alright, I implemented all those changes. The XviD intelligence was the biggest pain of all but it's all done now :)

[haubrija]

Doom9,

When hitting the Config button for AVC, I get an error message with 0.2.1.7. Here the debug log it gives me.

See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.ArgumentOutOfRangeException: Specified argument was out of the range of valid values.
Parameter name: '6' is not a valid value for 'index'.
at System.Windows.Forms.ComboBox.set_SelectedIndex(Int32 value)
at MeGUI.x264ConfigurationDialog.set_CodecSettings(x264Settings value)
at MeGUI.MeGUI.videoConfigButton_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)


************** Loaded Assemblies **************
mscorlib
Assembly Version: 1.0.5000.0
Win32 Version: 1.1.4322.573
CodeBase: file:///c:/windows/microsoft.net/framework/v1.1.4322/mscorlib.dll
----------------------------------------
MeGUI
Assembly Version: 1.0.2037.35636
Win32 Version: 1.0.2037.35636
CodeBase: file:///C:/MP4%20Encoding/MeGUI.exe
----------------------------------------
System.Windows.Forms
Assembly Version: 1.0.5000.0
Win32 Version: 1.1.4322.573
CodeBase: file:///c:/windows/assembly/gac/system.windows.forms/1.0.5000.0__b77a5c561934e089/system.windows.forms.dll
----------------------------------------
System
Assembly Version: 1.0.5000.0
Win32 Version: 1.1.4322.573
CodeBase: file:///c:/windows/assembly/gac/system/1.0.5000.0__b77a5c561934e089/system.dll
----------------------------------------
System.Drawing
Assembly Version: 1.0.5000.0
Win32 Version: 1.1.4322.573
CodeBase: file:///c:/windows/assembly/gac/system.drawing/1.0.5000.0__b03f5f7f11d50a3a/system.drawing.dll
----------------------------------------
System.Xml
Assembly Version: 1.0.5000.0
Win32 Version: 1.1.4322.573
CodeBase: file:///c:/windows/assembly/gac/system.xml/1.0.5000.0__b77a5c561934e089/system.xml.dll
----------------------------------------
xsuqgshi
Assembly Version: 0.0.0.0
Win32 Version: 1.1.4322.573
CodeBase: file:///c:/windows/assembly/gac/system/1.0.5000.0__b77a5c561934e089/system.dll
----------------------------------------
zwv8h0ae
Assembly Version: 0.0.0.0
Win32 Version: 1.1.4322.573
CodeBase: file:///c:/windows/assembly/gac/system/1.0.5000.0__b77a5c561934e089/system.dll
----------------------------------------
mca9j7ql
Assembly Version: 0.0.0.0
Win32 Version: 1.1.4322.573
CodeBase: file:///c:/windows/assembly/gac/system/1.0.5000.0__b77a5c561934e089/system.dll
----------------------------------------

************** JIT Debugging **************
To enable just in time (JIT) debugging, the config file for this
application or machine (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.

For example:

<configuration>
<system.windows.forms jitDebugging="true" />
</configuration>

When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the machine
rather than being handled by this dialog.


Do I not have something set up properly or is it a bug?

[berrinam]

haubrija, I can't reproduce this. How do you create this error, ie what x264 settings, do you use profiles, anything else you think might be useful.

[haubrija]

Tried to delete my post without success coz I had solved my problem. This is what happened though. I usually just overwrite my current version of MeGui with the new one. I had 0.2.1.4 set up but downloaded the new 0.2.1.7 and overwrote the old one. Apparently the new one didn't like my old profile setting for avc. Figuring that could be a potential problem, I exited MeGui and deleted the files in my profile directory. Opened MeGui back up and no problems. Except I had to resetup my profiles :) .

[azsd]

Progress window have no "High" priority item.

[Backwoods]

I tried this twice with the latest build and when I encode an Xvid from this script:

LoadPlugin("C:\Program Files\AviSynth 2.5\yea\DGDecode.dll")
LoadPlugin("C:\Program Files\AviSynth 2.5\yea\Decomb521.dll")
Mpeg2Source("00.d2v")
Telecide(order=1,guide=1)
Decimate(cycle=5)
CropBottom(8)
Lanczos4Resize(960,540)

The resulting file is corrupt. The video is roughly 1hr 30min and when I do a quick test (like one minute to three minutes) the video is fine. The resulting file is roughly 7gigs and does not play. Opening that file in VirtualDub results in 20min being recovered then nothing.

Xvid options: Q3, everything else not touched.
File Type: AVI

[Doom9]

@haubrija: you got this crash because you had an avc profile with rdo activated, and I changed the subq and me assignment code when I fixed the turbo bug. I used to increase subq by one directly in the GUI, now I'm doing it in the commandline generator.

@Backwoods: that almost sounds as if avi isn't up to that, or mencoder.

Progress window have no "High" priority item.Indeed, I forgot about that. It'll be in the next release.

[HookedOnTV]

@Backwoods: that almost sounds as if avi isn't up to that, or mencoder.

I'm thinking it is mencoder as I am not getting any good HD encodes out of MeGUI(XviD) where the resulting file size is larger than 4GB.

[MeteorRain]

d9: could you add a button to hide meGUI & status window into systray? XD

[Doom9]

that is kinda problematic. I have an app that does that when you press the X button.. with the effect that the X button becomes useless to close the application as you cannot catch button clicks outside if the client area (client area = anything below the title bar and inside the external frame border)

[stax76]

that is kinda problematic. I have an app that does that when you press the X button.. with the effect that the X button becomes useless to close the application as you cannot catch button clicks outside if the client area (client area = anything below the title bar and inside the external frame border)


Spy++ tells you the involved messages which you can trap either overwriting the controls WndProc (note that Form derives from Control) or before the message get posted to the control by setting a message filter (Application.AddMessageFilter).

[Doom9]

@stax: But is there a difference in between pressing X, minimize and maximize? I've already asked in the microsoft newsgroup and the answers I got pointed to only one catchable event, and that's simply not good enough.

[stax76]

never had to use it but yes, there should be a difference:

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/winui/winui/windowsuserinterface/userinput/mouseinput/mouseinputreference/mouseinputmessages/wm_nchittest.asp

which group did you ask? Most active appear to be:

comp.os.ms-windows.programmer.win32

do you know how to use Spy++? It's qite simple.

[Doom9]

I asked in a .NET group obviously ;) the thing is though, look at those events.. NC... is interesting here. You can catch non client area left, right middle and X button click (I figure that's a combination), and the position. So you'd need to figure out the coordinates of the X button (and then enter the people who use no standard DPI to give me a further headache). If somebody wants to submit a patch they're welcome, but this is just nothing that interests me.

[stax76]

I played a little bit around and found that you can do something like this:


Protected Overrides Sub WndProc(ByRef m As Message)
If m.Msg = WM_SYSCOMMAND AndAlso m.WParam = CType(SC_CLOSE, IntPtr) Then
Exit Sub
End If

MyBase.WndProc(m)
End Sub


There is a handy application called ApiViewer 2004 that knows all the Win32 declarations and even generates the code in various languages.

[Doom9]

but what does that? Basically the problem is not so much catching the X and minimizing instead of closing, but knowing when to close (Alt-F4 or File - Exit).. they all fire OnClose where you cannot differentate between the X button and the other means to close.

[stax76]

Maybe I can help you if you want to find a solution for this issue but I would need to know what exactly you want to achieve. I must admit I'm not too familiar with MeGUI, I made only some test encodes.

[Doom9]

This isn't tied to MeGUI. Basically an app that when pressing the X button minimizes to the system tray, and when pressing alt-f4 or file-exit it exits.

[stax76]

Alt + F4 could be handled explicit:


Protected Overrides Sub WndProc(ByRef m As Message)
If m.Msg = WM.SYSCOMMAND AndAlso m.WParam = CType(SC.CLOSE, IntPtr) Then
MoveToTray()
Exit Sub
End If

MyBase.WndProc(m)
End Sub

Private Sub MainForm_KeyDown(ByVal sender As Object, ByVal e As KeyEventArgs) Handles MyBase.KeyDown
If e.KeyData = (Keys.Alt Or Keys.F4) Then
Close()
End If
End Sub

[boombastic]

I've got a standalone divx player which can only playback AVI encoded with the xvid DXN HT PAL profile, if i use unrestricted it stops about every two minutes because of bitrate spikes i presume :angry:
I've got some questions:

1)is there a way with MeGui to assure that i can playback the file ?

2)What is "HC AC coefficients" option ?

3)I'd like to get a target size: if i use Automated 2 pass where can i set the desired size?

[Doom9]

is there a way with MeGui to assure that i can playback the file ?Don't use QPel, don't use GMC, and use maximum 1 B-frame. I'm not sure on the packed bitstream, that (but other things as well) depend on which player you have. Unfortunately you cannot limit bitrate buffers in mencoder, and thus MeGUI so if the buffers cause problems for you, then I'm afraid you have to stick to the VfW or use the lavc codec where you can control max bitrate and buffer size.

if i use Automated 2 pass where can i set the desired size?You need to use the auto-mode. You don't even have to set the encoding mode with that, just configure the rest of the options.

[boombastic]

I'm afraid you have to stick to the VfW or use the lavc codec where you can control max bitrate and buffer size.
.

What are vfw and lavc codec?If my player plays divx/xvid can also play avi made with them?Where can i find them?In ffdshow package?

[Doom9]

lavc is shorthand for libavcodec mpeg-4 asp codec.. it's used when you select ASP from the codec dropdown.
VfW is Video for Window (searching would've helped).. you use it if you encode XviD in VirtualDub or any app based on that (Gordian Knot, AutoGK, DVX), and other VfW based apps like avs2avi.

[haubrija]

Doom9,

I was setting up an encode last night and think I found a bug. I had the Show Commandline switch enabled. I set up the x264 encode for 3 Reference Frames but failed to see and resulting change in the commandline. If I'm not mistaken there was no switch for ref frames added and definately nothing changed when I would switch the number of ref frames in the dialog box (i.e. I saw no changes when switching from 3 to 4 refs). I hope I'm not showing my ignorance here of not understanding how one setting impacts another. Other than the default settings, here's how I have my encode set up:

2 Pyramid B Frames
RDO
Weighted Prediction
All Macroblock Options.

Let me know if you need any more info.

[Doom9]

let me guess.. you had encoding mode set to automated 2-pass or 3-pass and turbo checked? Or a multi-pass single pass mode with turbo enabled? In the former case, you pretty much get to see the first pass settings (only pass is left at 2), in the latter case you'll see the actual first pass settings with turbo enabled. Turbo overrides a bunch of options, as number of reference frames, subq, me method and which macroblock options are enabled (none with turbo). However, perhaps you've noted that once you queue, your automated 2/3 pass turns into 2 / 3 separate jobs. If you click on one, press load, then go back to the codec configuration, you'll see what you really get. Basically in autuomated 2/3 pass you configure the second pass.. if you activate turbo, turbo overrides the second pass commandline so it is not shown.. but your settings are all still kept for the second pass.. so when the two passes are separated, they will be as you want them.

[haubrija]

Ah... I was afraid it was something like that. Thanks for taking the time to explain. I did have Automated 3 pass with turbo checked.

[dejected_is_me]

I was encoding AD police last night with this:

# PLUGINS
LoadPlugin("C:\GORDIA~1\DGMPGDec\DGDecode.dll")
LoadPlugin("C:\GORDIA~1\AviSynthPlugins\decomb.dll")
LoadPlugin("C:\GORDIA~1\AviSynthPlugins\VSFilter.dll")
# SOURCE
mpeg2source("C:\DVD Encodes\Raws\AD Police 1-3\d2v\ad 1.d2v", idct=7)
# IVTC
Telecide(order=1,guide=1).Decimate(cycle=5, quality=3)
# CROPPING
crop(2,0,704,480)
# RESIZING
LanczosResize(704,480)
# DENOISING: choose one combination (or none)
TextSub("C:\DVD Encodes\Raws\AD Police 1-3\subs\logo\ad 1 logo.ssa")



and the resulting video came out all garbled. There are alternating lines in the video and the actual video can be seen blinking in the backround. The sizes came out wrong too. Im incodeing with XVID into an avi. here are my settings.

(PS i can put this script into Virtualdub mod and it encodes OK)

<VideoProfile xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<Name>2 Pass Xvid</Name>
<Settings xsi:type="xvidSettings">
<EncodingMode>4</EncodingMode>
<BitrateQuantizer>1153</BitrateQuantizer>
<KeyframeInterval>300</KeyframeInterval>
<NbBframes>1</NbBframes>
<MinQuantizer>2</MinQuantizer>
<MaxQuantizer>31</MaxQuantizer>
<SARX>0</SARX>
<SARY>0</SARY>
<Turbo>false</Turbo>
<V4MV>false</V4MV>
<QPel>false</QPel>
<Trellis>true</Trellis>
<CreditsQuantizer>20</CreditsQuantizer>
<FourCCs>
<string>XVID</string>
<string>DIVX</string>
<string>DX50</string>
<string>MP4V</string>
</FourCCs>
<Logfile>2pass.log</Logfile>
<CustomEncoderOptions />
<FourCC>0</FourCC>
<Zones />
<MotionSearchPrecision>6</MotionSearchPrecision>
<VHQMode>4</VHQMode>
<QuantType>0</QuantType>
<PAR>0</PAR>
<MinPQuant>2</MinPQuant>
<MaxPQuant>31</MaxPQuant>
<MinBQuant>2</MinBQuant>
<MaxBQuant>31</MaxBQuant>
<BQuantRatio>150</BQuantRatio>
<BQuantOffset>100</BQuantOffset>
<KeyFrameBoost>100</KeyFrameBoost>
<KeyframeThreshold>1</KeyframeThreshold>
<KeyframeReduction>20</KeyframeReduction>
<OverflowControlStrength>5</OverflowControlStrength>
<MaxOverflowImprovement>5</MaxOverflowImprovement>
<MaxOverflowDegradation>5</MaxOverflowDegradation>
<HighBitrateDegradation>0</HighBitrateDegradation>
<LowBitrateImprovement>20</LowBitrateImprovement>
<ReactionDelayFactor>16</ReactionDelayFactor>
<AveragingPeriod>100</AveragingPeriod>
<FrameDropRatio>0</FrameDropRatio>
<RateControlBuffer>0</RateControlBuffer>
<PackedBitstream>true</PackedBitstream>
<GMC>false</GMC>
<CartoonMode>true</CartoonMode>
<ChromaMotion>true</ChromaMotion>
<ClosedGOP>true</ClosedGOP>
<VHQForBframes>true</VHQForBframes>
<ChromaOptimizer>false</ChromaOptimizer>
<HQAC>true</HQAC>
<AdaptiveQuant>false</AdaptiveQuant>
<Greyscale>false</Greyscale>
<Interlaced>false</Interlaced>
<BframeThreshold>0</BframeThreshold>
<PARs>
<string>vga11</string>
<string>pal43</string>
<string>pal169</string>
<string>ntsc43</string>
<string>ntsc169</string>
</PARs>
<IntraMatrix />
<InterMatrix />
</Settings>
</VideoProfile>

any ideas...

[dejected_is_me]

ok i figured it out....

the aspect ratio intrestingly enough was what was doing it. I could of swore it was the tecline. On a side note is there increments to croping that i dont know about for megui (or in general). I had the values set to quotents of 2 with a aspect ratio of 704x480. The preview window would open for megui and it would look ok but after encode the error would ensue. I changed it to 640x480 and it worked. Another thing i dont get is why the script with 704x480 (the one that didn't work in megui) loaded and encoded ok in virtual dub mod? anywho...thanks for the great program.

[Doom9]

this certainly hasn't anything to do with your problem, but you're cropping, and then resizing to the same resolution.. get rid of the resizing, it doesn't do anything but potentially degrade quality and slow encoding down (I'm putting this in conditional tense because I don't know if the filter is intelligent and doesn't do anything if input and output resolution is the same).
I only support 16x resolutions because anything else is trouble.. certain codecs take care of that with tricks, and some don't work at all.. so to be on the safe side always go for 16x.

[LigH]

For example, x264.exe simply closes if width and height are not multiples of 16 (the size of a macroblock).

[theronmoore]

I'm definitely not the most versed reader of these forums, so I may be doing something incredibly simple wrong. But I seem to be running into a probelm when the Auto-Encode queue gets to muxing. It doesn't seem to be doing anything even after leaving it for a number of hours. Any suggestions?

[Doom9]

Any suggestions?Yes.. read the problem reporting guidelines and provide info.....

[Doom9]

a new build is up. Just a couple small things here and there, but those wishing to specify a bitrate rather than size in the autoencode window can rejoice.

[haubrija]

Doom9,

Just a small suggestion. Maybe on the abort button present during encoding, when its pressed have a seperate dialog that asks you if you're sure you want to do this. I was closing some other open windows last night while an encode that was half way done (and had been running for a day already) got accidentaly closed as well. I cursed at myself for an hour :). If its a pain, don't worry about it, but it might help with some grief people may experience.

[Yama4050242]

for the latest 0218
i choose exhaustive, use the show commandline, it is "--me esa --progress", but when encoding, it gives "--me --progress" and return a error
if i choose multi hex, use the show commandline, it is "--me umh --progress", when encoding, it gives "--me esa --progress"

other settings

"x264.exe" --pass 2 --bitrate 4096 --stats "2pass.log" --keyint 300 --ref 3 --bframes 3 --no-b-adapt --b-pyramid --subme 6 --weightb --analyse all --8x8dct --qpstep 1 --me umh --progress --no-psnr --output "I:\temp.264" "I:\temp.avs"

[MeteorRain]

for 0218:
do you forget to change the version number on the window title? :o

[leowai]

Ya. It's same here. Title shows 0.2.1.7 rather than 0.2.1.8.
for the latest 0218
i choose exhaustive, use the show commandline, it is "--me esa --progress", but when encoding, it gives "--me --progress" and return a error
if i choose multi hex, use the show commandline, it is "--me umh --progress", when encoding, it gives "--me esa --progress"

other settings

"x264.exe" --pass 2 --bitrate 4096 --stats "2pass.log" --keyint 300 --ref 3 --bframes 3 --no-b-adapt --b-pyramid --subme 6 --weightb --analyse all --8x8dct --qpstep 1 --me umh --progress --no-psnr --output "I:\temp.264" "I:\temp.avs"
Well, just have a quick test (queqe the job and exam on the job*.xml) on both single pass (CQ & ABR) and auto 2pass. All works fine for me.

[dejected_is_me]

Doom 9

thanks for the reply. the 16x resize is the answer i was looking for, incedently i was using 32x. with LanczosResize.

On a side note: i got the damn thing too encode but the sizes where way off. Previous version had been spot on. Im not sure if it has something to do with the source( AD police DVD: interlaced top field first) but i set it too 230 minus 10 megs for the audio, and it came out as the following, tried three times: 193mb, 177mb, and 181mb. Same settings as previous post and this time at a resoultion of 640x480 with Xvid into a avi.

????

just tried to mux a MKV with the built in muxer. using the "its alright baby" version and i get the following error:

Log for job job1

mkvmerge v1.5.0 ('It's alright, baby') built on Jul 1 2005 10:34:56

Error: 'jap' is neither a valid ISO639-2 nor a valid ISO639-1 code. See 'mkvmerge --list-languages' for a list of all languages and their respective ISO639-2 codes.

and then with no languages selected:

Log for job job1

mkvmerge v1.5.0 ('It's alright, baby') built on Jul 1 2005 10:34:56

Error: 'C:\DVD' is neither a valid ISO639-2 nor a valid ISO639-1 code. See 'mkvmerge --list-languages' for a list of all languages and their respective ISO639-2 codes.

the 'c:\dvd' is the location of the source chosen in the video input section.

[Doom9]

I really don't understand how people manage to kill their jobs without thinking. The abort button is kilometers away from the minimize button so you really have to want to kill it or just click at random and be really lucky. I've managed to close one or two programs that I didn't want to myself over the years, but explicitly pressing the abort button.. I don't recall that.

The version number is probably the smallest concern for any developer.. ;) You can always use a resource hacker. Seems I recompiled the minimized versions but forgot to recompile the full version when I finally changed the version number. I can almost promise that this is going to keep on happening in the future no matter how hard I try because version numbers in the title have zero significance to me.

@Yama4050242: I cannot reproduce that. I think you have some old jobs / profiles left. And as a side note, exhaustive is a rather insane setting;) You don't gain anything measurable but you lose out big in encoding time.

On a side note: i got the damn thing too encode but the sizes where way off.I spent a lot of time writing a nice bitrate calculator.. load your source, load your audio tracks and compare the bitrate the calculator shows with the bitrate that was used for the encoding jobs (if you didn't keep them, you'll always find the results of the bitrate calculation and the encoding commandlines in a logfile in your log folder). The fact that you got three different sizes (using the same settings I hope) is also a strong indicator that I am not to be blamed (the bitrate calculation should've yielded the exact same results with the same settings and source) The logfile is also needed for your mkvmerge problem (I am very interested in the commandline)

[Yama4050242]

i'v deleted all the jobs, logs, profiles folder, but it consists there, i tried 0216, works fine.i am using DGIndex 1.40 final, but all the dgdecode.dll i have change to the 1.40final, on settings in megui, i dont have mkvmerge, is that the problem?

btw, thx for ur hint, i just play around the parameters on some music video, no more than 5minutes

[Doom9]

you don't need mkvmerge... you don't need dgindex either untill you want to create such a project, and you don't need dgdecode.dll unless you want to create an avisynth script from a dgindex project.

about the me thing: are you sure you're telling me everything I need to know? Here's how I tried to reproduce it: create job, exit megui, open the xml file and look at the commandline - that's no encoding at all. When do you see these faulty commandlines?

[MeteorRain]

Doom9:
maybe you can make the progress bar thinner? :p

it's so fat i think ;)

so big blocks when it works ;)

[Yama4050242]

<Commandline>"G:\SoftWarez\Encoding\WorkShop\MeGUI\X264CLI\x264.exe" --pass 1 --bitrate 700 --stats "2pass.log" --ref 3 --bframes 3 --no-b-adapt --b-pyramid --subme 7 --weightb --analyse all --8x8dct --qpstep 1 --me --progress --no-psnr --output NUL "I:\Sports\TestField\HDTV\temp.avs"</Commandline>

this is for the exhaustive

[Doom9]

<METype>5</METype>I suspected that. You still didn't tell where you got this job from. Is that a job after encoding or before encoding, in auto-mode, one click mode or regular mode? I guess it's after encoding in auto-mode, and if you look at jobs prior to encoding, all is ok. Is this correct?

[Yama4050242]

i do the thing you told me to do, the commandline is from the job1-1.xml before encoding, yeah, i use automatic 2 pass,

[leowai]

<Commandline>"G:\SoftWarez\Encoding\WorkShop\MeGUI\X264CLI\x264.exe" --pass 1 --bitrate 700 --stats "2pass.log" --ref 3 --bframes 3 --no-b-adapt --b-pyramid --subme 7 --weightb --analyse all --8x8dct --qpstep 1 --me --progress --no-psnr --output NUL "I:\Sports\TestField\HDTV\temp.avs"</Commandline>

this is for the exhaustive
What if you extract the MeGUI program files into a new folder? Is the bug remains (will the program still produce such a output command line)?

[Yama4050242]

What if you extract the MeGUI program files into a new folder? Is the bug remains (can you reproduce this output command line)?
yeah, i did extract the MeGUI to a new folder, the problem did not solve

[Doom9]

@Yama4050242: I think you do not understand that MeGUI has three modes. Regular mode is using just the main window.. you press the Queue button and jobs are added to the queue. That is regular mode. In all other modes, you have another window on screen at the point where the jobs get added to the queue. There are two modes: auto-mode. You enter auto-mode if you press the button entitled AutoEncode. And then there's the one click mode which you can enter only via the tools menu.

Now, I presume you're using automode. If you search this thread you'll find a lengthy explanation by myself on the subject of updating bitrates. Can you tell me if the job you posted has had its bitrate updated or not? I fear that with every bitrate update, the me (and subq for that matter) might get increased.

[Yama4050242]

then i just use regular mode, i just add the video and choose the profile and press queue

i just choose any bitrate and test, it is the same, and i havent update it

[Doom9]

this is weird as this is what I'm doing and I cannot reproduce it. The only difference is that I don't use any profile (I don't have any)

[Yama4050242]

currently, i also dont have any profile, and just do the setting, the problem is still there? is it conflict with other software i install? is that possible?

[Doom9]

is it conflict with other software i install? is that possible?very doubtful. Can you try this: delete settings, jobs, profiles, start again, load video, press config, change me method (and nothing else!!!), press Ok, press Queue, close MeGUI and then open the job xml file and look at your commandline. On my machines it matches what has been configured.

[Yama4050242]

<Commandline>"G:\SoftWarez\Encoding\WorkShop\MeGUI\X264CLI\x264.exe" --bitrate 700 --analyse p8x8,b8x8,i4x4 --qpstep 1 --me esa --progress --no-psnr --output "I:\Sports\TestField\HDTV\temp.mp4" "I:\Sports\TestField\HDTV\temp.avs"</Commandline>

it is ok for your setting, but automated 2pass's 1st pass got problem

for your setting and just change ABR to automated 2pass it gives
<Commandline>"G:\SoftWarez\Encoding\WorkShop\MeGUI\X264CLI\x264.exe" --pass 1 --bitrate 700 --stats "2pass.log" --subme 6 --analyse p8x8,b8x8,i4x4 --qpstep 1 --me --progress --no-psnr --output NUL "I:\Sports\TestField\HDTV\temp.avs"</Commandline>

[leowai]

<Commandline>"G:\SoftWarez\Encoding\WorkShop\MeGUI\X264CLI\x264.exe" --bitrate 700 --analyse p8x8,b8x8,i4x4 --qpstep 1 --me esa --progress --no-psnr --output "I:\Sports\TestField\HDTV\temp.mp4" "I:\Sports\TestField\HDTV\temp.avs"</Commandline>

it is ok for your setting, but automated 2pass's 1st pass got problem

for your setting and just change ABR to automated 2pass it gives
<Commandline>"G:\SoftWarez\Encoding\WorkShop\MeGUI\X264CLI\x264.exe" --pass 1 --bitrate 700 --stats "2pass.log" --subme 6 --analyse p8x8,b8x8,i4x4 --qpstep 1 --me --progress --no-psnr --output NUL "I:\Sports\TestField\HDTV\temp.avs"</Commandline>
OK. I managed to reproduce your problem now!

Clean MeGUI program (no profile).

Test procedure:
a. Open up MeGUI (of course :) )
b. Load avis input file
c. Click Codec "config" button

Then follow the steps when "x264 Codec Configuration" dialog shown.
1. Advance tab-> Select ME Algo (see below)
2. Main tab-> Change ABR to Automated 2passes (Turbo not selected)
3. OK and queqe.

Results for different ME Algo
1. Diamond
first pass: --progress
2nd pass: --me dia --progress

2. No change (ME Algo=Hexagon)
first pass: --me umh --progress
2nd pass: --progress

3. Multi Hex
first pass: --me esa --progress
2nd pass: --me umh --progress

4. Exhaustive
first pass: --me --progress
2nd pass: --me esa --progress

A quick test on automated 3 passes, Exhaustive (Turbo not selected)
--me --progress
--me --progress
--me esa --progress

Clear enough, if Turbo is not selected, there will be errors in output command lines.

Probably Turbo should be forced when automated multi-passes is used?.

[edit: typo]

[Doom9]

@leowai: thank you for that report. Finally I can reproduce the problem as well.

@everyone: take note on how methodical leowai approached the issue. This is how an excellent bugreport should look.

[Doom9]

a fixed version is out now.

[TNM]

Is it possible to add more audio stream in MP4 muxer window? Currently only 2 audio streams are allowed... Sometimes we may want to add like 3 audio streams: 2 language streams and a directors comment stream :)

[Doom9]

Currently only 2 audio streams are allowedThat's right and this will not be changed either. Keep in mind that this is a backup tool. Commentary tracks are something I cannot image listening to for a second time, and to do that, I really can take out my original disc.

[Mc Onyx]

First I apologize if this has been asked before, but why does MeGUI save bitrate value to the profile, example if choose profile for the first pass, queue it, than choose profile for the second pass, i have to enter bitrate value again, it would be nice if it would stayed from the first pass, it's not a big deal, but kinda anoying!
Second thing i don't know if i am doing something wrong (probably:)), or it's a bug, but it happens in MeGUI and X264CLIgui, so i guess it's my fault, and it's concerning zones, usualy i use quantizer value, but lately i tried with weight, which i was using in Xvid and if my commandline is like this:

D:\Encoding Utilities\X264 CLI>x264 --pass 1 --bitrate 1119 --stats "2pass.log"
--bframes 3 --b-pyramid --filter -2,-2 --subme 1 --weightb --analyse none --qpst
ep 1 --direct none --me dia --zones 4202,4750,b=0,25 --progress --no-psnr --outp
ut NUL "D:\DVD\Encoding AVS\DD Test.avs"

- X264 says:

avis [info]: 688x368 @ 25.00 fps (4751 frames)
x264 [error]: invalid zone: bitrate_factor=0.000000
x264_encoder_open failed

- But if i change the comma into point, like this:

x264 --pass 1 --bitrate 1119 --stats "2pass.log"
--bframes 3 --b-pyramid --filter -2,-2 --subme 1 --weightb --analyse none --qpst
ep 1 --direct none --me dia --zones 4202,4750,b=0.25 --progress --no-psnr --outp
ut NUL "D:\DVD\Encoding AVS\DD Test.avs"

- It works, but i don't know if this is ok, because the commandline was generated by MeGUI and X264CLIgui, does it the same. So my question is, what's wrong and is it "point", or "comma"!


- P.S. Sorry for my english! :)

[Doom9]

why does MeGUI save bitrate value to the profileGood question. But either way round it's not ideal. Some people might prefer to have profiles with bitrates (or a quantizer), others would rather not have that value saved anywhere, so either way somebody is going to be unhappy. But why not use an automated 2/3 pass profile instead? That way you won't have to reset the bitrate. Likewise, you could use auto-mode, then update jobs, as in auto-mode, the bitrate is updated after audio encoding (that is assuming you are encoding audio.. if you don't, the bitrate is written into the jobs when they are added to the queue).

As for your second issue, it is not your fault. Well, it is sort of because your computer uses a comma as decimal separator, whereas x264 and any software made for the English market expects a dot. Unfortunately for me, that now means changing the commandline generator to use a different double/decimal -> string conversion for each double/decimal value :(

[mc_experimental]

For Doom9.

Why megui 0218a (very good tool Doom9!!!) not save log file? When i do an autoencode with shutdown, all work fine but no log, and also whit "delete completed jobs" unchecked in setting box, nothing in queue list. Other thing when select a video/audio profile sometime not working. Only select profile then press config and verify command line is safe, and appears SAR setting not saved in profile (es. make a profile for 16:9 whit SAR 64:45 then change to another profile, SAR remain same).

I use your tool for encoding DVBT recording. X264 and megui are fantastic!!! very very good quality.

Please can add *.mpv *.m2v extensions, or "all file" in D2V Creator input filebox? (Tired press *.* :p )

Many thanks for your work, and sorry for my bad english (i'm italian)


Bye

Mauro

[berrinam]

On the topic of AR, perhaps there should be an option in the OneClickWindow (not necessarily just the OneClickWindow, but I can't think of anywhere else it would be appropriate) to signal the AR instead of resizing.

[Doom9]

When i do an autoencode with shutdown, all work fine but no logHmm, it might be that due to the way I use to shut down the PC (native System calls), the close event may not be triggered and thus the log not be saved. I've only tested the shutdown once, probably even before the autosaving log was introduced, but I will add log saving to the shutdown method so it will be saved before the system is shut down. The log never made more sense than in the shutdown scenario.

and also whit "delete completed jobs" unchecked in setting box, nothing in queue list.That is desired behavior.. the option says so, doesn't it? If you want the jobs to be kept, don't activate that option.

About the SAR thing: it happens just in the scenario you described.. if a profile has no SAR, the current values are not overwritten because a 0:0 SAR makes no sense (0:0 is the default value). I can change that so that in case there's a 0:0, those fields are cleared.

perhaps there should be an option in the OneClickWindow (not necessarily just the OneClickWindow, but I can't think of anywhere else it would be appropriate) to signal the AR instead of resizing.Good idea, but it would be a codec conditional thing (not every codec has that feature). In such a case, auto-crop should still be done, but no resizing afterwards.

[berrinam]

About the 'delete completed jobs' problem: I mentioned it in the MeGUI dev thread a few days ago, but there hasn't been a new release since then, so the bug still exists, ie it currently ignores your settings, and always deletes completed jobs.

Good idea, but it would be a codec conditional thing (not every codec has that feature). In such a case, auto-crop should still be done, but no resizing afterwards.
Is it just Snow that doesn't support AR signaling? What happens with cropping to non-mod16 sizes? I suppose a rounding-resize would need to be put in.

[Doom9]

Is it just Snow that doesn't support AR signaling?It appears so.
What happens with cropping to non-mod16 sizes?That's going to be a problem, but that, too, is codec dependant. I know x264 requires mod16, XviD should work with mod2 and I have no clue about lavc - that would have to be tested.

[Doom9]

About the 'delete completed jobs' problem: I mentioned it in the MeGUI dev thread a few days agoI must've missed that. It's now taken care off, along with anything else reported. I just have to run a few test encodings to see if the numerous changes that were required to accomodate larger sizes (now using 9999MB as a target size is not a problem anymore) haven't broken anything

[Doom9]

the big bugfix release it out. enjoy. I'll hold off from putting up the x264 and snow release for a few days to see how these rather extensive changes play out.

[AnimeTheme]

So from 0.2.1.8a, x264 quantizer delta is now set to 4 by default. I know basically what quantizer delta means (the max q difference between consecutive frames), but what is its actual effect on encoding quality? Should I stick with 1, or use 4 now?

[Doom9]

I figure there was a reason for the default to be changed (it's the x264.exe default, that value didn't come from me). I'd go with the new default..

[mc_experimental]

the big bugfix release it out. enjoy. I'll hold off from putting up the x264 and snow release for a few days to see how these rather extensive changes play out.


Many thanks.

MC

[haubrija]

Doom9,

I'm having a big problem with audio encoding in 2.1.9. Here's my usual procedure.

1. Create AVS script with your creator and load it up. Load up AC3 file created by DGIndex 1.21 and create my settings (AVC 3 pass, AAC 5.1 HE, VBR High).

2. Hit Auto Encode and go for a 1/3 DVD setting.

3. Add Chapters and hit go.

4. Go to Jobs menu and hit start.

Now upon hitting start, the status dialog comes up but nothing ever appears there. MeGui just hangs. Now, I bring up the task manager and both MeGui and Besweet are there, but Besweet is consuming no CPU cycles. If I end the MeGui process, Besweet starts right up, instanly consuming 99% CPU.

I'm using Beswet b30. I tried another DVD to ensure I didn't have a bum AC3 file, but had the same problem.

Any help would be great.

[Doom9]

@haubrija: I don't see a log anywhere. Where is it? Also, can you break down the problem into parts (as per the problem reporting guidelines.. it's a process that you should be able to do without any help ;) ? In this case, if you just set up audio encoding, with the default settings for AAC, does the same happen? I very much think so, but it's essential information that allows to rule out a lot of code as the source of the problem...

[haubrija]

Doom9,

Sorry about the lack of log... here it is:

Generating jobs. Desired size: 1537212416 bytes
Setting desired size of video to 1537212416 bytes
Next job job1-1 is an audio job. besweet commandline:
"C:\MP4 Encoding\BeSweetv1.5b29\besweet.exe" -core( -input "D:\1 AC3 T02 3_2ch 448Kbps DELAY 0ms.ac3" -output "D:\audio.mp4" -logfile "besweet.log" ) -azid( -c normal ) -bsn( -6chnew -vbr_extreme -codecquality_high -aacprofile_he ) -ota( -d 0 )
successfully set up audio encoder and callbacks for job job1-1


As far as breaking it down into parts, I do not know what more I can tell you other than what is in my original post. I set up my auto encode like i said and then MeGui hung during the Audio encoding part.

Now, per your request, I ran it with default settings. No problems! It started just as it should had, so the problem must lie with my previous audio profile. Hope this helps.

[haubrija]

Oops... You may want the besweet log as well. Here ya go.

BeSweet v1.5b30 by DSPguru.
--------------------------
Using azid.dll v1.9 (b922) by Midas (midas@egon.gyaloglo.hu).
Using Shibatch.dll v0.25 by Naoki Shibata & DSPguru (shibatch.sourceforge.net).
Using bsn.dll v0.24 by DPeshev,Richard,E-Male,DSPguru (DSPguru.Doom9.org).

Logging start : 08/14/05 , 13:34:43.

C:\MP4 Encoding\BeSweetv1.5b29\besweet.exe -core( -input D:\1 AC3 T02 3_2ch 448Kbps DELAY 0ms.ac3 -output D:\1 AC3 T02 3_2ch 448Kbps DELAY 0ms.mp4 -logfile besweet.log ) -azid( -c normal ) -bsn( -6chnew -vbr_extreme -codecquality_high -aacprofile_he ) -ota( -d 0 )

[00:00:00:000] +------- BeSweet -----
[00:00:00:000] | Input : D:\1 AC3 T02 3_2ch 448Kbps DELAY 0ms.ac3
[00:00:00:000] | Output: D:\1 AC3 T02 3_2ch 448Kbps DELAY 0ms.mp4
[00:00:00:000] | Floating-Point Process: No
[00:00:00:000] +-------- AZID -------
[00:00:00:000] | Input Channels Mode: 3/2, Bitrate: 448kbps
[00:00:00:000] | Total Gain: 0.000dB, Compression: Normal
[00:00:00:000] | LFE levels: To LR -INF, To LFE 0.0dB
[00:00:00:000] | Center mix level: BSI
[00:00:00:000] | Surround mix level: BSI
[00:00:00:000] | Dialog normalization: No
[00:00:00:000] | Rear channels filtering: No
[00:00:00:000] | Source Sample-Rate: 48.0KHz
[00:00:00:000] +-------- BSN --------
[00:00:00:000] | bitrate: vbr extreme
[00:00:00:000] | HE-aac high quality encoding
[00:00:00:000] +---------------------

[AnimeTheme]

I suggest that aside from BeSweet, MeGUI should support another program for the audio encoding part, such as FFMPEG. BeSweet requires 2 DLLs from Nero AAC Encoder, which is NOT a free program (please correct me if I am wrong here). On the other hand, FFMPEG is FREE and supports AAC encoding as well (even though not as dedicated as Nero). What's cool is that you can use AVS for FFMPEG as well. So you can possibly write a single AVS script that can work for BOTH the video and audio parts.

[Doom9]

@AnimeTheme: This has been brought up before. I simply need BeSweet for its superior audio capabilities that no other program can offer. There was a volunteer to creating an faac plugin for BeSweet, but he seems to have disappeared again. mencoder also supports aac encoding, but there's no way audio encoding can be done in one step.. only besweet can do that.. any other solution relies on besweet decoding the audio, thus creating a huge temporary file which creates problems for people not using NTFS, and then encoding that again. That is why I'm using BeSweet with Nero.

ffmpeg's MP4 output is very buggy so using that is quite simply out of the question, I'm not going to support something that doesn't work properly.

Now, per your request, I ran it with default settings. No problems! It started just as it should had, so the problem must lie with my previous audio profile.Alright, so it's the setup after all.. can you pinpoint which option that you changed from the default trigger the problem?

[AnimeTheme]

I understand that BeSweet with Nero is better than other audio solutions (in terms of quality and such), but FFMPEG has its advantage as a FREE tool. I am not sure if FFMPEG's MP4 output is really that buggy, but I suppose it can handle AAC encoding just fine, and I have had NO problem using it to encode AAC for my x264 movies.

It will be cool if we can have a unified and completely FREE solution for x264 encodes. :cool:

[haubrija]

Ok, I discovered where the problem lies. I went step by step through my settings to find it. Not sure if its the combination but this is when it happened.

1. Default MeGui Settings - OK

2. Default + VBR Extreme - OK

3. Default + VBR Extreme + HE - OK

4. Default + VBR Extreme + HE + High Quality - OK

5. Default + VBR Extreme + HE + High Quality + Uncheck Increase Volume Automatically = NOT OK.

With that final combination above (unchecking increase volume), is where I had the problem with MeGui hanging.

[Doom9]

@haubrija: thank you for making these tests, I much appreciate it.

@AnimeTheme: I understand the feeling but as I said, give me an faac besweet plugin and I promise to support it. But I'm not going to rewrite MeGUI to require two tools for audio encoding when one is enough, free or not.

[m0rc1]

This really happens with lots of programs (most Adobe ones, for example - but also BeLight is completely unusable with a 120DPI display).
The problem is that if you set the AutoScale flag to true (which is a good thing), windows and dialogs can change their final size depending on the size of the text (which depends on the display resolution - in DPI).
To make a long story short: fixed windows sizes should not be used; in the case of MeGUI the problem is with the "Show commandline" options in most dialogs.
The handler should be changed to something like this:

if(commandlineVisible.Checked)
{
showCommandLine();
this.commandline.Visible = true;
this.Size = new Size(this.Width, this.Height + this.commandline.Height);
}
else
{
this.commandline.Visible = false;
this.Size = new Size(this.Width, this.Height - this.commandline.Height);
}

(here I'm assuming the commandline is shown by default).

m0rc1

[Igor Kharchenko]

Why I can't add mp3 audio in bitrate calculator when I select MP4 container? Is it non standart? I mixed raw x264 video stream and mp3 vbr audio using mp4box and it works fine.

[Doom9]

Why I can't add mp3 audio in bitrate calculator when I select MP4 container?Because megui doesn't support that combination. It doesn't make much sense using an inferior audio codec for a container made specifically to contain AAC audio (and MPEG-4 video of course).
You can also mux Vorbis or AC3 (not sure the latter is actually supported but it could be made to support it) into MP4, that's not saying that would make any more sense either. You'll get the best compatibility with MP4 if you stick to what it's meant for. If you want to use your prefered audio type, then use the Matroska container, it is made for flexibility and supports virtually every audio and video codec.

[DarkNite]

I love this app! The progress that's been made in this short span of time is amazing, and well appreciated. Kudos to everyone involved.

Now that I'm done with the praise, let's get down to the gripe.

Log for job job1-5

mkvmerge v1.5.0 ('It's alright, baby') built on Jul 1 2005 10:34:56

Error: 'jap' is neither a valid ISO639-2 nor a valid ISO639-1 code.
See 'mkvmerge --list-languages' for a list of all languages and their respective ISO639-2 codes.

'jpn' would be the appropriate entry here. Anime enthusiasts using mkv output would see this as a huge turn off. Other than that MeGUI is looking pretty sexy to me.

[dejected_is_me]

i noticed two things:

In the previous release, when a job was complted it was deleted from the queue, even if the "delete completed jobs" button was unticked in settings. I don't have anything to test if this was fixed just thought i would throw it out there...


the mux in mkv still works if the country code is disabled, with it enabled it just dosen't...

[Doom9]

@Darknite: this was previously reported. Unfortunately, without a log so I have only taken care of it after the last public release. It is already fixed in the development build, but I need to take care of the audio issue haubrija reported and the granny fonts issue when showing the commandline before a next release.

I don't have anything to test if this was fixed just thought i would throw it out there...If you check the changelog, this has been fixed.
the mux in mkv still works if the country code is disabled, with it enabled it just dosen't...could it be for the same reason darknite posted? If not, where's your log?

[noisehole]

hi,

i havnt encoded anything for a long time and just tried your gui (v0.2.1.9) for my first mp4 (nero he aac/x264cli high profile) encode and here is just a little feedback. there's some minor things i mention, but dont get me wrong - overall it worked great!

i used kung fu hustle ntsc ripped in ifo mode/movie only
attached is a queue screenshot, the log and the profiles i used.

-avisynth script creator: it suggested 640x352 which is 16:9 but the source is anamorphic and y-res of 256 would be correct (or did i mess up in dgindex?). also if suggest is checked and the input dar is changed the res should be updated

-input/audio i used 2 audio tracks, chi and eng. i have 2 audio profiles. if i change profile for stream1 it is changed for #2 too (i want different profiles for each stream)

-process status window: its set to some kind of always on top mode wich i find annoying

-i used automated 3pass and the commandline for pass 2 and 3 both had "--pass 3" as parameter. is that correct?

-i set the language names in the mp4 muxer, but mp4box wont take those arguments, without ";lang=chi" and ";lang=eng" the mp4box muxed correctly

-i could choose the vobsub generated *.sub file in the muxer but mp4box thought its a bad idea. do i have to convert it to ttxt?

using haali i got an impressive mp4 qualitywise. both audio streams are available, as are chapters.

great work :thanks:

[Doom9]

first thing: did you use the one click mode or the autoencode mode? the one click mode effectively only allows one audio profile that is applied to both streams. If you use auto-encode mode instead, the audio configuration will be taken as is.. so you configure your first input/output, select the profile, switch to the second track, configure it, select the profile, then encode. You can even switch between the tracks (obviously that won't show the profile you selected, but the settings will be there, press config to verify).

Please note that any profile selection is applied immediately to the currently active audio stream. Thus, you need to select the profile after selecting input and output for a track. If you select the profile before the audio track, it won't work the way you want it (you'll select the profile without input, so nothing will be applied, then you select input and output (once you select output the current settings from the profile will be applied), then you select the second profile, whose settings will be applied to the audio track currently shown (still track 1 at this point), then you switch to track 2, nothing is applied as there's no input and output, then you select input and output, and at this point the currently active settings (from the second profile you selected) will be used for that audio track. Thus, both tracks have the same settings.

This is a general principle throughout MeGUI. You always select your input, then output (not necessary if you are happy with the automatically generated output location and name), then the settings. I cannot prevent that you do this another way without severely restricting the GUI in ways I have no intention to do, but the results can be undesireable if you don't follow this rule.

According to this review (http://movie-reviews.colossus.net/movies/k/kung_fu.html) Kung Fu Hustle is effectively a 1:2.35 movie, so the correct resolution would be 640x272 (not 256.. that's ITU resizing and I don't accept telephony organizations to tell me how to resize video). I assume auto-crop failed.. if you open your avisynth script, do you have black bars? If you have, could you make a sample VOB available (you can strip audio, it won't have to be too long but it needs to be from a part other than the intro/credits but a part where there's a clear separation between black bars and the actual movie).

also if suggest is checked and the input dar is changed the res should be updatedduly noted.. it's just not the "normal" workflow

its set to some kind of always on top mode wich i find annoyingThat's not true actually.. you can always minimize. It just pops up, but that's what happens with new windows.. iirc the same happens in VirtualDub, and that's the model I used for MeGUI (the progress window is very similar after all and that's intentional, I've always liked the informative progress report VirtualDub provides, and I just improved upon that where I thought it would be useful (e.g. calculation of remaining processing time versus estimation of the entire process lenght so you have to substract elapes from estimated to get the remaining time))

i used automated 3pass and the commandline for pass 2 and 3 both had "--pass 3" as parameter. is that correct?yes, that's how it should be.

-i set the language names in the mp4 muxer, but mp4box wont take those arguments, without ";lang=chi" and ";lang=eng" the mp4box muxed correctly I have to put the blame on mp4box here: according to the list of ISO codes (http://www.w3.org/WAI/ER/IG/ert/iso639.htm), chi is the code for Chinese. You could use zho, perhaps that'll work, but if not you need to speak to the author of mp4box as it's not under my control if mp4box doesn't support a code.

-i could choose the vobsub generated *.sub file in the muxer but mp4box thought its a bad idea. do i have to convert it to ttxt?Actually, if you try you'll find that it'll fail. The thing is, there's a text based subtitle format that has the extension .sub and that's what mp4box supports, hence you can select .sub file (obviously a file dialog filter only checks extensions, not contents of the files).. the file open dialog also never speaks of VobSub which should be another indication that it won't work.. you can after all rename the extension of any file but unless the file contains what the extension suggests, it'll always fail. VobSub subtitle support may eventually come, but for now you need a supported text based format. Personally I'd use Subrip to create an .srt file.

[noisehole]

first thing: did you use the one click mode or the autoencode mode? the one click mode effectively only allows one audio profile that is applied to both streams. If you use auto-encode mode instead, the audio configuration will be taken as is.. so you configure your first input/output, select the profile, switch to the second track, configure it, select the profile, then encode. You can even switch between the tracks (obviously that won't show the profile you selected, but the settings will be there, press config to verify).

i used the autoencode mode. i didnt verify the audio config, just noticed that the profile display didnt change.

This is a general principle throughout MeGUI. You always select your input, then output (not necessary if you are happy with the automatically generated output location and name), then the settings. I cannot prevent that you do this another way without severely restricting the GUI in ways I have no intention to do, but the results can be undesireable if you don't follow this rule.

thats the way i expect a gui to function. i was just irritated by the options displayed

According to this review (http://movie-reviews.colossus.net/movies/k/kung_fu.html) Kung Fu Hustle is effectively a 1:2.35 movie, so the correct resolution would be 640x272 (not 256.. that's ITU resizing and I don't accept telephony organizations to tell me how to resize video). I assume auto-crop failed..

i didnt measure that exactly. guardian knot suggested 640x256 and comparing the dvd in software dvdplayers to the x256 avs (both fullscreen) seemed to fit more correctly. 272 would be 2.35, i just didnt check 2nd sources ;)

oh and autocrop worked perfectly, no bars at all (2,60,-2,-66). rechecked and its as accurate as it could be

That's not true actually.. you can always minimize. It just pops up, but that's what happens with new windows.. iirc the same happens in VirtualDub, and that's the model I used for MeGUI (the progress window is very similar after all and that's intentional, I've always liked the informative progress report VirtualDub provides, and I just improved upon that where I thought it would be useful

the similarity was obvious ;) so its just me that the window is really on top of others?
EDIT: hm enqueued an audio job and now the windows are normal. if i can reconstruct that issue ill report back. maybe it has something to do with starting hidden processes (besweet, x264...)
I have to put the blame on mp4box here: according to the list of ISO codes (http://www.w3.org/WAI/ER/IG/ert/iso639.htm), chi is the code for Chinese. You could use zho, perhaps that'll work, but if not you need to speak to the author of mp4box as it's not under my control if mp4box doesn't support a code.

thought so, but it didnt like eng either, so i didnt even try finding the correct value since it appears it wouldnt accept any

for the subtitles, i know that the correct mp4 format is ttxt, i just tried the vobsub. there was a chance your gui or mp4box converts them :p but ill try subrip, thx

[mc_experimental]

Ok, I discovered where the problem lies. I went step by step through my settings to find it. Not sure if its the combination but this is when it happened.

5. Default + VBR Extreme + HE + High Quality + Uncheck Increase Volume Automatically = NOT OK.

With that final combination above (unchecking increase volume), is where I had the problem with MeGui hanging.



Default + internet + HE + High Quality - OK

Default + internet + HE + High Quality + Uncheck Increase Volume Automatically = megui hang (218a - 219)

Bye

[noisehole]

":lang=LAN": sets imported media language code
thats all, just replace ";" with ":" and it works ;)

btw subrip method worked, i now got a nice mp4 with 2 langs, 3 subs and chapters. and all selectable/working with haali. i gotta say, im impressed with the results

[Doom9]

i just tried the vobsub. there was a chance your gui or mp4box converts them I'm afraid an automated OCR without human intervention is simply impossible (or you'd not be very happy with the result as everything would get discarded).
@mc_experimental: I guess that means that any profile causes this and the culprit is effectively the rest of the settings (HE, high and auto-volume adjustment disabled). Though I wonder, why would you want not to use the volume adjustment? You really have to crank up your stereo to hear anything if you don't use that option, and then when you listen to something else, you're going to blow your eardrums and speakers.

thats all, just replace ";" with ":" and it worksUhh.. my mp4box says to use a ;, not a :

And I need a VOB sample to look at the autosuggest resolution thing.. it properly suggests 640x272 with my 1:2.35 samples. Looking at your crop values, there can only be two reasons for a false detection: 1) dgdecode reports a wrong frame height, 2) you set a custom DAR.. it would need to be 1.778 for a 16:9 source. I tend towards 2 considering that this is the first ever report of a failure of this function.

[leowai]

Uhh.. my mp4box says to use a ;, not a :

That's the different version of MP4Box used.
v3.x uses ";" but v4.x uses ":"

[Doom9]

That's the different version of MP4Box used.
v3.x uses ";" but v4.x uses ":"I suspected that. But this is an user error.. the download url for mp4box given in the requirements only offers a v0.3x binary for download.

[AstaRoth]

Hi,

Congratulation for your software

But, do you find interesting to have an aspect error (in percentage) for resize in the avisynth script editor ?

[jellysandwich]

I found a small bug whilst trying to encode x264 to avi. I'm using MeGUI 0.2.1.9 and the mencoder from mplayer2005.08.13.Athlon-64.7z. It's reproducible for me.

Steps:

1) Open up MeGUI.
2) Tools -> Settings -> Set x264 encoder to mencoder.
3) Select an avs script.
4) Set Codec to AVC.
5) Set File Type to AVI or MKV.
6) Hit the Config button.

Then it crashes, with this error:


See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.IndexOutOfRangeException: Index was outside the bounds of the array.
at MeGUI.CommandLineGenerator.generateX264CommandLine(String mencoderPath, x264Settings xs, String input, String output)
at MeGUI.CommandLineGenerator.generateVideoCommandline(MeGUISettings settings, VideoCodecSettings vSettings, String input, String output)
at MeGUI.x264ConfigurationDialog.showCommandLine()
at MeGUI.x264ConfigurationDialog.x264EncodingMode_SelectedIndexChanged(Object sender, EventArgs e)
at System.Windows.Forms.ComboBox.OnSelectedIndexChanged(EventArgs e)
at System.Windows.Forms.ComboBox.set_SelectedIndex(Int32 value)
at MeGUI.x264ConfigurationDialog.set_CodecSettings(x264Settings value)
at MeGUI.MeGUI.videoConfigButton_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)


************** Loaded Assemblies **************
mscorlib
Assembly Version: 1.0.5000.0
Win32 Version: 1.1.4322.573
CodeBase: file:///c:/windows/microsoft.net/framework/v1.1.4322/mscorlib.dll
----------------------------------------
MeGUI
Assembly Version: 1.0.2050.42535
Win32 Version: 1.0.2050.42535
CodeBase: file:///E:/Downloads/Video/x264_cli/MeGUI.exe
----------------------------------------
System.Windows.Forms
Assembly Version: 1.0.5000.0
Win32 Version: 1.1.4322.573
CodeBase: file:///c:/windows/assembly/gac/system.windows.forms/1.0.5000.0__b77a5c561934e089/system.windows.forms.dll
----------------------------------------
System
Assembly Version: 1.0.5000.0
Win32 Version: 1.1.4322.573
CodeBase: file:///c:/windows/assembly/gac/system/1.0.5000.0__b77a5c561934e089/system.dll
----------------------------------------
System.Drawing
Assembly Version: 1.0.5000.0
Win32 Version: 1.1.4322.573
CodeBase: file:///c:/windows/assembly/gac/system.drawing/1.0.5000.0__b03f5f7f11d50a3a/system.drawing.dll
----------------------------------------
System.Xml
Assembly Version: 1.0.5000.0
Win32 Version: 1.1.4322.573
CodeBase: file:///c:/windows/assembly/gac/system.xml/1.0.5000.0__b77a5c561934e089/system.xml.dll
----------------------------------------
j0j6sedn
Assembly Version: 0.0.0.0
Win32 Version: 1.1.4322.573
CodeBase: file:///c:/windows/assembly/gac/system/1.0.5000.0__b77a5c561934e089/system.dll
----------------------------------------

************** JIT Debugging **************
To enable just in time (JIT) debugging, the config file for this
application or machine (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.

For example:

<configuration>
<system.windows.forms jitDebugging="true" />
</configuration>

When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the machine
rather than being handled by this dialog.


Would someone else mind trying to produce this error?

I found a simple workaround though:

1) Change File Type to MP4 or RAW.
2) Set up config.
3) Change File Type back to AVI or MKV.
4) Finish setting up and queue.

js

[jellysandwich]

What am I supposed to do with pgthreadGC2.dll?

js

[Doom9]

What am I supposed to do with pgthreadGC2.dll?just copy it wherever mencoder.exe is located. I'm not even sure you need it anymore, you can test that by setting the number of threads to 2 and start encoding. That dll was first also required for the VfW and exe version of x264 but subsequently was replaced with native threading code.. I suppose the same has been done for mencoder.

I can confirm your crash, I'll have a look at it.

But, do you find interesting to have an aspect error (in percentage) for resize in the avisynth script editor ?Not particularly.. I never found that indication in GKnot useful, especially since there's no way you can change it to something better without risking to break encoding (I enforce mod16 resolutions which is the only thing that will work with every codec MeGUI supports), and the resolution that is automatically picked with suggest resolution is the one that gives the lowest error compared to the real aspect ratio of the movie.

[Doom9]

alright, that crash, along with all other reported and reproducable problems are fixed now.

[Igor Kharchenko]

Firstly I made automated 2 pass job. Then I made 2nd pass postponed and started job. But after the 1st pass done, program started 2nd pass. Is it bug or feature? When I make 2 separate jobs, everything work as I wish, i.e. program stopped after 1st pass.

[Doom9]

s it bug or feature?A bug. I've fixed it in the development build.

[Doom9]

and the bugfix is now publicly available. See the first post for the changelog.

[m0rc1]

The audio file size is still a 32 bit integer but that should cover about 2 GB and I think we should be okay with that.

Mmm...
With a 3+h movie (LOTR) I got negative sizes for a 256kbps audio stream (MeGUI 0.2.2.0).

m0rc1

[Doom9]

that stupid calculator is going to be the end of me.. never again. Writing that was torture and it's not even over. It's no overflow though, 32 bits allow for up to 4 GB in size.

[leowai]

Hereby, I just want to suggest some cosmetic improvements to the MeGUI.

Pause feature while encoding using x264 works for me even though it takes some time to pause. However, MeGUI still shows the job is as "processing" in the Queqe tab after paused. Would it be better if MeGUI shows the status as "paused" here rather than "processing" after the pause?

On the other hand, the pause button "ll" should changed to ">" once it's clicked to pause the processes. Since the encoding processing takes quite a long time to response, so the change of button's status is telling the user to wait patiently for the precess to be paused.

[m0rc1]

that stupid calculator is going to be the end of me.. never again.
oh, well, I'm glad it's in the pack.

Writing that was torture and it's not even over. It's no overflow though, 32 bits allow for up to 4 GB in size.
I haven't checked but still might be an overflow (you know: if you firts multipy then divide, the multiplication can overflow the 31 bits for a positive integer...).

m0rc1

[Doom9]

Pause feature while encoding using x264 works for me even though it takes some time to pause. However, MeGUI still shows the job is as "processing" in the Queqe tab after paused. Would it be better if MeGUI shows the status as "paused" here rather than "processing" after the pause?
You forgot something crucial.. x264 encoding using x264.exetakes about 50 frames until it stops.. mencoder stops immediately. I'm suspending the thread the same way, I can only presume that x264 continues to work until the stdout and stderr buffers are full, and only then abort. It doesn't even take so long on my dual core X2 (even with all the options I have more than 16fps so the 50 or so frames it takes will be encoded rather quickly). Do you have a play icon for me with the right dimensions? I don't have any design tools, I drew the pause icon in pain and it was kinda annoying to get it to have the proper dimensions and be properly placed in the icon.

Oh and the paused thing.. when designing jobs there was no such state.. I would have to add that from the ground up.

I haven't checked but still might be an overflowthere's not only one.. there are tons of things you can do to really screw things up.. e.g. set a target size and then design an audio stream that's bigger than the video, set a zero length and I'm sure there's more.. with all the inter-dependencies of the GUI elements, it's a real pain to catch them all. You can go to 4 GB audio streams in the code I have now, I'm using unsigned 64 bit ints for temporary storage now.

[Egh]

FourCC selection for avc/mencoder seems to be b0rked in MeGUI last build.

that made several encoded fragments i tried to be encoded under VSSH fourcc.

Enable "show command line" and change fourcc's in the combobox. In my case what's selected in the list wasn't what was after --fourcc parameter in command line.

Also, sometimes there's no --fourcc key shown in command line at all, despite selecting different options from the combobox.

[Egh]

Another glitch.

still same build of megui. Selected x264 as my avc encoder. Selected .avi for it. MeGUI politely shows dialog x264 doesn't support that. Great. But why AFTER that dialog meGUI shows THAT:

*********************

See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.NullReferenceException: Object reference not set to an instance of an object.
at MeGUI.MeGUI.addVideoJob(Boolean start)
at MeGUI.MeGUI.queueVideoButton_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)


************** Loaded Assemblies **************
mscorlib
Assembly Version: 1.0.5000.0
Win32 Version: 1.1.4322.573
CodeBase: file:///c:/winxp/microsoft.net/framework/v1.1.4322/mscorlib.dll
----------------------------------------
MeGUI
Assembly Version: 1.0.2057.42352
Win32 Version: 1.0.2057.42352
CodeBase: file:///D:/VIDEOZZZ/mencoder/MeGUI.exe
----------------------------------------
System.Windows.Forms
Assembly Version: 1.0.5000.0
Win32 Version: 1.1.4322.573
CodeBase: file:///c:/winxp/assembly/gac/system.windows.forms/1.0.5000.0__b77a5c561934e089/system.windows.forms.dll
----------------------------------------
System
Assembly Version: 1.0.5000.0
Win32 Version: 1.1.4322.573
CodeBase: file:///c:/winxp/assembly/gac/system/1.0.5000.0__b77a5c561934e089/system.dll
----------------------------------------
System.Drawing
Assembly Version: 1.0.5000.0
Win32 Version: 1.1.4322.573
CodeBase: file:///c:/winxp/assembly/gac/system.drawing/1.0.5000.0__b03f5f7f11d50a3a/system.drawing.dll
----------------------------------------
System.Xml
Assembly Version: 1.0.5000.0
Win32 Version: 1.1.4322.573
CodeBase: file:///c:/winxp/assembly/gac/system.xml/1.0.5000.0__b77a5c561934e089/system.xml.dll
----------------------------------------
wr0pqh62
Assembly Version: 0.0.0.0
Win32 Version: 1.1.4322.573
CodeBase: file:///c:/winxp/assembly/gac/system/1.0.5000.0__b77a5c561934e089/system.dll
----------------------------------------
rzindssj
Assembly Version: 0.0.0.0
Win32 Version: 1.1.4322.573
CodeBase: file:///c:/winxp/assembly/gac/system/1.0.5000.0__b77a5c561934e089/system.dll
----------------------------------------
kobwwihr
Assembly Version: 0.0.0.0
Win32 Version: 1.1.4322.573
CodeBase: file:///c:/winxp/assembly/gac/system/1.0.5000.0__b77a5c561934e089/system.dll
----------------------------------------

************** JIT Debugging **************
To enable just in time (JIT) debugging, the config file for this
application or machine (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.

For example:

<configuration>
<system.windows.forms jitDebugging="true" />
</configuration>

When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the machine
rather than being handled by this dialog.

*********************
Although it seems to continue working as usual if you choose continue. But still such glitches are a bit worrying :)

[Doom9]

for future reference, you can save yourself the trouble of posting the crash report.. all that is required is the info on how to reproduce.

[Doom9]

what is "sometimes"? For modes where there's no output, there's not gonna be a fourcce either. Likewise, if the output is not fully configured in the main GUI, there will be no fourcc. This is because the commandline generator looks at the extension of the output filename to determine if we have avi output (in which case the fourcc will be appended), or something else (in which case the fourcc is not needed and will thus not be appended)

The fourCCs are stored twice, in an array and in the GUI and for some wicked reason the ones in the GUI got reordered. They're back where they ought to be now.

@edit: all fixed now.. there was also a reordering thing in the xvid dialogue and the asp dialogue had an empty entry.. no idea how that happened. I took the opportunity to improve the commandline generator for x264 (many options are superfluous in qp mode, and they are no longer added, and the corresponding GUI elements will be disabled as well).

[Egh]

Likewise, if the output is not fully configured in the main GUI, there will be no fourcc. This is because the commandline generator looks at the extension of the output filename to determine if we have avi output (in which case the fourcc will be appended), or something else (in which case the fourcc is not needed and will thus not be appended)

The fourCCs are stored twice, in an array and in the GUI and for some wicked reason the ones in the GUI got reordered. They're back where they ought to be now.

Thanx for explanation on that key. Where to get newer megui build? :)

Also, on the exception mentioned earlier. Have you managed to reproduce it? It's reproduced here w/o fail.

Steps I do:
Select x264 as avc encoder, select .avs script, select .avi as output, use queue. Dialog about x264 and avi incompatibility is shown. Press ok, dialog closes, MeGUI exception is shown.

[Doom9]

Have you managed to reproduce it?Yes, reproduced and fixed.

Where to get newer megui build?it'll be posted when it's ready. There are other things I want to take care off before new release, and the issues you've uncovered are mostly of cosmetical nature and not really a showstopper.

[AstaRoth]

Not particularly.. I never found that indication in GKnot useful, especially since there's no way you can change it to something better without risking to break encoding (I enforce mod16 resolutions which is the only thing that will work with every codec MeGUI supports), and the resolution that is automatically picked with suggest resolution is the one that gives the lowest error compared to the real aspect ratio of the movie.


Yes, but without error ratio (vary with the crop), it is difficult to minimize the "deformation" with the various values of the crop

[Doom9]

to minimize the "deformation" I have my doubts you'd notice it either way. We're really talking about tiny errors unless you grossly "mis-crop". And how would the error rate be computed anyway? What is your reference? What is a 0.0% error? Is it when you crop every black pixel and don't resize? What if you manually crop and screw up? where is the 0.0% error now? And next thing you're asking for a smart crop that works together with resize, right?

[AstaRoth]

sorry, my english is not very good, so it's difficult to explain clearly

For example :
I have a old movie with 4 black bands.
With autocrop and mod16, the movie is slightly stretched in height.
Then I decrease a little the crop in top and bottom to reduce the error.
At this time, if the height doesn't change, the image is less stretched in height.

I calculate the error with the new size and the crop compared to the true size

[Doom9]

you didn't answer my question.. what is a 0.0% error? Is it what I wrote in my post above?

Then I decrease a little the crop in top and bottom to reduce the error.and in the progress start wasting bits on encoding black lines (it's not the lines, it's having the cut between movie and black lines actually)? That's like swapping out one imperfection for one serious evil. The only option I consider remotely valid is cropping into the picture.. that's still trading one evil for another but the difference is smaller than if you crop less.

[Doom9]

a new build is up. enjoy

[leowai]

It doesn't even take so long on my dual core X2 (even with all the options I have more than 16fps so the 50 or so frames it takes will be encoded rather quickly).
:eek: I'm not that lucky as you because I'm still stick to a PIII 1GHz machine. So, it could take me few ten seconds for the stop! But this is not a big issue anyway. :p

Do you have a play icon for me with the right dimensions? I don't have any design tools, I drew the pause icon in pain and it was kinda annoying to get it to have the proper dimensions and be properly placed in the icon.

Oh and the paused thing.. when designing jobs there was no such state.. I would have to add that from the ground up.
I did the play icon as attached in this post. One which is the same size as the pause icon but looks smaller so I also did another slightly larger one. Hope it helps.

Thanks a lot. :)

[dejected_is_me]

this is more of a gripe then a bug... maybe both.

The new: "Warning about audio to small....thing" is rather annoying.
If there is a demand for such a feature then i will bite my tounge, other wise...COME ON! who sets the audio to larger then the video and doesnt notice. Or even the actual file size. If this is a must have featrue i suggest making the "to small check" when you push the apply button. When i go to put in a custom file size ie: 230 mb, it yells at me before i can add the 3 of 230 mb. Making me push the error button over and over again for each episode calculation. (Yes i was encoding more then one source.)

If im out of line slap me with a fish: (DOOM9 slaps dejected with a fish)

[Doom9]

@dejected_is_me: I'm trying to prevent people from stupid mistakes in the bitrate calculation with this feature.. its annoyingness is on purpose, it's there to make sure that people will set up the calculator to get a meaningful result. It takes but two clicks to make it disappear for good (one for the OK, another one to adjust the audio bitrate or output size). What good is the result of the calculation if it cannot be obtained? I figure you want audio for your episodes, don't you, so you need to calculate something that makes sense.. audio larger than output clearly doesn't make any sense at all.

[Igor Kharchenko]

and the bugfix is now publicly available. See the first post for the changelog.
Thank you for such fast fix.

Is there any plans to make compressibility test like in Gordian Knot? Or some other tool to estimate the complexity of the source.

[Doom9]

Is there any plans to make compressibility test like in Gordian Knot?No. I have never used that feature except when writing guides, and when even codec developers tell you it's not very meaningful, it is time to seriously reevaluate where you invest your time.

[bond]

That's the different version of MP4Box used.
v3.x uses ";" but v4.x uses ":"does megui already support mp4box 0.4.x with that? the link to celtic druids page points to 0.4.x builds already

[Liisachan]

This might be a known problem but:
MeGUI 0.2.2.2 seems to generate this option:
vcodec=snow:vqscale=5:vstrict=-2
for the 1st pass of SNOW 2pass. It doesn't generate the passlogfile specified.
Should be at least
vcodec=snow:vpass=1:vstrict=-2
or maybe something like
vcodec=snow:vqscale=2:vpass=1:vstrict=-2
would work (a la XviD).

[Doom9]

@Liisachan: hmm, I thought I had already fixed that but apparently not.
@bond: last time I checked, the latest build in CD's dev directory was based on 0.3.x, hence no change in the commandline generation. Is the 0.4.x series really stable enough now? I've seen a bunch of problems reported in the container form when it first appeared.

[Wishbringer]

In MeGUI (Avisynth Script Creator) it would be nice to have some templates in *.ini file to use per default.

e.g.:
LoadPlugin("RemoveGrainSSE2.dll")
RemoveGrain(mode=2)

LoadPlugin("FFT3Dfilter.dll")
FFT3Dfilter()

Because after changing something in first tab, all custom changes on second tab are gone and have to be written again.

[Doom9]

and where would those dlls reside? the way it's written, I suppose the directory where the avs resides, and that's not very practical, is it? On the other hand, there's the plugins directory to save you the hassle of loadplugin.

And I have to ask why don't you configure the standard options first, and then start to customize?

Last but not least, I'm very sceptical about making changes to the AviSynth editor.. there's a few good ones out there and I don't really want to compete with those.. what is offered is just a really basic set of features, enough to take care of basic resizing and interlacing/ivtc needs you might have, but those wishing for advanced features probably already have their favorite script editor anyway, and I'd have to go through considerable extensions to make them switch.

[MomoNyo]

I keep getting crashes here when it tries to start the second pass.
------------------------------------------------------
Microsoft Visual C++ Runtime Library

Buffer overrun detected!

Program D:\Program Files\Multimedia\MeGUI\x264.exe

A buffer overrun has been detected which has corrupted the program's internal state. The program cannot safely continue execution and must be terminated.
------------------------------------------------------
Same thing happens with mencoder. The only way I can finish a job is to copy/paste the commandline from the log window into a command prompt and run the encoder from there.

I'm not sure if it's my .NET Framework at fault (it's v1.1.4322, the one that's installed as default with Server 2003), or if something else is behind it. It's happened with the last few MeGUI builds so I don't think it's a new issue, but nobody else seems to have posted about buffer overruns.

At least I have a way around it, but it takes away the convenience of being able to let it run and come back to a complete mkv.

Just thought I'd let you know. Keep up the good work, I really like MeGUI :)

[Doom9]

It's happened with the last few MeGUI builds so does that mean that once upon a time it was working properly? Can you trace it back to a specific build? I have no W2K3 machine to try, but if you can tell me the last working build I could look at the differences between the last working and the first not working build.

[Doom9]

alright, mp4box 0.4.x is now supported and the snow bugfix is in.. and then there's some goodies (finally I don't have to change the number of threads manually anymore :)

[MomoNyo]

so does that mean that once upon a time it was working properly? Can you trace it back to a specific build? I have no W2K3 machine to try, but if you can tell me the last working build I could look at the differences between the last working and the first not working build.
It's never worked here. Well, I've only been trying out MeGUI for the last month or two so I've only used maybe the last 5 or 6 builds. I should have been clearer there.

The strange thing is it can do the first pass just fine. But when it starts the second pass, as soon as the encoding status window pops up, I get the crash dialog. For a while I thought the problem was with the encoders, but once I can use them fine via the command prompt I'm guessing it must be something to do with the way MeGUI hooks into them to report the encoding status. I'm not a programmer though, so that's not an educated guess ;)

[Doom9]

well.. the crashes are caused by the encoder, not MeGUI. I've seen .NET act a bit weird on W2K3 at work, so is there any need for you to run what's clearly a desktop app on a server OS?

[Liisachan]

Thanks for the update, I'm going to play with SNOW more later.
Meanwhile I'm feeling that this is a bit inconvenient:

MeGUI 0.2.2.3 : MP4 Muxer - You can set the FPS before you open the Video file, but you cannot set the FPS after you open the file (the pulldown list is grayed out).
Such a limitation doesn't make sense to me, but is this by design?

[Doom9]

Such a limitation doesn't make sense to me, but is this by design?This is effectively a bug and should not happen. The FPS should only be grayed out when the muxer is pre-fed with content that is to be encoded (so in auto-mode when you add additional audio streams, subs and chapters) and where the FPS is already known.

[Jerry_Sm@rt]

hi, i'd say it's really a powfull tool to encode with.
but i cann't make the one click encoder working ,maybe it's because the auto generated avs do not add LoadPlugin("dgdecode.dll") just like using the Avisynth Script Creator i had to add it myself.
Any way to fix it?

[Sirber]

Yes, add dgindex.dll in "C:\Program Files\AviSynth 2.5\plugins".

[Liisachan]

The FPS should only be grayed out when the muxer is pre-fed with content that is to be encoded (so in auto-mode when you add additional audio streams, subs and chapters) and where the FPS is already known. Then, perhaps this is by design after all. I tried to mux video-only MP4 (AVC encoded by x264.exe thru MeGUI) + MPEG-4 AAC in MP4, and what bothered me was, actually, not the grayed-out listbox, but MeGUI forcing -fps 25 if you don't specify FPS. I'm not sure, but my hunch is, you don't have to use the -fps switch in many cases, because MP4Box can auto-detect it. Nevertheless MeGUI seems to add -fps 25 whenever you don't specify it explicitly, and I'm wondering if that is really necessary.

[Doom9]

looking at it a bit more carefully, the fps is only grayed out if your input is an mp4.. in that case you don't need the fps. However, there are still two problems. One is that the fps is not reactivated when another non MP4 is being loaded, the other is that the default fps value for muxsettings is 25 fps.. since you must select an fps unless your input is an mp4, it makes no sense to force that default. I will set the fps to 0.0 so the fps won't be added to the commandline in case of mp4 input, but will be added for all other scenarios.

[Doom9]

@Liisachan: please try the new release, it contains the mp4 muxer fix.

[DeadRinga]

I find that if i select a language for the audio the mp4 muxer errors out with "Feature not supported"

[Jerry_Sm@rt]

Yes, add dgindex.dll in "C:\Program Files\AviSynth 2.5\plugins".
dgindex.dll???u mean dgdecode.dll ,it's already there.
i mean the auto generated avs is like this:
mpeg2source("D:\040602_2359\VIDEO_TS\VTS_01_1.d2v")
crop(0,0,-2,-2)
LanczosResize(640,352)
the one click encoder should've add a line like:
LoadPlugin("DGDecode.dll")

[Liisachan]

@Doom9: /me tested 0.2.2.3a MP4 Muxer for MP4 Video+MP4 Audio, and it worked fine.
For testing purpose, I even tried to confuse MeGUI by setting a random wrong value as FPS before I open my MP4 video file, but MeGUI just ignored it when the file was specified (the listbox was automatically reset, ignoring the CurSel), and the generated cmdline didn't have -fps either. :D
Thanks you!

[Doom9]

I find that if i select a language for the audio the mp4 muxer errors out with "Feature not supported"And which mp4box version would you be using? Please don't tell me 0.3.x, even the changelog states that two versions ago I moved to 0.4.x style syntax.

[DeadRinga]

Doh. I am usually good with keeping packages up to date, guess i missed the mp4box update. It was 0.3.x that was causing the issue. Now fixed. :)

[Doom9]

the one click encoder should've add a line like:
LoadPlugin("DGDecode.dll")No, the user should set up everything properly in accordance with what's posted in the first post. I've set up a completely new machine exactly like that and it works like a charm. Unless you mess up your AviSynth installation, copying dgdecode.dll into the plugins folder (and making sure you don't have an old mpeg2dec*.dll around there) works just fine and dandy. I don't understand why people insist on not using one of AviSynth's finest features: automatic plugin loading. It spares you a lot of grief when you move scripts around, install new software, etc.

[foxyshadis]

well.. the crashes are caused by the encoder, not MeGUI. I've seen .NET act a bit weird on W2K3 at work, so is there any need for you to run what's clearly a desktop app on a server OS?
The 4gig dual-xeon makes an excellent night-time encoding box, though it still doesn't compare to your X2. One of these days I'll try making a build farm out of a couple.

I haven't tried megui on it, so I can't offer more, sorry. If I have time I'll give it a try in the next few days and see if I can narrow it down to anything in particular.

[dejected_is_me]

I post this here because im unsure of the cause...

i have a hybrid DVD, Colorful from ADV films, that refuses to encode right. when i say hybrid i mean this:

If in DGIndex a source is switching between interlaced and progressive but is also being reported as completely FILM then don't worry - it's progressively encoded and Force FILM will restore the original frames. However, if it is switching and it's being reported as mostly NTSC then you have a hybrid dvd (just like the colorful disc I'm using below) and this will need to be handled in a different way, as I will describe later. Hybrid sources have two forms, one is where you have mostly FILM and only some parts interlaced and the other where only some parts will be FILM. These will be discussed in more detail later. Remember that some sources that only have a very small about of interlaced footage (such as FILM 98%) can often have Force FILM used.


I have the later. this is my script:

# PLUGINS
LoadPlugin("C:\PROGRA~1\GORDIA~1\DGMPGDec\DGDecode.dll")
LoadPlugin("C:\PROGRA~1\GORDIA~1\AviSynthPlugins\decomb.dll")

# SOURCE
mpeg2source("C:\DVD encodes\Raws\Colorfull\d2v\color.d2v", idct=7)

# IVTC
Telecide(order=1, post=4).Decimate(mode=1, threshold=1.0)

# CROPPING
#crop(0,0,720,480)

# RESIZING
LanczosResize(720,480)


I can encode a small part of the film, about 300 frames or so, and it comes out ok. 2 pass with latest xvid build and MEgui 2.2.2. But when i encode the whole movie and play the resulting file all i get is a black screen. The size looks right and the time is accurate.

Someone please help me. Im not sure if this my script error or a megui error.

-dejected_is_me

[LigH]

In my opinion, this cannot be the fault of MeGUI. Instead, better ask where DGMPGDec is discussed; MeGUI only handles the really active applications, but is not involved in the conversion process - this part is only done by AviSynth and the encoder.

[Doom9]

this is not the first time I hear this reported (long movie with xvid, output unusable). ligh is correct though, unless you can prove that it does not happen if you run the megui generated commandline from a dos prompt, it's the encoder's fault. I would do that test, and if it fails as well, like I suspect it will, file a mencoder bugreport via the appropriate channels (it may not help.. I've filed bugs before and they seem to be using the bugzilla mostly to be very quiet about what's happening - it happens with many open source projects in fact - in a forum it's much harder to ignore users clamoring so I guess that's why forums are often not liked for that kind of stuff ;))

[jmk]

hey, i just wanted to thank you, doom9, for your work on this great program!

i do have a problem though :rolleyes: :

what exactly has to be the format of subtitles inside an mp4 container? i know they have to be textbased but subrip's .srt format did not seem to work (at least, neither mplayer not vlc displayed any subs).

could you maybe post an example line?!


thx alot,
jmk

[Doom9]

@jmk: here are three sample lines from a file I know works (it's my standard subtitle track1)
1
00:00:14,328 --> 00:00:16,592
(mmam) Do youu fimdd mmme saddstc?

2
00:00:18,398 --> 00:00:20,730
Y ouu knmoww, Kiddddo...

3
00:00:20,801 --> 00:00:23,269
...I'dd Ikne to beeIeve...
If that doesn't work for you, then the error lies in the playback software.

[LigH]

Whattn thattn language?! :D

[Doom9]

that's English with me not having enough time to properly set up subrip.. I don't care that it's incorrect, I just needed some subs.

[Yama4050242]

a quick question, how much free space should be there with megui(0.2.2.3a)?

since i found a interesting thing that if my partition(with megui.exe on) space is 12x mb, the mp4 i muxed got no sound played.i tried for long to solve it, finally, i found that the disk space may be a problem, so i delete some file on the partition with megui.exe. after i deleted, i got 8xx mb space on that partion and the muxed mp4 is fine, the muxed mp4 output is 2xx mb.

do i need the space more than the output to run megui mp4 muxer?

i tried yamb with same version of mp4box.exe(both 0.4.0), of course yamb is on the same partition, the output file played fine

the output file is on another partition with enough free space

sorry for my messy organized information, but iv tried to provide as much as possible

[LigH]

Please expect to need at least twice the amount of desired video + audio size, because multiplexing requires that the data is duplicated once; no application is able to insert data into the same file it is reading from, it would destroy the file trying that, by overwriting data which would have been read later.

[Malkacoglu]

Hi everybody!

This is my first post and excuse my english.

First of all I want to say MeGUI is very perfect tool for x264 AVC encoding. I like it very much.

I found a bug in program.

Bug: if you setup default x264 encoder to mencoder, subq setting working wrong. When you select 6. RDO option in command line, its show subq=5. So I manualy enter this optin in custom command line en it works right.

http://img383.imageshack.us/img383/6403/mencoderbug8cj.jpg


And I want to ask some questions about some megui options

why dont you make a select option for psnr? I use it in mencoder at command line but i cant use it when i encode with x264. because in command line you add a option --no-psnr. is there a problem in x264 psnr option?

can you support mono mp3 format? for example I encode a very old movie and its sound format is mono. So I want to encode it mono mp3. Bu in your mp3 options there is no mono option.

why dont you support external audio files? For example I encode sound before the encoding proses so I want to use this file. Bu megui is not support external files. Its support it in muxer menu but i want to use it in autoencode mode.

Thank you! :cool:

Edit: I 'm using latest version MeGUI 0.2.2.3a.

[Doom9]

When you select 6. RDO option in command line, its show subq=5.Correct, I did not paste enough from the x264.exe commandline.

why dont you make a select option for psnr?psnr is useless to me.


can you support mono mp3 format?I have my doubts that I'll do that.. I like to have features I consider useful and since I don't care about old movies... You can always load an externally encoded MP3 though (see next point)

why dont you support external audio files?it is supported. Just set up your video as usual, do not load audio, press auto-encode. Then in the windows that pops up, check Add Audio Stream. Then when you press Queue, the audio muxer window will come up and you can select your MP3 audio stream.

[Malkacoglu]

Hi,

Thank you for answer my question.

[Doom9]

@Malkacoglu: the bug you reported is fixed now.

[Richard Berg]

Trying MeGUI for the first time. Nice interface, good amount of options without overwhelming.

How do I get it to use the audio track from the source?

[berrinam]

If you are doing each step separately, simply don't set up audio to encode, and then choose the original in the muxing stage. If you are using AutoEncode, similarly, don't set up the audio encoding, and when you press AutoEncode, check 'Add additional content', and you can select your audio in the muxing window which pops up.

In OneClick mode, check 'Don't encode audio', which will use the original audio.

[Richard Berg]

Hmm, I can't figure it out. Input -> Audio Input only lets me choose AC3, MP3, or WAV. Muxer -> Audio Input only lets me choose AC3, MP3, or AAC. One Click only lets me choose VOB, MPG, or TS. Just to make sure we're talking about the same thing: I do TV captures. My source is an AVI file (Huff/MJPEG + PCM) processed via Avisynth.

Since my Avisynth scripts are way slower than any encoder, an ideal front-end would also have an option to render out to a temp file whenever doing 2-pass. Should be fairly straightforward to automate Avs2Avi. Is the code available? I like C#.

Finally, a minor bug report: the command line shown in the AAC config dialog doesn't update when you choose different VBR presets.

[Doom9]

Is the code available? The first post of this thread is very enlightening ;) And I'm not using avs2avi.. there's no VfW here except for preview. And you need to extract your PCM.. there is no support for combined video/audio.. mencoder's audio capabilities stand no chance against BeSweet, never have and most likely never will.

[vidhead]

the mp4 video made with MeGUI - i used mplayer GUI - MPGUI to playback, its report shows 0 for bitrate - is this normal?

Playing J:\source\gw-3-04-e.mp4.
ISO: Unknown File Type Major Brand: avc1
Quicktime/MOV file format detected.
--------------
MOV track #0: 4310 chunks, 43100 samples
ID_VIDEO_ID=0
MOV: AVC decoder configuration record atom (43)!
MOV: Found unknown movie atom btrt (20)!
Image size: 512 x 384 (24 bpp)
Display size: 512 x 384
Fourcc: avc1 Codec: ''
--------------
MOV: longest streams: A: #-1 (0 samples) V: #0 (43100 samples)
VIDEO: [avc1] 512x384 24bpp 29.970 fps 0.0 kbps ( 0.0 kbyte/s)
ID_FILENAME=J:\source\gw-3-04-e.mp4
ID_DEMUXER=mov
ID_VIDEO_FORMAT=avc1
ID_VIDEO_BITRATE=0 <------?
ID_VIDEO_WIDTH=512
ID_VIDEO_HEIGHT=384
ID_VIDEO_FPS=29.970
ID_VIDEO_ASPECT=0.0000
ID_LENGTH=1438.10
==========================================================================
Opening video decoder: [ffmpeg] FFmpeg's libavcodec codec family
Selected video codec: [ffh264] vfm:ffmpeg (FFmpeg H.264)
==========================================================================
Audio: no sound
Starting playback...
VDec: vo config request - 512 x 384 (preferred csp: Planar YV12)
VDec: using Planar YV12 as output csp (no 0)
Movie-Aspect is undefined - no prescaling applied.
VO: [directx] 512x384 => 512x384 Planar YV12

mp4UI loads the mp4, show one video branch with Track 1 showing:
Type Video
Numberofsamples 43100
VideoType invalid <----?
Bitrate 0 <--- ?
duration 23:58.104 minutes
framerate 29.970fsp
width x height 0 x 0 <---?

if you try to export raw it throws
exception: MPEG-4 internal
reason: couldn'read sample 1

using MV2player the same mp4 shows:
resolution 512 x 384 < --looks correct
FPS = 0 <---?
Format = AVC1
Bitrate = 1154 kbps <--? if i remember correctly i fixed that at 700 or 800

the mp4 file size (without audio) 141696 kb - 2pass encode.

otherwise the mp4 plays without noticeable problem.

just curious.

[PatchWorKs]

Just a question: what about Theora ? and Dirac ?

[Doom9]

@vidhead: I wouldn't rely on MP4UI (created way before there was AVC).. but what mplayer reports could be atoms in the mp4 (somebody correct me if I'm wrong.. I never bothered learning all the details about the format).. and if an encoder / muxer doesn't write them, I guess 0 is the default.

@Just a question: what about Theora ? and Dirac ?: not available in mencoder so not really an option here. Perhaps one day in the future when they become more usable and deliver better quality and speed. In the case of Dirac, I don't even know of a tool that can take avs input and put the dirac stream into a container (plus then there's the thing about adding audio.. assuming AVI as container, any VfW based tool wouldn't work because there's no VfW Dirac codec....)

[haubrija]

Doom9,

Quick question. I saw that you were thinking about using encraw for xvid in MeGui. I'm getting ready to start my fall tv captures and was wondering if that's still your plan or if you're gonna still stick with mencoder. I really want to use custom quant matrix with windows and I think I remember you saying that with encraw we could use them. Thanks.

[Doom9]

encraw's commandline is still under heavy changes.. before it's reasonably settled I won't do anything that I have to redo two days after.

[babaz]

hi doom9
really longing for a version with "Nero-free" aac encoding (u know waht i mean, using latest besweet beta with dimzon plugins for FAAC)
would love it :D

[Doom9]

it'll happen.. it just takes time that I don't have right now.

[danpos]

Hi there! In order to sustain actualized myself in the present video editon scene, I did solve try MeGui out. The video used in present test is a piece of VOB (100 MB) chopped by kutterman.

For video encoding, I set x264.exe up through MeGui with following settings:

QPEL, CABAC, Loop -5, ChromaME, no B-Frames, 1 Reference Frames, P-Frames 8x8, Extra, other settings on default, ABR 1000 Kbits/s.

For audio encoding, I did choose AAC CBR 2.0 stereo 64 Kbits/s as output for each either AC3 5.1 tracks (english and portuguese audio tracks). Muxing is done by MP4 box CL app which is set up in GUI itself.

Follows down link for a resulting encoded clip:

MP4 AVC 1000 Kbps ABR - Two AAC 2.0 stereo 64 Kbps audio channels (http://uploadhut.com/view.php/325509.zip)
:o

Really is very impressive! :cool:

[neo_anderson]

hi,
i have 2 small questions, if want to set deblocking to -1 in megui that comes with x264 rev. 292, how to do that, should i set both alpha and beta deblocking options to -1? also, for dvd backups, which profile should be used, main or baseline or high? also, please tell me if there is any guide for using megui to do dvd backups using x264! i am little confused with 2-pass settings in megui!

[neo_anderson]

please someone help me with MeGUI Settings for dvd to x264 encoding!

[ipse]

First of all - thanks for good tool. MP4 absence is really boring in GK. :) But calculator and avs-editor in GK is much more smarter. I hope MeGUI will absorb best features from GK.

So, bugs and wishes on usability:

1. In MP4 muxer window in Video Input selection dialog I can't select nonexistent file. I want to add mux-job as final job after video and audio coding. But a have no video and audio files at this time.

2. Automaticaly set video output name in main window when opening avs-script. As it's in GK. E.g. simply changing <video>.avs to <video>.mp4 (or such other extension).
Addition: Hmm.. It's a good feature for muxing dialog too.

3. Put bitrate selection editbox in main window. This paramter changes on every new job. It is not comfortable to open codec settings window every time.

4. "Autostart job" checkbox in main window. I want to autostart only one job (usualy last) while I load chain of jobs. May be it would be better to add "Queue&Start" button near "Queue" button.


PS And do you think about centralized bugtraq? :)

[DarkNite]

@neo_anderson:

Main profile should be fine. High profile won't playback for everyone, at least not last time I checked. Nero may have updated sometime between the time I stopped paying attention to Recode\NVE\ShowTime and now.

[neo_anderson]

also, please tell me how to set deblocking to -1 in MeGUI , should alpha and beta deblocking both be set to -1?

[hellfred]

also, please tell me how to set deblocking to -1 in MeGUI , should alpha and beta deblocking both be set to -1?
I suggest you to have a look at DeathTheSheeps encoding guid :search: and mplayers manpage, there the x264encopts section. The parameters are not named exactly the same in mplayer/mencoder, x264 vfw interface and MeGUI (AFAIK) but you will get a good idea of what the different settings do.
Hellfred

[Doom9]

But calculator and avs-editor in GK is much more smarter.Please elaborate.

In MP4 muxer window in Video Input selection dialog I can't select nonexistent file. I want to add mux-job as final job after video and audio coding.Enter the awsome power of the auto-mode.. configure your video and audio, press the auto-encode button, select output and split size, check the checkbox to add streams, and you'll see a muxer window with everything needed pre-filled out, you can add your subtitle tracks and chapters.. so everything you can do with the muxer. There's no need to be able to select non-existent files (think about it logically for a sec.. it's not programmatically possible because a file open dialog needs existing files, and it doesn't make any sense because the automatization to mux after encoding is already here).

2. Automaticaly set video output name in main window when opening avs-script. Uh, I distinctively recall coding that... admittedly I had a few beers last night but my eyes do not deceive me, it's there. Not for the muxer though but I can put that onto the todo list.

3. Put bitrate selection editbox in main window. This paramter changes on every new job. It is not comfortable to open codec settings window every time.Let's see... I have a strong suspicion that you're unfamiliar with the auto mode, so that's feature 1 to make your suggestion superfluous. And there's option two: if you use the bitrate calculator, there's the apply button that applies the calculated bitrate to the currently selected codec.. and once again you don't need to configure the bitrate manually. With these two features, having a bitrate selector in the main window would be redundant, plus it breaks the separation between input/output and codec separation.

4. "Autostart job" checkbox in main window. I want to autostart only one job (usualy last) while I load chain of jobs. Uh, "load a chain of jobs"? How does that work? You probably meant to write something else as this makes no sense to me.

Let's see what happens if you add a job to the queue:
a) no job is currently being encoded
-> if autostart is enabled, the first job that will be added to the queue when you press the queue button will be encoded immediately.
-> if autostart is not enabled, the jobs will simply be added to the queue
b) a job is currently being encoded
-> regardless of the autostart, the job(s) is/are added to the queue. When the job that was being encoded when you pressed queue is done, there's another crossroads:
--> if you pressed the stop button in the queue tab, encoding will stop
--> if you didn't press stop, the next job in the queue will be encoded (taking into account job dependencies, chained jobs will be encoded after another regardless of their respective position in the queue).

There is no feature to encode "just this job" automatically and I don't see this as particularly useful. If you wish to get this, two clicks will take you there: 1) click on queue tab, 2)press the stop button. this will prevent any futher jobs from being encoded, but leaves the job that is currently being encoded to be encoded till the end.

When jobs error out, chained jobs are automatically skipped and the next non chained but queued job will be encoded (provided nobody pressed stop in the meantime).

Last but not least, pressing the stop button twice (it changes names from stop to start and reverse), will "re-start" the queue mode.. so if you decide at some point that you still want subsequent jobs to be encoded, just press that button again.

[bob0r]

Searched for "megui upsample"

I am not sure if this was already asked once, or in some to do list but:
Can MeGUI Upsample audio? like from 44KHz to 48KHz?
.... since Sony PSP only can play LC-AAC 48KHz, its quite wanted.


Also... what about winamp aac and aacplus encoding support?
Dimzon is going great with it, and the output is perfect, not those dirty nero files!

[Doom9]

audio wise I'm planning faac integration but nothing else at this point. The winamp encoders, as well as the reference encoder have one major drawback: they're CBR only. I'm waiting for a HA listening test to prove that those encoders beat faac despite CBR - perhaps that would change my mind.. but I have no plans in supporting 10 different AAC codecs.
And why would you need to upsample of digiTV and DVD uses 48KHz anyway?

[Sharktooth]

AAC+ v2 wont be bad though...

[bob0r]

..
And why would you need to upsample of digiTV and DVD uses 48KHz anyway?

Uhm, back in the day all movies were encoded 44KHz because some players could not handle 48KHz, including xbox in the beginning.

A lot of (old) divx/xvid movies can be converted to x264 for PSP with superb quality, but we MUST have 48KHz. Now i know encoding my own .aac with besweet and all with 48KHz is easy. BUTTTTTT since Megui is the best GUI i have seen in a long time, and i so love it, i would really love to see this, i would think, simple option.

---

As for the AACplus encoder, i agree about not supporting a lot of encoders, but FAAC for LC-AAC en winamp aacplus.dll for HE-AAC(AAC+SBR+PS) encoding would be perfect for now. CBR may not be what we want now, but until we can get any other, why not support it now.

(At least don't use nero for encoding AAC files, they are <insert nasty words here> !!

[Doom9]

A lot of (old) divx/xvid movies can be converted to x264 for PSP with superb quality, but we MUST have 48KHz.Cough cough, ayee matee (imagine me wearing an eye patch). If it's a legitimate backup, there should be a DVD to re-rip, shouldn't there?
why not support it now.Adding another audio encoder isn't such a small deal.. audio encoding related stuff is all over the place (well, not really, but there's plenty of instances that need to be changed now that I'm adding faac support, and one of the main reasons I never added Vorbis support is the additional complexity in adding yet another audio codec). I won't switch out the nero classes, conceptually it doesn't matter what the output is if the encoder is different.. just as there are two ASP codecs that are handled independently in the video area, there will now be two AAC codecs that will be handled differently.. and to make matters worse, I either have to mess with the dropdown in the main GUI or make an aac encoder selection in the settings.
PS is only useful for very low bitrates, which might be suited for mobile devices, but the PSP cannot handle HE, can it. For PC / Standalone playback, PS is really not needed as the bitrate simply is too low to give you a real movie feeling. Even I can hear bad audio at some point and I'm the exact opposite of an audiophile.

[bob0r]

Cough cough, ayee matee (imagine me wearing an eye patch). If it's a legitimate backup, there should be a DVD to re-rip, shouldn't there?
....

Uhm? Downloading in The Netherlands is still 100% legal.
Just sharing it is illegal, or when the contents itself is illegal (like kiddie porn, el-qaeda training video maybe... you get my point)

---

About the aac codec again, yes i agree, though psp will probably be "ready" in the future soon :)
You do whatever you want, its your party! ... you now know what the guests want though ;)

[Doom9]

well, I'm sorry, legal or not, I have always despised such format conversions and no tool of mine would ever support such a thing.. just like downsampling is out of the question for me. And obviously, somebody needs to share for you to be download ;) Those that downsample will need to come to my brainwashing seminar.. I'll teach them not to downsample.

[bob0r]

I will use -ssrc( --rate 48000 ) in besweet

bob0r slaps Doom9 with the :thanks: board

[Doom9]

a new release it out. there's your faac support...

[babaz]

a new release it out. there's your faac support...

for the holy ghost!
this is fantastic - have to try it immediately
:thanks:

[bob0r]

a new release it out. there's your faac support...

Great, now we can create complete PSP videos without extra tools.
Oh wait we can't, we can't upsample audio to 48000Khz :devil: :D

Next step replace NAAC with WAAC and we all happy! (N = Nero, W = Winamp) :scared: :goodpost:

(Nero = AACPLUS v1 (AAC+SBR))
(Winamp = AACPLUS v1/v2 (AAC+SBR+PS))
(Yes Nero can do ABR on AAC+SBR, but when the file size is so small and still sounds so well, who cares about ABR?)

:devil: :devil: mode: Support both Nero and Winamp, shall we start paypal for Doom9? The poor guy. :eek:

[max-holz]

Is it possible to have a guide that explain step by step how to encode using MeGUI and x264, also creation of AviSynth script and .avs files?
I have used the search function but I didn't find something suitable like the GordianKnot guide.

:thanks:

P.S

I'am a novice in this ground, I have always used tools like AutoGK or XMpeg doing my videos, is it a problem?

[Doom9]

@max-holz: tools - one click encoder and you don't really need a guide ;) you just need to create an audio and a video profile

[Doom9]

Oh wait we can't, we can't upsample audio to 48000KhzNot gonna happen. But you can always edit the job xml files and put whatever you like into the commandline and have it executed.. there just won't be any gui support for that.

Next step replace NAAC with WAAC and we all happy! (N = Nero, W = Winamp) Not gonna happen considering the lack of any non CBR mode. And PS is really pointless for DVD backups.

[max-holz]

@max-holz: tools - one click encoder and you don't really need a guide ;) you just need to create an audio and a video profile

I have tried with this script, MeGUI freeze and hang up:

LoadPlugin("C:\PROGRA~1\AutoGK\DGMPGDec\DGDecode.dll")
LoadPlugin("C:\PROGRA~1\AutoGK\filters\autocrop.dll")
LoadPlugin("C:\PROGRA~1\AutoGK\filters\RemoveGrainSSE3.dll")

movie = mpeg2source("C:\Scambio\Elaborazione Video\Hana\agk_tmp\Hana.d2v")
cropclip = autocrop(movie,mode=0,wmultof=4,hmultof=4,samples=8000,aspect=0,threshold=34,samplestartframe=1,leftadd=0,rightadd=0,topadd=0,bottomadd=0)
fixed_aspect = 1.42222222222222
c_width = width(cropclip)
c_height = round(height(cropclip) / fixed_aspect)
input_par = float(c_width)/float(c_height)
input_par = (input_par > 1.4) || (input_par < 1.25) ? input_par : (4.0/3.0)
out_width = 704
out_height = round(float(out_width) / input_par)
hmod = out_height - (floor(out_height / 16 ) * 16)
out_height = (hmod > 4) ? (out_height + (16 - hmod)) : (out_height - hmod)
new_aspect = (float(out_width) / float(out_height)) / fixed_aspect
autocrop(movie,mode=0,wmultof=4,hmultof=4,samples=8000,aspect=new_aspect,threshold=34,samplestartframe=1,leftadd=0,rightadd=0,topadd=0,bottomadd=0)
LanczosResize(out_width,out_height)
RemoveGrain(mode=2)
SelectRangeEvery(300,15)

[Doom9]

I swear one day we'll have a rule that if you claim a problem and don't provide reproduceability, you're going to get striked. It's not so much different from rule1..

[max-holz]

I swear one day we'll have a rule that if you claim a problem and don't provide reproduceability, you're going to get striked. It's not so much different from rule1..

I said I'am a novice.....

there is no error, simply the application freeze

[Doom9]

there's logs, jobs, etc.. it doesn't take a masters degree to post them. And if you say you're a novice, if your AviSynth script has more lines than you have fingers, something is really wrong.

[max-holz]

there's logs, jobs, etc.. it doesn't take a masters degree to post them. And if you say you're a novice, if your AviSynth script has more lines than you have fingers, something is really wrong.

No log, simply the application freeze and CPU goes to 100% when I press the button Queue,

[Doom9]

geez.. can I reproduce that? Screw that godawful script.. take a simple three liner that loads the d2v, crops and resizes, then explain what you do starting with you double clicking on megui.exe. This is the basics of error reporting, I presume everybody knows that as everybody knows the basics of what do do when your car won't work (check batteries, gas, the real obvious things that even somebody without any flair for technology can handle).
I like to make sure that my app runs as good as it can and that everybody can use it.. but it's people like you who'll eventually make me stop caring altogether.. I have already provided countless of hours for the community, and I think it's not unreasonable to ask for as little as a proper report in return. Gosh, I feel like never come back again right now.

[max-holz]

geez.. can I reproduce that? Screw that godawful script.. take a simple three liner that loads the d2v, crops and resizes, then explain what you do starting with you double clicking on megui.exe. This is the basics of error reporting, I presume everybody knows that as everybody knows the basics of what do do when your car won't work (check batteries, gas, the real obvious things that even somebody without any flair for technology can handle).
I like to make sure that my app runs as good as it can and that everybody can use it.. but it's people like you who'll eventually make me stop caring altogether.. I have already provided countless of hours for the community, and I think it's not unreasonable to ask for as little as a proper report in return. Gosh, I feel like never come back again right now.

With a simple script like this:

LoadPlugin("C:\PROGRA~1\AutoGK\DGMPGDec\DGDecode.dll")
mpeg2source("C:\Scambio\Elaborazione Video\Hana\agk_tmp\Hana.d2v")

the application works well, so I think there is something wrong in the script that I post above. As I said I'am not practice about AviSynth simply I run AutoGK and then I use his script.

[Doom9]

ahh.. see, now we're already getting somewhere ;) Was it that hard?
SelectRangeEvery(300,15)looks like you picked a compressibility check script. Still, a complete description of what you're doing is still essential to narrow things down.. it very much matters what you are doing in MeGUI, every click can potentially matter. Even a simple "load avs, press queue" goes through hundreds of lines of code. You cannot know at which line it freezes, but if you flood me with details, I might be able to figure it out, and that in turn might lead to something else, etc. Just look at http://forum.doom9.org/showthread.php?t=99909 for a good example on how the smallest of details can matter a lot, and how not properly investigating can lead to false conclusions.

[max-holz]

ahh.. see, now we're already getting somewhere ;) Was it that hard?
SelectRangeEvery(300,15)looks like you picked a compressibility check script. Still, a complete description of what you're doing is still essential to narrow things down.. it very much matters what you are doing in MeGUI, every click can potentially matter. Even a simple "load avs, press queue" goes through hundreds of lines of code. You cannot know at which line it freezes, but if you flood me with details, I might be able to figure it out, and that in turn might lead to something else, etc. Just look at http://forum.doom9.org/showthread.php?t=99909 for a good example on how the smallest of details can matter a lot, and how not properly investigating can lead to false conclusions.

I press the button to import the script and then ok, the application freeze at this moment. If you want you can use the script changing some few lines and test by yourself.

[dimzon]

Great, now we can create complete PSP videos without extra tools.
Oh wait we can't, we can't upsample audio to 48000Khz :devil: :D

Next step replace NAAC with WAAC and we all happy! (N = Nero, W = Winamp) :scared: :goodpost:

(Nero = AACPLUS v1 (AAC+SBR))
(Winamp = AACPLUS v1/v2 (AAC+SBR+PS))
(Yes Nero can do ABR on AAC+SBR, but when the file size is so small and still sounds so well, who cares about ABR?)

:devil: :devil: mode: Support both Nero and Winamp, shall we start paypal for Doom9? The poor guy. :eek:
And don't forget about reference AAC+2 encoder :)

[Doom9]

And don't forget about reference AAC+2 encoderAs I said, I won't support a gazillion AAC encoders. Plus, one thing to consider for your 5.1 attempts: there's only 2 ch channel coupling if you create 3 2ch streams and merge them together.. not quite ideal. And the reference encoder is cbr only as well and reference encoders aren't exactly known for speed.

I press the button to import the script and then ok, the application freeze at this moment.previously you said it froze when you pressed queue.. that's quite something different. Also, it matters if you have automatic script preview activated or not.

[berrinam]

@max-holz: If you want automated cropping and resizing, MeGUI can do that for you, without the hassle of copying the AutoGK script. As Doom9 said, the easiest thing to use if you want an AutoGK-like operating mode is the One Click Encoder which is part of MeGUI.

[vidhead]

I have tried with this script, MeGUI freeze and hang up:
...
RemoveGrain(mode=2)
SelectRangeEvery(300,15)

SelectRangeEvery() tells you its the compressability check avs script, just delete this line. also, the avs is called something_comptest.avs the movie.avs is exactly the same but without the last line.

my guess is the autocrop parameter samples=8000 that causing the big "freeze"...red HDD led was flicking like crazy so killed the task. change samples=10 works for me.

edit: LoadPlugin("C:\PROGRA~1\AutoGK\filters\RemoveGrainSSE3.dll") i changed this to RemoveGrain.dll coz i dont have an sse2 cpu :edit

[max-holz]

@max-holz: If you want automated cropping and resizing, MeGUI can do that for you, without the hassle of copying the AutoGK script. As Doom9 said, the easiest thing to use if you want an AutoGK-like operating mode is the One Click Encoder which is part of MeGUI.

Now I prepare a script by myself:

LoadPlugin("C:\Programmi\x264\DGDecode.dll")
LoadPlugin("C:\Programmi\x264\plugins\autocrop.dll")
LoadPlugin("C:\Programmi\x264\plugins\RemoveGrain.dll")
mpeg2source("C:\Scambio\Elaborazione Video\Hana\Hana.d2v")
AutoCrop(preview=false,wMultOf=4,hMultOf=4,leftAdd=0,rightAdd=0,topAdd=0,bottomAdd=0,threshold=34,samples=8000)
LanczosResize(720,416)
RemoveGrain(mode=2)

MeGUI works but I got this error:

The current job contains errors. Stopping queue mode
Generating jobs. Desired size: 1468006400 bytes
No audio encoding. Calculating desired video bitrate directly.
Setting video bitrate for the video jobs to 1174404 kbit/s
Setting desired size of video to 1468004352 bytes
Next job job1-1 is a video job. encoder commandline:
"C:\Programmi\x264\x264.exe" --pass 1 --bitrate 1174404 --stats "C:\Scambio\Elaborazione Video\Hana\Hana.stats" --analyse all --8x8dct --threads 2 --progress --no-psnr --output NUL "C:\Scambio\Elaborazione Video\Hana\Hana.avs"
successfully set up video encoder and callbacks for job job1-1
----------------------------------------------------------------------------------------------------------

Log for job job1-1

avis [error]: unsupported input format (DIB )
could not open input file 'C:\Scambio\Elaborazione Video\Hana\Hana.avs'

[max-holz]

Also this script doesn't freeze MeGUI but the error reported is the same:

LoadPlugin("C:\Programmi\x264\DGDecode.dll")
LoadPlugin("C:\Programmi\x264\plugins\autocrop.dll")
LoadPlugin("C:\Programmi\x264\plugins\RemoveGrain.dll")
movie = mpeg2source("C:\Scambio\Elaborazione Video\Hana\agk_tmp\Hana.d2v")
cropclip = autocrop(movie,mode=0,wmultof=4,hmultof=4,samples=8000,aspect=0,threshold=34,samplestartframe=1,leftadd=0,rightadd=0,topadd=0,bottomadd=0)
fixed_aspect = 1.42222222222222
c_width = width(cropclip)
c_height = round(height(cropclip) / fixed_aspect)
input_par = float(c_width)/float(c_height)
input_par = (input_par > 1.4) || (input_par < 1.25) ? input_par : (4.0/3.0)
out_width = 704
out_height = round(float(out_width) / input_par)
hmod = out_height - (floor(out_height / 16 ) * 16)
out_height = (hmod > 4) ? (out_height + (16 - hmod)) : (out_height - hmod)
new_aspect = (float(out_width) / float(out_height)) / fixed_aspect
autocrop(movie,mode=0,wmultof=4,hmultof=4,samples=10,aspect=new_aspect,threshold=34,samplestartframe=1,leftadd=0,rightadd=0,topadd=0,bottomadd=0)
LanczosResize(out_width,out_height)
RemoveGrain(mode=2)

[Doom9]

max, please search this thread for that error message..(yes, it's possible to search within a thread) and you'll find cause and what to do about it.

[bob0r]

NAAC/FAAC option: Delay Correction

When i try to out -300 in thats not possible, the "-" can't be added.

Also when i type a lot of numbers in the delay box, or remove the 0, then megui gives some quit message
(too large or too small for an Int32) guess we need a box limit :)

[max-holz]

max, please search this thread for that error message..(yes, it's possible to search within a thread) and you'll find cause and what to do about it.

I have resolved the problem, is an outdated version of autocrop dll.
I have one question about the autocrop, if I say to watch 8000 frames to determine the crop the application freeze (now I use 10 frames). Is it possible some workarounds about this problem in the next version?

Ciao

[Doom9]

8000 frames is an awful lot.. I use 10 myself in megui (well, we use, since berrinam greatly improved upon my code and fixed some bugs, and the whole thing is based upon ideas taken from gknot), and I haven't had any complaints.

When i try to out -300 in thats not possible, the "-" can't be added.You're saying you didn't demux with dgindex? Why on earth not? If the delay's in the filename, it'll be picked up even when it's negative ;) And you're evil trying to make MeGUI crash. Admit it, your audio doesn't have the delay you typed in <grin>

[bob0r]

@doom9:

cap MPA DELAY -300ms.mpa
When i typed i can't out, i meant i can't add :)

So i cant add negative values in delay for my audio encoding with megui-full.
I had to use belight, which delays and upsamples audio perfectly :goodpost:

And yes, i try everything in my power to break megui! :devil::D:devil::D

[Doom9]

just load that file, the delay will automatically be filled in (yes, negative delays are supported, I've personally re-verified yesterday evening). That kinda takes the need to type in anything away, doesn't it?

[locke86]

just load that file, the delay will automatically be filled in (yes, negative delays are supported, I've personally re-verified yesterday evening). That kinda takes the need to type in anything away, doesn't it?
is the delay taken in account when i just mux it using megui after encoding it with belight?

if so, is it possible to make it echo to the log that the delay is being taken care of? would help set my mind at ease

[bob0r]

just load that file, the delay will automatically be filled in (yes, negative delays are supported, I've personally re-verified yesterday evening). That kinda takes the need to type in anything away, doesn't it?

Yeah that really is great!
But, sometimes there are reasons to manually alter the audio delay, like satellite glitches or other errors.
Maybe i should use the word please, but audio delay(positive/negative) and audio upsample/downsample really complete megui as a simple complete encoding gui!

[AMED]

Is there any chance of implementing a force mono option for the audio output?
EDIT: I just tried using a mono WAV as the source audio, it still gets converted to 2 channels.


also on the automatic encoding window, could the file size box be in MB like how AutoGK does it's custom size, with up down arrows? http://img385.imageshack.us/img385/2672/clipboard018vo.png

[Doom9]

is the delay taken in account when i just mux it using megui after encoding it with belight? No, there's no delay option for muxing.. the whole delay thing in muxing still seems somewhat problematic so the smart thing to do is to take the delay into account when encoding the audio and compensate for it.
but audio delay(positive/negative)that's just nasty coding. You realize what negative GUI entry means: instead of just allowing numbers, I have do do another character comparison, and if it's a minus, see if there's not one already and that the entry box currently is empty and then allow it, otherwise do not react. Certainly not impossible and no great achievement but ugly another ugly code bit just for the GUI, that I think I'll do, but after the current dgindex rework phase, and right now coding really isn't on my mind (I hurt my neck, not as bad to take painkillers all the time but the lingering pain makes it hard to concentrate)
audio upsample/downsampleI'll say it for the last time: over my dead body. So you better go looking for your gun now or abandon hope because this is one issue where I will certainly not budge.

Is there any chance of implementing a force mono option for the audio output?I think that's been asked and answered before.

also on the automatic encoding window, could the file size box be in MB like how AutoGK does it's custom size, with up down arrows?Certainly possible but what good would it do?

[AMED]

Certainly possible but what good would it do?
make it easier for people who encode with sizes different to the ones that are pre set. i don't think anybody sets there encoding size down to the KB, correct me if i'm wrong.

[Doom9]

i don't think anybody sets there encoding size down to the KB, correct me if i'm wrong.good point.. in the autoencoding scenario, KB does indeed seem to be rather redundant.. going down to KB only makes sense with later muxing in mind and since that's all done in MeGUI.. but is a numeric up/down really preferable over a simple textbox? It may have a disadvantage (that a developer can hide from you): you need to press enter after manually typing in something (to be verified)

[AMED]

good point.. in the autoencoding scenario, KB does indeed seem to be rather redundant.. going down to KB only makes sense with later muxing in mind and since that's all done in MeGUI.. but is a numeric up/down really preferable over a simple textbox? It may have a disadvantage (that a developer can hide from you): you need to press enter after manually typing in something (to be verified)i personally wouldn't mind just a text box, what ever is easier for you to implement.

[Sharktooth]

good point.. in the autoencoding scenario, KB does indeed seem to be rather redundant.. going down to KB only makes sense with later muxing in mind and since that's all done in MeGUI.. but is a numeric up/down really preferable over a simple textbox? It may have a disadvantage (that a developer can hide from you): you need to press enter after manually typing in something (to be verified)
You can get the control value when it looses the focus or when typing the value in the box or when clicking the up/down arrows or when clicking the "Encode" button... etc... it there's an incorrect value set, just popup a messagebox with an "incorrect filesize" warning or (better choice) keep the focus on that control (maybe changing the background color to red?) until a correct value is set...

[wiak]

dude can you make it so it supports x64? to?
64bit encoding is way faster than crapy old 32bit!

here is some 64bit builds by squid_80 (http://forum.doom9.org/member.php?userid=67865) :D

XviD:
http://home.iprimus.com.au/ajdunstan/xvid64.zip
avisynth 2.55
http://home.iprimus.com.au/ajdunstan/avisynth64.zip
dgdecode:
http://home.iprimus.com.au/ajdunstan/dgdecode64.zip
x264 VFW:
http://home.iprimus.com.au/ajdunstan/x264vfw64.zip
x264 CLI:
http://home.iprimus.com.au/ajdunstan/x264cli_x64.zip
decomb:
http://home.iprimus.com.au/ajdunstan/decomb.zip
huffyuv:
http://home.iprimus.com.au/ajdunstan/huffyuv64.zip
undot:
http://home.iprimus.com.au/ajdunstan/undot64.zip

[berrinam]

@wiak: Can't you simply replace the 32bit binaries with the 64bit binaries?

[Doom9]

exactly.. there would be no measurable gain in a 64 bit MeGUI build as all the processing is done in AviSynth & filters, DGIndex, mencoder and x264.exe.. those need to be 64 bit, not MeGUI. Launching a commandline program is exactly the same in 32 and 64 bit operating systems

[wiak]

avs won't open in MeGUI, its why its not 64bit
it opens in VirtualDub-AMD64 :/

[jellysandwich]

Is it intentional that you can continuously move files up a queue, but not down?

js

[Doom9]

hmm.. if AVIFile is different on Win64.. somebody with one installed will have to have a look. Until I upgrade, there's no way for me to even have a look at this now.

Is it intentional that you can continuously move files up a queue, but not down?Hmm.. works fine here... that is, the "keep item marked" functionality seems to work improperly so if you move up, it marks jobs that are sent down the line, and then when you do the inverse, it only goes one step down, then up again, etc. But if you select the job you want to move around, then press down, it works every time. I don't know why it marks other jobs that are being moved around (could it be a problem in the listview component?), but I know why moving down without selecting the job each time works the way it works: selectedItems[0] returns the first job from the top, so if your order is job2 job1, you select job2 and press down, then both are marked and the next time you press down, selectedItems[0] is job1, so pressing down again moves that one down, etc.

[freshNewB]

I like megui very much . but...
thanks to flashget!!
There are many times I try to minimize the window by clicking the "close" bottum = ="
The megui will thoughtfully ask me if I really want to quit the program
however, no matter what I choose the encoding progress will be aborted
I know that I can ignore the message box and wait the encoder to finish its job.
But by this way I can't do anything before the encoding progress finished
I think it is not a good idea.
Could megui change the "close" function to "minimize to tray icon".
In general,we do not need to monitor the encoding progress.
I think that add a function "minimize to tray icon" will be great.

[Doom9]

Well, the X button kinda has to close the app.. that's what the windows design guidelines say anyway and it's not a good idea to derive from that. And, there's one inactive button in between the minimize button and the close button, and I will not believe that anybody can accidentally hit the close button when he means to hit the minimize button. Those buttons are big. I realize that you can accidentally hit the button that's next to the one you mean to press, but there's at least 1 cm in between those, so if you accidentally hit the wrong button, I'm 150% convinced that you cannot properly work on any PC as you'll do this in tons of other programs, too.
There's in fact a but when clicking X in the main GUI.. it shouldn't abort if you say no to the question asked. And then there's the famous "minimize everything to try" function ;)

[freshNewB]

Well, the X button kinda has to close the app.. that's what the windows design guidelines say anyway and it's not a good idea to derive from that. And, there's one inactive button in between the minimize button and the close button, and I will not believe that anybody can accidentally hit the close button when he means to hit the minimize button. Those buttons are big. I realize that you can accidentally hit the button that's next to the one you mean to press, but there's at least 1 cm in between those, so if you accidentally hit the wrong button, I'm 150% convinced that you cannot properly work on any PC as you'll do this in tons of other programs, too.

You are right.
All I need is a "minimize everything as a tray icon" function.
It 's not important how I achieve this thing(by clicking X or a menu item).

There's in fact a but when clicking X in the main GUI.. it shouldn't abort if you say no to the question asked. And then there's the famous "minimize everything to try" function ;)

My English is not very good.
I could not understand if you mean that a bu"g" .
and did you mean that there will be such a function soon?
If it's true,I'll look forward to the next release of megui.
thank you very much. very very much.

[Doom9]

windows adds an icon "minimize every app to the try" to the quicklaunch bar.. it minimized every app you have running, so there's really no need for something like that in megui. Eventually I'll make the progress windows optional, but that's that.

[celtic_druid]

If you want to minimise everything, just press D + the windows key (shortcut for show desktop).

[freshNewB]

i mean that minimize the window to the "system tray" (or something near the clock)
not minimize to the task tray (or something that the D + the windows key does)
it is just a suggestion.

[jellysandwich]

Quick question: For automated 2 pass, by default, where is the 2pass.log file placed? I thought it was in the same directory as x264.exe, but it's not there. I then searched all of my harddrives for it, but it came up empty (r304)...

js

[berrinam]

0.2.2.5a 09/20/2005
...
changed: stats file are written to the directory of the source and named to correspond to the source they are fromThis means they are now named something like moviename.stats.log and are placed in the movie's directory.

[Sharktooth]

I'm a bit confused... why 0.2.2.5 is newer than 0.2.2.5a?
What's the newer version?

[Doom9]

in the 0.2.2.5 zip: megui.exe, dated September 20th, 21:14
in the 0.2.2.5a.zip: MeGUI.exe, dated September 21st, 22:21
It's as it should be, isn't it? The order in which the downloads are displayed in a post is dependant on when they've been added.. the oldest one is on top, the newest one at the bottom.

[Sharktooth]

0.2.2.5 09/21/2005

changed: dgindex demuxing now only demuxes the chosen audio tracks (unless you select demux all) - this may require an update of dgindex so check the requirements above
changed: the way dgindex is being run has been simplified, this could potentially help people who've been having problems with the indexing function (I know of two people to have reported this). If it doesn't work, please download debugview from sysinternals, and run it while running megui and post the logged output here.

0.2.2.5a 09/20/2005

new: intermediate files can be deleted automatically
new: output of aborted jobs can be deleted automatically
new: aac encoding using faac is now possible
well... as is said 0.2.2.5a is dated 20 sep 2005... while 0.2.2.5 is dated 21 sep 2005... something is wrong.

[Doom9]

well.. it's always better to look at the actual files than the changelog ;) since everything is compiled on the same machines, those dates are less prone to human error..

[jellysandwich]

Ahh, I see, thanks berrinam.

js

[Kurtnoise]

@Doom9 : which values do you use for overhead & interleaving concerning mp4 file in MeGUI ?

[nightrhyme]

OK I need some newbie help :confused:

Tried this app and have some problems:

1: Why isn't it possible to queue more than one vob in d2v creator ?
(well I just did it manually in DGIndex)

2: Avisynth Script Creator always shows movie preview as 4:3 or stretched no matter what DAR I choose.
Screenshot:
http://img252.imageshack.us/img252/8208/avisynthcreator3tu.th.jpg (http://img252.imageshack.us/my.php?image=avisynthcreator3tu.jpg)

3: It's pretty hard to find a good resize. You have to manually change vertical and horizontal res and preview. Wouldn't it be possible to make it something like GordianKnot with instant preview ?

[Doom9]

which values do you use for overhead & interleaving concerning mp4 file in MeGUI ?It's all in BitrateCalculator.cs ;) 4.3 bytes/frame without b-frames, 10.4 bytes/frame with b-frames. Since audio is in MP4 already, there's no overhead there and I'm ignoring the small size difference between srt and srts subs muxed into MP4. If you have a formula there, please let me know, likewise for raw aac versus aac in mp4 (in both cases, muxed into mp4 the files get smaller).
1: Why isn't it possible to queue more than one vob in d2v creator ?That was discussed in the development thread. Encoding has basically no postprocessing.. you just do the next job after the encoder/muxer has completed. indexing has tons of postprocessing, starting with force film, locating and loading demuxed audio files, opening the avisynth script creator (all that in the context of the dgindex creator), create audio jobs based on a previously known profile, create avisynth script on a previously known resolution preference (and whether or not you want to keep the original ar or go 1:1), create video and mux job on previously configured container selection, profile selection and desired output size, subtitle and chapter files (all that in the context of the one click creator). And that's a heck of a lot of things you'd have to attach to an index job to allow automatation. I'm working on it now, but it's a long and tedious process.
Avisynth Script Creator always shows movie preview as 4:3 or stretched no matter what DAR I choose. Not correct. You get to see what's there, always the native resolution of the content without any resizing according to AR flags. That's how dgindex does it, and that's how GKnot does it. If you want to see what you get, that's what the preview button in the AviSynth script creator is for ;)
It's pretty hard to find a good resize.Huh? You select your AR (it's even done automatically when DGIndex can detect it from the input scream), then a desired horizontal resolution, then you just have to press auto-crop, and suggest resolution, so basically the only thing you have to set your mind on is the final horizontal resolution. If there is anything wrong with these functions I just mentioned please let us know.

[CEC]

Does the --no-psnr switch affect quality?

[nightrhyme]

Thanks for reply Doom9 ;)

D2V Creator:
I'm not sure I understand all the reasons for not being able to load more than one Vob in D2V Creator. But it sure sounds complicated. Good luck with implementing that ;)
I'll just do it manually with DGIndex for now

Regarding Avisynth Script Creator: Yes I see it's the same as DGIndex. I guess I'm just spoiled by GordianKnot and the instant preview of my resize and PAR it offers.

Regarding Resize: I did see a problem with the suggested resolution. However I figured out I had to check SUGGEST RESOLUTION after Crop.
BTW. Why Isn't it possible to go higher than 720 horizontal ?

Should have been 640 x 272
http://img279.imageshack.us/img279/4668/meguiresize4oh.jpg

I never did say thanks for developing this nice gui :p

[Doom9]

I'm not sure I understand all the reasons for not being able to load more than one Vob in D2V Creator. Now wait, I think I meant something else. There's no need to select more than one VOB.. subsequent vobs are automatically taken into account (as in you select VTS_05_1.VOB, and the dgindex project will be done for VTS_05_1.VOB, VTS_05_2.VOB, etc).

Why Isn't it possible to go higher than 720 horizontal ?The limit is imposed after loading the source.. you cannot go higher than the source resolution, but if you were to load a HDTV source, you'd see that your maximal horizontal resolution is higher. It just doesn't make sense to go higher than the source.

Should have been 640 x 272Could you cut a couple minutes worth of that VOB and upload them someplace for analysis.. according to my calculations that should indeed be a 1:2.35 movie and thus the suggested vertical resolution should be 272. You took that screenshot after applying the proper procedure (auto-crop, then suggest resolution, correct?)

I guess I'm just spoiled by GordianKnot and the instant preview of my resize and PAR it offers.You have the instant preview of cropping as well.. the output resolution really doesn't do much so I don't see any sense in complicating things by dynamically stretching and resizing the dgindex project preview.

[Doom9]

Does the --no-psnr switch affect quality?the way I read it, x264.exe can compute the PSNR while encoding, but that's of informational nature only.. since those calculations will take a few CPU cycles, I deactivated them for more speed.

[nightrhyme]

Thanx again for reply Doom9 ;)

Ohh I see that's how D2V creator works :D Didn't know

Resolution: ok 720 is max for pal. I guess It's just me who likes upsizing a bit :)

Resizing: No the resizing function works correctly. The screenshot was taken without cropping before checking SUGGEST RESOLUTION.

[locke86]

i have some problems with the mkv muxing function once you hit AutoEncode

it gives me no option to select if my .aac is AAC+ ( i understand the option needs to be checked for proper muxing if your .aac is AAC+ )

also the vobsub muxing doesnt work for me.. whenever i select a .sub to mux into the mkv i get an error saying there's a command line error.. i do not get an option to select a .idx - however in mkvmerge gui i have to select the .idx and it works perfectly

[Doom9]

it gives me no option to select if my .aac is AAC+Well, since MeGUI can create AACs on its own, and always does so in an MP4 container where the HE (I think that's what you mean) marker is already set and can be taken into account by a muxer, it's really no necessity for me, just additional work. And considering that I support not one but two different AAC encoders, it's not so off base thinking that people should use MeGUI for audio encoding as well, or at least provide an MP4 if they want features a raw stream muxer cannot accomodate properly. Then there's the thing that most players can figure out the type of stream regardless of the flags.
also the vobsub muxing doesnt work for methere's no such feature. mp4box doesn't suport vobsub subtitles... there's a text based format that has the extension .sub, I don't recall it's name right now but that is what the muxer supports (it stems from mp4box'es limitations.. it may get vobsub support one day but right now we just don't know)

[locke86]

Well, since MeGUI can create AACs on its own, and always does so in an MP4 container where the HE (I think that's what you mean) marker is already set and can be taken into account by a muxer, it's really no necessity for me, just additional work. And considering that I support not one but two different AAC encoders, it's not so off base thinking that people should use MeGUI for audio encoding as well, or at least provide an MP4 if they want features a raw stream muxer cannot accomodate properly. Then there's the thing that most players can figure out the type of stream regardless of the flags.
there's no such feature. mp4box doesn't suport vobsub subtitles... there's a text based format that has the extension .sub, I don't recall it's name right now but that is what the muxer supports (it stems from mp4box'es limitations.. it may get vobsub support one day but right now we just don't know)
but i am using mkv not mp4.. mkv supports vobsub subtitles but i get an error while muxing

for the aac i use besweet with dimzon's winamp dlls.. dont like NAAC because it requires nero installed and i hear winamp's dlls provide better quality sound than FAAC

[Doom9]

but i am using mkv not mp4.. mkv supports vobsub subtitles but i get an error while muxingThat doesn't matter.. the Matroska muxer is based upon the MP4 muxer, and I'm afraid the MP4 featureset in a way dictates the rest. Perhaps if you would share the error you're getting, it could be fixed in a future release ;)

[locke86]

That doesn't matter.. the Matroska muxer is based upon the MP4 muxer, and I'm afraid the MP4 featureset in a way dictates the rest. Perhaps if you would share the error you're getting, it could be fixed in a future release ;)
ok i will.. in like 10 hours ;)

muxing the .mkv movie file with .aac audio and vobsubs works fine in mkvtoolnix gui though.. thats why i thought it should work in megui as well :)

[locke86]

ok i will.. in like 10 hours ;)

muxing the .mkv movie file with .aac audio and vobsubs works fine in mkvtoolnix gui though.. thats why i thought it should work in megui as well :)


Error: 'D:\DVD\Projects\MOVIE_VTS_02_PGC1\MOVIE.sub': Error parsing a MPEG PS packet during the header reading phase. This stream seems to be badly damaged.

thats the error i get everytime i try to mux a .sub into an mkv with megui

[Doom9]

however in mkvmerge gui i have to select the .idx and it works perfectlyand there's no option to select a .sub file?

[locke86]

and there's no option to select a .sub file?
selection of the sub files is done in a dialog where you can browse for media files

i cant select a .sub file with 'all supported media files' in the dropdown menu for file types but if i switch to 'all files' it is possible to select a .sub

i havent tried if it works though.. all i know is that .sub muxing in megui doesnt work right and if i select .idx in mkvtoolnix it works fine

[Doom9]

i havent tried if it works though.Could you give it a shot please?

[dbzgundam]

I'm having a problem it seems, with MeGUI... Originally I thought it was a .NET problem

http://x1.putfile.com/10/27420491042.gif

Any causes, solutions?

[berrinam]

Not much information, dbzgundam. Perhaps you are running .NET 2? Otherwise, please explain when and how you get this error (eg, when you start the program, or when you press encode, etc).

[dbzgundam]

Not much information, dbzgundam. Perhaps you are running .NET 2? Otherwise, please explain when and how you get this error (eg, when you start the program, or when you press encode, etc).

Ahh, sorry.

No... I simply have to execute the program. >> And, no, I have 1.1. In fact, I reinstalled it (twice) to make sure, but no-go.

[movax]

Sorry for the obvious question, but any recent system changes/program installation?

[locke86]

i tried out muxing .sub into .mkv and this is what i got

http://img291.imageshack.us/img291/739/error8ir.th.gif (http://img291.imageshack.us/my.php?image=error8ir.gif)

[dimzon]

Seems like MeGUI trying to read "jobs" folder from current directory (not executable directory)

[Doom9]

@locke86: thanks for testing. I suppose the fix will be to simply disallow .sub input and enable .idx subtitle input instead. I'll put that into the next build but I have no release date yet as I'm completely restructuring the dgindex part to allow queueing of multiple one click jobs.

[dbzgundam]

Sorry for the obvious question, but any recent system changes/program installation?

Reinstallation of drivers for my mobo, GPU, LAN, and Sound (LAN and Sound are onboard if that matters)... Never caused me a problem before.

[Doom9]

Seems like MeGUI trying to read "jobs" folder from current directory (not executable directory)Well, according to the .NET class library, Environment.CurrentDirectory points to the directory where the process was started from. So, as far as the megui.exe process is concerned, that's the program directory.

[stax76]

Well, according to the .NET class library, Environment.CurrentDirectory points to the directory where the process was started from. So, as far as the megui.exe process is concerned, that's the program directory.

IMHO working dir can get you easily into trouble, I always try not to work with it. In fact I've never used it, couldn't even remember this property though I'm confident once I came across.

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemWindowsFormsApplicationClassStartupPathTopic.asp

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemEnvironmentClassCurrentDirectoryTopic.asp

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfsystemwindowsformsapplicationclassexecutablepathtopic.asp

[Doom9]

well, I'm only reading, not writing, and so far I have yet to see any evidence that it would cause any problems. After all, I'm reading this when generating the main class so I have a hard time anybody could change this, and even if it could be changed, at the point where I make note of it. Loading, saving and deleting is all based on my stored string, not getting the directory from the property again.

[FSB-SPY]

Okay, just went through 24+ pages of posts in hopes of making it fully clear on how to use this, to no avail...

lol (meaning, please don't scream or post little smiley faces that hold up the sign "SEARCH!")

1. Downloaded latest 315 build of x264
2. Downloaded AviSynth
3. Downloaded DGIndex
4. Downloaded MP4Box
5. Placed all into same directory
6. Write a totally basic AVS loading script off a created d2v project file:

# PLUGINS
LoadPlugin("F:\Apps\x264\DGDecode.dll")
# SOURCE
mpeg2source("F:\here\driven.d2v")

7. I can do everything (set-up codec, matrices, etc), but the pulldown box for Video Profile is empty, and I am guessing this is the problem. Hitting queue and then starting the job does nothing, it does not go anywhere obviously.

P.S. Someone posted a nice screen of the crop by pixel, etc options screen, I have no idea how to get there... but I am assuming this is the next step that I am failing to achieve. :P

P.P.S. Don't attack me too hard! :P

[stax76]

well, I'm only reading, not writing, and so far I have yet to see any evidence that it would cause any problems. After all, I'm reading this when generating the main class so I have a hard time anybody could change this, and even if it could be changed, at the point where I make note of it. Loading, saving and deleting is all based on my stored string, not getting the directory from the property again.

it's easily possible to launch the process in a working dir different from the startup dir e.g. from a shortcut or some other shell methods, some users have a real talent to screw things up ;)

[Doom9]

well.. I tried the shortcut but the jobs were still being loaded. Obviously it's easy to change but before I do, I really want to know in which situation the CurrentDirectory doesn't do its job.

but the pulldown box for Video Profile is empty,That's normal.. you need to go into the codec configuration, type a profile name and press the new button to create a profile.. But you can encode without a profile. Which queue button did you press? the one in the main GUI, Input tab in the video section? And there must be some entries in the log regardless of whether the job starts or not as the first thing is done before encoding starts is dumping the commandline used to the log, so where is your log?

Also, for cropping you don't need an AviSynth script.. you need to launch the AviSynth script creator, load your d2v file and do all the cropping and resizing and save the script file. This also requires your dgdecode.dll in the AviSynth plugin path as the readme states.

[Sharktooth]

@Doom9: Since i have really no time, could you please post the MeGUI-x264 2.2.6 binaries too?

[Doom9]

I will.. I basically got in the door this morning, had to answer a few voicemails and had a meeting right away so I only managed to post the full version. Now I'm at home with the flu :(

[Sharktooth]

Damn flu... sorry to bother you:(

[FSB-SPY]

@Doom9:

Alright! Now I see where the innitial confusion came from. I had previously been only using the x264 build of MeGUI, so it's no wonder I did not know where the AviSynth Script Creator was, etc. ;)

So here is my run-down with MeGUI 0.2.2.6:

I wanted to keep it really simple, and not even resize the video (from standard 720x480). Just crop the blackbars. So I check the "Crop" box, and un-grey the four field boxes of how many pixels I wish to crop vertically and horizontally. But, as soon as I try to change a value from 0, it gives me an error:

************** Exception Text **************
System.NullReferenceException: Object reference not set to an instance of an object.


Hitting AutoCrop, produces the same exact error.

So, I thought, ok... a bug for the time being. I can crop manually, via the AviSynth command Crop, right?

I had come up with a simple script line to get rid of the black bars manually: "Crop(0, 58, 0, -64)"

Hitting preview verifies it looks right, and I can see the video playing back just fine. So I hit Save, name the file and presto, I finally have made progress and have my AVS script ready to go. Time to encode!

Load my AviSynth Script, Video Output defined as an MP4 file, and then hit the Queue button. Click the Queue tab, and then hit Start. Nothing is happening... it is not processing any frames. :(


Next job job1-1 is a video job. encoder commandline:
"x264.exe" --pass 1 --bitrate 700 --stats "G:\Movies\Ripz\Ripz.Driven\preview.stats" --subme 6 --analyse all --8x8dct --progress --no-psnr --output NUL "G:\Movies\Ripz\Ripz.Driven\preview.avs"
successfully set up video encoder and callbacks for job job1-1
Job aborted, deleting output file...Deletion failed.


I even tried to use the most simple AVS, just the one that loads the d2v file and nothing else. Same result.

For the codec settings, I have all the macroblocks options checked, automatic 2-pass, and 6-RDO selected. I wanted the best possible quality, and did not care about encoding speed.

Any ideas? I feel so close, yet so far away. ;)

[kurt]

@FSB-SPY: did you set x264 as encoder? and place the x264.exe in the MeGUI-Folder?

[FSB-SPY]

Yep! They're all in the same folder... here's a picture, just in case:

[dimzon]

just a little suggestion for automatic huffyuv encoding support for slow avs scripts.

the idea is to automate such 3-pass encoding process
1 pass - encode provided AVS to HUFFYUV using mencoder
2 pass - first x264 pass using encoded losless video as input
3 pass - second x264 pass using encoded losless video as input
e.t.c.

[Doom9]

So I check the "Crop" box, and un-grey the four field boxes of how many pixels I wish to crop vertically and horizontally. But, as soon as I try to change a value from 0, it gives me an error:Did you load your d2v file and do you have a properly working preview of the video? the only reason I can imagine for you getting that error is that the script wasn't properly loaded.. then the image you're trying to crop is null and you get that error.

As far as encoding goes, the only way a statusupdate has the aborted flag set is if somebody presses the abort button. So I figure after waiting you pressed abort. Now your settings.. starts with the default values please.. always backtrack to something known to be working. Also, just in case configure the path to x264.exe (I don't know how you launch megui.. stax mentioned users can mess up paths and so perhaps x264 is actually not found for some wicked reason). Then go to the commandline and run that commandline and see if something happens.

@dimzon: and what about the 80 or so gigs that takes?

[fight2win]

can i use fielddeinterlace(full=false) in my avs script for use with x264 encoding?

[dbzgundam]

Still no luck with MeGUI over here... :(

I've done numerous uninstalls/reinstalls of the .NET Framework 1.1 but still nothing...

[fight2win]

dbzgundam, just use nero 7/recode, it has got awesome avc quality, no .net required, pm me for more details!

and yeah, why the friggin' hell no one answers my questions, are not not senseful mucho?

[stax76]

I've seen such weird dbzgundam screenshots from many DVX users over the years, that kind of stuff is hard to track. I would suspect it's related to how the application is launched and where it is located (network etc. cause such errors). Good look, if it cannot be solved I'll dig up my forum for those old topics regarding such issues.

[dbzgundam]

dbzgundam, just use nero 7/recode, it has got awesome avc quality, no .net required, pm me for more details!

and yeah, why the friggin' hell no one answers my questions, are not not senseful mucho?

Not all of us have money right now. :(

[haubrija]

Doom9,

I'm having an issue with encoding my HD caputres to Xvid using MeGui... First, here's my log:

Generating jobs. Desired size: 2398131200 bytes
Encoded audio file is present: D:\capture.ac3 It has a size of 116818944 bytes.
No audio encoding. Calculating desired video bitrate directly.
Setting video bitrate for the video jobs to 7498 kbit/s
Setting desired size of video to -2013655040 bytes
Next job job1-1 is a video job. encoder commandline:
"C:\MP4 Encoding\Mplayer\mencoder.exe" "D:\1.avs" -ovc xvid -o NUL: -passlogfile "2pass.log" -xvidencopts pass=1:bitrate=7498:max_key_interval=300:vhq=4:qpel:chroma_me:quant_type=mpeg:par=ntsc169:trellis:keyframe_boost=100:kfthreshold=1:kfreduction=20:overflow_control_strength=20:max_overflow_improvement=20:max_overflow_degradation=20
successfully set up video encoder and callbacks for job job1-1
----------------------------------------------------------------------------------------------------------

Log for job job1-1

xvid: bitrate setting is ignored during first pass

----------------------------------------------------------------------------------------------------------
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:
"C:\MP4 Encoding\Mplayer\mencoder.exe" "D:\1.avs" -ovc xvid -passlogfile "2pass.log" -xvidencopts pass=2:bitrate=7498:max_key_interval=300:vhq=4:qpel:chroma_me:quant_type=mpeg:par=ntsc169:trellis:keyframe_boost=100:kfthreshold=1:kfreduction=20:overflow_control_strength=20:max_overflow_improvement=20:max_overflow_degradation=20 -o "D:\1.avi" -of avi -ffourcc XVID
successfully set up video encoder and callbacks for job job1-2
----------------------------------------------------------------------------------------------------------

Log for job job1-2

desired video bitrate of this job: 7498 kbit/s - obtained video bitrate: 6251.28895217316 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:
"C:\MP4 Encoding\Mplayer\mencoder.exe" "D:\1.avi" -ovc copy -oac copy -audiofile "D:\capture.ac3" -mc 0 -noskip -o "D:\\1-muxed.avi"
successfully set up muxer and callbacks for job job1-3
----------------------------------------------------------------------------------------------------------

Log for job job1-3

MEncoder dev-CVS-050813-01:18-3.4.4 (C) 2000-2005 MPlayer Team
CPU: Advanced Micro Devices Athlon MP/XP/XP-M Barton (Family: 6, Stepping: 0)
Detected cache-line size is 64 bytes
CPUflags: Type: 6 MMX: 1 MMX2: 1 3DNow: 1 3DNow2: 1 SSE: 0 SSE2: 0
Compiled for x86 CPU with extensions: MMX MMX2 3DNow 3DNowEx SSE

86 audio & 201 video codecs
success: format: 0 data: 0x0 - 0x715a4032
AVI file format detected.
AVI: ODML: Building odml index (1 superindexchunks)
AVI_NI: No audio stream found -> no sound.
VIDEO: [XVID] 1280x720 12bpp 23.976 fps 6246.5 kbps (762.5 kbyte/s)
VIDEO: [XVID] 1280x720 12bpp 23.976 fps 6246.5 kbps (762.5 kbyte/s)
libavformat file format detected.
[V] filefmt:65536 fourcc:0x44495658 size:1280x720 fps:23.98 ftime:=0.0417
videocodec: framecopy (1280x720 12bpp fourcc=44495658)
Building audio filter chain for 0Hz/0ch/s16le -> 0Hz/0ch/??...
audiocodec: framecopy (format=2000 chans=0 rate=0 bits=0 bps=0 sample-0)
Writing AVI header...
ODML: Aspect information not (yet?) available or unspecified, not writing vprp header.
ODML: Aspect information not (yet?) available or unspecified, not writing vprp header.
File not found: 'frameno.avi'
Failed to open frameno.avi

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


Just to give u my exact procedure.

1. Capture .ts stream using MyHD.
2. Cut commercials using HDTV2MPEG2 and save back to .ts.
3. Demux .ts through Projectx.
4. Index using DGIndex 1.21.
5. Create Avisynth Script using MeGui... Script below

mpeg2source("D:\1.d2v")
SelectEven()
Decimate(cycle=5)

6. Load avs into MeGui for Automated 2pass with Turbo Checked, 2 bframes, Qpel, Overflows set to 20, VHQ 4, VHQ for B Checked, Chroma Motion, Closed GOP.

7. Hit Auto Encode, setting my desired bitrate manually. Check add audio stream and then add the ac3 that ProjectX created.

8. Go to Jobs and Start.

Now the 1st and 2nd Pass seem to go fine. But it crashes at the mux stage. When I open up the resulting .avi that MeGui had created in VirtualdubMod, I get Video Read Errors and no frames are displayed.

I've done dvd encodes using Xvid in MeGui with no problem. But I've tried two HD encodes with the same result. Is there a flaw in my procedure or did I uncover a bug? Thanks for any help.

btw... using MeGui 0.2.2.4... haven't gotten around to upgrading yet but it doesn't seem as if you've changed anything that would affect my problem.

[berrinam]

"D:\\1-muxed.avi"
From your log, it seems that this filename was suggested by the AutoEncode window. It isn't valid, and I'm guessing that that is what caused the problems. It seems that this illegal file is being suggested when the folder it is in is the root directory. You have two options for a temporary fix:
-override the output MeGUI suggests when you press AutoEncode, or
-don't encode in a root directory.

The bug should hopefully be fixed next version.

[haubrija]

From your log, it seems that this filename was suggested by the AutoEncode window. It isn't valid, and I'm guessing that that is what caused the problems. It seems that this illegal file is being suggested when the folder it is in is the root directory. You have two options for a temporary fix:
-override the output MeGUI suggests when you press AutoEncode, or
-don't encode in a root directory.

The bug should hopefully be fixed next version.

Thanks for the reply berrinam. But, if I understand you correctly, that the reason MeGui hung upon mux. However, shouldn't the video file (without the audio obviously) that MeGui encoded still be valid? why would it have all the video errors? Upon opening the file in Zoomplayer, the video just sits there at 0:00 and never moves. And like I said above, opening the file in Virtualdubmod just leads to video decode errors. Are these problems two different things or one in the same?

The main reason I ask is because, I'll run my encode again, but like I said its an HD file and I don't want to occupy my computer for 18hours if I don't have to :)

[berrinam]

Thanks for the reply berrinam. But, if I understand you correctly, that the reason MeGui hung upon mux. However, shouldn't the video file (without the audio obviously) that MeGui encoded still be valid?
Sorry, I didn't realise that the video file was also invalid. I don't know what the problem there is. From what you said in your previous post, MeGUI claims to be fine after the 2nd pass. The log doesn't indicate any failure either, so I'm not sure what is going on. Perhaps you should cut a few minute sample from your video and try re-encoding with that, to see whether it works or not.

[berrinam]

Setting desired size of video to -2013655040 bytes

There also seems to be something up with this, but according to log it didn't affect anything else.

[haubrija]

Just wanted to report back on some further testing.

I ran ProjectX on the source again, but only processed 17 second of the file. Created my .d2v on the file and set up the same script as outline above. Added my audio stream also as outlined above and started my queue. I followed Berrinam's advice and saved the output to a different directory.

This time the video output came out clean so Berrinam's quick workaround seems to have solved that problem. However, the muxing stage still did not work. Here's the log for that part of the job.

----------------------------------------------------------------------------------------------------------
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:
"C:\MP4 Encoding\Mplayer\mencoder.exe" "D:\Test\video.avi" -ovc copy -oac copy -audiofile "D:\capture.ac3" -mc 0 -noskip -o "D:\debug.avi"
successfully set up muxer and callbacks for job job1-3
----------------------------------------------------------------------------------------------------------

Log for job job1-3

MEncoder dev-CVS-050813-01:18-3.4.4 (C) 2000-2005 MPlayer Team
CPU: Advanced Micro Devices Athlon MP/XP/XP-M Barton (Family: 6, Stepping: 0)
Detected cache-line size is 64 bytes
CPUflags: Type: 6 MMX: 1 MMX2: 1 3DNow: 1 3DNow2: 1 SSE: 0 SSE2: 0
Compiled for x86 CPU with extensions: MMX MMX2 3DNow 3DNowEx SSE

86 audio & 201 video codecs
success: format: 0 data: 0x0 - 0xfa078a
AVI file format detected.
AVI_NI: No audio stream found -> no sound.
VIDEO: [XVID] 1280x720 12bpp 23.976 fps 7476.6 kbps (912.7 kbyte/s)
VIDEO: [XVID] 1280x720 12bpp 23.976 fps 7476.6 kbps (912.7 kbyte/s)
libavformat file format detected.
libavformat file format detected.
[V] filefmt:3 fourcc:0x44495658 size:1280x720 fps:23.98 ftime:=0.0417
videocodec: framecopy (1280x720 12bpp fourcc=44495658)
Writing AVI header...
ODML: Aspect information not (yet?) available or unspecified, not writing vprp header.
ODML: Aspect information not (yet?) available or unspecified, not writing vprp header.

Writing AVI index...
Fixing AVI header...
ODML: Aspect information not (yet?) available or unspecified, not writing vprp header.

Video stream: 7476.642 kbit/s (934580 bps) size: 16371526 bytes 17.518 secs 420 frames

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

it shows my .ac3 in the commandline but then later says no audio stream found. Mencoder can mux .ac3 streams right? I successfully muxed the stream using Virtualdub mod. So avi muxing is still an issue for me.

[haubrija]

Just noticed something while looking for something else on the forums.

Could this be my problem on the video end?

http://forum.doom9.org/showthread.php?t=101079

Is that a known issue? My resulting file from my first encode was 1.78 gb.

[dbzgundam]

Hmm... Is there a registry setting that .NET is not installing perhaps? When I uninstalled the package, nothing actually changed; same error as before. Could this mean the .NET package isn't even being recognized?

[dimzon]

@dimzon: and what about the 80 or so gigs that takes?
1) This must be optional feature!
2) I have enought HDD space for it :)

[leowai]

As a request from this post:
http://forum.doom9.org/showthread.php?p=722438#post722438
Yes that was the problem. I think this is very confusing for newbie's like myself. I wish this was made clear in a sticky somewhere.
Would it be nice to made this thread sticky on the AVC main page? Even this thread is linked from Sharktooth daily build, but not many newbies are able to caught this lovely GUI prog from there.

[fight2win]

get nero 7 from any warez site dude!

[sjchmura]

So when using the MP4MUX and besweet (to make AAC+AVC) the DELAY -922 SHOULD work - right??? That means it will make the audio start sooner?

This is wrong on my HDTV OTA transport streams. Can I just adjust this by renaming the AAC/MP4 audio file to -0ms???

[berrinam]

@sjchmura: Please be more clear. You haven't said what is wrong with the delay (whether it is changing at all, being removed, overcompensated, etc), and more importantly, you haven't said what you did which resulted in it not working

As a side note, MeGUI handles delays by fixing them upon encoding the audio. If you didn't set the delay when you encoded the audio, then I believe it won't work.

[haubrija]

So when using the MP4MUX and besweet (to make AAC+AVC) the DELAY -922 SHOULD work - right??? That means it will make the audio start sooner?

This is wrong on my HDTV OTA transport streams. Can I just adjust this by renaming the AAC/MP4 audio file to -0ms???

sjchmura, for HDTV OTA streams, you should really demux them first using ProjectX... this will give you the best streams and fix any problems you have with audio delay.

[zajc]

Moving post to http://forum.doom9.org/showpost.php?p=723496&postcount=371

:cool:

[max-holz]

I have an issue using AutoEncode button since version 0.2.2.6
Generating jobs. Desired size: 1433600 bytes
The second pass job has a desired final output size of 1433600 bytes
and video bitrate of 1637 kbit/s
The size of the first audio track is 135051582 bytes
Desired video size after substracting audio size is -132172
Setting the desired bitrate of the subsequent video jobs to -163 kbit/s
Next job job1-2 is a video job.
encoder commandline: "C:\Programmi\x264\x264.exe" --pass 1 --bitrate -163
--stats "C:\Scambio\Elaborazione Video\Febbre\Febbre_movie.stats"
--ref 5 --mixed-refs --bframes 3 --subme 6 --weightb --analyse all
--8x8dct --me umh --threads 2 --cqmfile "C:\Programmi\x264\eqm_avc_hr.cfg"
--progress --no-psnr --output NUL "C:\Scambio\Elaborazione Video\Febbre\Febbre_movie.avs"
successfully set up video encoder and callbacks for job job1-2

I set the final file size to 1400 MB and the audio track size after compression is 128 MB; I think there is a problem substracting the audio file size to the deisred final file size and this causes the application setting a negative bitrate for the encoding.

[berrinam]

The fix to the bug max-holz mentioned can be found here (http://forum.doom9.org/showthread.php?p=724251#post724251).

[max-holz]

Perhaps I have founded another bug; in the audio encoder configuration it seems to be impossible setting a negative value in the delay correction textbox. I suppose that this textbox has a pattern that accept only numeric values but in this case is not possible to digit the sign minus.

[stratocaster]

Hi,
Am I missing something or it's just MeGUI's rendered H264 files that are NOT COMPATIBLE with QuickTime7 ?
I simply can't play any of the rendered MP4[H.264,AAC] on QuickTime.
Please try to give me some hints, thxs a lot.

[Sharktooth]

It's not megui and neither x264/h.264 etc...
It's QuickTime fault, coz it doesnt follow the standards.

[Liisachan]

QuickTime doesn't like some of High Profile things. Try Config->Main->AVC Profiles->Main Profile.
Furthermore, QuickTime doesn't like MPEG-2 AAC (this problem was in QT6 and apparently not fixed in QT7). If you use psytel/faac/foobar2000 and get .aac file. it's not MPEG-4 AAC but MPEG-2 AAC by default. If you are using faac, make sure to output in .mp4 or, if you have to output in .aac for some reason, use "--mpeg-vers 4" to make QT happy.

[stratocaster]

QuickTime doesn't like some of High Profile things. Try Config->Main->AVC Profiles->Main Profile.
Furthermore, QuickTime doesn't like MPEG-2 AAC (this problem was in QT6 and apparently not fixed in QT7). If you use psytel/faac/foobar2000 and get .aac file. it's not MPEG-4 AAC but MPEG-2 AAC by default. If you are using faac, make sure to output in .mp4 or, if you have to output in .aac for some reason, use "--mpeg-vers 4" to make QT happy.

Thank you guys for replying.
As for the hints you gave me Liisachan, does it mean than I could manage somehow to make an MP4[H.264, AAC] file rendered by meGUI playable on QuickTime an on the new iPod ? or I must simply forget it as mentioned by Sharktooth?

[Liisachan]

you can. try "Config->Main->AVC Profiles->Main Profile" in megui (x264)

[Doom9]

Perhaps I have founded another bug; in the audio encoder configuration it seems to be impossible setting a negative value in the delay correction textbox. I suppose that this textbox has a pattern that accept only numeric values but in this case is not possible to digit the sign minus.It's not a bug, it's a feature in a way.. standard textboxes allow any kind of input, I limited it to numeric input only. I'm not much a fan of entering the delays in the first place but a big believer into dgindex's naming scheme that contains the delay.. if you have such a file, even if the delay is negative, it's being properly picked up.

I just got back from my holiday and need to get over the jetlag and lack of sleep first, but for now I have approved berrinam's bugfix build in the development thread: http://forum.doom9.org/showthread.php?t=95863&page=19&pp=20

I'm sorry I disappeared so quickly, but 1.5 days before the start of my holidays I got sick and thus couldn't take proper care of all the details that needed to be taken care of for my absence :/

[ChronoCross]

I'm not sure if this is a bug or it's already been reported but if you use the X button to close MeGUI after your queue is clear(finished encoding not the clear button) when you reload MeGUI those jobs reappear. If you go to file Exit this does not occur.

[haubrija]

I finally got around to upgrading to 0.2.2.6 last nite and the latest build of x264. Set up my normal 2 pass mode, doing an auto encode for 1/5 DVD size. My final file however ended up being a 328mb file. Looking through the log, there seems to be some weird oddities (at least to my untrained eye :))

Generating jobs. Desired size: 901120 bytes
Setting desired size of video to 901120 bytes
Generating jobs. Desired size: 901120 bytes
Setting desired size of video to 901120 bytes
Generating jobs. Desired size: 716800 bytes
Setting desired size of video to 716800 bytes
Next job job1-1 is an audio job. besweet commandline:
"C:\MP4 Encoding\BeSweetv1.5b29\besweet.exe" -core( -input "D:\PS\1 AC3 T01 3_2ch 448Kbps DELAY 0ms.ac3" -output "D:\PS\audio.mp4" -logfile D:\PS\audio.besweet.log ) -azid( -c normal ) -bsn( -6chnew -vbr_extreme -codecquality_high -aacprofile_he ) -ota( -d 0 -g max )
successfully set up audio encoder and callbacks for job job1-1
----------------------------------------------------------------------------------------------------------

Log for job job1-1

besweet: "C:\MP4 Encoding\BeSweetv1.5b29\besweet.exe" -core( -input "D:\PS\1 AC3 T01 3_2ch 448Kbps DELAY 0ms.ac3" -output "D:\PS\audio.mp4" -logfile D:\PS\audio.besweet.log ) -azid( -c normal ) -bsn( -6chnew -vbr_extreme -codecquality_high -aacprofile_he ) -ota( -d 0 -g max )

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

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

[01:39:32:128] |

SR: 48000, Table idx: 4 - start 13, stop 10
SR: 48000, Table idx: 4 - start 13, stop 10
SR: 48000, Table idx: 4 - start 13, stop 10
SR: 48000, Table idx: 4 - start 13, stop 10
SR: 48000, Table idx: 4 - start 13, stop 10
SR: 48000, Table idx: 4 - start 13, stop 10
[01:39:32:128] Finalizing...
[01:39:32:128] Conversion Completed !

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

----------------------------------------------------------------------------------------------------------
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-1 the first pass job1-2 and the second pass job1-3
The second pass job has a desired final output size of 901120 bytes and video bitrate of 700 kbit/s
The size of the first audio track is 195056554 bytes
Desired video size after substracting audio size is -191059Setting the desired bitrate of the subsequent video jobs to -262 kbit/s
Next job job1-2 is a video job. encoder commandline:
"C:\MP4 Encoding\x264.exe" --pass 1 --bitrate -262 --stats "D:\PS\1.stats" --bframes 2 --no-b-adapt --b-pyramid --subme 1 --weightb --analyse none --qpstep 1 --me dia --progress --no-psnr --output NUL "D:\PS\1.avs"
successfully set up video encoder and callbacks for job job1-2
----------------------------------------------------------------------------------------------------------

Log for job job1-2

avis [info]: 688x368 @ 23.98 fps (143188 frames)
x264 [info]: using cpu capabilities MMX MMXEXT SSE 3DNow!
x264 [info]: slice I:920 Avg QP:10.01 size: 55101
x264 [info]: slice P:48241 Avg QP:10.00 size: 37746
x264 [info]: slice B:94027 Avg QP:11.50 size: 19958
x264 [info]: mb I I16..4: 25.1% 0.0% 74.9%
x264 [info]: mb P I16..4: 23.4% 0.0% 0.0% P16..4: 73.6% 0.0% 0.0% 0.0% 0.0% skip: 3.1%
x264 [info]: mb B I16..4: 9.1% 0.0% 0.0% B16..8: 53.7% 0.0% 0.0% direct:33.2% skip: 4.1%
x264 [info]: kb/s:5021.0

Actual bitrate after encoding without container overhead: 125055.23

----------------------------------------------------------------------------------------------------------
job job1-2 has been processed. This job is linked to the next job: job1-3
Next job job1-3 is a video job. encoder commandline:
"C:\MP4 Encoding\x264.exe" --pass 2 --bitrate -262 --stats "D:\PS\1.stats" --ref 4 --bframes 2 --no-b-adapt --b-pyramid --subme 6 --weightb --analyse all --8x8dct --qpstep 1 --progress --no-psnr --output "D:\PS\VIDEO.mp4" "D:\PS\1.avs"
successfully set up video encoder and callbacks for job job1-3
----------------------------------------------------------------------------------------------------------

Log for job job1-3

avis [info]: 688x368 @ 23.98 fps (143188 frames)
x264 [info]: using cpu capabilities MMX MMXEXT SSE 3DNow!
mp4 [info]: initial delay 250 (scale 2997)
x264 [info]: slice I:920 Avg QP:22.95 size: 10080
x264 [info]: slice P:48241 Avg QP:25.75 size: 1694
x264 [info]: slice B:94027 Avg QP:27.46 size: 515
x264 [info]: mb I I16..4: 33.9% 55.6% 10.5%
x264 [info]: mb P I16..4: 4.5% 4.7% 0.5% P16..4: 26.1% 3.4% 0.8% 0.1% 0.0% skip:59.9%
x264 [info]: mb B I16..4: 0.4% 0.8% 0.1% B16..8: 14.8% 0.4% 0.4% direct: 0.8% skip:82.2%
x264 [info]: 8x8 transform intra:51.2% inter:51.3%
x264 [info]: ref P 64.4% 17.0% 13.7% 4.9%
x264 [info]: ref B 73.3% 14.3% 8.3% 4.1%
x264 [info]: kb/s:186.8

Actual bitrate after encoding without container overhead: 4655.03
desired video bitrate of this job: -262 kbit/s - obtained video bitrate: 189.230153687069 kbit/s
----------------------------------------------------------------------------------------------------------
job job1-3 has been processed. This job is linked to the next job: job1-4
Next job job1-4 is a mux job. mp4box commandline:
"C:\MP4 Encoding\mp4box.exe" -add "D:\PS\VIDEO.mp4" -add "D:\PS\audio.mp4" -chap "D:\PS\VIDEO_TS\VTS_01 - Chapter Information - OGG.txt" -fps 23.976 -new "D:\PS\PS.mp4"
successfully set up muxer and callbacks for job job1-4
----------------------------------------------------------------------------------------------------------

Log for job job1-4

IsoMedia import - track ID 1 - Video (size 688 x 368)
IsoMedia import - track ID 1 - Audio (SR 48000 - 6 channels) - SBR AAC
IsoMedia import - track ID 2 - media type odsm sub-type odsm
IsoMedia import - track ID 3 - media type sdsm sub-type sdsm
Saving D:\PS\PS.mp4: 0.500 secs Interleaving

----------------------------------------------------------------------------------------------------------
Muxjob ended and deletion of intermediate files is activated
----------------------------------------------------------------------------------------------------------

Log for job job1-4

IsoMedia import - track ID 1 - Video (size 688 x 368)
IsoMedia import - track ID 1 - Audio (SR 48000 - 6 channels) - SBR AAC
IsoMedia import - track ID 2 - media type odsm sub-type odsm
IsoMedia import - track ID 3 - media type sdsm sub-type sdsm
Saving D:\PS\PS.mp4: 0.500 secs Interleaving
an exception ocurred when trying to read from stdout: Object reference not set to an instance of an object.
----------------------------------------------------------------------------------------------------------

It seems that MeGui is trying to set my bitrate at -262 kbit/s which seems odd.

Also, I had two other jobs set up. However, even after this job finished, those two jobs didn't go. Let me know if you need any more info.

[berrinam]

It looks like you have the same problem described by max-holz here (http://forum.doom9.org/showthread.php?p=724074#post724074) and on the development thread. Try using the version posted here (http://forum.doom9.org/showthread.php?p=724251#post724251)

[haubrija]

It looks like you have the same problem described by max-holz here (http://forum.doom9.org/showthread.php?p=724074#post724074) and on the development thread. Try using the version posted here (http://forum.doom9.org/showthread.php?p=724251#post724251)

Thanks berrinam, that was one of my problems. I ran an encode with 2.2.6a last nite without any problems.

However, I'm still having an issue with MeGui not going to the next job in the queue. I set up two Automated 2-pass encodes and after the first finished, the second failed to start. Its still in the queue, it just didn't automatically start the second job after the first job.

[berrinam]

Perhaps the first pass had an error? That would cause the queue to stop. If not, please post a log.

[haubrija]

Perhaps the first pass had an error? That would cause the queue to stop. If not, please post a log.

I can see now I was extremly unclear from my post above, sorry about that.
Here's my issue.

I use MeGui to generate a set of jobs for one backup, then use MeGui to generate another set of jobs for the next backup. For example, I set my first backup to do a 2 pass AutoEncode for x264. This generates four jobs, labeled (I beleive, not in front of encoding machine right now) 1-1,1-2,1-3 and 1-4. Then, I set up my second backup using the same 2 pass AutoEncode and MeGui set them up as 2-1,2-2,2-3 and 2-4. I then press Start.

Now 1-1, 1-2, 1-3 and 1-4 all finish fine. However, the jobs on my second backup never start. This used to work with 2.2.4 as MeGui would continue processing until all jobs were done.

If you look at the look I posted above, you'll see I generated 3 backups. Now after the first backup was done, MeGui doesn't continue to the jobs for the second set of backups. There does seem to be an error for job 1-4:
an exception ocurred when trying to read from stdout: Object reference not set to an instance of an object. I don't know if that's the issue or not.

I have a log for 2.2.6a that I can post when I get home if necessary. Let me know if I was unclear.

[Doom9]

I don't know if that's the issue or not. It is.. if a job errors out, the queue is stopped. And since that error happens when mp4box cannot be properly started or exits immediately, something is wrong with the mp4box commandline (or the files you're trying to mux) and the log is a must.. as is running the commandline from a command prompt to see if there are any other messages that point towards the error.

[Doom9]

alright, the subme 7 support is now included in the latest build.

[Doom9]

a new build is up. main features are improvements in the queue, x264 configuration and support for the --crf switch in x264

[Sharktooth]

Doom9, the --aq switch was removed in the new patch.
the there are only 2 options now, aq-strenght and aq-sensitivity. setting strenght to something other than 0 just enables AQ.

[Doom9]

I've updated the AutoQ feature.

[Wishbringer]

0.2.2.8a 10/23/2005
new: support for the x264 constant quality feature

I thought it used percentage input and inserted 75 like in AutoGK and got a filesize of 4 MB for a whole 90 mins film.
What range is usefull for that new feature?

[Sharktooth]

@wishbringer: the quantizer.

@doom9: thanks:)

[Rafik]

Hello everybody !
First, please excuse my english (I'm from Algeria but live in Tunisia). For two years, i used XviD and Ogg Vorbis for my encodings but i lately discovered this codec (x.264) and i find that it's a very impressive one. Thank you for this codec and for MeGui (i use it with GK).
My problem is that when i encode with High Profile (it can w/MP), MPC 6.4.8.4 cannot read it. i have the latest A/V codecs (and all softs relative).
Merci (Oops !), thank you for your help.

[Sharktooth]

there are some options of the high profile (like custom quantization matrices) that open source decoders doesnt still support. you need to use Nero (sometimes buggy) or Moonlight/Elecard decoders to playback those HP streams made with custom matrices.
However that support is coming and soon even the opensource decoders will support the custom matrices.

[Rafik]

I don't think that i have used this type ofcustom matrix. Is it automatically employed with HP ?

[Sharktooth]

no. then you need the latest CVS build of ffdshow.

[Rafik]

Thank you M. Sharktooth for replying. Are you the one who create x.264 ? Vous êtes un vrai génie ! I go to sourceforge to bring this CVS build of ffdshow but i haven't understand anything. Can you give me a direct link ? i have downlowded the latest version of ffdshow but it doesn't work anyway ...
other questions :
1. what about AAC vs Ogg ?
2. what about a detailed guide for Megui ? now it becomes a great -little complicated- soft (it pursuit the same way of GK in its evolution).
3. will High Profil give me a significant amelioration of quality ?
Thank you.

[Sharktooth]

Well, i didnt "create" x264, i just build the sources and make the binaries available for windows users.
Get ffdshow from here: http://www.aziendeassociate.it/cd.asp?dir=/ffdshow
or search the doom9 forum for other builds.
the other questions:

1- it depends if you want to use .mp4 container or not. if you're going to use MKV then use Ogg because from the "blind-tests" it was the best audio codec for quality.
2- i just created a thread that may be of help: http://forum.doom9.org/showthread.php?t=101813
3- Yes it will.

[Rafik]

thank you a lot !
see you soon.

[bob0r]

Next job job1 is a video job. encoder commandline:
"x264.exe" --crf 26 --ref 8 --mixed-refs --aq-strength 2.0 --aq-sensitivity 22.0 --bframes 4 --b-pyramid --filter -2,-2 --subme 7 --weightb --analyse all --8x8dct --b-bias 4 --progress --no-psnr --output "I:\cap\_x264\test.mp4" "I:\cap\_x264\cap.avs"
successfully set up video encoder and callbacks for job job1
----------------------------------------------------------------------------------------------------------

Log for job job1

avis [info]: 640x352 @ 25.00 fps (7957 frames)
x264 [info]: using cpu capabilities MMX MMXEXT SSE 3DNow!
mp4 [info]: initial delay 2 (scale 25)

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

Can anyone test these settings too?
After the encode Status = error, and the test.mp4 does not play.

[Sharktooth]

AQ is broken... but not for everyone... bah...

[Egh]

Seems there's very minor interface bug in last MeGUI version.

If lossless is chosen, Quantizer editbox is disabled, as it should.

But if MeGUI is restarted using same profile, then the editbox is enabled despite "Lossless" being checked. So you can enter value there and thus it's CQ mode now :P

[Sharktooth]

There's another interface bug. When selecting Main or Baseline Profile, even if 2nd pass or Automated 2-pass is set the Bitrate box gets always resetted to 26.
Selecting High Profile works as expected.

[smok3]

weird crash on 2nd pass (trying to encode with x264, video only) megui 0.2.2.8, avisynth 2.55, log file:
---------------------------------
Generating jobs. Desired size: 48234496 bytes
No audio encoding. Calculating desired video bitrate directly.
Setting video bitrate for the video jobs to 599 kbit/s
Setting desired size of video to 48164864 bytes
Next job job1-1 is a video job. encoder commandline:
"x264.exe" --pass 1 --bitrate 599 --stats "D:\path\avs.stats" --analyse p8x8,b8x8,i4x4 --progress --no-psnr --output NUL "D:\path\avs.avs"
successfully set up video encoder and callbacks for job job1-1
----------------------------------------------------------------------------------------------------------

Log for job job1-1

avis [info]: 512x384 @ 25.00 fps (16066 frames)
x264 [info]: using cpu capabilities MMX MMXEXT SSE SSE2 3DNow!
x264 [info]: slice I:95 Avg QP:22.51 size: 13430
x264 [info]: slice P:15971 Avg QP:25.90 size: 2916
x264 [info]: mb I I16..4: 32.1% 0.0% 67.9%
x264 [info]: mb P I16..4: 4.5% 0.0% 2.8% P16..4: 39.9% 15.8% 3.0% 0.0% 0.0% skip:34.0%
x264 [info]: kb/s:595.7

Actual bitrate after encoding without container overhead: 595.72

----------------------------------------------------------------------------------------------------------
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 599 --stats "D:\path\avs.stats" --analyse p8x8,b8x8,i4x4 --progress --no-psnr --output "D:\path\avs.mp4" "D:\path\avs.avs"
successfully set up video encoder and callbacks for job job1-2
----------------------------------------------------------------------------------------------------------

Log for job job1-2

avis [info]: 512x384 @ 25.00 fps (16066 frames)
x264 [info]: using cpu capabilities MMX MMXEXT SSE SSE2 3DNow!
mp4 [info]: initial delay 0 (scale 25)
x264 [error]: More input frames than in the 1st pass
Assertion failed: frame >= 0 && frame < rc->num_entries, file encoder/ratecontrol.c, line 467

This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.

----------------------------------------------------------------------------------------------------------
The current job contains errors. Skipping chained jobs

[QuadraQ]

I'm trying to get MeGUI up and running, and I downloaded all the necessary software and set up the directories in MeGUI. However, the link for bse_FAAC.dll isn't working because the files have expired. I did a search and found the dll, but I think it's an old version, because when I choose the FAAC option in MeGUI the audio starts to encode, but quits immediately. It works OK when using the Nero encoder. If someone could point me to the latest version of the bse_FAAC.dll I'd appreciate it.

For video, I don't know what's going wrong. It starts the first pass and the status dialog box comes up, but never changes. There's lots of hard drive activity and when I check the task manager it shows that x265.exe is using ninety-some percent of the processor, but even after four hours the pass isn't complete. (I know from using AutoAC that it doesn't take THAT long on my machine.) The status screen hasn't changed, and the x264 app and hard drive activity are just the same, so it seems that it's hanging on something. Any ideas? :confused:

Here is a pic to illustrate what I mean:
http://www.mindspring.com/~quadra2/MeGUI%20Problem.PNG

It just stays like this indefinitely.

Here are my settings:
http://www.mindspring.com/~quadra2/MeGUI%20Settings.PNG

Help! I want to get MeGUI working, so that I can start backing up my DVD collection to mp4 files that I can watch on my xbox. Thanks.

[Doom9]

@QuadraQ: where is the most important of all, ... the logfile? take the x264 commandline from there, start a command prompt (start - run - type "cmd" and press enter), paste the commandline and press enter, then see what is happening.

[QuadraQ]

The "logs" directory in my MeGUI directory is empty, so how do I get the command line without a log?

[jellysandwich]

The "logs" directory in my MeGUI directory is empty, so how do I get the command line without a log?

You can get the command line through MeGUI itself. There's a button that says "Show commandline."

js

[QuadraQ]

OK here is the command line:

"x264.exe" --pass 2 --bitrate 1129 --stats ".stats" --aq-strength 0.5 --no-cabac --analyse p8x8,b8x8,i4x4 --progress --no-psnr --output "C:\SONY\VIDEO_TS\The Net.mp4" "C:\SONY\VIDEO_TS\The Net.avs"

and the error I'm getting at the command line:

C:\Program Files\x264>"x264.exe" --pass 2 --bitrate 1129 --stats ".stats" --aq-s
trength 0.5 --no-cabac --analyse p8x8,b8x8,i4x4 --progress --no-psnr --output "C
:\SONY\VIDEO_TS\The Net.mp4" "C:\SONY\VIDEO_TS\The Net.avs"
avis [info]: 640x352 @ 0.00 fps (165080 frames)
x264 [error]: ratecontrol_init: can't open stats file
x264_encoder_open failed

I'm not sure if this is what you wanted. I don't use the command line much.

[berrinam]

avis [info]: 640x352 @ 0.00 fps (165080 frames)
Something's up with your AviSynth file; the framerate should not be 0. See if you get the same framerate with (a) other avisynth files, or (b) other programs, like VirtualDub(mod). Also, if you know what the framerate should be, try adding assumefps(25.0) to the end of your avisynth file, replacing 25.0 with the correct framerate.

x264 [error]: ratecontrol_init: can't open stats file
x264_encoder_open failedThis shouldn't be the problem, because it is just due to the way MeGUI handles stats files.

[Doom9]

This shouldn't be the problem, because it is just due to the way MeGUI handles stats files.But without a first pass, it'll never work. The framerate is definitely the first thing to look into, but if that doesn't work out, please try a valid first pass commandline (just change encoding mode to 2pass first pass.. your settings won't be changed but if you configure automated 2 or 3 pass.

[berrinam]

This shouldn't be the problem, because it is just due to the way MeGUI handles stats files.
What I meant was that this problem was caused because of the incomplete commandline given in the x264 config dialog, which isn't actually a problem when it comes to encoding, as the stats file is filled in.

Of course, you're right; a first pass is definitely needed.

[QuadraQ]

OK, I switched to "2pass - 1st pass" copied the command line and ran it. Still had 0 fps but this time x264 actually launched and started doing something (Although like you said 0 fps is still wrong, and it seems to me that x264 should probably just quit if given that invalid fps.) Basically the disk activity went out the roof and x264 started sucking down all the processor time like I previously described.

What doesn't make sense to me, is that in the bitrate calculator window of MeGUI it said 25 fps when I first opened it up (which is wrong BTW, since this is not a PAL encoded video, or even a "true" NTSC 30 fps, but a film source which should be 23.976 fps). I changed it to 23.976 to reflect that this is a film source, and had it acount for 128 kbps AAC audio and clicked save. I guess those settings didn't reflect in the command line I pulled from the codec configuration window.

[Doom9]

you do need to fill out the name of the stats file in this case.. the commandline you get in the codec configuration screen is not complete. Did you try all the things berrinam suggested? Also, next time please just copy&paste the contents from the commandline window (and only the part that does matter.. starting with the commandline).

[QuadraQ]

OK I edited the avs file (didn't realize there was so little in there) and added the line berrinam suggested, so that the contents of my avs file are this:

mpeg2source("C:\SONY\VIDEO_TS\VTS_01_1.d2v")
crop(4,0,-8,-2)
LanczosResize(640,352)
assumefps(23.976)

and then I gave the stats file a name in the command line and this is what I got:

C:\Program Files\x264>"x264.exe" --pass 1 --bitrate 759 --stats "test.stats" --a
q-strength 0.5 --no-cabac --subme 1 --analyse none --me dia --progress --no-psnr
--output NUL "C:\SONY\VIDEO_TS\The Net.avs"
avis [info]: 640x352 @ 23.98 fps (165072 frames)
x264 [info]: using cpu capabilities MMX MMXEXT SSE 3DNow!
encoded frames: 826/165072 (0.5%), 23.42 fps

So it looks like it's working now at least from the command line.

So at least I've learned a few things. Still I'm not sure why the AVS script didn't have the fps information in it in the first place. What else should I try now? I appreciate your help.

[berrinam]

Well, if it works in the commandline, it should almost definitely work from MeGUI, too.

As to the problem with AviSynth, see if other AviSynth scripts also signal 0fps (I doubt it, considering that it worked when you added assumefps(...)), or try using the same script with VirtualDub. OTOH, perhaps it is just an unusual source.

[QuadraQ]

I've got MeGUI working on it now. I'll let you know what the results are. Assuming it works, then the next thing is to figure out why the avs script created in MeGUI didn't include the fps...

[hpn]

A small bug: When I start MeGUI, specify the avs then click "Config", it's initialized with ABR mode with bitrate 26, instead of bitrate 700. Switching to Const.quantizer then back to ABR fixes the bitrate to its normal value.

EDIT: oops, it's been posted above by ST, sorry

[QuadraQ]

OK, just an update. MeGUI did finish the job of creating the video mp4 file this time using the automated two-pass option and the "fixed" avs script (see previous posts). However the video file is corrrupt or something. When I try to play it I get a garbled scene from the movie, and then Media Player Classic crashes. (Same results for any other media players I've tried.) So I'm going to have to create a small test so that I can quickly test things. (It took all night to finish the encoding job for the entire movie.)

I'm not sure why I'm having so much trouble getting MeGUI Setup. From what I can tell, MeGUI is THE tool for creating x.264 mp4 files, but I guess I'm cursed.

Any suggestions would be appreciated. Thanks.

[acidsex]

Finally got around to playing with this a little today and I must say, I am VERY impressed with Doom9 and others work on this. Took a couple minutes getting used to the layout and finding where everything is but once that was under control I was off to encoding in no time. Still waiting for encode to finish but if the finished encode comes out well, I may have found my new favorite encode tool.

I am assuming Doom9 is accepting donations for all of this hard work and if so, where do I send?

Awesome work and much appreciation from this user. :)

[Blue_MiSfit]

So erm... little problem here. I am trying to run an x264 comptest - CQ18 with the following settings:

keyframe interval: 240
6 refs, mixed
3 bframes, pyramid, adaptive
deblock 0,0
cabac
rdo2
weighted prediction, chroma me
all macroblock options
otherwise all defaults

I am using MeGUI 0.2.2.8 downloaded off this forum 5 minutes ago, and the latest x264 package from x264.nl, v348.

My avs script works perfectly fine, tested with vdub and core media player.

The problem is as follows. I queue the job, targeting MP4. input and output files are perfectly valid. When I go to the queue and start the job, it starts for a moment and then exits immediately. Here is the log:


Next job job1 is a video job. encoder commandline:
"C:\Program Files\x264\x264.exe" --qp 18 --keyint 240 --min-keyint 24 --ref 6 --mixed-refs --aq-strength 0.5 --bframes 3 --b-pyramid --subme 7 --weightb --analyse all --8x8dct --progress --no-psnr --output "E:\Movies Work 2\New Jack City\New Jack City.mp4" "E:\Movies Work 2\New Jack City\New Jack City.avs"
successfully set up video encoder and callbacks for job job1
----------------------------------------------------------------------------------------------------------

Log for job job1

unknown option (


wtf? :)

Any ideas? Everything was working perfectly fine before when I had 0.2.2.6, which interestingly enough had the option to DISABLE adaptive quant. I noticed this error before whenever I tried to use adaptive quant, and so I had always just disabled it. Now with 0.2.2.8, there is no option to disable adaptive quant (that I have noticed)

I guess my questions are
1) why is using AQ crashing things?
2) how can I disable it with 0.2.2.8


Just tried manually CLI encoding, it crashes saying something about unknown option. Removing "--aq-strength 0.5" from the commandline makes the encode start normally.

I read also that AQ is broken for some, but not all. What's the latest on this?


Thanks all
~MiSfit

[QuadraQ]

OK I created a small test d2v file and then opened it up in MeGUI just to test the AviSynth Script Creator function. I load the d2v file and the click the Suggest Resolution check box, which selects a resolution of 640 x 352. I then click the Auto Crop button which checks the crop checkbox and chooses a value of 2 for the right and bottom of the image. (The Input DAR is 16:9 and the Resize Filter is Lanczos (Sharp) which I never changed.) I then click the Edit tab to see what the AVS script will be and this is what I find:

mpeg2source("C:\TWO_WEEKS_NOTICE\VIDEO_TS\Test.d2v")
crop(0,0,-2,-2)
LanczosResize(640,352)

So again the fps is missing. Any ideas why? The d2v project was manually generated from DGIndex 1.4.4.

[berrinam]

@Blue_MiSfit: bob0r's builds at x264.nl don't support AQ. If you want AQ, try Sharktooth's builds from the sticky. If you want to disable AQ, set strength to 0.0

@QuadraQ: Do you mean that, when you encode it, it signals 0.0fps, as before? There is nothing wrong with the generated script, and you seem to have had the same problem with two films, so there is probably something wrong with either DGIndex or AviSynth on your computer. Try reinstalling them.

[Doom9]

I am assuming Doom9 is accepting donations for all of this hard work and if so, where do I send?Not for the software specifically, but since it's me doing it in both cases, you can go here: http://www.doom9.org/donate.htm

@QuadraQ: if it's still not clear: adding assumefps to an AviSynth script is a workaround for what you're encountering. It is most likely an issue with your AviSynth installation and is definitely not a MeGUI issue. If you load your script in the main window, then go to the calculator, that's when MeGUI will show what it found out with regards to the framerate.. it uses that for calculations and mp4 muxing (unless you manually specify another framerate). If the fps value in the calculator is wrong (you absolutely must load your AviSynth script before entering the calculator), then that once again hints at an AviSynth problem and you should get the same fps report when opening the script in VirtualDub because both use AviFile to get the file properties.

[QuadraQ]

@QuadraQ: if it's still not clear: adding assumefps to an AviSynth script is a workaround for what you're encountering. It is most likely an issue with your AviSynth installation and is definitely not a MeGUI issue. If you load your script in the main window, then go to the calculator, that's when MeGUI will show what it found out with regards to the framerate.. it uses that for calculations and mp4 muxing (unless you manually specify another framerate). If the fps value in the calculator is wrong (you absolutely must load your AviSynth script before entering the calculator), then that once again hints at an AviSynth problem and you should get the same fps report when opening the script in VirtualDub because both use AviFile to get the file properties.

I just got back from work, and to give you and update of what I discovered last night, you are right (of course). I'm basically sure that the problem at this point it the DGIndex dll or program. The reason I say that is that if I manually create the d2v file from within DGIndex 1.4.4 and then load it in MeGUI to create the AVS script it works fine. However if I try to create the d2v project file from within MeGUI, then I experience the problems previously described. So I'm going to try downloading the latest version of DGIndex and then make sure that I have the latest version of the dll everywhere it's supposed to be installed.

BTW how exactly does that work, as far as the integration of DGIndex and MeGUI?

[QuadraQ]

OK I've been trying to do some digging and this is what I've found:

I updated DGIndex to version 1.4.5 (according to the developer's website this is the latest release version). I did a search for DGDecode.dll on my system, and made sure they were all the latest version (including the one in the MeGUI folder).

I'm using a single VOB file as my test. So I launched DGIndex and opened the vob file. I choose to demux all audio tracks, and the "Forced Film" option. I then saved the project as ManualTest.d2v.

I then launched MeGUI and brought up the d2v creator and selected the same VOB file as before. I selected the AC3 audio channel to demux and saved it as MeGUITest.d2v.

Now I opened the ManualTest.d2v file in MeGUI's AviSynth Script Creator and check the "Suggest Resolution" checkbox and click the "Auto Crop" button and then save the script as ManualTest.avs.

Next I followed the same exact procedure except this time I opened the file MeGUI created MeGUITest.d2v, and save the script as MeGUITest.avs.

OK here's the fun part. If I open the ManualTest.avs and then bring up the Bitrate Calculator, the fps show as 23.976 (correct). If I shutdown MeGUI and bring it back up and this time open the MeGUITest.avs and again go to the Bitrate Calculator, the fps show as 25 (incorrect). In addition if I queue the job I get the dead status window problem I'm trying to track down (works fine with the ManualTest.avs).

I did a line by line compare of the two d2v files using ExamDiff 1.6 and the only difference is this line:

ManualTest.d2v
"Field_Operation=1"

MeGUITest.d2v
"Field_Operation=1 (0:None 1:ForcedFILM 2:RawFrames)"

The avs scripts are identical except for the d2v files they point to.

When I remove the " (0:None 1:ForcedFILM 2:RawFrames)" from the MeGUITest.d2v file so that it's identical to the ManualTest.d2v file then everything works (the bitrate calculator shows 23.976 and the encoding job proceeds normally).

Could someone run this test to confirm my results. Thanks.

[berrinam]

@QuadraQ: :goodpost: This seems to be a result of MeGUI's auto force film (it's in the settings), probably in combination with varying versions of DGIndex. I can reproduce this problem by reducing the Auto Force Film threshold to 0% in MeGUI's settings.

[QuadraQ]

@QuadraQ: :goodpost: This seems to be a result of MeGUI's auto force film (it's in the settings), probably in combination with varying versions of DGIndex. I can reproduce this problem by reducing the Auto Force Film threshold to 0% in MeGUI's settings.

OK that makes sense! What version of DGIndex are you using?

[berrinam]

v1.4.0, but it causes the same problems that you described (ie, it shows up as 0.0fps)

What I meant by version considerations is that I do seem to recall some d2v files which had (0:None 1:ForcedFILM 2:RawFrames) in them, and I doubt that Doom9 would accidentally have made MeGUI to insert that line unless it was previously accepted by DGIndex, and so I presume that it was simply a line which is now obsolete.

[Doom9]

I added that because when I wrote the autoforcefilm code that suffix was in the file (I always wondered why something that looks like comment was in the file, but on the other hand it's nice not to have to search for it).

[hpn]

Required tools:
.NET Framework 1.1 (http://www.microsoft.com/downloads/details.aspx?FamilyID=262d25e3-f589-4842-8157-034d1e7cf3a3&displaylang=en) Version 2.0 is currently not supported!
For a few days I've been testing the final 10/27/2005 (not beta) .NET Framework Version 2.0 (http://www.microsoft.com/downloads/details.aspx?familyid=0856EACB-4362-4B0D-8EDD-AAB15C5E04F5&displaylang=en) and seems it works fine with MeGUI. I don't want to jump to any conclusion and say it's safe to use, just if other people want to try it and see if they encounter problems.

[Sharktooth]

i have it installed and it does work (at least with megui-x264).

[dimzon]

i have it installed and it does work (at least with megui-x264).
.NET Framework support side-by-side execution (so v1.1 may be used)

[Doom9]

I have downloaded VS2k5, Express, MSDN docu, runtime and SDK but I cannot install it right now.. I might whip up a VM to test it and if it all works out upgrade.. the thing is though I sometimes develop on the way from and to work and upgrading at work means I have to get a lot of colleagues to upgrade because they use software I've written (and am still working on).

[stax76]

Try to always install the runtime a application was build against. I'm hoping most developers will make the switch to 2.0 soon. Retail version of VisualStudio 2005 as well as SharpDevelop 2.0 is not out yet but hopefully soon.

[QuadraQ]

I added that because when I wrote the autoforcefilm code that suffix was in the file (I always wondered why something that looks like comment was in the file, but on the other hand it's nice not to have to search for it).

Well I went to the DVD2AVI / DGIndex forum to ask neuron2 about this and this was his reply:

The extra stuff on the strings was removed as of version 1.3.1 beta 8.

So I'm hoping that you'll be able to update MeGUI soon to reflect that. Thanks! :cool:

[Doom9]

So I'm hoping that you'll be able to update MeGUI soon to reflect that.already done.

@Sharktooth: I've been unable to reproduce your problem in the 0.2.2.9 build.

[Doom9]

Regarding AVC Levels I need your input: VBV isn't so much of a problem, but levels impose limits on frame size and bitrate. Now if we're queueing video jobs manually and have the AviSynth script loaded prior to configuration, I can display the appropriate warning right in the configuration. But once you start using profiles the problems start: say you select your profile prior to selecting the input. When do I notify that the level is incompatible with the frame size, and what about the bitrate?
It gets worse in auto mode as there the bitrate may only be known after audio encoding, so I would have to interrupt the queue to ask you if you want to relax the level for a certain bitrate, or reduce the bitrate (thus not achieving your desired size anymore).

One click mode is worst as there prior to encoding I know neither the framesize of the AviSynth script, nor what bitrate I'm getting.

Either way, as soon as we go automated, levels either have to be ignored or I have to interrupt the queue and you can forget about setting up a couple of movies and encode them through the night or while you're at work if you've made one small mistake with regards to levels.

[subcool]

i'v come across a really annoying bug in MeGui... "sticking to jobs"
when a job is supposed to be finished, MeGui will _not_ start the next job scheduled...
This is version 0.2.2.8 im using

http://arienai.com/Capture.jpg <-- screenshot

also, when i output a x264 encode in .MP4, i cant playback the MP4 (even when muxed with sound)
So i encode to raw first and then mux audio + video -> MP4 wich works fine.


forgot to mention this, but when i Abort the stuck job and manually start the next job, the resulting file is playable (when muxed) without errors

[Doom9]

also, when i output a x264 encode in .MP4, i cant playback the MP4 That is definitely in the wrong thread here.. it's an x264 issue not a megui issue. Using the exact same commandline you will get the exact same file regardless of who runs x264.exe. And I see no logs, commandlines and such.. and how do you know it's a bug if nobody else has a problem?

[Sharktooth]

use the "nicefps()" filter in your .avs file: http://mirror05.x264.nl/eMotionEstimation/nicefps.zip

[bond]

mp4 files created during an aborted encode will not work. thats the normal behaviour

[bob0r]

"new: you can now manually enter a negative audio delay (delay in filenames was always properly recognized)"

:thanks: **** KISS **** :thanks:

[hackboyz]

Hi

what means this error:


Log for job job2-4

IsoMedia import - track ID 1 - Video (size 640 x 272)
Error importing D:\Leon\VTS_01_1 T01 3_2ch 448Kbps DELAY 0ms.mp4: Invalid IsoMedia File

----------------------------------------------------------------------------------------------------------
The current job contains errors. Skipping chained jobs
----------------------------------------------------------------------------------------------------------

Log for job job2-4

IsoMedia import - track ID 1 - Video (size 640 x 272)
Error importing D:\Leon\VTS_01_1 T01 3_2ch 448Kbps DELAY 0ms.mp4: Invalid IsoMedia File
an exception ocurred when trying to read from stdout: Key cannot be null.
Parameter name: key
-------------------------------------------------------------------

[subcool]

mp4 files created during an aborted encode will not work. thats the normal behaviour

I know that, but if you look at the screenshot. All the frames have been processed ;)

@Doom9:
just because nobody else has the same problem, doesnt mean it can't be a bug :P
i'v had this 'sticking' of jobs in multiple encode over multiple version of MeGui en its kinda annoying when you wanna do long encodes at night.

and if you wanna read logs, here is the log of the job that got stuck:
----------------------------------------------------------------------------------------------------------
Next job job1-1 is a video job. encoder commandline:
"C:\x264\x264.exe" --pass 1 --bitrate 718 --stats "D:\encoding\raws\kaleidoscope\Kaleidoscope.stats" --keyint 240 --bframes 2 --subme 1 --weightb --analyse none --qpmax 27 --ratetol 90 --qcomp 0.9 --me dia --sar 1:1 --progress --no-psnr --output NUL "D:\encoding\raws\kaleidoscope\Kaleidoscope.avs"
successfully set up video encoder and callbacks for job job1-1
----------------------------------------------------------------------------------------------------------

Log for job job1-1

avis [info]: 640x480 @ 23.98 fps (34884 frames)
x264 [info]: no need for a SAR
x264 [info]: using cpu capabilities MMX MMXEXT SSE 3DNow!
x264 [info]: slice I:250 Avg QP:22.16 size: 22593
x264 [info]: slice P:16274 Avg QP:24.32 size: 5707
x264 [info]: slice B:18360 Avg QP:25.93 size: 1001
x264 [info]: mb I I16..4: 43.0% 0.0% 57.0%
x264 [info]: mb P I16..4: 11.5% 0.0% 0.0% P16..4: 36.4% 0.0% 0.0% 0.0% 0.0% skip:52.1%
x264 [info]: mb B I16..4: 0.6% 0.0% 0.0% B16..8: 11.7% 0.0% 0.0% direct: 4.9% skip:82.8%
x264 [info]: kb/s:642.8

Actual bitrate after encoding without container overhead: -174933.45

----------------------------------------------------------------------------------------------------------
The current job was aborted. Stopping queue mode
The current job contains errors. Skipping chained jobs

[Richard Berg]

Version 2.0 final may work as well. Please report your findings.
Different versions of the .Net framework install side-by-side. MeGUI will always be run inside the 1.1 framework unless you recompile it with VS2005.

[Richard Berg]

Bugs in 0.2.2.9a:

* Tools -> Settings -> OneClick Defaults gives an unhandled exception. Stack trace:
System.ArgumentOutOfRangeException: Specified argument was out of the range of valid values.
Parameter name: '2' is not a valid value for 'index'.
at System.Windows.Forms.ComboBox.set_SelectedIndex(Int32 value)
at MeGUI.OneClickDefaultWindow..ctor(Hashtable videoProfiles, Hashtable audioProfiles, Int32 videoIndex, Int32 audioIndex)
at MeGUI.SettingsForm.configOneClick_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)


* Adding/deleting profiles does not refresh the main window. New profiles don't show up; selecting deleted profiles gives an unhandled exception:
System.NullReferenceException: Object reference not set to an instance of an object.
at MeGUI.MeGUI.audioProfile_SelectedIndexChanged(Object sender, EventArgs e)
at System.Windows.Forms.ComboBox.OnSelectedIndexChanged(EventArgs e)
at System.Windows.Forms.ComboBox.WmReflectCommand(Message& m)
at System.Windows.Forms.ComboBox.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)

[Doom9]

* Tools -> Settings -> OneClick Defaults gives an unhandled exception. Stack trace:And the scenario would be? I see index two meaning you have profiles.. I can't just reproduce it with the amount of information you've given me. I suspect what happened is that you deleted a profile but due to issue number 2 you mentioned, it wasn't removed from the combobox in the main gui, was still selected, then you went to the settings- one click settings, and it tried to set the video profile combobox to the non existing profile.

However, I cannot reproduce your deletion problem either so can you please give me a scenario, starting with a blank megui.exe (no settings, profiles and jobs), how to create profiles and how I can reproduce your second problem?

Different versions of the .Net framework install side-by-side.Does that really work? I'm wondering if I could create 1.1 compatible binaries with VS2.5.. if so I'll probably upgrade shortly (just burned the DVD image yesterday).

@subcool: does using mencoder work? besweet? mp4box? mkmerge? mencoder for avi merging?

@hackboyz: it probably means something is wrong with your mp4 file

[stax76]

Of course does side by side execution work, you can install different .NET versions. Assemblies can be installed to the GAC that have same filename but are different in version. Your application will run with the runtime and assembly versions it was compiled against. DLL hell is a thing of the past.

I don't think VS 2005 can compile against .NET 1.1 so you would have to fire up csc.exe by hand. You might have a hard time not to use .NET 2.0 features ;)

[Doom9]

hmm... they finally did something right then. This is a major bonus over Java. I know the runtime picks the proper DLL versions but I wasn't aware it also applied to the whole runtime libraries. Thinking about it, it does make sense though. Since you have 2.0 installed and know how to handle a compiler, have you tried compiling MeGUI with the 2.0 csc? It would be neat if I could develop with VS2k5 and then for the release just compile with the 1.1 csc.. but as you said, I've been using the new Java 1.5 features extensively and have missed typed arraylists and hashtables in C# ever since.

[stax76]

irc compiling your app didn't even issue a compiler warning. When I started StaxRip in april using DVX as base I enabled "treat all warnings as errors". I got more than hundred compile time errors and warnings as the compiler was much improved. Not to mention I had cross thread gui code *everywhere* which worked fine with 1.1 but it is not permitted with 2.0 (you'll get a nice runtime exception). I knew it shouldn't be done back then but I didn't care since it appeared to work very well. Since I felt like redoing anything (having some lessons learnt...) I wasn't much concerned that my code was completely broke using the new runtime. Anonymous methods can be handy for cross gui code btw, not a VB feature as it don't mix well with basic VB concepts but maybe they'll come anyway.

[subcool]

@subcool: does using mencoder work? besweet? mp4box? mkmerge? mencoder for avi merging?

Besweet works, MP4box and mencoder work too. I do not use mkvmerg and avi merging. I only output to RAW and mux that to MP4.


Strange thing is that sometimes is does do the chained jobs (1-1 and 1-2) but then gets stuck on job 1-2.

[Doom9]

over multiple version of MeGui en its kinda annoying when you wanna do long encodes at night.with which version did it start?
Is x264.exe still running before you manually abort?
Also, could you run the exact same commandline that gets stuck (does it always? if you restart the job does the same thing happen) in a commandline and paste everything you see here?

[Richard Berg]

Your application will run with the runtime and assembly versions it was compiled against.
Yup. I have about 15 versions of the framework on my dev machine...

It would be neat if I could develop with VS2k5 and then for the release just compile with the 1.1 csc..
I don't know if there's a 2.0 compiler switch to warn you before using 2.0-only features, so you'd have to be careful. The 2.0 framework is actually a smaller download than 1.1 was, so if you switch to VS2k5 you may as well have people grab 2.0 instead.

I will see about reproducing that OneClick Settings problem when I get home. I've never been to that dialog before (analog capture = no OneClick for me). I have Sharktooth's x264 profile collection installed.

[Sharktooth]

@Doom9: x264 has got a new option: trellis quantization.
usage:
-t, --trellis <integer> Trellis RD quantization. Requires CABAC. [0]
- 0: disabled
- 1: enabled only on the final encode of a MB
- 2: enabled on all mode decisions

[Doom9]

I've just released a build with trellis support.
I'm already working on levels but I have received zero feedback to my questions. Since levels limit framesizes, using levels can be disastrous (if you want to enforce a level, you may need to make compromises on frame size, and likewise, if you don't want to compromise on framesize, you must bump up the level or use unrestricted) so I really need a good way to handle this. I suppose the first release will just take care of the VBV values (the necessary mv option is not exposed in cli anyway) and mb decisions, not frame sizes.

[berrinam]

I'm already working on levels but I have received zero feedback to my questions.I can't see myself using levels much, but in any automated process, what would seem most logical to me is to give the level precedence over all other settings, ie compromise frame size and/or bitrate to meet the required level.

[max-holz]

Don't care of my post!!!

[Chainmax]

I think there's a bug in MeGUI that's been going on since 0.2.2.9a. When configuring the first pass in a 2-pass encode, after selecting a custom matrix the "Video Output" option gets greyed out, and so does the dropdown box with the Mode selection. Any idea why this happens? The only workaround I found is: configure the 1st pass as normal, queue it, close MeGUI, open it again, configure the second pass, queue it and start the encoding.

[Doom9]

The only workaround I found is: configure the 1st pass as normal, queue it, close MeGUI, open it again, configure the second pass, queue it and start the encoding.The description isn't entirely accurate.. it has nothing to do with the matrix.. it also happens if you just set the profile to high profile, close and reopen the configuration dialog. Should be easy to fix. Here's the workaround: select main profile, then select high profile again and the encoding mode field will no longer be locked. Also, why do you not use automated 2 or 3 pass mode?

[netchris]

If that aint much trouble, i would like to see a start frame-end frame option in the avisynth script creator (or maybe itll be more noob friendly to make it starting/ending time).
Megui rocks! Thanx alot for your effort Doom9.

:thanks:

[Doom9]

hmm... I'm assuming you're using a DGIndex project.. and in that case to make audio synch you need to limit the range of your DGIndex project.. if you do it in AviSynth, since there's no audio, limiting the range of frames actually does harm and no good. Or how exactly do you plan to get the audio in synch if you're limiting the encoding range in AviSynth?

[ChronoCross]

@Doom9
The only way he can do it is in DGIndex...unless he's changing the audio to wav(which is a little umm well dumb) then he could just use audio dub and then trim. but yeah it makes no sense if he's planning on using it with other types of advanced audio.

Perhaps you could add the function for people who are encoding video only. They might be using it to overlay a song or something to a personal movie clip which can always be done later because sync really doesn't matter in that case.

[Sharktooth]

New x264 option: --b-rdo (requires --subme 6+)
Extends RDO to B-Frames (similar to b-vhq in xvid).

[Doom9]

@Sharktooth: will do as soon as I'm done with the levels. I can already force the non source dependant things and I've added a nice little check that you can run against your source and that can automatically increase the level to match your source if the current level isn't enough. I plan on using something similar for the one click mode to reduce the resolution until it matches the required level.

[Sharktooth]

cool :eek:

[Chainmax]

Also, why do you not use automated 2 or 3 pass mode?

I will try that, is it any different from manually setting the two passes?

[netchris]

Im encoding mpeg files (dvb source- video clips in exact), so i have to use DGIndex to create d2v files. I only play with video (testing different x264 options for my own sake). This can be done with creating new d2v files (each time containing the frames i want to process) but its easier having a starting full video-clip-d2v and just choose the portions of the clip i want to play with each time.
This can be done by manually editing the avs file (adding trim() ) but it would be easier to have such an option ready at the gui.
(Im sure i could have said all that with less words so sorry for the big message)
Im aware of the problems related to audio (when using the full audio clip while part of the vid), but doesnt the Nero aac encoder or the Faac codec have an option to choose the starting time and end time of the audio clip you want encoded (encode part of the audio clip)? If the timestamps are the same as the ones in the video, wouldnt they be synched?

[Doom9]

I will try that, is it any different from manually setting the two passes?less work... and if you insist you can still load the jobs from the queue and reconfigure them.

[Doom9]

A new build is out.

A few words about the level feature: levels enforce VBV and certain macroblock values. But AVC levels mostly concern source properties, which may not be known at configuration time. Hence, I have added a new tool called AVC profile validation. After loading a video source, you can use it to verify if your source can be encoded at the selected level. If not, you're informed which level is needed for your source and you'll have an option to automatically change the level accordingly. In one click mode, if your video profile has a level set, the resolution will be adapted until the movie can be encoded fullfilling your desired level. In extreme circumstances (say you're selecting a very low level), this could lead to the output no longer being as large as desired because the resolution has to be reduced considerably, so chose your levels wisely. In addition, please refer to aku's posts about levels and how they apply to x264.

[DeadRinga]

I am having trouble with the D2V creator. When i put in the vob and select an audio track pressing Queue doesnt do anything. If i check both the checkboxes at the bottom the window just closes. I've got the newest version of dgindex and i made sure it was in the MeGUI folder. I'm using 0.2.3.1

[DeadRinga]

Nevermind. It adds it as a separate job. Just found it.

[bond]

doom9, is it ok that with high levels p4x4 isnt useable anymore, but with low levels it is?

[Doom9]

did you check out the link in the changelog? It explains it.. it's needed for compliance.

[charleski]

For a few days I've been testing the final 10/27/2005 (not beta) .NET Framework Version 2.0 (http://www.microsoft.com/downloads/details.aspx?familyid=0856EACB-4362-4B0D-8EDD-AAB15C5E04F5&displaylang=en) and seems it works fine with MeGUI. I don't want to jump to any conclusion and say it's safe to use, just if other people want to try it and see if they encounter problems.
I've had .NET v2.0.50215 installed for a couple of weeks now and MeGUI works fine with it.

[bond]

did you check out the link in the changelog? It explains it.. it's needed for compliance.ah ic, so its not really an explicit requirement but the only way to ensure compliance atm in x264

[subcool]

with which version did it start?
Is x264.exe still running before you manually abort?
Also, could you run the exact same commandline that gets stuck (does it always? if you restart the job does the same thing happen) in a commandline and paste everything you see here?

it started with 0.2.2.8.
I haven't looked at if x264.exe is stuck too, i'll look at that next time it happends. I'll give the commandline a shot too soon.

But another thing i noticed is that it doesnt happen on short encodes (like if the encoding takes less than 5 mins) just on longer ones where (for me) the first pass takes 1 hr and the 2nd bout 1.5 ~ 2 hrs

[Doom9]

it started with 0.2.2.8.Are you sure it's megui or is it perhaps the x264 revision you're using? I've been looking at the source code archive and the video encoder hasn't been changed since october 4th or release 0.2.2.6.. and I'm pretty sure that's the only place your problem could stem from (well.. actually I think it's your setup but on my end the videoencoder makes the most sense looking at your log and what is missing from it). It is quite important to know if x264.exe is still running or not.. it narrows down the section where something could've gone wrong (basically your reported bitrate makes me thing that's where something goes wrong.. hence me asking to run x264 from the commandline).

[subcool]

I have updated x264 but the problem stayed the same. And when a job remains stuck, x264.exe is still running too. the 1-2 job got stuck too >_<

[Doom9]

now run the job from the commandline please... I have a suspicion but the lack of reports plus my own experience seem to contradict it.
also, it would be useful to run a job that gets stuck (long one) and one that doesn't on the commandline and post the entire output here for both cases so that I can see the difference.

[Richard Berg]

@Doom9 - FYI, the latest build fixes both of the exceptions I saw before.

[charleski]

Umm, unless I'm very much mistaken (which is always possible! :) ), it looks like there's a bug in the way MeGUI constructs the commandline for BeSweet using Nero AAC. I was trying to work out why my delay compensation wasn't happening when I noticed that the commandline was:
"...\BeSweet\BeSweet.exe" -core( -input "stuff.mpa" -output "stuff.mp4" -logfile stuff.besweet.log ) -bsn( -2ch -vbr_normal -codecquality_high -aacprofile_lc -ota( -d -80 -g max )
Surely there needs to be a closing parenthesis after -aacprofile_lc? It would help if the name of the logfile is enclosed in quotation marks as well, DGIndex produces demuxed tracks with spaces in the filename. This only affects use of the NAAC encoder, the other options seem fine.

[Edit]This is using version 0.2.3.1 of meGUI, whcih is otherwise excellent.

Here's the relevant portion of the log (had to copy it from the tab, for some reason nothing is saved in my logs directory):

----------------------------------------------------------------------------------------------------------
Next job job1 is an audio job. besweet commandline:
"C:\Program Files\GordianKnot\BeSweet\BeSweet.exe" -core( -input "C:\New Folder\stuff T01 DELAY 0ms.mpa" -output "C:\New Folder\stuff T01 DELAY 80ms.mp4" -logfile C:\New Folder\stuff T01 DELAY 80ms.besweet.log ) -bsn( -2ch -vbr_normal -codecquality_high -aacprofile_lc -ota( -d 80 -g max )
successfully set up audio encoder and callbacks for job job1
----------------------------------------------------------------------------------------------------------

Log for job job1

besweet: "C:\Program Files\GordianKnot\BeSweet\BeSweet.exe" -core( -input "C:\New Folder\stuff T01 DELAY 0ms.mpa" -output "C:\New Folder\stuff T01 DELAY 80ms.mp4" -logfile C:\New Folder\stuff T01 DELAY 80ms.besweet.log ) -bsn( -2ch -vbr_normal -codecquality_high -aacprofile_lc -ota( -d 80 -g max )

BeSweet v1.5b31 by DSPguru.
--------------------------

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

[Doom9]

@charleski: it's all fixed in the "b" release.

[max-holz]

@charleski: it's all fixed in the "b" release.


I see that's pending.

[charleski]

Thanks for the speedy fix. Sync issues are a major pain for me as I'm encoding from DVB-T streams that almost always start with an open GOP. I was tearing my hair out until I noticed the commandline.

[subcool]

now run the job from the commandline please... I have a suspicion but the lack of reports plus my own experience seem to contradict it.
also, it would be useful to run a job that gets stuck (long one) and one that doesn't on the commandline and post the entire output here for both cases so that I can see the difference.

here is one run in CLI that gets stuck in MeGui
I copy/pasted the 1st pass CLI that MeGUI uses, so i didnt expect any problems... but as you see, there were.

there only was a 1.4 MB kaleidscope.stats.temp file in the x264 directory while normally the stats files would be around 3 MB


C:\x264>x264.exe --pass 1 --bitrate 690 --stats ".stats" --keyint 240 --bframes
2 --subme 1 --weightb --analyse none --qpmax 27 --ratetol 90 --qcomp 0.9 --me di
a --sar 1:1 --progress --no-psnr --output NUL "D:\encoding\raws\kaleidoscope\Kal
eidoscope.avs"
avis [info]: 640x480 @ 23.98 fps (34407 frames)
x264 [info]: no need for a SAR
x264 [info]: using cpu capabilities MMX MMXEXT SSE 3DNow!
encoded frames: 16172/34407 (47.0%), 13.45 fps, eta 0:22:35
C:\x264>x264.exe --pass 2 --bitrate 690 --stats ".stats" --keyint 240 --ref 4 --
mixed-refs --bframes 2 --subme 7 --weightb --analyse all --8x8dct --qpmax 27 --
ratetol 90 --qcomp 0.9 --me umh --sar 1:1 --progress --no-psnr --output "D:\encoding\raws\kaleidoscope\Kaleidoscope.mp4" "D:\encoding\raws\kaleidoscope\Kaleidos
cope.avs"
avis [info]: 640x480 @ 23.98 fps (34407 frames)
x264 [info]: no need for a SAR
x264 [error]: ratecontrol_init: can't open stats file
x264_encoder_open failed

[bond]

the "--stats ".stats"" looks strange, try writing a real filename in there

btw x264's statsfiles have the extension .log normally

[subcool]

i actually restarted the encode before going to school and replaced '.stats.' with 'kaleidoscope.stats' and it continued with the 2nd pass (i wrote the jobs in a batch file)

Output for 1st pass was:
C:\x264>x264.exe --pass 1 --bitrate 690 --stats "kaleidoscope.stats" --keyint 24
0 --bframes 2 --subme 1 --weightb --analyse none --qpmax 27 --ratetol 90 --qcomp
0.9 --me dia --sar 1:1 --progress --no-psnr --output NUL "D:\encoding\raws\kale
idoscope\Kaleidoscope.avs"
avis [info]: 640x480 @ 23.98 fps (34407 frames)
x264 [info]: no need for a SAR
x264 [info]: using cpu capabilities MMX MMXEXT SSE 3DNow!
x264 [info]: slice I:255 Avg QP:22.46 size: 21314 0:00:00
x264 [info]: slice P:15888 Avg QP:24.64 size: 5559
x264 [info]: slice B:18264 Avg QP:26.18 size: 997
x264 [info]: mb I I16..4: 44.2% 0.0% 55.8%
x264 [info]: mb P I16..4: 11.4% 0.0% 0.0% P16..4: 35.6% 0.0% 0.0% 0.0% 0
.0% skip:53.0%
x264 [info]: mb B I16..4: 0.6% 0.0% 0.0% B16..8: 11.6% 0.0% 0.0% direct:
4.9% skip:82.8%
x264 [info]: kb/s:624.2

[Sharktooth]

just a note: --subme 7 was broken on certain builds and made x264.exe crash or lock.
please use the new rev365 build OR use --subme 6.

[subcool]

Output from 2nd pass (using build from 6-11-2005 from x264.nl)
the x264.exe is not even closing now... o.O
it doesnt appear to be doing anything either


C:\x264>x264.exe --pass 2 --bitrate 690 --stats "kaleidoscope.stats" --keyint 24
0 --ref 4 --mixed-refs --bframes 2 --subme 7 --weightb --analyse all --8x8dct -
-qpmax 27 --ratetol 90 --qcomp 0.9 --me umh --sar 1:1 --progress --no-psnr --out
put "D:\encoding\raws\kaleidoscope\Kaleidoscope.mp4" "D:\encoding\raws\kaleidosc
ope\Kaleidoscope.avs"
avis [info]: 640x480 @ 23.98 fps (34407 frames)
x264 [info]: no need for a SAR
x264 [info]: using cpu capabilities MMX MMXEXT SSE 3DNow!
mp4 [info]: initial delay 262144 (scale 6285217)
x264 [info]: slice I:255 Avg QP:19.89 size: 253130:00:00
x264 [info]: slice P:15888 Avg QP:22.00 size: 6063
x264 [info]: slice B:18264 Avg QP:24.14 size: 1158
x264 [info]: mb I I16..4: 31.6% 29.7% 38.7%
x264 [info]: mb P I16..4: 6.3% 3.1% 3.9% P16..4: 26.9% 8.5% 4.7% 0.4% 0
.2% skip:46.1%
x264 [info]: mb B I16..4: 0.4% 0.3% 0.2% B16..8: 14.0% 0.9% 1.7% direct:
2.1% skip:80.4%
x264 [info]: 8x8 transform intra:24.3% inter:28.0%
x264 [info]: ref P 79.0% 9.8% 7.2% 4.0%
x264 [info]: ref B 82.1% 8.7% 5.8% 3.4%
x264 [info]: kb/s:690.9

encoded 34407 frames, 1.74 fps, 690.93 kb/s

[bond]

subcool, try to search for "nicefps" in this forum. there was (is?) a problem with strange framerates fixeable with nicefps and other methods (like changefps())

[Sharktooth]

.... ensure your commandline contains options not supported by SVN builds... --subme 7 for example........

[zajc]

Bug?!

MeGUI version 0.2.3.1

Test case:
settings
uncheck the "Open progress window"

When I try to encode HUFFYUV .avi file into XVID the megui.exe process takes most of the CPU instead mencoder (mencoder.exe 40% CPU, megui.exe 60% CPU). Encoding is horribly slow.

When I check the Open progress window then mencoder.exe use 99% CPU, megui.exe 1% CPU.

It might be a bug!?

[Doom9]

I'm encoding right now without progress window. mencoder takes 50%, megui 0% (it's a dual core so only using 50% is normal.. XviD doesn't contain any SMP optimizations).

[zajc]

Hmmm, now it works fine too when I restarted megui.

I put 7 jobs in queue to encode huffyuv -> xvid

1 1st pass 20 fps (.avi length 45 min)
1 2nd pass 10 fps
2 1st pass 25 fps (.avi length 130 min)
2 2nd pass 10 fps
3 1st pass 14 fps (.avi length 45 min)
3 2nd pass 6 fps
4 1st pass 7 fps (.avi length 21 min)
4 2nd pass 4 fps
5 1st pass 4 fps (.avi length 3 min)
5 2nd pass 2 fps
6 1st pass 3 fps (.avi length 5 min)
6 2nd pass 3 fps

Then I found out megui.exe procces takes more then 60% of CPU time and I abort the 7th job. After restarting megui.

7 1st pass 23 fps (.avi length 22 min)
7 2nd pass 11 fps

I have never experienced such behavour with previous version of megui althought I put 20 jobs or more in queue.

[zajc]

I forgot that the megui created a log. I check the log which was 9.5 MB big and contain endless messages, message in bold was repeated for 1.000.000 times (I think this was the main reason why megui.exe take more then 60% CPU):

Next job job3-1 is a video job. encoder commandline:
"C:\util\megui.tools\mplayer\mencoder.exe" "C:\xvidanje\sk.2005.11.06_XVID.avs" -ovc xvid -o NUL: -passlogfile "C:\xvidanje\sk.2005.11.06_XVID.stats" -xvidencopts pass=1:bitrate=1426:max_key_interval=300:packed:vhq=1:qpel:chroma_me:trellis:min_iquant=1:min_pquant=1:min_bquant=1:keyframe_boost=100:kfthreshold=1:kfreduction=20
successfully set up video encoder and callbacks for job job3-1
Exception when trying to update status while a job is running. Text: Cannot call Invoke or InvokeAsync on a control until the window handle has been created. 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)Exception when trying to update status while a job is running. Text: Cannot call Invoke or InvokeAsync on a control until the window handle has been created. 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)Exception when trying to update status while a job is running. Text: Cannot call Invoke or InvokeAsync on a control until the window handle has been created. stacktrace: at System.Windows.Forms.Control.MarshaledInvoke(Control caller, Delegate method, Object[] args, Boolean synchronous)

[Doom9]

I double checked.. ran 5 jobs after another, (same file all the time) and it actually got faster.. not slower. And looking at the source code that message doesn't make sense either, the only thing that "show progress window" does it add a window.Show when starting a code.. the window is always there regardless of whether that option is checked or not.. you couldn't even get an exception (your logs indicate one) if the window weren't created.

[Doom9]

weird, I'm seeing those exceptions as well but they have no performance impact on my system. I guess mine's better than yours ;) I'll have to rework the whole show/don't show part then.

[Tima]

I queue a job which uses mencoder, exit MeGUI, move mencoder.exe to another location, start MeGUI, set the new location in Settings, save, run my job and MeGUI says 'mencoder.exe not found'..

Maybe it's better to revise format of jobs' storage? How's about to store only commandline switches, and substitute the proper path to encoder at the actual start of the job?

[Doom9]

Maybe it's better to revise format of jobs' storage? How's about to store only commandline switches, and substitute the proper path to encoder at the actual start of the job?I'm afraid it's not that simple.. it used to be like that but because people wanted to be able to edit complete commandlines, the commandlines are not touched by the program anymore once written (except for the scenarios where the commandline needs to be regenerated due to a bitrate change).
Here's a workaround for you though: select the job, press load, press update and the commandline should be regenerated with the new path. I know where you're coming from, but the scenario is too exotic to be worth much programming time.

[Doom9]

btw, if there's anybody wondering why the "c" release isn't out yet, I pulled it at the last minute in order to fix the exceptions you get when you deactivate the progress window via settings.

[Tima]

Here's a workaround for you though: select the job, press load, press update and the commandline should be regenerated with the new path.
Thanks for the hint. It solves the problem quite good.. :)

[Liisachan]

A very small problem about this switch of x264:
--filter <alpha:beta> Loop filter AlphaC0 and Beta parameters [0:0]

megui uses a comma instead of a colon, for example
--filter -1,-2
instead of
--filter -1:-2

Although, x264.exe seems to be ok with this comma.

[Richard Berg]

Simple bug in MeGUI.videoOutputOpenButton_Click() -- it doesn't handle filenames with "." in them correctly. For example, if I enter "video-1.5mbps" as the filename, MeGUI will automatically call changeVideoOutputExtention which changes it to "video-1.mp4". You should check for a valid video extension first; if not present, the file type needs to be appended instead of replaced.

[Doom9]

if I enter "video-1.5mbps" as the filenameAnd how can you do that in the first place? The input open fields should all be non-editable, thus forcing you to use a fileopendialog which only returns valid files.

[Richard Berg]

Video Output uses a filesavedialog, so you can type whatever you want.

[Sharktooth]

My impression on Trellis still enabled with CABAC disabled was right.
Uncheck CABAC and trellis get disabled... save the profile and close the config window.
Select another profile then re-select the "just saved profile" and click on the config button. "magically" trellis is enabled even if CABAC is still disabled and it's still in the command line!

ALSO

Selecting baseline profile disables the b-frames options but only in the guy. The command line still shows "... --bframes 3 --b-pyramid --b-rdo --weightb...".
Switching back to another profile only the b-frames textbox is enabled. when you change the number of b-frames then all b-frames options become available.
The same happens with --8x8dct when switching from high-profile to lower profiles.
if "turbo" is previously selected and a mode where turbo is grayed out is set, "-me dia" and all the turbo speed ups are always set in the commandline even if other modes are specified...
this is the same for all options when they get grayed out, for example if --weightb was previously selected, it remains in the commandline even if b-frames are decreased to 0.

Possible fix: when disabling the control you should also reset, uncheck/set it to "false", set it to "0"... depending on the control...

ALSO

RDO for B-frames remains enabled even if B-Frames are set to 0 or gets disabled by other options

EDIT: only in MeGUI-x264... (coz it was not updated).

...

ALSO

when selecting automatic 3 passes the 1st pass command line gets displayed... and when enabling turbo, you cant compare your command line settings with the ones in the GUI.

i missed other bugs for sure...

[Doom9]

GUIs are going to be the end of me.... now you know why open source software often has no good GUI.. it's tedious boring work without rewards. Gosh do I hate GUIs. Give me something interesting to code please.

BTW: those problems are mainly caused by your insistence on triple state.. I used to simply clear options that don't mix, now I have to keep the logic twice to enable triple-state (an example of triple state: go high profile, check 8x8i, go main profile.. it stays checked.. to do that, I need the same disabling logic again in the commandline generation and I need to return the actual checked options regardless of whether they're enabled or disabled). In addition, in order to allow the proper opening of such a profile, I once again have to apply the entire enabling/disabling GUI logic when the configuration dialog comes up.

[Sharktooth]

eheh... well, an easy way is to create a function for disabling controls which scans the control type and disables it in the correct way (resetting its value too).
if i have some time i'll look at the megui source and will post a patch. but that won't be soon since im busy more than ever.

another way is to create an exclusion list for every x264 parameter and parse it everytime you load the xml profiles... but that's a pain in the a$$... :D

another way: dont parse disabled controls (but that requires the deletion of some tags in the xml...) OR add a status field for the controls in xml data file :)

[Sharktooth]

Auto 3-passes with turbo is buggy too...
the first pass "turbo" settings are propagated for all the 3 passes...

[zajc]

I have 3 questions/problems:

software used: megui 0.2.3.1

1. question/problem: I created (2 times) 1310 MB xvid .avi from 25 GB mjpeg .avi source. Somehow .avi isn't playable. After investigation I found out in Gspot 2.52b1 that the .avi file is Multipart OpenDML AVI (162443 frames in first part, 35651 frames follow). How to make the file playable in BSplayer? Also in VirtualDub file can not be opened.

2. question/problem: I tried to mux (Avi Muxer) this .avi file (1. question) and mp3 (ABR) and then split the output into 700 MB files. The result is 1400 xvid .avi file (shouldn't be there 2 files :confused: ), which again is not playable. Should AVImuxer and spliting the output work?

3. question/problem: This has nothing to do with 1. and 2. question. After muxing several playable .avi files, I have a problem to open muxed .avi file in virtualdub. It always warn me: "Truncated or invalid MP3 audio format detected (18 bytes, should be 30)." When I try to demux the file, .mp3 file is playble but corrupted. Is this a mencoder or .avi format problem. Can somebody please explain what is the problem?

Thanks! :confused:

[stephanV]

Whats the error VirtualDub gives?

[zajc]

Also in VirtualDub file can not be opened.

Error is in the status bar: VideoSourceAvi error: file read error (8004406d) :confused:

[Sharktooth]

@Doom9: i compiled MeGUI-x264 with the 0.2.3.1b sources and the RDO thing is still buggy (the control doesnt get disabled if b-frames = 0).
i posted the patch in the development thread... maybe tonight i'll add a couple of fixes too...

[Doom9]

Should AVImuxer and spliting the output work?No, I'm afraid mencoder doesn't offer proper splitting.. since all mux windows are based on the mp4 ones, they all have that ability but if the underlying program doesn't support it, there's nothing I can do about it (want to write an avi muxer/splitter? I'll be happy to support it)

[stephanV]

Error is in the status bar: VideoSourceAvi error: file read error (8004406d) :confused:
zajc: mencoder avi files larger than 1GB only appear to work in mplayer... :(

[Devinator]

Possibly noobish questions here. Will x264 produced like this play on any standalones? I have a Phillips 624. And also must you use MKV if you plan to include AC3 audio tracks?

[Doom9]

Will x264 produced like this play on any standalones?If you manage to get one that can handle AVC... currently there are no such devices. And once there are, levels will also play an important role. Since at this point we cannot know what players will look like, the safe answer is "your content will never play on a standalone".. everything else is speculation because there are no players. Your Philips cannot and will never be able to handle AVC.

And also must you use MKV if you plan to include AC3 audio tracks?Well, if the mencoder guys fix the AC3 muxing bug, AC3 would work as well. You can try.. if it freezes during muxing phase, you know they still haven't fixed the bug, if it works, you're in luck.

[Devinator]

Thanks for the info... Still a very promising codec. I was getting 30+fps on a test to encode a small video clip. Up from 15-18 before using the MT avisynth plugin. However I tried to encode a full movie overnight and it just stopped encoding after 5 minutes or so. The program didn't crash or stop responding. Set automatic 3 pass under config. Then under the bitrate calculator I set MKV, 1/3 DVD size and selected the two audio tracks I wanted.

Oh well, I'll mess around with it a bit.

[berrinam]

I don't know if the right place to post it, but since a lot of people have been reporting problems with x264 here, there seem to be a few things to say before doing this:

1. Work out whether it is x264 or MeGUI causing the problem. This tends to be simple enough: if MeGUI crashed, then it is almost certainly causing the problem. If MeGUI stays active, but flags the job as an error, then look at the commandline in the MeGUI log. If there are any outrageous values in the commandline (especially negative/very low/very high bitrates), then see the commandline MeGUI generated had a problem, and so it is not x264's fault. In almost any other situation, it is an x264 problem, not a MeGUI problem.

2. Read the MeGUI log through yourself. This often has a section which will say the error and you may be able to solve it based on that.

3. Check if it can be solved by adding nicefps to the end of your avisynth script (see here (http://forum.doom9.org/showthread.php?p=717181#post717181)).

Of course, nobody is forcing you to do what I say, but it seems that a lot of problems can be solved by these three steps. They also prevent clogging up the MeGUI thread with non-MeGUI-related bugs.

[leowai]

@berrinam,
:goodpost: , especially step 1.

I believe if bug reporter goes through these steps, he/she can make a more accurate bug report.

[Revgen]

"Pyramid" seems to be grayed out in the latest version of MeGUI bundled with Sharktooth's 367 version. I can't seem to enable it even though I've set my b-frames to 3.

Has there been a change in the last few builds?

[stax76]

GUIs are going to be the end of me.... now you know why open source software often has no good GUI.. it's tedious boring work without rewards. Gosh do I hate GUIs. Give me something interesting to code please.

I find it quite fun and always work on the GUI until I think it's perfect, especially since VS 2005 has much to offer in this regard, maybe you are getting wrong at the problem. Here (http://www.joelonsoftware.com/uibook/chapters/fog0000000057.html) is a nice article. I like this guy's blog, most of the time his articles are fun to read and very interesting.

[Sharktooth]

"Pyramid" seems to be grayed out in the latest version of MeGUI bundled with Sharktooth's 367 version. I can't seem to enable it even though I've set my b-frames to 3.

Has there been a change in the last few builds?
i've just noticed it... well... i dunno :)
ok, i'll check it asap.

[Sharktooth]

another bug... if you save a high profile megui profile when you click the config window b-pyramid will be grayed out.
workaround: set your bframe options (excluding b-pyramid)... switch to main profile then switch back to high profile...

EDIT: fix posted in the megui dev thread along with fixed binaries and new x264-full package.

[Chainmax]

"Pyramid" seems to be grayed out in the latest version of MeGUI bundled with Sharktooth's 367 version. I can't seem to enable it even though I've set my b-frames to 3.

Has there been a change in the last few builds?

I think I had the same problem and got around it by using the arrows to increase the number of bframes rather than directly writing it on the box.


Does anyone know when a new version that can properly do automated 3-pass with turbo will be released?

[Sharktooth]

i'll fix the b.frames and trellis thing first. then i'll check the turbo issue.
bear with me... megui code is too much chaotic for me...

[Chainmax]

Oh, it was not my intention to appear pushy or demanding. I apologize if it came out like that :o.

[Sharktooth]

Oh well, no problems, mine was only an informative post:)

[Sharktooth]

new MeGUI and MeGUI-x264 binaries in the MeGUI dev thread.

[Chainmax]

What fixes are included in this new version?


[edit]Why does the full x264 package has rev367D and the lite package still has rev367A?

[Sharktooth]

the tri-state things... (the glue code).
well the options should be now grayed/ungrayed out in the correct way.
i also included the berrinam patch for the "one click encoder".

[bob0r]

x264 revision 368 now has --b-rdo option (--b-rdo RD based mode decision for B-frames. Requires subme 6.). (SVN)

Please update megui(x264) source and ill compile a new megui-x264 for x264 SVN users :)

[Sharktooth]

i'll update it tonight.

[Sharktooth]

the patch is up on the megui dev thread.

[foxyshadis]

With recent versions I'm getting an unhandled exception when clicking on the job config option in x264 version, after loading an avs file. I haven't had a chance to test full version yet. Setting the profile level to anything other than unrestricted works fine.

stack dump is:

************** Exception Text **************
System.ArgumentException: '0' is not a valid value for 'Value'. 'Value' should be between 'Minimum' and 'Maximum'.
at System.Windows.Forms.NumericUpDown.set_Value(Decimal value)
at MeGUI.x264ConfigurationDialog.set_CodecSettings(x264Settings value)
at MeGUI.x264ConfigurationDialog.EnforceLevel(x264Settings inputSettings)
at MeGUI.x264ConfigurationDialog.showCommandLine()
at MeGUI.x264ConfigurationDialog.avcLevel_SelectedIndexChanged(Object sender, EventArgs e)
at System.Windows.Forms.ComboBox.OnSelectedIndexChanged(EventArgs e)
at System.Windows.Forms.ComboBox.set_SelectedIndex(Int32 value)
at MeGUI.x264ConfigurationDialog.set_CodecSettings(x264Settings value)
at MeGUI.MeGUI.videoConfigButton_Click(Object sender, EventArgs e)

I can't verify that.. it must be settings related so you need to share a lot more info. Plus, this is a topic for the user thread ;)

Sorry about the wrong thread earlier. Anyway, I deleted my settings file and all profiles, and it still occurs. I have whatever the latest release of .Net 1.1 is, on XP SP2. It also occurs on a Server 2003 SP1 machine also with .Net 1.1.

[Sharktooth]

try the version included with x264 rev375A.

[charleski]

@foxyshadis: That bug is due to an error in the first release of the levels code. get one of the latest builds, as it was fixed a few days ago.

[Edit] BTW, if anyone wants to test the level-enforcement code I wrote, please pickup Sharktooth's latest build from the end of the MeGUI development thread. It especially needs to be tested on video with odd framesizes and framerates, if you have any such stuff lying around.

I'm currently working on a set of UI additions, trying to maintain the established workflow of the program while adding things that make it a bit more intuitive for n00bs like me who are upgrading from GordianKnot. I'm already adding things to the avisynth creator so that it can directly load additional filetypes, though avi is going to be a fair amount of work because of the kludge that 'avi' is. If you can think of other improvements (that are real improvements and not along the lines of wanting VfW support :) - I'll put in code to let the avisynth creator read VDub frameserver files ), then post here and be as specific as you can.
BTW, all my additions are going to be targeted at the full version of MeGUI only.

[Razorholt]

Quick (stupid?) question: I'm trying to convert to .AVI using MeGUI (with mencoder). Selecting AVC doesn't do any good but with ASP it does work. Why?


Thanks,
- Dan

[Doom9]

because the x264 version of MeGUI only supports x264.exe and that doesn't support AVI?
Or did you post in the same thread (and forgot a bunch of details.. I don't really have a clue what you're doing).

[Razorholt]

oooooh ok! Thanks Doom9!

What I'm trying to do? Oh man, I dunno. The aim is to encode a mov to ogm. I'm very limited in size and I want maz quality. So I tried:

AVS -> MKV (with MeGUI + AVC) then MKV -> OGM (with VirtualDudMod) => failed. Bunch of errors with VDM.

Now, I know I can succeed with the ASP codec but I doubt whether I could end up with the same quality/compression as with AVC. Am I wrong? MKV was impressive though.

- Dan

[Doom9]

VirtualDubMod can't handle AVC in MKV.. so your problems start right there
OGM imho has outlived its usefulness.. use either MKV or MP4 for AVC.

[Razorholt]

But I need a streaming container and OGM was perfect...

[klicker4546]

Hello,

I'm using the latest version of MeGUI and I'm trying to convert a vob-file to xvid. When I opened my avs-script everything looked fine in the preview. As soon I start the conversion-job it's says "processing" but mencoder doesn't seem to react. I tried it with several versions of mencoder. In the end nothing happens. :confused:

When I copy the commandline to a batch file and execute it, mencoder starts working. Can someone help me?

[charleski]

@klicker4546: We need a log.

But I need a streaming containermp4 is a streaming container :)

[klicker4546]

Hi, thanks for the quick reply. I ran another encoding session and here's the log:

Next job job1-1 is a video job. encoder commandline:
"D:\MeGUI\mencoder.exe" "D:\MeGUI\test.avs" -ovc xvid -o NUL: -passlogfile "D:\MeGUI\2pass.stats" -xvidencopts pass=1:bitrate=700:max_key_interval=300:vhq=4:chroma_me:trellis:interlacing:keyframe_boost=100:kfthreshold=1:kfreduction=20
successfully set up video encoder and callbacks for job job1-1
Job aborted, deleting output file...Deletion failed.

Is this line corrrect? "D:\MeGUI\mencoder.exe" I was wondering if it needs those quotation marks or not...


Here's the avs-script I used:

LoadPlugin("C:\Programme\AviSynth 2.5\plugins\DGDecode.dll")
MPEG2Source("D:\MeGUI\test.d2v")
ConvertToYV12()

Output container was avi. Correct me if it's not supported for xvid. (Although it worked for me with releases of MeGUI.)

Does that help??? :)

@klicker4546: We need a log.

[charleski]

-o NUL:
Are you sure you have an output file set in the GUI?

[klicker4546]

Yes, absolutely!

See attachements!

Are you sure you have an output file set in the GUI?

[charleski]

Well there haven't been any changes to the xvid side of meGUI recently, but it's possible that this is an unintended side-effect of some of the modifications to commandline generation. Exactly which version of meGUI are you using?

I've never used mencoder, but I assume you see the same abort if you just paste "D:\MeGUI\mencoder.exe" "D:\MeGUI\test.avs" -ovc xvid -o NUL: -passlogfile "D:\MeGUI\2pass.stats" -xvidencopts pass=1:bitrate=700:max_key_interval=300:vhq=4:chroma_me:trellis:interlacing:keyframe_boost=100:kfthreshold=1:kfreduction=20into a command window?

[klicker4546]

Well there haven't been any changes to the xvid side of meGUI recently, but it's possible that this is an unintended side-effect of some of the modifications to commandline generation. Exactly which version of meGUI are you using?

I've never used mencoder, but I assume you see the same abort if you just paste "D:\MeGUI\mencoder.exe" "D:\MeGUI\test.avs" -ovc xvid -o NUL: -passlogfile "D:\MeGUI\2pass.stats" -xvidencopts pass=1:bitrate=700:max_key_interval=300:vhq=4:chroma_me:trellis:interlacing:keyframe_boost=100:kfthreshold=1:kfreduction=20into a command window?

I've just created a batch file:

logfile.bat

"D:\MeGUI\mencoder.exe" "D:\MeGUI\test.avs" -ovc xvid -o NUL: -passlogfile "D:\MeGUI\2pass.stats" -xvidencopts pass=1:bitrate=700:max_key_interval=300:vhq=4:chroma_me:trellis:interlacing:keyframe_boost=100:kfthreshold=1:kfreduction=20


and it worked. That's what the problem is. When I create a batch-file it's always working (using the command line created by MeGUI). I guess there's something messed up with passing the command line to the mencoder. I'm currently using MeGUI 0.2.3.1023. But I also tried it with 1021 and 1022. I can't find any older version below 1021 to give it a try with those.

Again I'll add two pictures.

[Razorholt]

Charleski, I tried many containers with our streaming software and, so far, only MPG(files have been encoded with MainConcept), WMVand OGM were usable. I don't seem to be able to stream any other formats and that includes MP4. FYI, we're using WMP.

Is there any specific settings I'm missing here?


Thanks,
- Dan

[Shinjite]

Pardon me for asking, I was wondering is it the latest MEGUI version posted in the first page?

[Doom9]

Pardon me for asking, I was wondering is it the latest MEGUI version posted in the first page?It wasn't.. now it links to the proper place.

[charleski]

@klicker4546: Can you try this version (http://homepages.nildram.co.uk/~cajking/MeGUI/MeGUI.NETv1.1.Bins_0.2.3.1018.rar) and see if it works? The commandline is fine, but you might be having an issue with the process call-backs.

[klicker4546]

Ok, I'll give it a try and let you know if it works.

@klicker4546: Can you try this version (http://homepages.nildram.co.uk/~cajking/MeGUI/MeGUI.NETv1.1.Bins_0.2.3.1018.rar) and see if it works? The commandline is fine, but you might be having an issue with the process call-backs.

[klicker4546]

It's still the same story. Nothing is going to happen after I hit the start button. Just an encoding status window pops up, but there's no activity at all. The calling event for loading the avs-script produced an error message. Is it the problem you referred to in your posting? And I need to set the output file manually. :confused:

Here's the commandline produced by mencoder:

Next job job1 is a video job. encoder commandline:
"C:\Programme\Videobearbeitung\MPlayer\mencoder.exe" "C:\Dokumente und Einstellungen\akw\Eigene Dateien\test.avs" -ovc xvid -xvidencopts bitrate=700:max_key_interval=300:vhq=1:chroma_me:trellis:lumi_mask:interlacing:rc_reaction_delay_factor=16:rc_averaging_period=100 -o "C:\Dokumente und Einstellungen\akw\Eigene Dateien\test.avi" -of avi -ffourcc XVID
successfully set up video encoder and callbacks for job job1

I also attach a screenshot of the status window.

This is really weird... but thanks anyway!!!

Ok, I'll give it a try and let you know if it works.

[Doom9]

The calling event for loading the avs-script produced an error message. What is "calling event" ? If there's an error loading the AviSynth script, it's no wonder it doesn't work.. MeGUI is very picky about its input and needs to be able to load it via VfW or nothing will ever be encoded.

[klicker4546]

I know it's very picky! But the avs-script works fine with version 0.2.3.1023. The preview works fine. And the MPC also plays the avs-script. So I don't think there's an issue with the avs. If you wanna have a look at the script, I'll post it.

What is "calling event" ? If there's an error loading the AviSynth script, it's no wonder it doesn't work.. MeGUI is very picky about its input and needs to be able to load it via VfW or nothing will ever be encoded.

[charleski]

Ok, we need to dissect the problem a bit more.
When you start the queue, press ctrl-alt-del and go to the Processes tab of the Task Manager. Is mencoder listed there, and if so, is it doing any work (look at the CPU%)?
Are you able to run other encoders, like x264, with meGUI?

[klicker4546]

Ok, here we go! Mencoder ist listed there, it starts to work for 1 or 2 seconds before it seems to get stuck. CPU-Usage 0-2%. That's odd. And I tried several versions of mencoder. Generic builds and also k7-because I've got an Athlon XP CPU. When I hit abort in the job-list or in the status window, the windows does not close. I need to close the whole application (MeGUI) or just click the status window that it disappears.

I tried it with x264 and it worked fine for me.

Alternatively I gave it a try with a directshowsource command in my avs-script to see whether that's gonna work or not.

DirectShowSource("C:\Dokumente und Einstellungen\...\Eigene Dateien\04VB.wmv",audio=false,video=true)
ConvertToYV12()

Is it an issue that I've got Avisynth version 2.56 installed instead of 2.55?


Ok, we need to dissect the problem a bit more.
When you start the queue, press ctrl-alt-del and go to the Processes tab of the Task Manager. Is mencoder listed there, and if so, is it doing any work (look at the CPU%)?
Are you able to run other encoders, like x264, with meGUI?

[charleski]

The avisynth version won't matter as long as it's over 2.55.
The commandline is formed correctly and the mencoder thread is being started, but I suspect it's hanging when mencoder tries to report back to meGUI, though this works fine on my machines (and this is the first time someone has reported such a problem).
Try running it with the progress window closed (an option in settings).
If this doesn't work, we need to add some more debugging code to see what's failing.

[klicker4546]

I'm actually trying it with MeWIG and mencoder works fine. ;)

Ok, I'll give it a try the way you suggested it.

I've got .net framework 1.1 and 2.0 installed. It possible that interferes?

The avisynth version won't matter as long as it's over 2.55.
The commandline is formed correctly and the mencoder thread is being started, but I suspect it's hanging when mencoder tries to report back to meGUI, though this works fine on my machines (and this is the first time someone has reported such a problem).
Try running it with the progress window closed (an option in settings).
If this doesn't work, we need to add some more debugging code to see what's failing.

[klicker4546]

Ok, I did as you told. I deselected the progress window in settings. And it is still the same. :-)

MeWIG is properly working. Damn, it's so strange!!!

[Shinjite]

Mine the problem started when I use MeGUI 0.2.3.1b (haven't update yet) and I couple it up with the latest mencoder with Xvid 1.2 dev and the 1st pass is not even working. When I switch back to mencoder with Xvid 1.1.0Beta 2, it works....

[klicker4546]

Hi, so you think the newer xvid version causes your problems then? Hmmm, I i have xvid 1.1.0-cvs from 9/12/2005 installed. And got mencoder not working under MeGUI.
:rolleyes:

Mine the problem started when I use MeGUI 0.2.3.1b (haven't update yet) and I couple it up with the latest mencoder with Xvid 1.2 dev and the 1st pass is not even working. When I switch back to mencoder with Xvid 1.1.0Beta 2, it works....

[Doom9]

I've got .net framework 1.1 and 2.0 installed. It possible that interferes? No, .NET binaries will pick the runtime they've been compiled on if it's available.. I have both runtimes installed as well. I guess the important question would be, can you handle a debugger? I have a feeling such an issue would be caught within a minute if you can debug. I could tell you where to set the breakpoints and which methods to step through.

Also, you quoted me above but forgot your reply ;)

Can you have a look at the stats file? How many frames does mencoder encode? And could you capture all stdout and stderr output when running mencoder from the commandline and attach here so we can see what MeGUI sees as feedback from mencoder. Since you report it starts up properly but then does nothing, this isn't so much a problem of events propagating back to the GUI rather than reading stdout and process that data I suspect. Event routing has a try/catch in it so if there were a problem updating the progress window, you'd notice an error message in the logs.

[weaver4]

I'm sorry but I have been looking for 30minutes on where to download the latest Executable MeGui. I found the source code but where is the executable? Can someone point me to it? Thanks,

[Doom9]

'm sorry but I have been looking for 30minutes on where to download the latest Executable MeGui. 30 Minutes? Why do I not believe that? Binaries have always been available from the first post of this thread. So, if you go to that post and use your browser's search (if you don't know that.. you need to take a crash course in computer use), and you type in download and see where it gets you. The second hit is
You can also download Sharktooth's builds And there's a link there.. and it goes to a page that has 4 file downloads.. so you have a 25% chance of hitting the right one without looking at the filename.. and a 100% chance if you look at the filename.. (anything with src in it looks suspiciously like source code).

Sorry, I can't resist.. nobody spends 30 minutes and doesn't find if a search on "megui download" yields the result in the first thread. If you said two minutes, maybe but even that's pushing it.. search engines were created so that you can search, and check out at least the 10 first links.. and if you didn't find anything after that, okay, it happens.

[klicker4546]

First of all thanks for your reply. Ok, now to your question, if I can handle a debugger. I have a little experience with programming VB .Net. Just a tiny little bit though, because I've just started to learn :rolleyes:. But I think I should be able to debug it with your (detailed) instructions. Where to set the breakpoints and which methods to step through. So let's give it a try.


No, .NET binaries will pick the runtime they've been compiled on if it's available.. I have both runtimes installed as well. I guess the important question would be, can you handle a debugger? I have a feeling such an issue would be caught within a minute if you can debug. I could tell you where to set the breakpoints and which methods to step through.

I wasn't aware of that. Can you forgive? :)

Also, you quoted me above but forgot your reply ;)

Ok, I gonna have a look at the stats file for you, in order to see how many frames are encoded and also at the stdout and stderr when I am running mencoder from the commandline. It could take some time though. Pls send send me the debugging info I need.

Can you have a look at the stats file? How many frames does mencoder encode? And could you capture all stdout and stderr output when running mencoder from the commandline and attach here so we can see what MeGUI sees as feedback from mencoder. Since you report it starts up properly but then does nothing, this isn't so much a problem of events propagating back to the GUI rather than reading stdout and process that data I suspect. Event routing has a try/catch in it so if there were a problem updating the progress window, you'd notice an error message in the logs.

[Doom9]

I wasn't aware of that. Can you forgive?I wasn't either initially, even though I should've known after taking that MS exam.

As far as debugging goes, you'll want to look at the method mencoderEncoding() in VideoEncoder.cs and set a breakpoint at the line line = sr.ReadLine(); // reads a line from stdoutthen go step by step from there. The while loop basically is a stdout reader loop, it reads everything from mencoder's stdout. So, if you start encoding, the first question is, do you even get to the breakpoint. If not, we'll have to start looking earlier than that. If you get to the point, start iterating (F5 in visual studio) and watch the contents of the variable line. As soon as it starts with "Pos:", start going step by step and watch what happens inside "if (line.StartsWith("Pos:")) // status update". If you get that far, pay special attention to the first time "counter" equals 10, as I suspect that's the last bit of code you're going to hit. Most likely, you get an exception thrown somewhere that will make the encoder thread exit or block, but I'm just guessing.

I think if you do that, we'll get real close to the problem rather quickly.

[weaver4]

30 Minutes? Why do I not believe that? Binaries have always been available from the first post of this thread. So, if you go to that post and use your browser's search (if you don't know that.. you need to take a crash course in computer use), and you type in download and see where it gets you. The second hit is
And there's a link there.. and it goes to a page that has 4 file downloads.. so you have a 25% chance of hitting the right one without looking at the filename.. and a 100% chance if you look at the filename.. (anything with src in it looks suspiciously like source code).

Sorry, I can't resist.. nobody spends 30 minutes and doesn't find if a search on "megui download" yields the result in the first thread. If you said two minutes, maybe but even that's pushing it.. search engines were created so that you can search, and check out at least the 10 first links.. and if you didn't find anything after that, okay, it happens.


Ok, I am not a newbe. Every link I found using a search tool pointed me back to this thread including Video Help, DivX Digest and such. I am not looking for the source just the executable.

http://www.google.com/search?sourceid=navclient-ff&ie=UTF-8&rls=GGGL,GGGL:2005-09,GGGL:en&q=megui


The first post has links to:
--.Net Framework
--Avisynth
--x264
--besweet (very nice)
--mp4box
--mkvtoolnix
--DCMPGDec

and links for just the MeGui x264 and Snow edition. I wanted to try MeGui with XVID so I did not think these were the right files.

When I go to Sharktooth site. It has two files with a .7z extension on them (wouldn't know what to do with those) and the other two files are: MeGui-Src*.rar which look like source files to me.

Regardless; with your exceptional guidance I was able to download the source code and get it to compile.

[Doom9]

well, if you get to Sharktooth's site, you're already there. 7z is just another compression format, that Winrar can handle (or 7zip can handle as well. there's a bunch of tools that can handle it.. but I suspect most people who handle rar use Winrar for it since it's the native tool.. since version 3.x Winrar can handle 7zip archives (open, but not create)).
So this is the latest compiled version: http://files.x264.nl/Sharktooth/force.php?file=./megui/megui_0.2.3.1023b.7z .. as I said, it's the only one without src in the filename. Though I admit, it would make much more sense to put the source in a separate directory so you'd only have one file in the main directory. I'm going to suggest that to Sharktooth.

I'm afraid as long as I'm taking a break from development, I can't make things as easy as they used to be since I'm no longer distributing anything myself. That may change again in the future but I'm booked till the end of the year.

[Sharktooth]

Binaries are now here: http://files.x264.nl/Sharktooth/?dir=./megui/Binaries
Sources here: http://files.x264.nl/Sharktooth/?dir=./megui/Sources

[Doom9]

thanks, I've updated the links.

[Chris Benoit]

Ok here's my question.I want to use MEGui to encode videos for psp.I have got the profiles and i see the PD-PSP one.I want to ask:Will i have better results if i enable rd0 2 instead of rdo?

Also what will i gain if i enable B-frame pyramid,i8x8 and lossless quantitizer.

And lastly will i get better results if i load a custom matrix?What are custom matrices anyway?

[Sharktooth]

Chris Benoit, "Video profiles for MeGUI" discussion is here: http://forum.doom9.org/showthread.php?t=101813
After my answer let's continue there the discussion.

RDO 2 (--subme 7) is only marginally better than standard RDO, but much slower.
The profile is good as it is and any modification may compromise the playability on the PSP.
So, do not enable b-pyramid coz the PSP doesnt support it.
All the PSP is not compatible with High Profile too.
i8x8, adaptive dct, lossless encoding (not quantizer!) and custom matrices are all in the High Profile and are not supported.

[Chris Benoit]

Ok thanx for clearing that up.Also one more thing.Should i tamper with the deblocking options?Alpgha and Beta?What do they actualy do?

Is this profile for megui the best solution for avc encoding for psp?

thanx for your answer.

[Sharktooth]

Ok thanx for clearing that up.Also one more thing.Should i tamper with the deblocking options?Alpgha and Beta?What do they actualy do?
If the picture is too washed out you may lower the deblocking levels. Find the sweetspot between a sharp picture and a blocky picture.

Is this profile for megui the best solution for avc encoding for psp?
Rule number 12 applies:
12) How NOT to post on this forum:

5 minutes after your initial post you reply to your own post writing something like "Why is nobody helping me? I'm sure you know the answer". Once somebody replies to your thread but doesn't give you exactly the answer you've been expecting you insult them.

Do not ask "what's best" because this question cannot be answered objectively. Each and everyone has their own view about what's best in a certain area. The best is what works best for you!

[Chris Benoit]

Oops sorry i forgot about that rule.Well let me rephrase.

Is there anything else i should be concerned with in order for the quality of the encoded file to yield better results?

So i tried encoding a file and the resulted mp4 was not playable.Well on the pc it played only the video,no sound but on the psp it displayed "corrupt file"

I used the default psp settings,didn't tamper anything.
And my avs was this:

DirectShowSource("C:\Documents and Settings\Administrator\My Documents\a.avi")
LanczosResize(368,208)
ChangeFPS(29.97)

[klicker4546]

Ok, I tried the debugging now. I set the breakpoint at the line where you wanted me to. No problem so far with mencoder. I was able to step to the breakpoint without any problems. I was able to iterate by pressing F5. The loop was done 9 times before it gave 2 exceptions: System.IO.IOException, System.OutOfMemoryException. I'll attach you two screenshots. You were right when you suspected that the last line I'll be able to hit is the first time "counter" equals 10. That's the point where it either blocks or the program exits. Pretty good!

I hope that this helps to isolate the problem.

Also I attached the xvid-stats file and 2 screen captures of mencoder's command line stdin/stdout. Hopefully it's all you need. I'm not really sure if I did it right or not. Pass me some feedback, please. As I am eager to learn. :)


I wasn't either initially, even though I should've known after taking that MS exam.

As far as debugging goes, you'll want to look at the method mencoderEncoding() in VideoEncoder.cs and set a breakpoint at the line line = sr.ReadLine(); // reads a line from stdoutthen go step by step from there. The while loop basically is a stdout reader loop, it reads everything from mencoder's stdout. So, if you start encoding, the first question is, do you even get to the breakpoint. If not, we'll have to start looking earlier than that. If you get to the point, start iterating (F5 in visual studio) and watch the contents of the variable line. As soon as it starts with "Pos:", start going step by step and watch what happens inside "if (line.StartsWith("Pos:")) // status update". If you get that far, pay special attention to the first time "counter" equals 10, as I suspect that's the last bit of code you're going to hit. Most likely, you get an exception thrown somewhere that will make the encoder thread exit or block, but I'm just guessing.

I think if you do that, we'll get real close to the problem rather quickly.

[Doom9]

hmm, can you set a conditional breakpoint that hits when counter is 9, then go step by step from there to find out exactly which line causes the exceptions, and show me your autos (the variables visual studio automatically tracks) as well as the current value of line ? And OutOfMemoryException really scares me.. are you running low on memory? Also, can you get the Message property of these two exceptions? Especially the IO Exception.. I'm wondering what could cause this.. actually I suspect it could be the
if (job.Output != "") // if its empty, we're dealing with a 2pass first pass that does not generate an output file
{
FileInfo fi = new FileInfo(job.Output);
su.FileSize = fi.Length / 1024;
} part, which then of course raises the question, which job are we talking about? Is this a single pass job or a second pass job? And can you verify that the file mentioned in job.Output actually exists.

[klicker4546]

Oh my, that's quite a hard crash course of debugging for me! :p

But ok, I consider it as sort of an challenge for me. I'll give it a try tomorrow or on sunday.

Hmm, I have 768 MB of RAM. It should be fine, I guess.

Can you tell me something how to set up conditional breakpoints and a little bit of those variables VS automatically tracks? Where to find etc... ?

hmm, can you set a conditional breakpoint that hits when counter is 9, then go step by step from there to find out exactly which line causes the exceptions, and show me your autos (the variables visual studio automatically tracks) as well as the current value of line ? And OutOfMemoryException really scares me.. are you running low on memory? Also, can you get the Message property of these two exceptions? Especially the IO Exception.. I'm wondering what could cause this.. actually I suspect it could be the
if (job.Output != "") // if its empty, we're dealing with a 2pass first pass that does not generate an output file
{
FileInfo fi = new FileInfo(job.Output);
su.FileSize = fi.Length / 1024;
} part, which then of course raises the question, which job are we talking about? Is this a single pass job or a second pass job? And can you verify that the file mentioned in job.Output actually exists.

edit:

I almost forgot: I tried both kind of jobs. First I tried two pass, because it didn't work, I tried it with single pass. There's a little avi-file as an output. It's only a few kbytes, because mencoder gets stuck.

[Doom9]

when you start debugging, you have various tabs at the bottom (unless you deactivate them).. one is called autos, and there's one called breakpoints. You'll see that your regular breakpoints have no condition set, then you can right click on one, select properties and configure it. Or do it the easy way, just press F5 8 times after hitting the breakpoint, then continue with F10 until it crashes.. I often do that to get a feeling of how the software works.

[klicker4546]

Hi, I tried to step over. Think I found it where the exception occurs. And I think I also traced the variables value. I made a few short avi-sequences and also screenshots. I'll send them as PM to you, hope that's ok.

Maybe it helps.

Furthermore it's really interesting that mencoder still runs after MeGui exits, while debugging. This normally does not happen if I run MeGUI. Mencoder doesn't do anything and hangs.

I'm uploading the files of the debug to megaupload.com. I'll send you the link as PM.

when you start debugging, you have various tabs at the bottom (unless you deactivate them).. one is called autos, and there's one called breakpoints. You'll see that your regular breakpoints have no condition set, then you can right click on one, select properties and configure it. Or do it the easy way, just press F5 8 times after hitting the breakpoint, then continue with F10 until it crashes.. I often do that to get a feeling of how the software works.

[Sharktooth]

@Doom9: May i include MeGUI (full) in a completely new package that will include x264 and faac also?

[Doom9]

absolutely.. the more it's being spread the better. I just regret not being able to put more time into it at this point but I hope to change that next year.

[Sharktooth]

The idea is to create a all-in-one solution for DVD to MP4 (AVC+AAC) backup maybe including also dvd ripping thru mencoder + libdvdcss.
In any case (x264 CLI or mencoder), MeGUI is a real lightweight app and the one click encoder is very easy for newbies.
In a near future the packages will be renamed to x264-lite, x264-std and x264-full.
Also if coding tech aac+ (the winamp encoder) or nero aac+ support could be added it would be great.

[Doom9]

I plan to look closely at the audio department, going through what dimzon suggested. If that can be done properly, we can implement proper cutting, for any kind of stream to the tool, thus creating a huge benefit over traditional solutions.

I'm no fan of using mencoder for decoding and ripping though.. I frankly don't trust anything but DGDecode, and mencoder lacks in x264 and xvid features (xvid_encraw will be supported in the new improved version).
Another point where serious improvement can be made is the avi muxing / splitting area.

We should also give serious thought to the current codec configuration dialogs, and perhaps how the software starts up.. most people seem to miss the one click mode.. perhaps this should be the default, and people using more advanced modes can be trusted to find their tools instead of going to other way round.

[Sharktooth]

yeah. i totally agree. a "basic" and "advanced" choice at start would be cool.
one click encoder could have different presets for the newbies too.
for what concerns the audio part, i would drop all the non-free stuff (including the nero encoder) and use only free (OS or not) softwares (lame, faac, winamp...).

[Doom9]

well.. winamp is commercial too.. you just don't have to pay for it.. but how long is this going to last? If I have significant reason to believe that the free alternatives are at least equal if not superior than the nero encoder, I have no quarrel dropping it.. but if it means giving in in quality, then this shouldn't be an option, and since you can chose different AAC encoders, we can still offer a free version, and even a completely open source based version as well.

[Sharktooth]

well, from the first tests the winamp 5.12 encoder performs better than nero (at least on low bitrates).
samples are available in the Real Anime LE thread.
However there will always be a free version of winamp... :)

[Doom9]

but who says it they won't move the AAC encoder to the pay version? Unless something is open source you can never be 100% sure it's going to be available forever.

[Sharktooth]

well, nero is already payware and is limiting their software more and more... in the worst case we will have a free AAC+ solution for a while.

[Doom9]

well.. those 32 kbit comparisons are completely useless to me, in fact it makes me want to shoot myself. They prove nothing, there's no settings, nothing. Winamp only does CBR, Nero has quality based mode as well. And interesting bitrate ranges for DVD backups would be 96 kbit up to 160 kbit/s, with Winamp's CBR having to face Nero's quality mode.. you gotta use the best of each codec.. who cares of Winamp CBR is better than Nero CBR if you're going to use Nero quality mode? I'll await ramorjim's tests if he ever does a test that suits DVD backups, or any other test that looks halfway serious (I don't trust myself with audio.. I'm a videophile and can live even with 128 kbit/s CBR MP3).

[Sharktooth]

well... aac+ at 64kbps is quite good, similar to LC-AAC at 96kbps.
Yes, 32kbps samples maybe are too much, but if yo go over 96, then AAC becomes useless (just use MP3).
However, even at 32kbps they sounds pretty good...

[Doom9]

@: let me recapitulate your videos and screenshots:

line contains "Pos: 0.8s 10f (0%) 0.00fps Trem: 0min 0mb A-V:0.000[0:0]
the IOException happens in the line "line = sr.ReadLine();" with counter being set to 9.

And MeGui crashes at the line "su.FPS = this.getFPS(line);

Is that correct? What is the content of line when megui crashes and can you step into the getFPS method to find the exact location, and the important variables in that method?

The warnings are just from .Net 2.0.. just shows some of the differences to the 1.1 runtime but they are nothing to be worried about.

Also, can you try commenting out all the code inside the "if (line != null)" and see if you can get past the 10th frame?

also try wrapping all the code inside "(while !proc.HasExited)"
in a try {}

and add the following catch:

catch (Exception e)
{
log.Append("exception in mencoderEncoding: " + e.Message);
}

And just to make sure nothing goes haywire on your system, can you try encoding via x264.exe for a change just to see if that works out properly? or try audio encoding

[klicker4546]

Yes, you're right. I stepped in to the method again and made another screen capture vid, which shows the value of the variable before it crashes. After the program exits. I can't see it's value. Maybe I should set here a breakpoint?

@: let me recapitulate your videos and screenshots:

line contains "Pos: 0.8s 10f (0%) 0.00fps Trem: 0min 0mb A-V:0.000[0:0]
the IOException happens in the line "line = sr.ReadLine();" with counter being set to 9.

And MeGui crashes at the line "su.FPS = this.getFPS(line);

Is that correct? What is the content of line when megui crashes and can you step into the getFPS method to find the exact location, and the important variables in that method?

Ok, so I take it that I can just ignore those messages then.

I've tried to go along with your suggested debugging instructions. But it seems way to complex to me. I've just started programming (VB .Net) and C# looks way strange to me.

I had an idea though. I'm running VM Workstation. I could set up a working environment, where someone could go ahead with the debugging on my computer as it seems that I am not able to go ahead.

It's the point that I'm not aware where for example the method "(while !proc.HasExited)" starts and ends. Where to insert the try{} and the catch. :scared:
The warnings are just from .Net 2.0.. just shows some of the differences to the 1.1 runtime but they are nothing to be worried about.

Also, can you try commenting out all the code inside the "if (line != null)" and see if you can get past the 10th frame?

also try wrapping all the code inside "(while !proc.HasExited)"
in a try {}

and add the following catch:

catch (Exception e)
{
log.Append("exception in mencoderEncoding: " + e.Message);
}

And just to make sure nothing goes haywire on your system, can you try encoding via x264.exe for a change just to see if that works out properly? or try audio encoding

[Doom9]

alright, I'm attaching a zip file containing two source files.. just plug them into your source directory, compile and run and see what you get. I suspect there will still be problems so try debugging again. Once counter is equal to 9, step through everything pressing F11.. that will jump into every other method that is being called as well. Then please give me the exact line you were on before you pressed F11 and an exception was catched. And if the program still crashes, the same for the crash please (which line are you on before pressing F11 caused the crash).

[Sharktooth]

uhm. well, i'll add the winamp AAC+ encoder support (thru besweet+bsn) and will update the nero encoder support.

[klicker4546]

Ok, thanks again for your help. This this will make it a little easier for me.

I'll let you know what happened.

alright, I'm attaching a zip file containing two source files.. just plug them into your source directory, compile and run and see what you get. I suspect there will still be problems so try debugging again. Once counter is equal to 9, step through everything pressing F11.. that will jump into every other method that is being called as well. Then please give me the exact line you were on before you pressed F11 and an exception was catched. And if the program still crashes, the same for the crash please (which line are you on before pressing F11 caused the crash).

[molitar]

Question on mencoder I have a AMD 64bit processor but running 32bit windows should I install the xp or the 64bit version? In other words is it based on the operating system or the processor?

[Doom9]

@molitar: mplayer2005.11.23.Athlon-64.7z = a 32 bit build for the athlon64.. basically it's an sse3 build.. but it really doesn't seem to matter which build you take.. you can make your own speed tests if you like to verify that.

[molitar]

Ok I got all the components but one suggestion it took me a while to figure out where the full megui was. Was looking for a link for it throughout the thread.. I would suggest where you have the link to download the x264 CLI that you add (includes megui).

[Doom9]

the download link is in the first post. I'll add a bold "click here to download" on line4 of that post right after the program description and before the links to all the additional components you will need. I hope that'll be satisfactory. What sharktooth and bobor distribute is not under my control, though at least Sharktooth is going to include the full version in the future.

[molitar]

I crashed using megui. Crash log below: I also noticed that the file requires haali media splitter to open it but when I go to queue it I have 4 haali media splitter tray icons don't know if that could be a part of it or not.

See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.NullReferenceException: Object reference not set to an instance of an object.
at MeGUI.AVIReader.AVIFileRelease(Int32 pfile)
at MeGUI.AVIReader.Dispose(Boolean disposing)
at MeGUI.AVIReader.Close()
at MeGUI.VideoPlayer.OnClosing(CancelEventArgs e)
at System.Windows.Forms.Form.WmClose(Message& m)
at System.Windows.Forms.Form.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)

[klicker4546]

Ok, now. I build MeGui with your changes applied. The application did not crash anymore. :p

And I did a little more of debugging. The line before it throws the exception is

su.NbFramesDone = getFrameNumber(line);

The counter variable had a value of 10. I stepped once more with F11 and it threw an exception in line

public int NbFramesDone
{
get {return nbFramesDone;}
---> set {nbFramesDone = value;}
}


Error message: - AudioPositionTicks 'this.AudioPositionTicks' threw an exception of type 'System.NullReferenceException' long {System.NullReferenceException}
- base {"Object reference not set to an instance of an object."} System.SystemException {System.NullReferenceException}
- base {"Object reference not set to an instance of an object."} System.Exception {System.NullReferenceException}
+ Data {System.Collections.ListDictionaryInternal} System.Collections.IDictionary {System.Collections.ListDictionaryInternal}
HelpLink null string
+ InnerException null System.Exception
Message "Object reference not set to an instance of an object." string
Source "MeGUI" string
StackTrace " at MeGUI.StatusUpdate.get_AudioPositionTicks() in D:\\megui_src\\StatusUpdate.cs:line 206" string
+ TargetSite {Int64 get_AudioPositionTicks()} System.Reflection.MethodBase {System.Reflection.RuntimeMethodInfo}
- Static members
- Non-Public members
_COMPlusExceptionCode -532459699 int

Ok, thanks again for your help. This this will make it a little easier for me.

I'll let you know what happened.

Hope it helps to trace the problem now! :sly:

[Doom9]

when you step into the method "getFrameNumber(line)", what does happen? If you press F11 when you're on line
su.NbFramesDone = getFrameNumber(line);You'll go to line 494 where the method getFrameNumber starts.. what is the content of the variable
string frameNumberinside that method? It should be 10, should it not?
And what's the value of nbFramesDone and value in
set {nbFramesDone = value;}

Perhaps you could just give me a link to the mencoder build you're using? Man I wished I would sit in front of that pc.. it's probably the most frustrating thing for any programmer.. while it doesn't always solve things, being able to get your hands on a debugger that shows the actual problem.. you just can't beat the bugfixing power of that.

Your exception location makes no sense though, you the only way the ProgressWindow accesses the variable AudioPositionTicks is when you have an audio status update. Are you really 101% sure you are looking at the right place? On line 222 in VideoEncoder.cs I declare StatusUpdate. On line 227 in the same file I set su.JobType to 0, meaning it's a video job, and that's not changed through event propagation or anywhere in the class itself.

So can you add additional breakpoints in StatusUpdate.cs on line 18 (double div = (double) AudioPositionTicks / (double)AudioLengthTicks;) and line 373 in ProgressWindow.cs (if (su.JobType == 1) // audio status update). If those are triggered, step through them until you get an exception. Note the line number of the exception, do the whole thing again, stop stepping one line before the exception and give me a list of the locals please (only local variables of ProgressWindow and StatusUpdate please).

Basically the exception you're reporting here makes no sense.. it looks like you're encoding video but the status update is for an audio job.. needless to say that this will never work.

Another perhaps easier attempt: put a breakpoint on line 272 in VideoEncoder.cs. Dump the contents of the variable su at that point.. that's the StatusUpdate object that gets propagated to the MeGUI and ProgressWindow class, and that's where the exception comes from ultimately. And do you ever get into the catch in VideoEncoder.cs on lines 285 and below?

@molitar: loaded assemblies are usually not info anybody needs, however, all steps taken from the loading of MeGUI until th exception.. that's information you should never leave out, even if it turns out not to be useful.. it's covering all the basics that make a good bug report.

[stax76]

I'm not a debugging expert but for me the only thing that really works is to configure VS to break immediatelly even if the exception is handled, appears to have many advantages and on top of that some really weird things happened here until I configured VS like that. Of course sometimes a exception can be expected and this is not wanted but on such methods the DebuggerNonUserCodeAttribute can be applied so VS won't break.


On the Debug menu, click Exceptions.

In the Exceptions dialog box, select Thrown for an entire category of exceptions, for example, Common Language Runtime Exceptions.


http://msdn2.microsoft.com/en-us/library/d14azbfh.aspx

[klicker4546]

Oh man, do we ever get it resolved? :eek:

And I am absolutely sure that it was that line where the exception occurs. So far can see it! I'm not too familiar with debugging and just a beginner with programming in general.

Ok, I will try what you'd wanted me to try. I'll attach two vid-caps of the last debugging session to my next message.

when you step into the method "getFrameNumber(line)", what does happen? If you press F11 when you're on line
su.NbFramesDone = getFrameNumber(line);

[Doom9]

Oh man, do we ever get it resolved?if there's a way for me to remote access your desktop then I think it would be rather easy. However, if you just gave me the link to your mencoder build, I could compile the latest code on my own to see if anything as funky happens. I'm almost certain su.JobType is equal to 1 on your box, no idea why it happens, but it would explain the exception you're getting.

[klicker4546]

Ok, I'll download vnc and setup remote access. It would really ease up the whole process. :-) Let me see what I can do. Ok, here's the link to the mencoder build I use.

Mencoder (http://oss.netfarm.it/mplayer/builds/mencoder-k7-cvs-20051213.zip)

if there's a way for me to remote access your desktop then I think it would be rather easy. However, if you just gave me the link to your mencoder build, I could compile the latest code on my own to see if anything as funky happens. I'm almost certain su.JobType is equal to 1 on your box, no idea why it happens, but it would explain the exception you're getting.

[Chris Benoit]

IS there a way to import a bunch of avs files altoghether?Instead of opening the avs one by one and adding to the queue wouldn't it be better to open a bunch of them at the same time,so they will be queudd altogether?

[Doom9]

well,it's a pretty big presumtion to assume every source would be encoded exactly the same way..

[klicker4546]

Hello doom9,

I have set up ultravnc. If you want you can do the debugging on my desktop.

I will send you the rc.key file for a secured connection if you like.

Do you have any instant messenger like ICQ or so?

Please let me know if you wanna go ahead with it.

Edit: I did a litlle more debugging. I am able to get to line 285 and further. So that an exception was catched. I attach a screenshot and a copy of the error message.

[Chris Benoit]

Well what harm could it be for that option to exist?If someone doesn't need it he's not obligated to use it.

I on the other hand only need avc encoding for psp,and for every file i need to encode i use the psp profile,so it would save me a considerable amount of many if every time i could just open all avs files at once.

So what do you say?

[Sharktooth]

opening multiple avs files would mean a complete rewrite of the job and settings controls.
dunno if it's worth adding it, since it can lead to some problems too (for example bitrate setup).

[Doom9]

@Chris: I'm afraid it's not that easy to achieve.. an app is built a certain workflow, and in case of MeGUI, it's load an avisynth script, load a profile / select codec and configure, select the container, press queue, or before pressing queue load the audio file, configure that as well, and go the autoencoding route.

It gets even more complex when you consider the one click encoder.

How would your idea work with all those modes? And keep in mind that you shouldn't break existing workflows while at it.

[Chris Benoit]

I see,i just asked if ti was possible without having to go to that trouble,but since you say that it needs lots of work and it could result to problems then i gues i'll just have to add manually every .avs.

Thanx for your replies guys.

[greggerm]

Problem:
I am attempting to use the one-click mode - After MeGUI passes a job to a video encoder (tested with both x264 and mencoder) for a two-pass job, the progress window pops up and no progress is made. The .stats file is created, but remains empty (0kb), and the (x264/mencoder) encoder process appears to do work at 50% processing time (hyperthreaded cpu).

I've left the system in this state overnight when attempting to encode both a 4 minute chapter of a DVD, and an entire DVD itself, but when I wake up in the morning, everything is just as it was - processor use at 50% and no stats. In essence, no progress.

Programs
Megui Full 0.2.3.1023d (tested with previous versions over the past few days)
x264 Full 387E / mplayer 2005.11.23.P4
Avisynth 2.5.6
dgdecode 1.4.5
besweet 1.5b31 +nero AAC
mp4box (downloaded as linked here Friday)
yuvcodecs-1.2

.net 1.1

Settings
I've tried my own settings, but I also tested with the "generic" suite of profiles provided on the forums (v.91?).

Edit: When I attempt to play the AVS file, media player pops up then closes immediately - is this part of the issue?

Edit: I also attempted to run the command line found in the logs FROM the command line - it launches the encoder, gets to the processor id section (SSE, SSE2, etc), and holds there. CRTL-C escapes.

Edit: Edited out the log files and command lines, as it seems that Doom9 has uncovered an issue with One Click Encoding and the resultant D2V file. (Below)

[Doom9]

Edit: When I attempt to play the AVS file, media player pops up then closes immediately - is this part of the issue?Yes I believe so. Could you recreate the d2v file manually (using dgindex directly, not via megui), make sure you enable force film if megui enabled it (to find that, open the d2v file via notepad and look at the last line.. if it mentions a percentage larger than what is in the settings (95 by default) enable force film in dgindex. Then please post both d2v files so I can have a look at them.. I believe megui does something that corrupts the d2v file and this propagates through the AviSynth script and makes encoding fail.

[greggerm]

The oneclick D2V file has some extra wording (almost comments) in the first block of information. The dgindex native file does not have that commenting. (Inside the Field_Operation line)

I edited the oneclick one to remove those words, and I was able to open the AVS - and presumably the encode would continue, but I can't quite figure out how to resume an aborted job.

I've attached the two files in a zip for your pleasure.

Hopefully this little hiccup can be addressed - the One Click option is *HUGE* for us newbs who are migrating over from Nero. :)

Edit:

In the interest of speed (seeing as the attachment needs approval), here's the difference I noticed... I cannot guarantee that it's the ONLY difference, but when I removed the extra coding, it was usable in AVS.

MeGUI/One Click Created
Field_Operation=1 (0:None 1:ForcedFILM 2:RawFrames)

DGIndex Native Created
Field_Operation=1

Thanks,
-Greg

[Doom9]

but I can't quite figure out how to resume an aborted job. Just double click on it.. it goes back to waiting state ;) Thanks for the project files, I'll have a look tomorrow.. it's getting late.

[Doom9]

aww, crud.. thanks for those d2v files.. they remind me of what I should've fixed a long time ago. I'm pretty sure that if you take this line:

Field_Operation=1 (0:None 1:ForcedFILM 2:RawFrames)

and convert it into

Field_Operation=1

The file should work just fine.

Umm.. which release of MeGUI it is you're using? Turns out that's been long fixed.

[greggerm]

Yes, removing the extra stuff makes a world of difference. I noticed that running the logged DGIndex command line on it's own creates a clean file, but the resulting file if left to MeGUI has the comments in it.

Using the latest and greatest build posted today by Shark in the Dev thread... 0.2.3.1023D.. is there a different one I should be using?



In my testing with a clean file, I came across a question about the one-click functionality: ...it doesn't... at least for me. :)

I run a one-click job, and manually edit the D2V file as seen above. It runs the audio portion fine, and starts the 1st pass of the video. But it errors immediately when starting the 2nd pass. The logs show some sort of odd calculations, which result in the 2nd pass bitrate to be set at 0. x264 doesn't like this, and errors out.


----------------------------------------------------------------------------------------------------------
job job2-1 has been processed. This job is linked to the next job: job2-2
this series of jobs starts with an audio job and is followed by regular twopass video jobs
The audio job is named job2-1 the first pass job2-2 and the second pass job2-3
The second pass job has a desired final output size of 20480000 bytes and video bitrate of 700 kbit/s
The size of the first audio track is 5787017 bytes
Desired video size after substracting audio size is 14261Setting the desired bitrate of the subsequent video jobs to 0 kbit/s
Next job job2-2 is a video job. encoder commandline:
"C:\Audio and Multimedia\MeGUI\x264\x264.exe" --pass 1 --bitrate 0 --stats "C:\TIJ\VIDEO_TS\VTS_04_1.stats" --bframes 3 --b-pyramid --filter -1,0 --subme 1 --analyse none --me dia --threads 2 --progress --no-psnr --output NUL "C:\TIJ\VIDEO_TS\VTS_04_1.avs"
successfully set up video encoder and callbacks for job job2-2
----------------------------------------------------------------------------------------------------------

Log for job job2-2

avis [info]: 640x272 @ 23.98 fps (8614 frames)
x264 [info]: using cpu capabilities MMX MMXEXT SSE SSE2
x264 [info]: slice I:48 Avg QP:47.44 size: 1546
x264 [info]: slice P:3338 Avg QP:50.98 size: 251
x264 [info]: slice B:5228 Avg QP:50.97 size: 143
x264 [info]: mb I I16..4: 91.4% 0.0% 8.6%
x264 [info]: mb P I16..4: 10.4% 0.0% 0.0% P16..4: 8.0% 0.0% 0.0% 0.0% 0.0% skip:81.5%
x264 [info]: mb B I16..4: 6.1% 0.0% 0.0% B16..8: 18.5% 0.0% 0.0% direct: 0.3% skip:75.2%
x264 [info]: final ratefactor: 231.11
x264 [info]: kb/s:36.9

Actual bitrate after encoding without container overhead: 37.92

----------------------------------------------------------------------------------------------------------
job job2-2 has been processed. This job is linked to the next job: job2-3
Next job job2-3 is a video job. encoder commandline:
"C:\Audio and Multimedia\MeGUI\x264\x264.exe" --pass 2 --bitrate 0 --stats "C:\TIJ\VIDEO_TS\VTS_04_1.stats" --ref 5 --bframes 3 --b-pyramid --filter -1,0 --subme 6 --weightb --trellis 1 --analyse all --8x8dct --threads 2 --progress --no-psnr --output "C:\TIJ\VIDEO_TS\VTS_04_1_Video.mp4" "C:\TIJ\VIDEO_TS\VTS_04_1.avs"
successfully set up video encoder and callbacks for job job2-3

...and then it errors out and stops...


This is with the versions listed a few threads above (all current as of 12/19/05)

Somewhere along the lines, signals are getting crossed and the one click system seems to be getting confused. If I cut n' paste the 2nd job's command line, edit the bitrate and run it in a window, I get a properly created mp4 which I can then mux together.

And with that, I have an additional question - I am looking for the encoder to do it's work targetting a specific bitrate, not file size. Using the "standard" but slower workflow, a box pops up using the AutoEncode mode asking if you want to target the encode to a size, target a bitrate, or target a quality. How can I control these options in a one-click mode? I am leaning on this to take away my "dependancy" on Nero Recode, as it provides you with the ability to set the bitrate independant of any desired size restrictions.

Edit: On Page 10 of the Dev thread (Post 190 (http://forum.doom9.org/showpost.php?p=684806&postcount=190) ), doom9 mentions that the automatic modes are NOT rate based, and are very much "target size" oriented. Unless that has changed, looks like I may be out of luck. While the "full" encoding method may be a bit tedious with the great number of DVD's I want to rip down, perhaps someone can offer up a very smooth workflow to nicely set up a half-dozen DVDs at a time or so...

Thanks for your continued help and pointers,
-Greg

[Chris Benoit]

Guys can i make some other suggestion for features to add?

A)Can you add the feature off time-start jobs?In order for the queud files to be encoded in a speicified time.

B)Also when you input an avs,then the output should have the same name.For the first avs it does that,but when you put a second the output stays the same.

E.g. you put a.avs and the output automatically becomes a.mp4 but if you put b.avs the output remains b.mp4,so can it become b.mp4 and so on?

P.S.If i have any further suggestions should i address them here or in the megui development discussion?

[amango]

Feature request:

I encode usually recorded stuff from DVB. For this material it is useful if I could set ranges (start-ending) which frames to encode to cut out advertisement.

Without the cutting-feature I am limited to VirtualDub, so I have to use the VfW-version of x264.... MeGui can only be used for DVD-ripps in his current form (as other apps like Auto Gordion Knot).

[buzzqw]

trim with cuttermaran/Mpeg2Schnitt
make a d2v project
import d2v to megui

BHH

[greggerm]

aww, crud.. thanks for those d2v files.. they remind me of what I should've fixed a long time ago. I'm pretty sure that if you take this line:
Field_Operation=1 (0:None 1:ForcedFILM 2:RawFrames)
and convert it into
Field_Operation=1
...
Umm.. which release of MeGUI it is you're using? Turns out that's been long fixed.

Doom9 - just curious - did I stumble upon a bug that was reintroduced into the program, or should I be using another build other than the one I am (Sharktooth's 0.2.3.1023D, as found in the development thread yesterday)

Thanks!
-Greg

[Doom9]

@amango: once we rewrite audio to no longer use BeSweet, that will be possible, but prior to that there's just no way.. going AviSynth we can accurately cut audio and video and that's what's needed to cut out commercials.

@greggerm: I'm honestly perplexed why this happens, I only have the 0.2.3.1023 source code here right now but that one seems to have the proper code. As x264.nl is currently down I can't check if the very latest source has this problem as well. But the funny thing is that I experienced the same problem (I'm not sure about the d2v containing the wrong contents.. I never checked) with the build on my HD (an older one).. and that one seems to have the proper code as well so I need to investigate this a bit more, but with the codec comparison I have my hands full.

P.S.If i have any further suggestions should i address them here or in the megui development discussion?Here please

A)Can you add the feature off time-start jobs?In order for the queud files to be encoded in a speicified time.Can you give me a reason not to start them immediately?

[Doom9]

well.. I found the dgindex bug alright, the problem is it was fixed when I was making the indexer more flexible and copied code around.. I was still using the code in the old location and fixed that, so once I started using the code at the new location, that one didn't include the fix. Somebody needs to change line

208 in DGIndexer.cs to

sw.WriteLine("Field_Operation=1");. And if the method public static void applyForceFilm(string fileName)is still in VideoUtil.cs, it can be safely removed (I hope.. I can't download the latest sources to compare with what I have and see if it compiles).

[stax76]

@amango

The available MPEG-2 cutters "don't seem to cut it" so until it's supported by MeGUI or StaxRip maybe you can generate your script using AVSEdit. I already wanted to start working on it as you and some others requested it but was scared of because the required changes will have rippling effects all over the application.

[greggerm]

well.. I found the dgindex bug alright, the problem is it was fixed when I was making the indexer more flexible and copied code around.. I was still using the code in the old location and fixed that, so once I started using the code at the new location, that one didn't include the fix. Somebody needs to change line...

I take it I'd need development tools in order to compile with that change on my own. :)

I'll sit tight and watch for the next build and hope it's cleaned up in there.

THANKS for your effort in weeding that out!
-Greg

[Sharktooth]

well.. I found the dgindex bug alright, the problem is it was fixed when I was making the indexer more flexible and copied code around.. I was still using the code in the old location and fixed that, so once I started using the code at the new location, that one didn't include the fix. Somebody needs to change line

208 in DGIndexer.cs to

sw.WriteLine("Field_Operation=1");. And if the method public static void applyForceFilm(string fileName)is still in VideoUtil.cs, it can be safely removed (I hope.. I can't download the latest sources to compare with what I have and see if it compiles).
I'll do it as soon as files.x264.nl is back online...

EDIT: done. check the development thread. Sources and Bins are available.

[greggerm]

EDIT: done. check the development thread. Sources and Bins are available.

Schweet - fetched - tested - works!

MeGUI operational question -
What's the parallel setting between MeGUI and Nero Recode for the Nero-branded "Psychovisual Enhancements" (the things that compress dark scenes more, theoretically savings space by sacrificing dark details). I'd like to tweak the settings a touch in MeGUI/x264 - I've been using Nero as a crutch, so I have to learn the REAL settings now.

[Sharktooth]

x264 has no "real" psy enanchments yet.

[sh0dan]

Would it be possible for any of you put up a mirror somewhere. I haven't been able to download the binaries for more than a day. Very frustrating! :angry:

[Sharktooth]

Would it be possible for any of you put up a mirror somewhere. I haven't been able to download the binaries for more than a day. Very frustrating! :angry:
a mirror is already provided. check this post: http://forum.doom9.org/showthread.php?p=754913#post754913

[Paul Atreides]

nsis 2.12 could be use by Sharktooth to make x264 package

[charleski]

@amango

The available MPEG-2 cutters "don't seem to cut it"
The vast majority of my encodes are DVB MPEG-2s cut and demuxed with ProjectX or PVAstrumento/cuttermaran. I have no problems with them in meGUI whatsoever.
Introducing editing functions into meGUi would hugely add to the complexity (as you need to maintain sync with the audio) and is completely unessecary as there are other tools that do the job.

[stax76]

Maybe those apps have improved but compared to the application I use to cut I found those apps much of a pain last time I've tried.

[nixo]

Is it possible in MeGui to do a fixed quant XviD encode using a quantizer that isn't a whole number?

It seems to work fine from command line but I'm not having a lot of success in MeGui.

[sh0dan]

a mirror is already provided. check this post: http://forum.doom9.org/showthread.php?p=754913#post754913
I cannot see the Full Package anywhere - and it's still down.

[Doom9]

Is it possible in MeGui to do a fixed quant XviD encode using a quantizer that isn't a whole number?No (well, yes but doing that is only for programmers). And I'm pretty sure as far as XviD or other ASP codecs are concerned, you only have integer quantizers.

@sh0dan: I've added a link to the temporary mirror.

[stax76]

No (well, yes but doing that is only for programmers). And I'm pretty sure as far as XviD or other ASP codecs are concerned, you only have integer quantizers.

Don't know about mencoder but VFW codecs don't need integer, for DivX there is quite a bit difference beween 3 and 4, I tend to use XviD at 2.5, iirc it compares to DivX at 3.

[Doom9]

and what would 2.5 result in? 50% 2 and 50% 3? Don't tell me there's 2.5 quantizer I'm unaware off (and for that matter the XviD status window)

[stax76]

I just recently started to play with advanced codec settings so I'm pretty much clueless. I made however a quick XviD test, there appear to be a file size/quality difference:


q4 = 2.89 MB
q3.5 = 3.75 MB
q3 = 4.13 MB
q2.5 = 6.28 MB
q2 = 6.76 MB

[akupenguin]

Yes, XviD dithers the quants, 50% q2 and 50% q3.
lavc allows a qscale=2.5, and really does it (rounds to the nearest integer quant, but tweaks RD and trellis to get a quality point halfway between qscale=2 and qscale=3).

stax: Notice how your q2.5 is nowhere near halfway between q2 and q3. That's because the q3 half of the frames are lower quality, but most of the details missed there just have to be encoded in the next q2 frame. So overall you don't save many bits, and just lose a little compression efficiency.

[nixo]

AutoGK uses this approach when you choose 'Target Quality' mode. 75% quality equals quant 2.67, 67% equals quant 2.99 and so forth... It's really nice to do 1-pass encodes when your hardware isn't exactly state-of-the-art and file size isn't an issue.
I've been doing 2.67 quant encodes through VDubMod for a while and I just thought I'd ask since MeGUI looks really good to me... :-)

[Doom9]

well, it's no problem changing those up/down boxes. I don't see the sense of 1 pass encoding *at all* but it's no problem to make the change.

[nixo]

That'd be great. Thanks!

[stax76]

I use always single pass quality mode. Regarding multipass vs quality mode I started a thread recently. While there were great answers and help I'm still much interested in other peoples opinion on the topic, it can be found here:

http://forum.doom9.org/showthread.php?t=104548

[Sharktooth]

nsis 2.12 could be use by Sharktooth to make x264 package
got it.

I cannot see the Full Package anywhere - and it's still down.
coz thats no longer the latest version. get this: http://www.webalice.it/f.corriga/megui/megui_0.2.3.1024.7z
and the sources are here: http://www.webalice.it/f.corriga/megui/MeGUI-src.ChngdFls_0.2.3.1024.rar

[smok3]

I use always single pass quality mode. Regarding multipass vs quality mode I started a thread recently. While there were great answers and help I'm still much interested in other peoples opinion on the topic, it can be found here:

http://forum.doom9.org/showthread.php?t=104548
what command line exactly are you using for x264 quality mode?
how do you calculate the proper q amount (based on input resolution?)?

[stax76]

what command line exactly are you using for x264 quality mode?
how do you calculate the proper q amount (based on input resolution?)?


Nixo had requested it for XviD, I'm not using AVC. There is a reason why I should educate myself regarding x264 and want to do so pretty soon.

[smok3]

right, actually my 2nd question 'how do you calculate the proper q amount' does not make any sense (just figured that out few minutes after posting...)

[Inventive Software]

*Bump*

[berrinam]

Does this thread really need to be revived? For all those not yet aware, MeGUI now has a home on Sourceforge: http://sourceforge.net/projects/megui

Bugs should be posted on the MeGUI Bug-Report Thread (http://forum.doom9.org/showthread.php?t=105160) and feature requests should be posted on the MeGUI Feature Request Thread (http://forum.doom9.org/showthread.php?t=105162). As a result, there doesn't seem much need for this thread, does there?

[Morte66]

Does this thread really need to be revived? For all those not yet aware, MeGUI now has a home on Sourceforge: http://sourceforge.net/projects/megui

Bugs should be posted on the MeGUI Bug-Report Thread (http://forum.doom9.org/showthread.php?t=105160) and feature requests should be posted on the MeGUI Feature Request Thread (http://forum.doom9.org/showthread.php?t=105162). As a result, there doesn't seem much need for this thread, does there?

Some sort of "User" thread would be handy for people who use MeGUI without being part of the development team. Maybe a sticky. It should cover where to download it, how to install it, what else you need; and it would point to the bug/dev/request/x264 threads. That should keep things going until MeGUI settles down and gets a Guide and download link on the Doom9 static site.

It took me the best part of a day to find MeGUI and get it working for DVD backup, and I still ended up unknowingly using an old build. :)

[TNHitokiRi]

i wish i had enough patience to read through the 50 pages, im pretty sure that this problem has been addressed. in the first few pages, Rash had a problem with loading a AVS file.

http://img408.imageshack.us/my.php?image=untitled16px.png

thats the exact error i get. The AVS works fine in virtualdub(and mod), and in all video players. I use ffdshow (libavcodec) to get it to work in virtualdub.

I think the problem could be related to the fact that im on Windows x64 edition. Thanks

[lexor]

I don't want to start a new thread for this little question, so I'll add to this one.

Where is the menu bar? namely where is bitrate calculator? I can't find it in config dialog either. Where did it move?

this is what I see: http://img429.imageshack.us/img429/2584/meguimain8sv.jpg (latest Shartooth's build)

[Mutant_Fruit]

use MeGUI full.

[lexor]

Woah? But it was no problem before. Do I really need full megui for bitrate calc now?

/edit: oops, just noticed ST's explanation in bug report thread :) nvm

[berrinam]

Guys, why are you reporting bugs here? There is a dedicated Bug-Reporting thread for exactly that. Why come back here? The bug report thread even has a list of all known bugs on the first page, to avoid you having to wade through all the pages.

If you want to get help with your bugs, please report them in the right place.

[lexor]

If you want to get help with your bugs, please report them in the right place.
sorry, I didn't realise what I was having is a bug, I read in the other thread about options redesign, I thought calc moved somewhere and I couldn't find it.

[ggab]

(r394A) Updated MeGUI (ver 0.2.3.1030) and AVC2AVI GUI with .NET 2.0 binaries.
(r394) Updated Installer. Added MeGUI Context Sensitive help (patch by mutant_fruit).
what is the last version that can run with .net v1.1 (i don't have the new 2.0 one yet)?

r394?

if yes, is there any URL link to download it?

thanks :)

[Doom9]

r394?don't confuse x264 with MeGUI.. you can use an old MeGUI version with a new x264 build and vice versa.. obviously if x264 is newer than MeGUI then you may not have all x264 options available.. MeGUI needs to be updated to support new x264 options.

Just download the 2.0 runtime.. you can have both runtimes in parallel and there are no negative sideffects whatsoever (I have both at work, with two development environments, and I wouldn't recommend it if I weren't absolutely sure that it would have any negative effects.. I couldn't risk that with my machine at work).
We don't keep old builds around.. it's up to you to do that, or check out the source code by a specific data and do your own builds.. you are unlikely to find a dev willing to spend time to worry about oudated builds, and the 2.0 move has various advantages for us, nontheless the one that those who do not have the full blown Visual Studio IDE (which is not cheap), can still participate using the free of charge Visual Studio Express.

[max-holz]

I want understand one thing, why 0.2.3.2024 modifies Sharktooth profiles and reset all the application path?
I think that since this project had became public with cvs there has been a big confusion.

[Doom9]

why 0.2.3.2024 modifies Sharktooth profilesHuh? There have been no changes in Profile, VideoProfile or VideoCodecSettings and those are the objects that have something to do with profiles. But MeGUI always have and always will write all profiles to your HD when you exit.. so these files are updated each time you exit megui. But as I said, it has always been like that ever since MeGUI got profiles.

and reset all the application path?It doesn't. But the refactoring changes the format of the settings file so it has to be recreated.. since your settings file can no longer be opened (This is no different than you having to redo dgindex projects every now and then), it means you lose your configuration. It takes you about 1 minute to redo that so I don't see the problem.
Somewhere in between my two latest releases (prior to the 2024) jobs became incompatible with old ones.. I heard nobody complaining..

[max-holz]

It doesn't. But the refactoring changes the format of the settings file so it has to be recreated.. since your settings file can no longer be opened (This is no different than you having to redo dgindex projects every now and then), it means you lose your configuration. It takes you about 1 minute to redo that so I don't see the problem.
Somewhere in between my two latest releases (prior to the 2024) jobs became incompatible with old ones.. I heard nobody complaining..

Why that? Why I must recreate all the general settings every time I reopen the application, what's the meaning of that? In every application I set my general settings and then they are saved till I decided to change them.

[Doom9]

Why I must recreate all the general settings every time I reopen the applicationYou don't.. but refactoring means making changes to existing code.. for instance the settings object.. so old ones cannot be opened. This has happened once in I don't know how many builds.. it's been months upon months with no change. I think it's rather rude to whine when you get a free software, constant improvements and all that free of charge. In other projects, like DGIndex for instance, compatibility is broken a lot more frequently. There are just two ways to make necessary changes: 1) bending over backwards to keep the whiners happy, or 2) make your improvements properly without regard for compatibility, and that every now and then breaks something. As another example, it is not uncommong for VfW codecs to require a "load defaults" when you install a new build.

[The Link]

Why that? Why I must recreate all the general settings every time I reopen the application, what's the meaning of that? In every application I set my general settings and then they are saved till I decided to change them.
??? I just had to go thru the settings for one time after the upgrade. The settings were saved and are available every time I restart MeGUI.

[max-holz]

Ok Doom9

[ggab]

thks doom9 for the tips :)

[Hyper Shinchan]

I haven't really understood if .net 2.0 works on XP SP1 (why are you using it? Well, I can't update it, that's all, for various reasons).
It seems to work, but it shows badly the frame speed. It says something like 1000 fps, when it's 10.00 fps. But it seems to be the only problem, I hope (but maybe I'll start using command-line, also if I need to make huge batch).

[Doom9]

It says something like 1000 fps, when it's 10.00 fps.using an old release? That was fixed in 2024.

I haven't really understood if .net 2.0 works on XP SP1Yes it does.. it works even on old and crappy systems. And using XP without SP2 is like having sex with a prostitute and not using a condom.. very risky. And there's no reason why you couldn't install the 2.0 runtime.. it works side by side with the 1.1 runtime.. unlike java where you have to tell an app which runtime to use, it's all done automatically in .NET.. any .NET program will look for the version it was compiled again.. it will run in newer versions as well, but it'll pick the closest match.. all your .NET 1.1 programs will keep on using the old runtime, so they will work exactly as before.

And I do hate repeating myself.. I've been pointing out all the .NET 2.0 facts before. I have a dual installation at work.. and there's no way I can risk breaking anything there.. a lot depends on me being able to maintain code made for the old runtime.