MeGUI - mencoder x264/snow/mpeg4/XviD GUI with AAC encoding and MP4 output

[Doom9]

yippie.. now I really need that volunteer to expose xvid zones in mencoder so that I can get rid of the merging altogether. And I guess now would be the time to go over the x264 support again as the first mencoder build supporting the new ABR has shown up on CD's site.

@JoeBG: this is good news... gets rid of your additional merging step and intermediate files.. now the raw way for x264 is going to use less space and time ;) I might still support x264.exe though because of the mp4 overhead thing.. but it's not a priority feature (I really need to get the resolution suggestions done.. sending the selected audio tracks to the main gui is on halt until North101 sends me the finished GUI code).

[Mc Onyx]

I have a question about using MeGUI with CD's newest Mencoder builds, dated 05.24.05 and i was wondering will Mencoder use ABR for the 1st pass in H.264/AVC encoding, because MeGUI says that it is CBR, i know it's because, there was no ABR, when this version of MeGUI came out. And by the way i know this was asked before, but @Doom9, when will there be a new version and will it use zones for the credits?

Sorry about my english, i'm from CE :) !

[Doom9]

1) since specifying a bitrate in first pass means ABR, I think the CBR mode will effectively be ABR. The next version will reflect that (and I'll recheck to make sure I'm setting all the options right).

As far as zones go.. of course. It will be in the next version as well. In addition, I have created a patch for mencoder to allow the use of zones in xvid, so I will be able to get rid of separate credits encoding altogether (the two libavcodec codecs are not relying on separate credits encoding anymore).

[North2Polaris]

@Doom9,

It would be useful to have the following options in the "Size" box in the Automatic Encoding section:

1/3 DVD-R (1466 MB)
1/4 DVD-R (1100 MB)
1/5 DVD-R (880 MB)

More and more folks are getting DVD burners...

North

[JoeBG]

@Doom9,

It would be useful to have the following options in the "Size" box in the Automatic Encoding section:

1/3 DVD-R (1466 MB)
1/4 DVD-R (1100 MB)
1/5 DVD-R (880 MB)

More and more folks are getting DVD burners...

North

:goodpost: :) Would be helpful for me too :)

[Mc Onyx]

Is there a way to make MeGUI shutdown the computer, after completing the last job(like in VDub and VDubMod), i didn't find it anywhere. If that function doesn't exists, i'd like to add it to the wishlist, because mainly i do my encodings overnight(especially with AVC) and it would be very usefull, so that my computer doesn't stay turned on, when not doing anything! I use that in VDubMod all the time!

[Doom9]

Is there a way to make MeGUI shutdown the computerYou mean shutdown -s -f -t 0?

[JoeBG]

You mean shutdown -s -f -t 0?

Is this a DOS Command? When I add "-s -f -t" to the a MeGUI commandlinie manually it will shutdown the computer? Would be nice :)

[Doom9]

nah.. that's the process with arguments that I'd have to launch to shut down the computer. Personally with all the power saving mechanisms already in todays PCs I don't really see the need to shut down the PC (lifetime is no issue either.. modern PCs should be able to handle 24/7 operation during their normal lifetime). But I'll put it into the todo list.. but at the bottom. There's a lot more important things, like abr mode, x264 and xvid zone support (hopefully CD can provide a new mencoder compile soon.. my xvid zones patch was just comitted), restructuring the backend code to facilitate the new GUI, getting the new GUI running (I haven't had any contact with North101 in a while:(

[yaz]

Is this a DOS Command? When I add "-s -f -t" to the a MeGUI commandlinie manually it will shutdown the computer? Would be nice :)the command 'shutdown -s -f -t 0' means : shutdown immediatly, close running application(s) without warnings (& confirmation requests). afaik, it's winxp only

the bests
y

[xtknight]

Doom9:

After I load an AVISynth script for video input, the program abruptly exists without warning. so I did a little debugging myself and found out this line is causing a problem. Under the AVIReader constructor (New):

