MeGUI development

[berrinam]

0.2.4.1029
Commit by berrinam:
- Fixed 1621767: Made OneClick suggest an output filename again
- Fixed 1646330: Made OneClick show the correct output filename filter

[berrinam]

0.2.4.1030
Commit by berrinam:
- Fixed 1599119 (updater does not respect user-selected paths)
- Fixed 1646706 (crash with autoencode and audio)

[berrinam]

Note: this question is really meant for the devs, so I don't want people clamouring here with feature requests -- use the SF tracker for that.

What do you think of aiming for a MeGUI 1.0 sometime soon, so people can actually have a tool they can trust? I want to put a video cutter in, and perhaps we want a compressibility check. Any other features for before 1.0? What do you think?

[Sharktooth]

maybe adding some controls for trimming (multiple trims) and cutting videos and eventually locale support for swapped decimal and thousands separators (that's causing mayem for non US ppl).
also, if you have enough free time (otherwise i'll do it when i finished moving into my new home), it wouldnt be bad to add a dropdown list to the autoupdater to select which update server you want to manually check and update from. also if autoupdate finds multiple updates but Core or Libs or other core components are in it should automatically check only the core and libs and the core components and gray out all the other updates. so after the restart the autoupdate can automatically select the other updates as well.
another thing to do is remove undot() and use RemoveGrain(mode=1) or RemoveGrain(mode=2) for minimal noise (removegrain should be included in autoupdate), add Lanczos4Resize, GaussResize (with sharpness control) and Spline16/Spline36Resize or just some of them...
A checkbox for using AviSource instead of DirectShowSource for .avi files (or just a messagebox in case the input file is an avi? - useful to fix delay issues with avi files as input).
Add the deadzones settings to the x264 config.

[berrinam]

maybe adding some controls for trimming (multiple trims) and cutting videosI'm doing this now (unless I misunderstand you)
and eventually locale support for swapped decimal and thousands separators (that's causing mayem for non US ppl).Where is this a problem? Interfacing with AviSynth requires a decimal *point*... are there any bug reports about this? EDIT: AAh, I see: the bug report thread.

also, if you have enough free time (otherwise i'll do it when i finished moving into my new home), it wouldnt be bad to add a dropdown list to the autoupdater to select which update server you want to manually check and update from.Why? Isn't it better to randomly check a server, so that the load is shared?

also if autoupdate finds multiple updates but Core or Libs or other core components are in it should automatically check only the core and libs and the core components and gray out all the other updates. so after the restart the autoupdate can automatically select the other updates as well.Yep

another thing to do is remove undot() and use RemoveGrain(mode=1) or RemoveGrain(mode=2) for minimal noise (removegrain should be included in autoupdate), add Lanczos4Resize, GaussResize (with sharpness control) and Spline16/Spline36Resize or just some of them...All pretty easy. Except for a sharpness control on GaussResize... I'll think about that.

A checkbox for using AviSource instead of DirectShowSource for .avi files (or just a messagebox in case the input file is an avi? - useful to fix delay issues with avi files as input).Alternatively, I could try opening the file first with AviSource, and use DirectShowSource only if that fails.

Add the deadzones settings to the x264 config.I haven't heard about these. What are they?

[Sharktooth]

GaussResize is not mandatory. It could be taken out. For the decimal point there were and are a lot of bugreports. 29.976 becomes 29970.xxxx (same for 23.976) and then i let you imagine what happens...
deadzones settings are: --deadzone-intra and --deadzone-inter. they control the deadzones in x264 and can be usefull to retain fine details at high bitrates (such as grain, noise, ultra-detailed textures like in video games, etc...).
About the avisource i think it's better to have a choice, coz sometimes there are problems with it (and DSSource fixes them) as well as DDShource could cause problems that get fixed with Avisource. So there is no preferred method... it's all a matter of how was muxed the source and what kind of streams were put in the container...
Also i proposed the listbox for the autoupdate servers coz now that you can define your custom servers we can use 1 for "stable" releases and another for the "testing" releases so we can mantain a stable set of binaries and packages for the masses as well as a "bleeding edge/testing" version AND custom update servers...

[berrinam]

Also i proposed the listbox for the autoupdate servers coz now that you can define your custom servers we can use 1 for "stable" releases and another for the "testing" releases so we can mantain a stable set of binaries and packages for the masses as well as a "bleeding edge/testing" version AND custom update servers...How about not providing this option in the autoupdate window, but instead providing separate server lists, eg a server list for stable, one for bleeding edge, etc?

[berrinam]

0.2.4.1031
Commit by berrinam:
- Add an AviSynth cutter (allows audio and video cutting)
This comes in two parts:
a tool in the tools menu called AVS cutter, which opens an avs file and allows you to select sections to keep
A file bar in the audio encoding part of the main form which allows you to select a MeGUI-generated cut file, and audio you encode will then be cut according to that file

So, if you have a source that you want to cut (say, remove the ads) then you generate the avs however, open it with the AVS cutter, save the cuts to the AVS and to a cut file, then load that cut file in the main form, to encode your audio.

This doesn't (yet) support cutting of unprocessed audio (if you like to keep your original audio tracks). The issue is that this needs external tools, so more work needs to be done for that. If people know some tools that I can use, please tell me (I'm thinking about BeSplit)

Enjoy!

[berrinam]

0.2.4.1032
Commit by berrinam:
- Fixed 1647454 (crash with German FPS in AVS window)

0.2.4.1033
Commit by berrinam:
- Fixed 1647524 ("optional output extensions" are not saving at next sessions)
- Fixed 1647520 ("advanced tooltip" not working)

[berrinam]

I need a suitable AVI muxer. I was loking back through this thread and we abandoned mencoder because it was faulty. DivXmux only works with DivX files. AviMuxGUI doesn't interface with the commandline well (errors are shown in messagebox form).

This leaves ffmpeg and virtualdub. I'm thinking about trying ffmpeg -- does anyone have any experience with that? Does it have any glaring problems to be aware of?

[buzzqw]

pardon me berrinam ... but avimux don't prompt error message if input file are correct and muxing file is correct too.

The only problem i am aware is from xvid with not "fixed" framerate, or not well rounded... like 25.002 or 29.986...

this is a muxing file for avi+ac3

CLEAR
LOAD c:\movie.avi
LOAD C:\audio.ac3
SELECT FILE 1
ADD VIDEOSOURCE
SET INPUT OPTIONS
SET OPTION MP3 VERIFY CBR NEVER
SET OPTION MP3 VERIFY RESDLG OFF
SET OUTPUT OPTIONS
WITH SET OPTION
OPENDML 0
RECLISTS 0
AUDIO INTERLEAVE 3 FR
AVI ADDJUNKBEFOREHEADERS 0
PRELOAD 200
WITH AUDIO
NAME 1 english
END WITH
OVERWRITEDLG 0
CLOSEAPP 1
DONEDLG 0
ALL AUDIO 1
LEGACY 0
RECLISTS 1
NUMBERING OFF
MAXFILESIZE OFF
END WITH
START C:\_aaa_full.avi

other examples could be generated by automkv

BHH

[berrinam]

But think about what would happen if there was an error. AviMuxGUI would hang forever, and the rest of the queue wouldn't complete until a user comes along and finds the error. The rest of MeGUI is built so that you can continue with independent jobs after an error...

I suppose that AviMuxGUI is really the best avi muxer, so maybe it's just worth using it, and if there's an error, hope the user isn't too bothered.

[buzzqw]

yes, i know and understud :( but there isn't an easy solution.
(but megui should not build or give to avimux bugged files...)

since megui has in its arsenal even mencoder, this could be used for muxing. Mencoder is a good muxer and allow a very wide range of input files :)

BHH

[berrinam]

We used mencoder before and it seemed to have problems with ac3. I tried out ffmpeg today and it seemed to also have problems with ac3 (it claimed to support it, but when muxing ac3 with a video track, the video was sped up ridiculously)...

[buzzqw]

i am not used to ffmpeg but have you try to pass the -r switch (the framerate)?

BHH

[check]

Why allow ac3 in avi? It's rather unusual, and case of fitting a square peg in a round hole, a la h264-in-avi. I can see no discernible benefit to allowing it, and on this note I'm a fan of removing the avc2avi frontend too.

[Sharktooth]

oh, something i forgot... there are major problems with Vista and Win2k. I dont know how to test coz i havent those OSes.

[buzzqw]

ac3 in avi is perfectly legal and widely used. I think MeGui should allow this muxing.

Almost all SAP support this format.

BUT h264-in-avi is another story and imho cannot be permitted at all.

just my 0.02€

BHH

[berrinam]

0.2.4.1034
Commit by berrinam:
- Added support for --deadzone in x264

[shon3i]

why when i select trellis, deadzone is off?

EDIT: I founded answer http://forum.doom9.org/showthread.php?p=883255#post883255

[Sharktooth]

Uhm, while you're at it can you also change the x264 quantizer/crf from int to float (1 decimal)?

[check]

shoni, trellis & deadzone are mutually exclusive.

aside to devs: tooltips to this effect could be useful.

[moadib2k]

MeGui has problems under vista x64, the problem I am having is the AviSynth Attempted to read or write protected memory.

I downloaded the source and here is where I am at. I set everything to compile for x86 (sometimes this is the problem). I stepped through the AviSynth wrapper and everything was working fine.

There is a loop in MediaFileFactory.cs Line 23
foreach (IMediaFileFactory factory in mainForm.PackageSystem.MediaFileTypes.Values)

It does not break until it gets to: IMediaFileFactory type MeGUI.MediaInfoFileFactory

It crashes in MediaInfoFile.cs line 127:
MediaInfo info = new MediaInfo(file);

I have downloaded the media info library and tried to compile it but I have to figure out where the wx/wxprec.h is coming from.

Its a library thats referenced from the mediainfolib source thats not included. I know of wxWidgets but it does not make much sense that he included it in a non-ui chunk of code.

I ran out time for now but if I find anything I'll let you know.

[berrinam]

@moadib2k: Thanks for looking into this. I'm sure you understand that we can't find the MeGUI problem with Vista since we don't have it, so I appreciate your attempts to isolate the bug. If you can suggest anything to change in MeGUI to fix the bug, if you upload a patch, I will be happy to commit it to the SVN.

[berrinam]

0.2.4.1035
Commit by berrinam:
- Added support for non-integer crf in x264

Should x264 also support non-integer qp? Because the r620 doesn't.

[devaster]

can you make the program paths in settings dialog relative ???
f.e. : \utils\mencoder.exe ?

(megui would be more portable(on USB disks...))

[berrinam]

I could do that, but I think it might require some internal reworkings, so I'm not keen to do that yet (anyway, AviSynth+DGIndex are the main blockers with portability, I think). Could you post this request on SourceForge please, so it can be kept for later?



NOTE TO EVERYONE: This thread is not for feature requests

[berrinam]

0.2.4.1036
Commit by berrinam:
- Fixed 1650271 (Queue analysis pass does nothing)

[devaster]

I could do that, but I think it might require some internal reworkings, so I'm not keen to do that yet (anyway, AviSynth+DGIndex are the main blockers with portability, I think). Could you post this request on SourceForge please, so it can be kept for later?

avisynth and filters is in most cases placed in his default dir in program files ....
anyway , may be there be a switch for absolute or relative paths ...

request posted ...

[TwoToad]

I don't suppose Spline36Resize could be added to the list of meGUI's resizers? Thanks for the great work on this program!

Edit: WOOT! I feel like I've contributed to meGUI now!! Thanks berrinam (down several posts in the changlog) and to check for making me look at the small print in berr's sig. The resizers were added =)

[check]

@twotoad, please read the post 3 up. Then read berrinam's signature. Then think! :devil:

[moadib2k]

Do you compile mediainfo.dll in your build or do you just include the win32 build from souceforge? I have a suspicion that this is going to end up being an invalid malloc call or something similar so it might actually require a change to mediainfo.

[Sharktooth]

0.2.4.1035
Commit by berrinam:
- Added support for non-integer crf in x264

Should x264 also support non-integer qp? Because the r620 doesn't.
uhm... dunno. but i think it's not planned

[berrinam]

MeGUI uses a precompiled build of MediaInfo. I suspect it comes from the sourceforge build, but I can't remember for sure.

[moadib2k]

Well, the version of mediainfo you are shipping is 0.7.2.1, the latest release is 0.7.4.3. Thats not the problem though, I recompiled mediainfowrapper.dll using 0.7.4.3 and it did not solve the problem with vista x64. I have narrowed it down to being a mediainfo problem, it is definitely not a MeGUI problem.

I have posted some questions to the developer of mediainfo. It uses a ton of other libraries so the problem could be just about anywhere in there.

If I get any resolution I will let you know.

[Zerofool]

0.2.4.1035
Commit by berrinam:
- Added support for non-integer crf in x264

Should x264 also support non-integer qp? Because the r620 doesn't.

Finally!!
It's supported since r591 (http://trac.videolan.org/x264/changeset/591). But it doesn't work because MeGUI is doing it wrong. It sends xx,x in the command line and it should be xx.x ;).

0.2.4.1034
Commit by berrinam:
- Added support for --deadzone in x264Thanks for that too. Now MeGUI is completely perfect for my needs :D.

[Sharktooth]

the usual non-US problems when it comes to locales.

[berrinam]

0.2.4.1037
Commit by berrinam:
- Made PgDn/PgUp do a jump of 1000 frames; made >> jump 25 frames
- Add extra resizers for AviSynth
- Save jobs on creation
- Support 'install priority' for autoupdate -- allows very coarse dependencies to be expressed
- Fixed 1650887 (x264 doesn't understand --crf 18,0)
- Fixed 1651387 (reset button does not remove audio cut file reference)

[berrinam]

0.2.4.1038
Commit by berrinam:
- Support update server branching
- Fixed 1651704 (CQ- profiles create error "not valid value")
There are now two update server branches: 'stable' and 'development'. Currently they're identical, but the idea is that stable will be updated less frequently.

[foxyshadis]

Why not just email Alexander Noé and ask him if he knows of and can fix the command-line error popups? (Also any issues that can cause such prompts.) You won't find much better than avimuxgui for doing that.

[berrinam]

I have already spoken with him, and he doesn't really want to send the errors to stdout (since stuff is already written there). I don't know what's wrong with stderr, though...

I was going to modify AMG myself and send him a patch, but I can't get it to compile on VS2005.

[berrinam]

About MeGUI 1.0 again:

I plan to add support for AviMuxGUI, and perhaps update MeGUI to support TIVTC 1.0, and then I think it should be ready for a 1.0 release candidate. Anything else needed beforehand?

[Sharktooth]

uhm, comp.test (in tools & oneclick encoder) is the only thing that was left on my list.
network encoding will be after 1.0 since it requires huge changes.

EDIT: i noticed the commandline in the codec config is only visible for x264. xvid, snow and lmp4 commandlines are not visible.

[moadib2k]

Hello all - some good news. I have worked with the gentleman from MediaInfo. After some work it looks like I have a version of the MediaInfoWrapper dll that works on vista x64. Its an x86 compile so it will also work on vista x86.

You will need the latest version of MediaInfo and I need to get the wrapper to the right person.

[berrinam]

Great! Thanks for that.

Can you upload the wrapper to rapidshare or some other filehost please? I'll put it on MeGUI's autoupdate then.

[moadib2k]

Can you upload the wrapper to rapidshare or some other filehost please? I'll put it on MeGUI's autoupdate then.

I uploaded it here (http://www.thebensons.org/MediaInfoWrapper.rar)

It has the wrapper and latest version of mediainfo.dll. I set the version for the wrapper to match the version of mediainfo.dll.

I will pull this down in 24 hours or so.

[berrinam]

I've put it on the server. A big thanks goes to you and the MediaInfo people.

[moadib2k]

Any interest in adding wmv encoding to MeGui?

[MaxPlanck]

thanks in advance for the vista fix, will be testing it tonight :)


Works beautifully guys...thanks.

[Sharktooth]

thanks goes to berrinam, moadib2k and the MediaInfo ppl.
did anyone made some tests to see if it fixes the problems in win2k as well?

@moadib2k: adding WMV encoding to megui shouldnt be so hard but it will require some time and tests. i think it can be taken into consideration after 1.0 release.