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