if (AVIFileGetStream(m_pAVIFile, out m_pVideoStream, ConvertFourCC("vids"), 0) != 0) {

I think AVIFileGetStream is failing, and crashing your program before it returns a value. Probably one of the parameters it's being fed has a bad value for some reason? Not sure if there's much you can do about it. Maybe I FUBAR'd my Windows something awful? :confused: Or am I a complete moron and not using the software correctly? Quite possible...this is my first time trying it.

Here is the AVISynth script:

DirectShowSource("C:\Documents and Settings\unknown\My Documents\May 31-Channel 67 (3 23 pm).avi")

Yes, the file exists and plays fine in Windows Media Player.

I was just trying to input a normal file for encoding. I have MeGUI 0.1912 and AVISynth 2.5.6 Beta3 [050505].

Edit: Just for the record, when I open the AVS file in mplayer2, it crashes that program also. Time to reinstall AVISynth. Not your program's fault, never mind. Seems like every version of AVISynth I've had crashes in some manner. What's wrong with this program? I guess I'll install the version that crashed when the file is closed instead. OK AVISynth 2.5.5 is fully stable for me now.

[LigH]

I have MeGUI 0.1912 and AVISynth 2.5.6 Beta3 [050505].
...

OK AVISynth 2.5.5 is fully stable for me now.
Well - just another example: AviSynth 2.5.6 beta3 is known for so many problems, starting at shifted, distorted video -- and ending at application crashes. :rolleyes:

[Doom9]

this example is a good one why you'll see many programs in this place where programmers explicitly discourage you from using untested versions. As long as new versions act the same way as old ones, it's not going to be a problem, but if something changes (and AviSynth is know to do just that.. there was a report a while back using DirectShowSource and the new AviSynth betas and the result was just the same), it's going to be very problematic. Hence my version recommendations. But even I am dependant on mencoder stdout output not changing or it'll break MeGUI just as well.

Though, why use DirectShowSource anyway? What is wrong with AviSource? In my past experience, DSS has always been a lot more problematic and I have encountered a bunch of crashes even with release versions.

I'm glad that you tried out playing the file in a mediaplayer... definitely the thing to do to narrow down problems :) I'll take one thing from this report though: I didn't write the AVI opening class, but it does throw exceptions that I am not catching. Normally that's not a problem and MeGUI will only crash if you open a script it cannot handle, but a more graceful exit couldn't hurt.

[xtknight]

OK...so you are saying you are not catching exceptions that you could? The code looked like it would... I think that is out of your control, and I'm sure Microsoft has lots of error-checking in media player, and even that hard-crashes. The function causes the program to exit and without returning a value, so it is out of your control, unfortunately. :( Well you could start another thread to call this function and set a variable bGracefulExit=true when it succesfully finishes. Then when the thread exits, just check if bGracefulExit=true, and if not, throw an exception. This will limit the ability of the function to crash the main thread. Instead, it will crash its own separate thread which won't hurt anything else.

Sorry for the super-newb question, but how do I use DGIndex to get the .wav file I need to input in MeGUI? I don't know much about this program...it outputs something.demuxed.m2v and I have no idea what that's supposed to be. I don't see any exported audio. Can someone tell me what this program does?! What exactly is being indexed? What's in the index? By the way Doom9, check the development forum where I answered your minimize window question.

You could make your program easier for n00bs like me if you could make DGIndex extract the audio for me. Or does it? lol :o

I guess when AVISynth says alpha they mean it. But couldn't they at least test the opening of an avs file? Alpha isn't supposed to mean completely untested, is it? They should at least test the vital function.

[Leo 69]

xtKnight

DGIndex -> Audio -> Output Method -> Decode to WAV

[xtknight]

xtKnight

DGIndex -> Audio -> Output Method -> Decode to WAV

I did that...how do I start the process and where is my wav file??

[Leo 69]

Open the .vob files with DGIndex in the order they appear on your hard drive,
then press "Save Project" . The project is saved as a .d2v file - this is the result of indexing of your vobs. And besides, the .wav file from the vobs you're indexing is also saved to the same directory as .d2v project.

[LigH]

The audio stream is demultiplexed or decoded, while the project file (*.d2v) is written [F4].

[berrinam]

DGIndex -> File -> Save Project [F4]

The wav file will be put in the same place as where you save the d2v file. Anyway, you don't need to input wav into MeGUI -- you can just select

DGIndex -> Audio -> Output Method -> Demux All tracks

and MeGUI should accept the ac3 or mp2/3/a file (although it doesn't accept dts)

[Doom9]

you really don't have to bother with running dgindex manually. Instead of opening an AviSynth script, open an .ifo file and the dgindex project creator will pop up and allow you to create a dgindex project, and demux the audio tracks you want. If you want audio decoding, feed the .ac3 or .mpa files you get from the dgindex project creator into the audio input and configure it (it'll give you AAC though.. why use WAV anyway? there's no need for WAV anywhere in MeGUI).

[lexor]

Though, why use DirectShowSource anyway? What is wrong with AviSource? In my past experience, DSS has always been a lot more problematic and I have encountered a bunch of crashes even with release versions.

for compatibility with out past mistakes :D

[Doom9]

Here is release 0.1913

new: x264: all x264 options available in mencoder are supported. This includes abr, me range, me type, vbv buffer size, vbv initial buffer size, vbv maximum bitrate, bitrate variance (rate_tol), p8x8, number of threads and zones
new: xvid: supports adaptive quantizer (requires a brand new mencoder build, it was just added to mencoder yesterday) and zones
new: should be more stable towards improper AviSynth scripts (catches native Win32 errors as well now whenever it opens an AviSynth script)
new: additional disc sizes have been added as requested

changed: x264 options that do not apply to a certain mode are not used for the commandline anymore
changed: x264 and xvid credits rely on zones in the codec rather than external files. This will resolve whatever problems might have ocurred in the past using separate files.

For now I have left most of the code dealing with separate credits in there (including the filemerger in the settings), so that if you have old jobs that you'd like to re-encode, you still can (you cannot load and modify them though). Once the GUI is restructured, all those bits of code and GUI options will be removed though.

[Doom9]

here is release 0.1914

new: supports the AVC High Profile 8x8 transform in x264 (you will need a bleeding edge mencoder build for that.. CelticDruid has not yet released such a build at the time I'm writing this)
new: automatic vertical resolution suggestion for the AviSynth script creator, based on the DAR set and the croping values

This latter feature will only work properly if the DAR is properly set (it's normally done automatically but there are a few cases where the MPEG-2 video stream does not have the proper DAR signalling, so you may want to make sure that your 16:9 video is properly recognized) and you've already set your cropping values. There is no "least error" mode that would limit the AR error at the expense of cropping some video lines away (volunteers to add that are welcome :)

[LigH]

Hee Doom9 - do you outrun yourself today, again?! :D

[guada 2]

Hello Doom9 :)

I have a problem with meGUI

I downloaded the software:
- MeGUI-0[1] .1914;
- dgmpgdec140b3;
- BeSweet_v1.5b29_Completo;
- dotnetfx version 2.0 bêta1;
- MP4Box;
- mplayer2005.06.04.P4

no problem of installation.

my report:

ASP /MP4 and XVID /MP4 :
These two modes works perfectly (encoding + multiplexing).

however, the mode x264 doesn't function.

where can come the problem? Thank you for advance.

NOTE: You will excuse me, I didn't follow the latest news.. ;)

[Doom9]

however, the mode x264 doesn't function. That doesn't tell me anything.. what do you get in the log for the video encoding jobs? Did you try the high profile option? your mencoder version doesn't support that (the changelog says so)

[guada 2]

Doom9,

" Did you try the high profile option? your mencoder version doesn't support that (the changelog says so)".
"hpo" don't work with the lastest mencoder, (for Me).

The normal test says this (AVC/x264/MP4): profil log


Desired size of this automated encoding series: 2146304 bytes
No audio encoding and no separate end credits encoding. Calculating desired video bitrate directly.
Setting video bitrate for the video jobs to 337 kbit/s
Next job job1-1 is a video job. mencoder commandline:
"C:\Documents and Settings\mario\Mes documents\dossier megui\mencoder.exe" "C:\Documents and Settings\mario\Mes documents\Xvidtest\avs\film.avs" -ovc x264 -o NUL: -passlogfile "mencoder-2pass.log" -x264encopts pass=1:bitrate=700:4x4mv:ratetol=2,0:scenecut=100:me=0
successfully set up video encoder and callbacks for job job1-1
----------------------------------------------------------------------------------------------------------

Log for job job1-1

File not found: 'frameno.avi'
Failed to open frameno.avi
The me option must be >= 1: 0

----------------------------------------------------------------------------------------------------------
job job1-1 has been processed. This job is linked to the next job: job1-2
Next job job1-2 is a video job. mencoder commandline:
"C:\Documents and Settings\mario\Mes documents\dossier megui\mencoder.exe" "C:\Documents and Settings\mario\Mes documents\Xvidtest\avs\film.avs" -ovc x264 -passlogfile "mencoder-2pass.log" -x264encopts pass=2:bitrate=337:4x4mv:ratetol=2,0:scenecut=100:me=0 -o "C:\Documents and Settings\mario\Mes documents\Xvidtest\Nouveau dossier\filmtestx264.264" -of rawvideo
successfully set up video encoder and callbacks for job job1-2
----------------------------------------------------------------------------------------------------------

Log for job job1-2

File not found: 'frameno.avi'
Failed to open frameno.avi
The me option must be >= 1: 0
Exception in compileFinalStats. Message: Could not find file "C:\Documents and Settings\mario\Mes documents\Xvidtest\Nouveau dossier\filmtestx264.264". stacktrace: at System.IO.__Error.WinIOError(Int32 errorCode, String str)
at System.IO.FileInfo.get_Length()
at MeGUI.VideoEncoder.compileFinalStats()
----------------------------------------------------------------------------------------------------------
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:\Documents and Settings\mario\Mes documents\dossier megui\MP4Box.exe" -add "C:\Documents and Settings\mario\Mes documents\Xvidtest\Nouveau dossier\filmtestx264.264" -fps 25 -new "C:\Documents and Settings\mario\Mes documents\Xvidtest\Nouveau dossier\filmtestx264.mp4"
successfully set up muxer and callbacks for job job1-3



Xvid/Xvid/MP4

Desired size of this automated encoding series: 2097152 bytes
Encoded audio file is present: C:\Documents and Settings\mario\Mes documents\video\demuxaudio\audiomp4.mp4 has a size of 311650 bytes.
adjusting desired size. New desired size = 1785502 bytes
No audio encoding and no separate end credits encoding. Calculating desired video bitrate directly.
Setting video bitrate for the video jobs to 285 kbit/s
Next job job2-1 is a video job. mencoder commandline:
"C:\Documents and Settings\mario\Mes documents\dossier megui\mencoder.exe" "C:\Documents and Settings\mario\Mes documents\Xvidtest\avs\film.avs" -ovc xvid -o NUL: -passlogfile "mencoder-2pass.log" -xvidencopts pass=1:bitrate=285:max_key_interval=250:max_bframes=0:vhq=4:chroma_me:max_iquant=4:max_pquant=13:max_bquant=14:trellis:kfthreshold=1:kfreduction=20
successfully set up video encoder and callbacks for job job2-1
----------------------------------------------------------------------------------------------------------

Log for job job2-1

File not found: 'frameno.avi'
Failed to open frameno.avi
xvid: bitrate setting is ignored during first pass

----------------------------------------------------------------------------------------------------------
job job2-1 has been processed. This job is linked to the next job: job2-2
Next job job2-2 is a video job. mencoder commandline:
"C:\Documents and Settings\mario\Mes documents\dossier megui\mencoder.exe" "C:\Documents and Settings\mario\Mes documents\Xvidtest\avs\film.avs" -ovc xvid -passlogfile "mencoder-2pass.log" -xvidencopts pass=2:bitrate=285:max_key_interval=250:max_bframes=0:vhq=4:chroma_me:max_iquant=4:max_pquant=13:max_bquant=14:trellis:kfthreshold=1:kfreduction=20 -o "C:\Documents and Settings\mario\Mes documents\Xvidtest\Nouveau dossier\film.m4v" -of rawvideo
successfully set up video encoder and callbacks for job job2-2
----------------------------------------------------------------------------------------------------------

Log for job job2-2

File not found: 'frameno.avi'
Failed to open frameno.avi
desired video bitrate of this job: 285 kbit/s - obtained video bitrate: 276,114668769716 kbit/s
----------------------------------------------------------------------------------------------------------
job job2-2 has been processed. This job is linked to the next job: job2-3
Next job job2-3 is a mux job. mp4box commandline:
"C:\Documents and Settings\mario\Mes documents\dossier megui\MP4Box.exe" -add "C:\Documents and Settings\mario\Mes documents\Xvidtest\Nouveau dossier\film.m4v" -add "C:\Documents and Settings\mario\Mes documents\video\demuxaudio\audiomp4.mp4" -fps 25 -new "C:\Documents and Settings\mario\Mes documents\Xvidtest\Nouveau dossier\film.mp4"
successfully set up muxer and callbacks for job job2-3
----------------------------------------------------------------------------------------------------------

Log for job job2-3

MPEG-4 Video import - 720 x 576 @ 25.0000 FPS
Indicated Profile: Simple Profile @ Level 3
Import results: 1269 VOPs (12 Is - 1257 Ps)
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
Converting to ISMA Audio-Video MP4 file...
Saving film.mp4: 0.500 secs Interleaving
MP4 muxing info:
Size of audio track 1: 311650 bytes
Size of audio track 2: 0 bytes
Size of raw video stream: 1750567 bytes
Size of final MP4 file: 2068032 bytes
Size of video in MP4 file: 1756382 bytes
Total overhead: 5815 bytes
Overhead per frame: 4,58596214511041 bytes

source information
codec: XviD
number of b-frames: 0
number of source frames: 1268
----------------------------------------------------------------------------------------------------------


I don't understand my problem.I tried everything :(
I don't like that, I prefer to use VD + x264 and MP4Box again..

[dinolib2]

The problem is in the first job:
The me option must be >= 1: 0

If you look at the cmd, you can see "me=0".
Now, you shold see it there's an option tha force this value to 0... otherwise could be a bug (are you using latest MeGUI version, didn't you?)

[Doom9]

The me option must be >= 1: 0bah.. yet another way to report errors, not even mentioning that it's an error.. I hope somebody will change that in the future.. errors should be signalled as such and megui will abort right away.

You shouldn't even be able to set me to 0, iirc I increase the selectedItem from the dropdown by one before saving.. but if you do not touch the motion estimation type then you shouldn't run into any problems as the default is 2 and in that case me is not written to the commandline.

[Mc Onyx]

About the shutdown function, i agree that in power savings it's not important, but if you happen to be as "lucky" :) as i am, to have computer in the same room, where you sleep, then it's a different thing. Although i have water cooling, it's far from noiseless, so... But other things like X264 and ABR are more important.

[guada 2]

Thank you very much Doom9 :)

[Doom9]

@guada: when using x264, go to the advanced tab, and set the me option to the 2nd option in the dropdown. I forgot to force this (it's the default), and since the default index of a dropdown is -1 and I add 1 you get 0. This is a bug that is already fixed in the next release but unfortunately the code is in the hotel and I am not.

x264.exe is also fully supported now, including direct mp4 output (joebg owes me many beers for that.. all the additional workarounds I had to put in everywhere because all the code is based for mencoder and thus raw output.. it's a major pain in the ass). And all the credits code I removed.. when thinking about what time I put into this I'd better have waited and coded something else until zones were ready...

[LigH]

when thinking about what time I put into this I'd better have waited and coded something else until zones were ready...
No, don't think about that too much!

:thanks: :thanks: :thanks:

http://www.cheesebuerger.de/images/more/schilder/a074.gif http://www.cheesebuerger.de/images/more/schilder/c014.gif

for so much work - and so much success!

[JoeBG]

[@x264.exe is also fully supported now, including direct mp4 output (joebg owes me many beers for that.. all the additional workarounds I had to put in everywhere because all the code is based for mencoder and thus raw output.. it's a major pain in the ass). ...
:thanks: You defenitly get as much beer from me as you can drink. :D
I will make a guide for your tool in german language and I hope you will like it :)


And all the credits code I removed.. when thinking about what time I put into this I'd better have waited and coded something else until zones were ready...

But we all loved it :thanks: :thanks: :thanks:

[Doom9]

You defenitly get as much beer from me as you can drink.better watch out because I can get thirsty ;)

Better wait with the guide.. I plan to implement North101's GUI suggestions this week-end.. on my own if he doesn't resurface until then.

I'm wondering about the cli editing feature.. the new GUI does not forsee an editable commandline (I figure I add some cli preview in the codec configuration screen but that's that). How important is that feature really? And if it were to be replaced by certain fields that you can use to put commands a) before the codec string, b) in the codec string, and c) after the codec string.. wouldn't that be just enough to handly pretty much anything? I tend to think that if somebody asks new cli features are quickly implemented, so cli editing only applies to non supported parameters (virtually none in case of x264, be it x264.exe or mencoder), and using additional mencoder options. That way of handling things would also make it possible to load a custom edited job, make changes and encode it afterwards. So you can make your custom edits at any point you like, the configure GUI options afterwards and your custom options are preserved (which isn't the case right now).

Then again, is all that work really useful? I mean you can always exit, open the xml file in notepad, edit your commandline, relaunch, and run the job and except for re-configuring the job you can do everything you can do with any non custom job (created solely in the GUI).

[dude051]

First off, just want to say how great it is to see this project grow so fast into something better and better. Your continued work is appreciated in the community :D

Now on to the biz, i've run into a wierd bug and can't seem to figure it out. I'm using a fresh copy of MeGUI, no previous configurations from old versions. After trying to load my AVS, I get the following error twice:

http://www.exiled-destiny.com/Error.JPG

Although I can play it in MPC and load in VirtualDub with no errors or problems at all. The MeGUI VideoPlayer then loads blank, and when i try to skim through it I get an exception and after hitting Quit it crashes. Error report is as follows:

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.VideoPlayer.positionSlider_Scroll(Object sender, EventArgs e)
at System.Windows.Forms.TrackBar.OnScroll(EventArgs e)
at System.Windows.Forms.TrackBar.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.1982.36860
Win32 Version: 1.0.1982.36860
CodeBase: file:///C:/Documents%20and%20Settings/Justin/My%20Documents/Ripping%20Appz/MeGUI-0.1914/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
----------------------------------------
lfmy3uic
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
----------------------------------------
nk_x48u2
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
----------------------------------------
ii63xkhq
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.

Hope I could help, untill next time :scared:

Peace, DuDe

[Doom9]

that's the additional error catching I've added to prevent MeGUI from crashing if an error ocurrs when opening the AVI. AVIFile reports it so there's really nothing I can do about it. Can I see the script please? Also, can you try a pre 0.1913 version which doesn't have this errorchecking, and see if you can open the script then?

The crashdump makes sense.. you're trying to read a frame from the video but since the video cannot be loaded, you're drawing just blanks. I guess I should not even let the player open if there's a problem opening the script.

[thed33p]

@dude051

I've seen that error before on my old man's Athlon. The script was MPEG2SOURCE=("file.d2v") and played just fine in WMP but MeGUI woud'nt open it (it was the last build to not support subtitles & chapters IIRC.) I never bothered getting to the bottom of it as the pc was being upgraded about a week later but now that I think back, the only thing that wasn't installed on it was a DVD playback package (like Win / Power DVD)

I dunno how relevant this post is but you never know.

later

[Doom9]

here is version 0.1915

new: supports x264.exe as alternative x264 encoder
new: supports x264 minimum gop size

changed: all references to merge jobs have been removed
changed: extension defaults to mp4 when using x264 for mp4 output (no separate muxing unless you are
in auto mode)

bugfix: the me type is set to the default in the GUI, preventing a mencoder abort if you didn't configure
the me type on your own
bugfix: invalid custom paths & working default path no longer causes a crash


important notes:
the format of the configuration file has changed, your old config may or may not work in this version
since merge jobs are no longer supported, make sure you clear the queue before using the new version
if using x264.exe for x264 encoding, setting the output type to .avi will create a raw AVC stream
with extension .avi. Before you start suggesting I add a workaround and start using avc2avi -
I spent a lot of time adding support for credits encoding only to have the work made superfluous
by vrc_override, and zones, so you rather look into x264 and avc2avi source code and add avi output
to x264.exe on your own.. then I'll support it.

[berrinam]

I searched and I looked through this thread, but I couldn't find anything about this: could you tell me why MeGUI (for x264) defaults to an SCD sensitivity of 100, when the default in the x264 CLI is 40? Also, why does MeGUI use ratetol 2.0?

Sorry if I missed it somewhere else in the forum, but I did try to find out.

[Doom9]

@berrinam: ratetol most likely because I accidentally clicked the up button in the GUI designer, and for the SCD I must've read the wrong line in the manpage.. obviously both are wrong.

[JoeBG]

@berrinam: ratetol most likely because I accidentally clicked the up button in the GUI designer, and for the SCD I must've read the wrong line in the manpage.. obviously both are wrong.

But I always use ratetol 2,0 as my preferred. But you´re right, the default is ratetol 1,0.

[guada 2]

Hello Doom9 :)

I think that there is a difference in size and in change concerning the news version.
look at this you see it:
MeGUI-0[1].1915 / MeGUI-0[1].1914 and MeGUI-0[1].1914 / MeGUI-0[1].1914

But MeGUI-0[1].1915 : 632ko / MeGUI-0[1].1914 : 640ko

just this :) :) :)
To soon ;)

[Doom9]

there's a perfectly simple explanation why the executable got smaller. A quote from the changelog explains it: changed: all references to merge jobs have been removedSeparate credits encoding required a lot of extra code. Since I have now eliminated that code, the executable got smaller.

[JoeBG]

Just finished some tests, everything works fine :)

[Sharktooth]

Doom9 can you post the sources please? ill see what i can do.

[Sharktooth]

well... lets start learning C# ....

[Sergejack]

change doesn't happen for cplxblur and qblur in megui.

EDI : oups, my bad, sorry ^^'

[Doom9]

change doesn't happen for cplxblur and qblur in megui.mode? mencoder or x264.exe?
I can't verify that in both modes.. the commandline changes.

[Sergejack]

It's missing pthreadGC2.dll.
I guess I'll look arround MPlayer website.

[Sharktooth]

try this one: http://www.webalice.it/f.corriga/misc/pthreadGC2.dll (MMX required)

@Doom9: make your big changes, i need some days of "study" :)

[Sergejack]

There are somes bugs with param sued for encoding.
There also is a bug when muxing into mp4, looks like (for instance) 23.976 fps is 23976 fps.

[LigH]

looks like (for instance) 23.976 fps is 23976 fps.
Just a guess without checking: Try if it uses local "decimal" values; e.g. in Germany, we use a decimal comma instead of a decimal point.

[Doom9]

thanks

Now, in the course of the GUI reorganization, there are two things that weren't properly designed yet:

a) commandline preview: where should that be placed in the future? Right now I have the configuration for each codec in a separate dialog, and once you've configured the codec, the resulting commandline will be shown. I think the commandline should go away from the main window.. so the question is should there be a preview in the codec configuration dialog? and should it always be there, or be activated upon demand?

b)commandline editing: how important is that feature? wouldn't editing xml files be sufficient?

c) I figure the average user will never bother to configure the logfile and just use the default. Hence it might make sense not to show it all the time. In a design study, North101 placed it in the input2 tab, but I want to get rid of that tab (it's empty except for the logfile). So where to best place this? I was thinking about the codec configuration dialog, which is how VfW codecs handle it.. but is that really how it should be?

[Doom9]

here is version 0.193 alpha:

This is the first preview of the GUI reorganization that is currently ongoing (it's not done yet).

new: codec configuration has been put into separate dialogs, thus making the main screen less cluttered
new: settings have been moved into a separate dialog
new: "standalone" mp4 muxer has been extended to support pretty much all the features you should need (there's no support for audio delays) and moved to a separate dialod
new: access to 4x4 I-frame options

changed: d2v and avs creator are now accessible via the menu

bugfix: mb option activation should fullfill the prerequisites (some options require other options to properly function)
bugfix: defaults of ratetol and scd have been restored

since it's an alpha, please consider it as such.. not everything will work. For instance, using x264.exe in auto mode will cause problems at the muxing stage, because there's no differentiation between the video-only output and the final output (that's due in a next version where automatic encoding will be moved to a separate dialog).

commandline editing and updating is currently also not in its final form.. same goes for the default audio track selection in the settings, audio track assignments in the muxer and probably a lot more.

[berrinam]

Is it just me, or is the version you posted v0.1914?

[LigH]

At first I thought we had a newer version already; then I realised:

0.1915 < 0.193 ;)

[JoeBG]

@ doom9

Version 0.139a really rocks :)

[dinolib2]

here my 1 cent: in avisynth script creator, checking and then unchecking Denterlacer check box raise a run-time error...
************** Exception Text **************
System.NullReferenceException: Object reference not set to an instance of an object.
at MeGUI.AviSynthWindow.setIVTC(Boolean enable)
(...)

[Doom9]

@dinolib2: it's going to be a while until I can even look at that.. right now I have a couple 100 errors compiling... the GUI restructuring is done, but I might change a couple more things (move logfile to codec config dialog.. full zone support for all codecs with a visual zone setter, etc). All that influences the new classes I'm currently working on.

However, all the parts I mentioned earlier today can be safely edited if somebody wants to help out. And another thing comes to mind.. a chapter creator (North101 posted a design study a bit earlier in this thread).. make it a separate dialog that interacts with an avisynth preview window.

[Maximus_G]

When i'm trying to use the checkbox
"I8x8 High Profile",
i get mencoder error
"Option x264encopts: Unknown suboption i8x8mv".
Also, it the mencoder-mode, it's impossible to use 2 or more threads.
And when in x264.exe-mode - everything works fine, i.e. I8x8High, 2 and more threads. But this mode is unusable since MeGUI doesn't see, for example, that x264.exe has finished 1-st pass and it's the time to start 2-nd pass.

What should i do in order to use mencoder with I8x8High and multiple threads?
Or make x264.exe-mode usable?

[celtic_druid]

It should be just i8x8. As for threads. Perhaps you use a build that doesn't have threads enabled?

[Maximus_G]

It should be just i8x8.
So MeGUI passes to mencoder an incorrect parameter?

"C:\temp\mp4\050614\mplayer2005.06.09.P3\mencoder.exe" "C:\temp\mp4\test\!test.avs" -ovc x264 -x264encopts bitrate=700:4x4mv:i8x8mv:me=1:threads=2 -o "C:\temp\mp4\test\b.264" -of rawvideo

As for threads thing - i'm using:

* mplayer2005.06.09.P3
* pthreadGC2.dll (mencoder won't work without it)
* X264CLI_rev261_mmx
* MeGUI-0.1915.

It starts encoding well, mencoder.exe uses about 90% of dual-CPU time, then at about 800-900 frames encoded, MeGUI.exe utilises ~100% CPU time, and the process stops.

Maybe i'm using not fully compatible builds of software?
For example, is there's a difference between "x264.revision260" and "X264CLI_rev260_mmx", and if so - what would be better with the mencoder+MeGUI?

[celtic_druid]

x246 threads were enabled for that build. Why do you want 2 threads on a P3 anyway?

[Maximus_G]

x246 threads were enabled for that build. Why do you want 2 threads on a P3 anyway?
As a readme nowhere seen, I was thinking a "P3" build means no special optimisations, though it still uses sse2 on a P4, and multithreading on a multi-CPU server platforms.

After trying "mplayer2005.06.09.P4" i see this build really working with multithreading, thank you.

So, just one question left:
Does MeGUI really use the wrong parameter "i8x8mv" which really should be "i8x8"?

[yokem55]

Also any idea why mencoder doesn't recognize SSE/SSE2 in my Athlon64? Maybe you need a different operating system :sly: . Under 64-bit Gentoo:
$ mencoder
MEncoder dev-CVS-050606-21:29-3.4.4 (C) 2000-2005 MPlayer Team
CPU: Advanced Micro Devices (Family: 8, Stepping: 0)
Detected cache-line size is 64 bytes
CPUflags: Type: 8 MMX: 1 MMX2: 1 3DNow: 1 3DNow2: 1 SSE: 1 SSE2: 1
Compiled for x86 CPU with extensions: MMX MMX2 3DNow 3DNowEx SSE SSE2

85 audio & 199 video codecs
File not found: 'frameno.avi'
Failed to open frameno.avi
No file given

Exiting... (error parsing cmdline)
Granted, encoding under Linux can be a ROYAL PITA (64-bit even more so at times) there are certain fringe benefits.

[dude051]

On my earlier problem, it was just a borked AVI Decompressor... thanx tho :o

One small thing , since version 1913 I have not been able to set the quantizer for 2pass 1stpass using AVC encoding. The setting is avaliable in 3pass 1stpass though. Any reason to this, or is this just a GUI error?

Also, i encountered an error when setting the jobs list. I set some encodes, 2 passes each queued for two episodes totalling 6 queues. I then deleted the first 4 jobs so the new numbers in the job list starting at 5 and 6. I then closed MeGUI to restart the computer, and reopend MeGUI and made new queues in the job list... their numbers starting at 1 and 2. Now lies the error, when i started the encoding of the job list, MeGUI sets not only the job its working on (which was job 5 from the old list) but jobs 1 and 2 to "processing". This then caused MeGUI to skip jobs 1 and 2 and go on to jobs 3+. If I didnt explain that well... heres what I mean in a more graphical-MeGUI way:

job5(existing job from previous list, processed and finished)
job6(existing job from previous list, processed and finished)
job1(set to "processing" and not finished when list was started)
job2(set to "processing" and not finished when list was started)
job3(processed and finished)
job4(processed and finished)
job7(processed and finished)
job8(processed and finished)

This seems an internal error in the GUI, but I'll ask for an option to maybe reset the status of existing job queues, much like in VDub. Also where I can set jobs to pause so they aren't processed, ect. Maybe some future features.

[Maximus_G]

Does MeGUI really use the wrong parameter "i8x8mv" which really should be "i8x8"?
Yes it does.. sorry about that. So before encoding, close MeGUI, open the xml files in question and edit the commandline, save them, restart MeGUI and start the jobs in the queue.
OK, that didn't work in automated mode. I guess MeGUI changes all the command-line values again, after recalculating target bitrate, for example.
And it can be seen in the attached log-file. After manual editing and program restart, job 1-2 goes well. When it's time for the 2-nd pass, that "i8x8mv" shows up again.
So, i'm looking forward to a new MeGUI build :)

BTW, is that normal statistics?
"x264 [info]: ... I8x8:0.0% ..."

[Doom9]

One small thing , since version 1913 I have not been able to set the quantizer for 2pass 1stpass using AVC encoding. The setting is avaliable in 3pass 1stpass though. Any reason to this, or is this just a GUI error?Since first pass is now ABR, you shouldn't be able to specify a quantizer anymore. Apparently I forgot to change that for 3 pass mode.

This seems an internal error in the GUI, but I'll ask for an option to maybe reset the status of existing job queues, much like in VDub. Also where I can set jobs to pause so they aren't processed, ect. Maybe some future features.You can do that.. double click on a job.. a double click sets an errored/aborted job back to waiting, and a waiting job to postponed (meaning it won't be processed if you start the queue).

However, I'm not sure I get your scenario right. Could you elaborate the exact process without leaving any details out (basically I'm asking you to redo all the steps and explain in great detail what you did.. this also serves to make sure we're not dealing with a glitch and I need to redo this at home.. I'm afraid since I cannot follow your description at this point I'm unable to reproduce the behavior)).. and use as little jobs as possible (makes my life reproducing a lot easier).

But I'll try to put what you wrote in my own words.. you tell me if it's correct.
You set up job1: 2 pass 1st pass, job2: 2 pass 2nd pass, job3: 2 pass first pass, job 4: 2 pass second pass, job5: 2 pass first pass, job6: 2 pass second pass.

(why not use automated 2 pass by the way?)

Then you delete jobs 1-4 and exit.

When you restart, you have 2 jobs in the queue: job5 and job6 (in that order). You then add another 2 pass first pass (job1), and a 2 pass second pass (job2), another 2 pass first pass (job3), another 2 pass second pass (job4), another 2pass 1st pass (job7) and another 2 pass 2nd pass (job8).

Then you go to the queue tab and hit Start.

Job5 & 6 are encoded properly. Job1 is started (do you get a progress window?, does it disappear again? what is entered into the log?), then Job2 is started (same set of questions), then Job3 is started and encoded, and so on. Or, were job1&2 immediately set to processing when you pressed start?

Can you reproduce this behavior using a smaller number of jobs (like add two, delete the first, exit, start again, add a new job, start encoding and see if both get encoded.. or if not, at which point the second one (in the queue, it'll be named job-1) is set to status processing. Also, does the progress window disappear? What status is the GUI in? Is the first button in the queue labelled start or stop? Can you add another job and encode it successfully after a job was incorrectly marked as processing?

[Doom9]

@Maximus_G: still waiting for an answer...

btw, there's another mencoder parameter bug when using x264.. i4x4.. I used i4x4mv. Both are fixed in the upcoming new version (due Saturday). The AviSynth script creator problem dinolib2 has reported is also fixed as well as some other not really nice things in that part of the program.

Naturally, the next version will support all new developments made in x264 (it already does, I'm creating clips with RDO like crazy), and it'll be much more userfriendly than before.

[JoeBG]

@Maximus_G: still waiting for an answer...
Naturally, the next version will support all new developments made in x264 (it already does, I'm creating clips with RDO like crazy), and it'll be much more userfriendly than before.

Can´t wait to test RDO :)

[JoeBG]

Can´t wait to test RDO :)

Testet it with cli version for 2 clips - I think it´s very useful :)

@ doom9

Please tell me when the gui is optikal ready. Than I can begin with the manual. MeGui really is the best freeware solution of mp4 and in the moment it kicks ass to every payware :)

[Doom9]

Please tell me when the gui is optikal ready.I'm working really hard on it. Right now I'm testing auto-mode, then I have to make sure that adding additional streams and assigning languages in auto mode works (it works when muxing separately). After that it should be ready.

BTW, you can already use the lossless mode (always could), since MeGUI doesn't restrict the number range you can put into the quantizer field.

[Doom9]

Alright, the next version is out. I've opened a new thread because this one is way too long.

Go here for any further discussion: http://forum.doom9.org/showthread.php?p=674495#post674495