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.

[berrinam]

I agree with Sharktooth.

[JarrettH]

What was the libs update? :sly:

[Sharktooth]

mediainfolib update.

[moadib2k]

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

Wow, I actually expected to hear a no :) since MeGui is really a x264 tool.

I am starting to write an encoder for wmv using some of the concepts from encode360 and some of the code from MeGui (namely the mediainfo wrapper and the avsynth wrapper). This is so I can write an x64 version.

What is your time-frame for 1.0?

[Sharktooth]

uhm... there isnt any precise date but the actual megui is close to what 1.0 should be.

[berrinam]

Well, we need to add a compressibility check, which I think could take a few weeks, as will supporting AviMuxGui.

Then, after that is RC1. Leave it one month for the bugs to surface, and release 1.0.

Mind you, during that one month, we can already start working on post-1.0 features.

[Sharktooth]

Seems some files were not commited to the SVN.
The referenced component 'MediaInfoWrapper' could not be found.

[berrinam]

I presume this is a error that occured when you ran it from visual studio?

You have to copy all the dlls from \trunk\ to \trunk\bin\debug, under the default VS settings.

[berrinam]

Sharktooth, are you working on MeGUI again, or do you still have very little time?

I think that the compressibility check is going to definitely be the largest thing before 1.0, and I'm unsure of how it is supposed to work (eg what script, and what adjustments do I make based on the results?). Do you want to implement the compressibility check?

[Sharktooth]

ill be back working full time on megui after 16th of feb.
i already have a prototype for the comp. check but no adjustments are made.
it only tells you the compression percentage in different colors (red from 0 to 45%, orange from 45 to 65% and green for results over 65%)
adjustments should be always a manual thing unless you want to create something that is aware of EVERY codecs option impact on compression and the same for EVERY possible avisynth filter...

[berrinam]

ill be back working full time on megui after 16th of feb.
i already have a prototype for the comp. check but no adjustments are made.
it only tells you the compression percentage in different colors (red from 0 to 45%, orange from 45 to 65% and green for results over 65%)Sounds good.

adjustments should be always a manual thing unless you want to create something that is aware of EVERY codecs option impact on compression and the same for EVERY possible avisynth filter...Not necessarily so. In particular, there are two things you could do:
Suppose that the bitrate of all codecs increases the same way as the resolution increases (I think that's a fair assumption). Then, find out how the resolution affects bitrate, and scale the resolution or bitrate accordingly, until your quality demands are satisfied.
Create a pluggable way to adjust codec settings, so that you can implement adjustments for individual codecs at a time (eg x264 first, then xvid, maybe never lavc or snow). You would do this by adding to the PluginManager another plugin type which had an interface like the following:
interface SettingsAdjuster
{
bool CanAdjustTheseSettings(VideoCodecSettings t);
VideoCodecSettings GetAdjustedSettings(double currentQualityPercent, double targetQualityPercent, VideoCodecSettings current);
}

This could allow for different behaviours of different codecs.

[moadib2k]

Zenitram introduced a bug in 0.7.4.4 of MediaInfo. In short, the dispaly aspect ratio string is wrong. If you use the numerical version your fine but if you use the "16/9" text there is a problem.

If you need a fix, I can pull the latest svn and compile a build for you. I don't know when he is going to release 0.7.4.5 but it should be soon.

For details see http://forum.doom9.org/showthread.php?t=96516&page=9

[JarrettH]

I had a couple good ideas for MeGUI in my dreams tonight. I only remember one of them :scared: :D

To save some time I think there should be a way to queue up the mux even if the audio or video file hasn't been created yet. You could point it to the directory where the files will appear...since the queue is obviously in an order by the time it gets to the mux the files will be there to join.

What do you think?:devil:

[berrinam]

Most of the time, autoencode should be satisfactory for that. When it isn't, there's nothing you can do for the moment, but a possibility for the future is MeGUI writing little placeholder files where it expects files to be.

[smuthy]

The avisynth cut functionality is great, however, there is a drawback with the current work flow;

Deinterlacing checks are made in the megui AVS script creator on the whole d2v file. This means that interlace behaviour in the adverts to be cut out will influence the interlace settings.

I've checked by running an interlace test with the adds in and edited out (using an mpeg2 editor) and got different results. Not sure how to fix this without possible some difficult changes to the work flow (putting avisynth cutter before avisymth creator?).

This can be got around by maunually inspecting the video and editing the avisynth file.

Not sure if this affects the crops - does the cropping refer to the frame visable in the preview?

Sorry for posting this in this form as its not really a bug or feature request.

[squid_80]

@Devs: Can you update the version of xvid_encraw on the auto-update servers to the current one available on my homepage (http://members.optusnet.com.au/squid_80)? aviwriter.dll will have to be pushed out with it too. The reason I'm asking specifically for it to be done is because the older versions use the avifile API for writing avi files, and vista's avifile library is BROKEN. Newer versions use aviwriter.dll (made from virtualdub's avi writing code) so they should be ok.

[Gilgamesh83]

Hiya! Noob here with some things to say :p

Concerning the muxer avc2avi in megui, the problem that most users face is that when using the FPS 23.976 it results in a 23.975 FPS on the file written this also applies to convertfps=23.976 in avisynth files. What i have figured out is that when using the FPS 23.9762 instead of 23.976 fixes the problem thus when using avc2avi_gui.exe with avc2avi and writing 23.9762 in the FPS field the correct FPS is the used for the file and this also applies to convertfps command in avisynth. Well the reason I'm saying this is because I would like to be able to convert in batch mode but since meguis interface doesn't allow for manual input of FPS and one has to choose 23.976 which results in the error mentioned above. Well was wondering if this could be fixed in later revisions and also this seems to affect the FPS 119.88 which should be 119.881.
Oh and also the 23.9762 comes from the stats files header wich when converting 23.976 sources uses the 250000/10427 division.

Well thx for listening to my noob comment and keep up the good work :)

[gino25]

any news about linux port? Thank you

[Sharktooth]

cant do much without an internet connection at home...

[jeffy]

cant do much without an internet connection at home...

You can rest which should be good for you... not that bad, eh? :D

[Sharktooth]

well, i planned to do some stuff but the damn ISP told me the service was available in my (new) area while it isnt...
so i shall wait about 40 days until they move their a$$...

[Sharktooth]

Found some time at work to commit a bugfix:
0.2.4.1039
Commint by Sharx1976:
- Fixed 1672842 (x264 lossless broken)
- Fixed MediaInfoWrapper reference in the megui project

[berrinam]

Sharktooth: what do you think of DSpider's icons at http://sourceforge.net/tracker/index.php?func=detail&aid=1656502&group_id=156112&atid=798479

??

[leinieman]

I know I'm way over my head in this forum but I thought someone here would know what this error is trying to tell me. Any help appreciated.

MeGUI encountered a fatal error and may not be able to proceed. Reason: The given key was not present in the dictionary. Source of exception: mscorlib stacktrace: at System.ThrowHelper.ThrowKeyNotFoundException()
at System.Collections. Generic. Diclionary ‘2.get_Item(TKey key)
at MeGUI.baseMuxWindow.convertLanguagesToISO()
at MeGUI.AdaptiveMuxWindow.getAdditionalStreams(SubStream[]& audio, SubStream[]& subtitles, String& chapters, String& output, ContainerType& cot)
at MeGUI.AutoEncodeWindow.queueButton_Click(Obiect 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. Control. ControlNativeWindow.OnMessage(Message& m)
at Systern.Windows. Forms. Control. ConfrolNativeWindow.WndProc(Message& m)
at System.Wiridows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPfr wparam, IntPtr iparam)

[check]

Not so helpful. Please post the error with more information (what you were doing, whatOS, etc etc) over on the big report tracker.

[Doom9]

@leinieman: bugs aren't the topic in this thread. Unless you know C# you have no business in this thread. You report is also severely lacking. Keep in mind that for bugs to be fixed, they first have to be reproduced.. with the amount of information you have provided, this is impossible. And I shouldn't have to ask which languages you had selected in the language dropdowns..

[Soshen]

@doom9

you think that can be add in megui the option for allow writing stats when is used the CBR pass?
imho this is the bigger problem of megui at now ^^;

[leinieman]

My humble apologies.

[Adub]

@Soshen
As doom9 would agree, judging by the content of his post right before yours, this isn't the thread for feature requests.

[Sharktooth]

Sharktooth: what do you think of DSpider's icons at http://sourceforge.net/tracker/index.php?func=detail&aid=1656502&group_id=156112&atid=798479

??
Uhm, i dont like them, but those are better than nothing.

[Raere]

I'm looking to do some changes to the meGUI form for a custom build for myself, but in the SVN repository on SF, all I see are the regular code files. Are the forms available anywhere to edit in Visual C#? Or are the forms built using some other program?

:thanks:

[tebasuna51]

You are using NicAudio.dll 2006-03-14 from Dimzon than crash when an ac3 frame with different parameters than the first arrive.

In this post (http://forum.doom9.org/showthread.php?t=114968) is exposed the problem and Nic make a new version 2006-09-01 (http://nic.dnsalias.com/NicAudio_alpha3.zip), based in last Dimzon sources with DRC.

This version is working fine by months with BeHappy, maybe you can add it to MEGUI install.

Edit: From 2007-02-24 this version is in Nic's Web Page (http://nic.dnsalias.com/nixaudiostuff.html) like v1.7

[Eric B]

I wonder why meGUI main window form is locked. It is quite boring not to be able to see the queue list in a bigger window.

Instead of setting the locked bool in the form, why not using proper anchoring, so that the GUI elements are resized when the main window is made bigger?

I wanted to do it in my own build by getting the sources, but I have some difficulties with CVS. I'm using TortoiseCVS under Windows, I set the proper CVSROOT in checkout, but I don't receive any file. Here my log:
Dans E:\Download\MeGui : "C:\Program Files\TortoiseCVS\cvs.exe" -q -z6 checkout -P MeGUI
CVSROOT=:pserver:anonymous@megui.cvs.sourceforge.net:/cvsroot/megui

Empty password used - try 'cvs login' with a real password
cvs checkout: in directory .:
cvs checkout: cannot open CVS/Entries for reading: No such file or directory

Succès : opération CVS terminée

What's wrong here?

[cc979]

because it got transfered to svn
https://svn.sourceforge.net/svnroot/megui/

[Eric B]

ok, so I've taken TortoiseSVN and now, I've the sources.

PS: It could be nice to edit the code page in sourceforge and saying that only SVN is used.

so, I've opened the solution in VS (and for Raere, the forms are there too, check under core\gui).

1) I've renamed "Form1" to "MainForm"
2) I've edited the form & control properties, adding the following:
this.autoEncodeButton.Anchor = ((System.Windows.Forms.AnchorStyles)((System.Windows.Forms.AnchorStyles.Top | System.Windows.Forms.AnchorStyles.Right)));
this.resetButton.Anchor = ((System.Windows.Forms.AnchorStyles)((System.Windows.Forms.AnchorStyles.Top | System.Windows.Forms.AnchorStyles.Right)));
this.log.Anchor = ((System.Windows.Forms.AnchorStyles)((((System.Windows.Forms.AnchorStyles.Top | System.Windows.Forms.AnchorStyles.Bottom)
| System.Windows.Forms.AnchorStyles.Left)
| System.Windows.Forms.AnchorStyles.Right)));
and removed
this.FormBorderStyle = System.Windows.Forms.FormBorderStyle.FixedDialog;

and now, I have a GUI which can be resized.
All others controls seems indeed to be already set with the proper anchoring.

Is it possible to have the same behavior in the "normal" build? If not, why?

[S¡nTë£]

Is there a specific reason why megui ignores the output file name when encoding from AVS to x264 (either mp4 or mkv)? It always encodes to the same location/filename of the input with the extension of the output format.

I had 4 jobs based on the same avs where i specified different output filenames, but in the end each one overwrote the previous, which was a major loss of time.

[check]

use the [...] button to specify the output location.

[mcka]

Hi!

What about making MeGUI create anamorphic videos which work with Quicktime/AppleTV/IPod? If you create an anamorphic video (e.g. H.264/MP4) using MeGUI, it works with VLC, but not with Apple products. But this problem seems to be solvable if you set PAR in the MP4 container using Quicktime Pro:
http://discussions.apple.com/thread.jspa?messageID=4297526�
http://appletvhacker.blogspot.com/2007/03/mikes-hands-on-report-step-by-step-how.html

People from handbrake/MediaFork have made anamorphic MP4 work with Quicktime by adding an "atom" to the MP4 container:

The container in beta2 remains .mp4, with a .mov atom patched in for QuickTime support. QT still doesn't recognize PAR...the atom applies a transformation matrix, similar to setting the DAR in an .mkv.

http://handbrake.m0k.org/forum/viewtopic.php?t=256
http://handbrake.m0k.org/forum/viewtopic.php?t=265

AFAIK that's done by the following patch:
http://handbrake.m0k.org/trac/changeset/353

One of the patched files belongs to mpeg4ip:
http://mpeg4ip.cvs.sourceforge.net/mpeg4ip/mpeg4ip/lib/mp4v2/atom_tkhd.cpp?view=markup

Do you think this could be implemented in MeGUI too?

best regards
mcka

[Doom9]

there's a lot of discussion about the whole aspect ratio thing in the megui threads.. there are good reasons why things are done the way they are being done now but I don't recall those offhand.. berrinam did all the research and coded the version that is now used.
I strongly object to any time investment to support the POS software Apple writes.. their MPEG4 video products are a disgrace.

[McCauley]

Hi,

i would like to suggest an option to use multipass and huffyuv in a more efficient way:
It's not my idea, i borrowed it from a IRC conversation.
While the Huffyuv is created the output could be used at the same time for the first pass, that would save some encoding time.
Have a look at this (http://akuvian.org/src/avisynth/avs2yuv/).

Are there any reasons why this isn't implemented?

Regards
McCauley

[Doom9]

Are there any reasons why this isn't implemented?Because we don't use mencoder for the main video encoding scenarios? mencoder as primary encoder was dropped for various good reasons that have all been publicly stated (there even was some discussion about it in this very forum).

[squid_80]

There's an avisynth plugin called twriteavi that can write a huffyuv avi file while the first pass is being done. With some clever scripting it's possible to use the exact same script for first and second passes, but the second pass actually uses the huffyuv avi written during the first pass as the source. It's not something I'd recommend be added to MeGUI (too many things to go wrong), but it is a possibility for people who want speed and know how to manually write scripts.

[mcka]

there's a lot of discussion about the whole aspect ratio thing in the megui threads.. there are good reasons why things are done the way they are being done now but I don't recall those offhand.. berrinam did all the research and coded the version that is now used.
I'm quite sure your solution is the better solution. I don't ask to change the way Aspect Ratio is implemented. Perhapy only a small option/flag like "add QT-compatible AR information". You probably think that nobody should use QT, but you cannot choose a different player if you want to use FrontRow (Apples Media Center, Apple TV...). AFAIK you don't need to change the way you set the AR, you only have to add an extra atom to the MP4 container, which doesn't bother other players. Currently only Quicktime Pro and Hanbrake SVN support that. Because I like MeGUI a lot more, I'd like to use it for encoding Apple-compatible, anamorphic videos.

Can you tell me if "adding an atom to the mp4 container" is implemented in MeGUI itself or mp4box? Perhaps I could try to write a patch and you could decide on that?

[Doom9]

megui doesn't do anything on a container level (or encoding level for that matter).. it's strictly a control application (well, almost strictly, it does some audio decoding via avisynth and pipes that data to audio encoders).

[thuongshoo]

Hi! I like to have newest source code of MeGui. Version which is at SourceForge is too old 0.2.3.x
Thanks!

[check]

browse the svn @ sourceforge for the latest revision.

[bob0r]

or http://x264.nl for a compile (still revision 117)

[thuongshoo]

@check: I have not still got newest version. In tag directory, newest version is 2193

Version Megui , is at x264.nl, has many new feature but also lost many old feature such as: in queue tab, click button "load", then ... nothing....

[Thunderbolt8]

my megui doesnt update any more, it just saying "There are 0 files that can be updated". its been like this for ~1 month now (?) and even continues after I reinstalled windows & megui completely. I dont believe there would be nothing to update since that long time e.g. x264 version is from 635, while 655 seems to be the latest right now, or dgindex still bein 1.48 etc.

the 2 update servers in the update list I have are the 2 standard ones.

[chickenmonger]

my megui doesnt update any more, it just saying "There are 0 files that can be updated". its been like this for ~1 month now (?) and even continues after I reinstalled windows & megui completely. I dont believe there would be nothing to update since that long time e.g. x264 version is from 635, while 655 seems to be the latest right now, or dgindex still bein 1.48 etc.

the 2 update servers in the update list I have are the 2 standard ones.

Check has created an alternate unofficial update site that's described in this post (http://forum.doom9.org/showthread.php?p=996003#post996003). It might be just what you're looking for.

[Thunderbolt8]

thanks, but it still doesnt work, theres also no update coming from that update site.

[berrinam]

Bug bash:
0.2.4.1040
Commit by berrinam:
- Small new feature: AutoEncode has better filesize choosers.
(addresses 1654588)
- If the bitrate calculator doesn't contain an appropriate framerate, one is added
(fixes 1676934, includes code from there)
- Removed the unused avsConfigurationDialog.cs
- Fixed 1652664 (no commandline previews)
- Fixed 1653755 (Muxer reports audio in wrong notation)
- Fixed 1679572 (Turbo Mode in LMP4 multipass sometimes not selectable)
- Fixed 1696067 (Video encoding doesn't use the specified filename)
(a duplicate of 1653186: Video Output not passed to commandline)
- Fixed 1688789 (One Click Encoder Crashes with Automatic Deinterlace checked)
- Fixed 1675408 (mkvmerge split option incorrect)
- Fixed 1666878 (Vobsubber changing output doesn't work)
- Fixed 1659596 (Load DLL in Avisynth configuration dialog)
- Fixed 1652312 (xvid b-frames default wrong)
The filesize displays meant some biggish internal changes, so there may be some new bugs in displaying and calculating filesizes.

[JarrettH]

omgosh an update!

thank you so much team!

no download to be found for 1040

[berrinam]

What range of values does XviD cq allow?

[check]

It should be 1-31.

[berrinam]

Some cosmetic features this time.
0.2.4.1041
Commit by berrinam:
- Allow non-integer XviD quantizers (1650574)
- Make the main window expandable (1704963)
- Groups of jobs can be moved up and down in the queue (1685623)
- Allow autoscrolling the log (1661785)

[Raere]

Thanks for the cosmetic fixes! I've been waiting for those. Is there any chance that they'll be a feature that'll save the position of the tab things in the queue window? Like, the size in pixels would be saved to a file and read when you started up meGUI. I like to have them just right so that it fits nicely into the window.

[bob0r]

x264.nl: 14-05-07: megui 0.2.4.1041 added

[berrinam]

@Raere: it's a possibility. Please don't ask for it here, though, but on the SourceForge bug tracker. See my signature

[dinolib]

Since latest update (core 0.2.4.1041) Autoupdate button doesn't work anymore. I click but nothing happends!:confused:

Video Input: avs
Video output: mp4 (x264)

Audio input: avi (mp3)
Audio output: mp4 (aac)

I'm used to work with these settings and I've done tons of encodings, but now autoencode button is died.

Can anyone check, please?
Thanks
-----------------------
update: rolled back to 0.2.4.1039 and everything is ok.
-----------------------
update 2: version 1041 works using menu for autoencode

[SpAwN_gUy]

Well,.. guys,.. i'm currently adding support for x264farm to MeGUI, as far as i'm not so good C# programmer.. i have few questions on using profiles,.. can anybody contact me via e-mail or iCQ ? ...

it seems like new encoder-Property works (i've been working for 3 days already..).. i'm not sure if Job addition does(didn't try that).. and i think i have settings properly made :) ... and commandline generation..

now i need(or want) to add "ProfileControl" to show up x264Configuration itself.. and then get some needed params..
BUT.. i'm currently lost in those lines(looked throug code):
profileHandler = new ProfilesControlHandler<VideoCodecSettings, VideoInfo>("Video", mainForm, profileControl1,
x264codecHandler.EditSettings, Empty.Getter,
x264codecHandler.Getter, x264codecHandler.Setter);

x264codecHandler = new SingleConfigurerHandler<VideoCodecSettings, VideoInfo, VideoCodec, VideoEncoderType>(profileHandler, CodecManager.X264);

ProfilesControlHandler<VideoCodecSettings, VideoInfo> profileHandler = new ProfilesControlHandler<VideoCodecSettings, VideoInfo>(
"Video", mainForm, profileControl1, CodecManager.X264, Empty.Getter,
new SettingsGetter<AviSynthSettings>(settingsProvider.GetCurrentSettings), new SettingsSetter<AviSynthSettings>(settingsProvider.LoadSettings));

SingleConfigurerHandler<AviSynthSettings, Empty, int, int> configurerHandler = new SingleConfigurerHandler<AviSynthSettings, Empty, int, int>(profileHandler, settingsProvider);
configurerHandler.ProfileChanged += new SelectedProfileChangedEvent(ProfileChanged);
well,.. i don't need All Codecs(as MultipleConfigurersHandler) and i need(i think) "SingleConfigurerHandler" ... but i can see sample only for AviSynth.. wich is not what i need :)

help. :)

[Doom9]

@berrinam: could it be that you didn't close all bugs/feature requests that you recently implemented?

[mitsubishi]

I'm glad to hear that I can now use a decimal for cq in Xvid without having to break to command line.

But is this all on autoupdate?

I have 1039 and nothing has updated in a week or so..

[Raere]

Instead of sitting around and waiting for autoupdate to work, you could just manually download it from x264.nl. It looks like it's broken; it's not going to fix itself if you wait long enough.

Also, I wish I could help you, SpAwN_gUy, but keep it up!

[kurt]

I'm glad to hear that I can now use a decimal for cq in Xvid without having to break to command line.

But is this all on autoupdate?

I have 1039 and nothing has updated in a week or so..
try the new update server from check: http://forum.doom9.org/showthread.php?p=996003#post996003

[check]

my new update server was closed again now that development has resumed :) I will be keeping it in sync with megui.org

[ChronoCross]

also remember that you need to switch the updater to the development branch.

[Doom9]

I have a serious problem with all those people abusing this thread for all kinds of non development related stuff. Get back to topic or familiarize yourself with rule 16.

[homerpez]

Newest build will not load ANY video-related AVS files.. Tried numerous times... brings up a "protected memory" error

VirtualDub Mod loads the same AVS files just fine.

http://forum.doom9.org/showthread.php?t=125971

This is pretty serious, as it means I can no longer use MeGUI to encode basically anything, and I don't completely know how to go back and fix this...

HELP!

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

EDIT: I don't know if this was entirely necessary...

We have discovered that you have violated forum rule #16 in one of your posts. If you violate the forum rules 2 more times you will be suspended for 30 days.

You really should've read the post right above yours.

I only posted that as I thought it had to do with the development of MeGUI (addressing a potential serious bug)... I guess my apologies if I was confused as to what a "development" thread is for... yikes...!

[Doom9]

@Lolitka: this would be a topic for the development forum at the bottom.

[Lolitka]

Ok ... moved :)

[GenoSV]

hope noone'll get mad when I post this in this thread (know this is the development-thread so, but since the problem was brought up here, hope it's ok guys)

Newest build will not load ANY video-related AVS files.. Tried numerous times... brings up a "protected memory" error

VirtualDub Mod loads the same AVS files just fine.
Hadn't used megui for a while, and just got it again yesterday. Ran into the same problem as you.
Although, if i disabled "Open Preview after Avisynth script selection" the error won't happen, and I succesfully managed to encode several videoclips after that.

So:
Open MeGUI -> Tools -> Settings -> uncheck "Open Preview after Avisynth script selection" -> Save

Hope it works for you too =)

[Mutant_Fruit]

Not so much a bug as a huge performance hit...

When encoding audio in MeGUI the GUI is updated several dozen (or more) times a second. This results in MeGUI taking a huge proportion of CPU time to keep the gui updated.

The code should be altered so that the screen is only refreshed once a second (or thereabouts). For people on single cores (or people using multithreaded audio encoders), it'll vastly increase encoding speed for audio.

At the moment MeGUI is taking up 60-70% of one of my cores due to the frequent GUI updates.

[Adub]

This is a known issue, so please just wait patiently like the rest of us.

[Mutant_Fruit]

This is a known issue, so please just wait patiently like the rest of us.
Rightio. I didn't realise it was a known issue.

[Mutant_Fruit]

Ok, i've worked up a quick workaround. The way the code is structured doesn't lend itself well to doing delayed GUI updates, so this is more of a hack than a full solution. However, it may be the best solution as it involves the minimum amount of code change.

If one of the full-time dev's has a better solution, let me know.

[Warren]

Has anyone looked at compiling this with mono lately? It appears that mono supports .NET 2.0 and part of 3.0 now (http://mono-project.com/CSharp_Compiler)

[Mutant_Fruit]

It won't run on mono as it uses methods which aren't suppoted as of yet. Secondly, the necessary 3rd party libs don't exist on linux/macos x yet, so the advantage of being able to run MeGUI is nil as you won't be able to do anything useful with it ;) Basically, you need Avisynth 3, which ain't out yet.

[Mutant_Fruit]

Ok, i've worked up a quick workaround. The way the code is structured doesn't lend itself well to doing delayed GUI updates, so this is more of a hack than a full solution. However, it may be the best solution as it involves the minimum amount of code change.

If one of the full-time dev's has a better solution, let me know.
Any comments on the patch? It's only a three liner, so it should be easy to review ;)

[check]

There are sadly only three devs (berrinam - the main one, sharktooth, and doom9). All three have put up signs saying "no time sorry", so sadly you might be waiting a long while. On the other hand, I am interested in putting up an alternate update mirror again ;)

[Mutant_Fruit]

I'll port MeGUI to mono along with the change i put above over the next few days and you can mirror it if you want. I may ping the dev's and see what the story is.

[berrinam]

Hi everyone, I'm back for a little while.

@Mutant_Fruit: I haven't yet looked at your patch, but I will probably be happy to commit it to SVN. How's the port going? I'm not entirely sure why a port is necessary, given that MeGUI still needs a lot more work to run on Linux anyway...

[berrinam]

0.2.4.1042
Commit by berrinam:
- Make main window maximizable (1734262)
- Fixed 1648638 with Mutant_Fruit's patch
- Fixed 1737423 adapting foxyshadis's patch
- Fixed 1734260 (must select profile in AVS creator for settings to be applied)
- Fixed 1728899 (AutoEncode button does not work)
- Fixed 1728890 (mp4box problem). mp4box muxes now use the output file's folder as the temp dir
- Fixed 1727973 (crop limit 200 pixels). The crop limit is now half the video's size
- Fixed inability to serialise jobs created with non-adaptive muxers
- Fixed 1659923 (Audio Delay ignored in muxer)
More still to come.

[berrinam]

0.2.4.1043
Commit by berrinam:
- Add support for AVI-Mux GUI muxing
It's not in AutoUpdate, because putting it there would crash current MeGUIs. I've fixed that bug in 0.2.3.1043; I'm going to wait about a week for people to update to 1043 before putting AVI-Mux GUI on AutoUpdate. In the meantime, you can get it from http://www.alexander-noe.com/video/amg/

[Doom9]

I'm not entirely sure why a port is necessary, given that MeGUI still needs a lot more work to run on Linux anyway...Not really megui.. rather the other way round :) You can all but forget AviSynth under Linux at this point, and there are various support programs (the video codecs may be open source, but other than lame and faac audio encoding on LInux is rather limited) that require windows, including support libs (e.g. mediainfo).

What Sharktooth is/was trying is to change megui, rolling back to using mencoder for all encoding purposes and at the same time convert all avisynth based stuff to use mencoder as well (which will never yield as much flexibility as we have with avisynth). Megui stands and falls with AviSynth - it's a very central component.

[berrinam]

0.2.4.1044
Commit by berrinam:
- Allow future programs to be added to AutoUpdate without crashing

[rack04]

Are these updates on the update server? MeGUI doesn't find any updates. Thanks for the great work.

[Selur]

@rack04: Tools->Settings->Extra Config->Configure Servers->Auto-update Servers->Developement

---
Did anyone check if "Add support for AVI-Mux GUI muxing"
also fixes 1646837 ?
(will check later; going to sleep now :))

Cu Selur

[berrinam]

0.2.5.1001 Libs update
- Same as 0.2.4.1038, but corrected because autoupdate had an old version

0.2.5.1001
Commit by berrinam:
- Add support for BeSplit audio cutting/joining, based on cutlists

See http://mewiki.project357.com/wiki/MeGUI:Audio_cutter for details.

@Selur: it should be fixed, but I'll see later.

[Adub]

thanks for the Audio GUI Update fix!

Rock on!

[Selur]

@berrinam: just tested, avi(Xvid/mp3) encoding work again.

Did the besplit support kill the cultlist support in the main window?
just tried to encode with a cutlist and got:
Log for job job1

Error:
MeGUI.AviSynthException: Script error: Invalid arguments to function "BlankClip"
bei MeGUI.AviSynthClip..ctor(String func, String arg, AviSynthColorspace forceColorspace, AviSynthScriptEnvironment env)
bei MeGUI.AviSynthAudioEncoder.encode()
----------------------------------------------------------------------------------------------------------
The current job contains errors. Skipping chained jobs
encoding without the cutlist works fine.

[JarrettH]

is it safe to just update x264.exe myself? does auto-update use a different compile from the x264 website?

auto-update also has not final DG index 1.4.9
mp4 box 0.4.4 http://kurtnoise.free.fr/mp4tools/MP4Box-0.4.4.zip

[berrinam]

@berrinam: just tested, avi(Xvid/mp3) encoding work again.Great!

Did the besplit support kill the cultlist support in the main window?
just tried to encode with a cutlist and got:
Log for job job1

Error:
MeGUI.AviSynthException: Script error: Invalid arguments to function "BlankClip"
bei MeGUI.AviSynthClip..ctor(String func, String arg, AviSynthColorspace forceColorspace, AviSynthScriptEnvironment env)
bei MeGUI.AviSynthAudioEncoder.encode()
----------------------------------------------------------------------------------------------------------
The current job contains errors. Skipping chained jobs
encoding without the cutlist works fine.That's a bug, which is weird, because I haven't touched that code...
Can you add it to Sourceforge please?

is it safe to just update x264.exe myself? does auto-update use a different compile from the x264 website?Yes, because x264 tends not to require a different calling syntax.

auto-update also has not final DG index 1.4.9
mp4 box 0.4.4 http://kurtnoise.free.fr/mp4tools/MP4Box-0.4.4.zip
I wouldn't replace them if I were you, because they are more likely to break MeGUI. Furthermore, what advantages are you likely to get? With x264, speed and compressibility, but nothing so clear with mp4box and DGIndex.

[Selur]

Can you add it to Sourceforge please?
I'll write a post in the bug tracker tomorrow :)
-> done

[berrinam]

0.2.5.1004
Commit by berrinam:
- Fixed avc2avi muxing (d'oh!)
- Fixed error on corrupt input in Adaptive Muxer

0.2.5.1003
Commit by berrinam:
- Nicer progress window displaying consistent information for all jobs
(and much nicer internal code)

0.2.5.1002
Commit by berrinam:
- Removed the DivX avi muxer
- Fixed up mux-path-finding with AutoEncode+AddSubsNChapters to support changing output format with same codec.
Result: you can now encode to AVI through AutoEncode+AddSubsNChapters

[mitsubishi]

Audio encoding seems to be broken now, I'm guessing because of the new progress window. If trying to start with an audio:
http://img179.imageshack.us/img179/7477/meaudvi5.png

If coming after a video, then meGui crashes and the previous video job gets stuck in "processing"

[berrinam]

I'm aware of the bug, and my working copy has a fix. But I still need to make some other changes before releasing it.

[berrinam]

0.2.5.1005
Commit by berrinam:
- Fixed audio encoding
- Fixed ColorCorrect's missing 'interlaced=true' on interlaced sources

[deets]

is the fps in the queue after an encode now gone, or is just me?

[kOoL tHuG]

Where can i get MeGUI Build 0.2.5.1005????????

Thanks in Advance

[deets]

Where can i get MeGUI Build 0.2.5.1005????????

Thanks in Advance

auto update? if its set to developer?

[berrinam]

0.2.5.1006
Commit by berrinam:
- Applied chiklit8963's patch for 1696276 (Ask whether to overwrite file if already exists)

[berrinam]

0.2.5.1007
Commit by berrinam:
- Fixed some profile behaviour bugs in OneClick window
- Added a help button to all the windows, which links to the relevant page on http://mewiki.project357.com/wiki/Main_Page

[bob0r]

Please update x264 to revision 663, this x264 revision fixes some blocking issue with certain h.264 decoders.

megui 0.2.5.1007 is on http://x264.nl

[fight2win]

0.2.4.1043
Commit by berrinam:
- Add support for AVI-Mux GUI muxing
It's not in AutoUpdate, because putting it there would crash current MeGUIs. I've fixed that bug in 0.2.3.1043; I'm going to wait about a week for people to update to 1043 before putting AVI-Mux GUI on AutoUpdate. In the meantime, you can get it from http://www.alexander-noe.com/video/amg/

is it working in vista?

[Adub]

You Rule Berrinam! Keep up the good work. Thank you very much!

[Mutant_Fruit]

I'm not entirely sure why a port is necessary, given that MeGUI still needs a lot more work to run on Linux anyway...

I got it all up and running, but there are a fair few rendering issues in Mono which are (i think) currently being worked on. So at the moment it doesn't look particularly pretty, but does run.

The port was mostly to see how it ran under mono, so i could report bugs and suchlike to the mono team (i'm currently interning at novell and working on mono ;) ). So hopefully when avisynth does get finished everything will render beautifully.

[Selur]

little 'bug' (since latest versions) in Automatic Encoding -> Size and Bitrate:

When entering an average bitrate, filesize is calculated, but not the other way around. :(
Iirc in older versions one could entering a file size and the resulting average bitrate was calculated and shown. ;)

Cu Selur

Ps.: didn't post this in the tracker since I'm not totally sure if it really was possible in older versions and this is a bug or if it wasn't and it's a feature request. ;)

[berrinam]

0.2.6.1001
Commit by berrinam:
- Parallel job execution. See http://mewiki.project357.com/wiki/MeGUI:Parallel_job_execution for details.

[SkilledAbbot]

Mr. Berrinam,
Is the Job Worker Feature only applicable to multi-cored PCs?


0.2.6.1001
Commit by berrinam:
- Parallel job execution. See http://mewiki.project357.com/wiki/MeGUI:Parallel_job_execution for details.

[berrinam]

Well, you'll only get speed gains on multi-core (and for the video encoders, only small gains). But the ability to run jobs now, without waiting for other jobs to finish is available to all PCs

[SkilledAbbot]

I see. Thank you. I went back to 0.2.5.1007 though . . . for now.
Here's a little something I saw, some of the help buttons throw a fatal error, but the meguiwiki still opens up fine.

[seggitek]

I hope this is the right place to post this. I noticed that I can't rename the video output file in MeGUI. Regardless what filename I enter the output video is always rendered to the file suggestes by MeGUI by default.

Example:

I load my file called nighty_frags.avs

MeGUI inserts nighty_frags.mp4 into the output filename textbox

I change this to nighty_frags_aqstrength05.mp4 but in the queue there is always nighty_frags.mp4 as output filename and the video is also rendered to that file.

I'm using MeGUI 0.2.5.1007

[~bT~]

^ just change the name of the .avs file to whatever filename you want instead.

[Dot50Cal]

Just curious if it would be possible to support the Logitech G15 keyboard's LCD screen in Megui? Im often times using my monitor for other tasks while encoding, and it would be great to have it display the percentage, time left etc on the LCD screen. Has anyone thought of this?

[anybody]

With 0.2.6.1001, in the AviSynth script generator,
i always get a
ColorMatrix(hints=true,interlaced=true)
for progressive sources.

This happens when "Deinterlace: Do nothing" is selected, which is the default after analyzing a progressive source... I have to manually uncheck the Deinterlace checkbox to get rid of the interlaced=true option.

Other than that, i'm pretty happy with the new 2.6.1001 version, the new worker thing is cool and seems to work fine for me :-)

[check]

This thread is not for support, or for reporting bugs, or for suggesting features. This is for megui coding work!

A patch has been made available here to fix mp4box muxing: http://forum.doom9.org/showthread.php?p=1026270#post1026270

[chros]

I have invastigated the calculator, and I don't understand the given DVD sizes. eg:
- if a 1 DVD: 4586496 ,
- how come a 1/4 DVD : 1126400 (*4: only 4505600; which is 80896 minus KB or 79 MB minus)

Is this for the file-overhead of the DVD structure? But 79 MB ?

And is this DVD size for DVD+5 discs?

Thanks

[Sharktooth]

ask doom9. IIRC it was him to code the bitrate calc.

[Kurtnoise]

Can we discuss freely the future meGUI development here or should I use my SF account ?

I played with the code during few days last week and I changed several things (mostly redesign and fixed some bugs).

I need to play again with the sources though...:D C# is quite new for me.

I plan to add Aften encoder and redesign some other parts...

[Sharktooth]

we can discuss here, but if you have feature requests it's better you post them into the appropriate place.
however if you're interested in megui development i can add you to the project devs and give you svn write access since i sincerely have almost no time to contribute to megui dev at least for the near future.

[Kurtnoise]

My free time is also limited. :)

For the moment, I haven't features requests. Aften encoder was already mentioned by someone else in the tracker.

The only thing I would like to have, it's some feedback about redesign. If it's ok to speak about that here, I'll post some shoots soon (better to have pictures than code concerning design, isnt it ?)...Let me just finish to play with the sources. I'll be in vacation the next week.

btw, thanks for the offer about svn write access. :)

[chros]

ask doom9. IIRC it was him to code the bitrate calc.
Thanks Sharktooth, I think it's a little bug, so I'll post it in the proper topic ...

EDIT: I can't post in the proper topic: it's closed ... :)
So where should I post it?

@Kurt.: It would be nice to see Aften in megui ...
Thanks

[berrinam]

I don't have much to say right now, just encouraging Kurtnoise with contribution to MeGUI, and I'm happy if you want to redesign. I'll read what you post, but probably won't code much.

[chickenmonger]

Thanks Sharktooth, I think it's a little bug, so I'll post it in the proper topic ...

EDIT: I can't post in the proper topic: it's closed ... :)
So where should I post it?

@Kurt.: It would be nice to see Aften in megui ...
Thanks

I'd say the bug tracker (https://sourceforge.net/tracker/?group_id=156112&atid=798476) on SF.

[Bigmango]

I'd say the bug tracker (https://sourceforge.net/tracker/?group_id=156112&atid=798476) on SF.

Are you sure ? The tracker doesn't seem to be used.

I see bugs listed there since 2006 and none of them has been assigned to anyone.

It rather looks like a good black hole to drop the bugs so they won't get lost until some kind soul resurects the project. :)

[Sharktooth]

devs read it, so post it there.

[berrinam]

I never really assign to anyone, but I do fix a lot of bugs there, and I do appreciate people using that, as it's the easiest way to keep track. If you want evidence that it gets used, why not look at the list of 52 closed bugs?

[Kurtnoise]

Yes, it's a great feature...:) All users should use it to summit bugs.

Speaking of bugs, I've uploaded some patches here (http://kurtnoise.free.fr/MeGUI/) to fix them :

# 1758807
# 1767122
# 1772571
# 1785319

@devs : Feel free to submit them. Some other might follow...Otherwise, if you haven't time I'm ok to have the write access. (my login in SF is the same as D9 :: kurtnoise13)

[ACrowley]

Any Chance for a fixing the Time Calculation Engine ?

I mean :
1. "Elapsed Time" Value resets to zero after 24h
2. Remainig Time Value jumps around. Older Builds and x264 in cmd Window shows a more or less "static" Remaing Time Value

[Kurtnoise]

Why not posting in the SF bugs tracker instead of here ?

btw, I'll look at this...

[berrinam]

I've given you SVN access on SF. Have fun.

[Sharktooth]

mitsubishi posted a patch for megui. get it here: http://forum.doom9.org/showthread.php?p=1033012#post1033012
also i think we can now remove the tags folder, berrinam?

[Kurtnoise]

I've given you SVN access on SF. Have fun.
thanks...:)

The *big* question now : how to close bugs tickets ?

[Sharktooth]

http://img511.imageshack.us/img511/6140/bbhi0.th.png (http://img511.imageshack.us/my.php?image=bbhi0.png)
then hit the submit button on the bottom of the page

[berrinam]

mitsubishi posted a patch for megui. get it here: http://forum.doom9.org/showthread.php?p=1033012#post1033012
also i think we can now remove the tags folder, berrinam?

Sounds fine

[Sharktooth]

0.2.6.1002
Commit by Kurtnoise:
- "Do all and Close" button for the AVS Cutter. Patch by mitsubishi (http://forum.doom9.org/showthread.php?p=1033012#post1033012)
- PreRender fix. Patch by mitsubishi.
- fix a typo for the FFmpeg AC-3 Encoder Type.
- fix some typos for the MP4Box command line generator.
- ANSI Encoding type instead of UTF-8 for the chapters file saved + some revamping.
- add MP4 Container support for the XviD compressor.
- fix ac3 bitrate command line for the new FFmpeg builds.

P.S.: i removed the folders in Tags
i also think i closed all the bug-reports regarding the fixes in this version

[Sharktooth]

0.2.6.1003
Commit by Sharx1976:
- Fix One Click Encoder crash (patch by bbel)
- Drag&Drop support for avs input in main window (patch by dako-kun)

[Sharktooth]

since today it seems i have some free time i posted a couple of builds and i did a small cleanup on the project trackers. i also disabled the CVS since it's no longer in use.

@devs: please ensure to check the feature request tracker frequently.

EDIT: Where i can get the megui install script used for the 0.2.5.1007 release?

[Kurtnoise]

EDIT: Where i can get the megui install script used for the 0.2.5.1007 release?
you mean the NSIS script ?


btw, here is a screenshot of the audio part refactoring :

http://img211.imageshack.us/img211/9956/meguiaudioenc0409200718rv6.th.png (http://img211.imageshack.us/my.php?image=meguiaudioenc0409200718rv6.png)

A white panel on the top with a short text + the logo of the encoder with a direct link for download or something when we move the mouse on it.

What do you think about that ?

Note: the ND logo is free of charge (available for free on the official website (http://www.nero.com/eng/AppLogos_NDA.html))...

[Sharktooth]

yep the NSIS script.
some time ago i was thinking to add ftp download capabilities to the auto-updater so to fetch the nero encoder directly from their FTP. however, i like the encoder logo on the audio cfg window.

[Bigmango]

@ berrinam, Kurtnoise13, Sharktooth & Co

Thanks a lot for the great work on this app, it's good to know it is still updated :thanks:

Btw, if anyone of you guys happens to be looking at the source files, there is one very small fix I would like to use:

- increase the max possible nero audio (aac) bitrate from 320k to 640k (like the official nero gui allows 448k and 640k). This is primarily for multichannel audio.

[Sharktooth]

done.

[Sharktooth]

0.2.6.1004
Commit by Sharx1976:
- Always check to see if an event handler delegate is non-null before calling it (Patch by Sean McGovern)
- Increased the neroaac encoder max bitrate to 640kbps
- (Kurtnoise) add "Français" in the Language Selection (supported by the ISO 639 code and also needed for the parsing of the DVDDecrypter Info Text File)

[Bigmango]

Awesome ! :thanks:

[Sharktooth]

we have 27 bugs left in the megui bugtracker.
i suggest to concentrate our attention on fixing those bugs before implementing new features.
i think 0.2.5.xxxx is a bit too buggy to call it "stable".
what do you think?

[Kurtnoise]

we have 27 bugs left in the megui bugtracker.
i suggest to concentrate our attention on fixing those bugs before implementing new features.

yes, it's my main goal...:)



About NSIS script, try to ask to bob0r maybe...

[Sharktooth]

rev164 disables the updates if the avisynth plugins path is not found in the settings (that could mean avisynth is not installed since this path is get stright from the registry). afterall avisynth is required or megui wont work...
if you dont agree with that behaviour ill change it.

[Sharktooth]

0.2.6.1005
Commit by Sharx1976:
- Using Avisource() to open .avi files.
- Added a warning if avisynth is not installed and automatically disables the update button.
- (Kurtnoise) m4a extension missing for MKV mux.
- (Kurtnoise) allow m4a extension for AudioType.
- (Kurtnoise) Drag & Drop support for Audio Encoding.
- (Kurtnoise) Drap & Drop support for D2V Creator Tool (bug #1718007)
- (Kurtnoise) Drag & Drop support for the OneClick Tool. (bug #1718007)
- (Kurtnoise) remove Aften code...
- (Kurtnoise) -add Subtitles Streams Name for MKV and MP4 Muxer. -enable some missing features for the Muxers. Adaptive Muxer issues not fixed yet...
- (Kurtnoise) -add Subtitles Streams Name for MKV and MP4 Muxer. -enable some missing features for the Muxers. Adaptive Muxer issues not fixed yet...

[Kurtnoise]

I'm ok with it but the stored path in registry is not OS dependent ? I mean, is it the same name for Vista and XP/2K ?

[Sharktooth]

it should. however the user is warned to check if avisynth is installed AND if the path is set...

[Kurtnoise]

ok...great.

[chickenmonger]

Here's a tiny visual bug in the d2v creation window:
"Track1" and "Track 2"

http://www.imagehosting.com/out.php/t1106106_untitled.PNG (http://www.imagehosting.com/out.php/i1106106_untitled.PNG)

Here's what I hope is a patch to fix that single missing space. Let me know if I managed to do it correctly. It's my first time making a patch.


Index: VobinputWindow.cs
===================================================================
--- VobinputWindow.cs (revision 166)
+++ VobinputWindow.cs (working copy)
@@ -309,7 +309,7 @@
this.track1Label.Name = "track1Label";
this.track1Label.Size = new System.Drawing.Size(72, 23);
this.track1Label.TabIndex = 11;
- this.track1Label.Text = "Track1";
+ this.track1Label.Text = "Track 1";
//
// track2
//

[Atak_Snajpera]

0.2.6.1005
Commit by Sharx1976:
- Using Avisource() to open .avi files.

What If user has loseless HD avi larger than 2GB? I suggest OpenDMLSource instead of AVI...

[squid_80]

AVISource is just a wrapper for avifilesource and opendmlsource. It scans the avi file and uses whichever one is appropriate.

[Sharktooth]

Here's a tiny visual bug in the d2v creation window:
...
Done. Also added some logic to control the "Suggest resolution" control activation based on the "Resize" status.

Question for Berrinam: I see TIVTC 1.0.1 in the auto-update but it doesnt get updated (fixable)... but the point is, does megui already support version 1.0.1 (i have no interlaced content to test it and i dont wanna waste time in something you may have already did...)?

[berrinam]

I didn't put TIVTC 1.0.1 on the update servers, it was probably check, who kindly offered to manage and update them. I haven't done anything to change the interlacing, so that may have to be reverted to an older version which does still work with MeGUI.

Edit: Sometime, I plan to replace the auto-deinterlacing in MeGUI with my external program, bautodeint. It's a better analyser, and it will also be integrated into the job queue more nicely. (Being able to run small jobs like this without waiting for larger encodes to finish is one of my main motivations for having parallel job encoding)

[check]

I just updated TIVTC to the latest version a while ago. I have been using it without worries so far, but I dont use the MeGUI script creator much. Did I miss a problem with MeGUI & TIVTC 1.0.1?

[Sharktooth]

uhm... well, the problem may be the script creator. if TIVTC 1.0.1 has different parameters than the actual one (1.0RC6), the script created by MeGUI may not work.
Infact 1.0RC7 was reverted to 1.0RC6 for that reason until berrinam could have a look at the auto-deinterlacer and update it to support a newer TIVTC version.

[Atak_Snajpera]

Why MeGUI does not use Yadif deinterlacer? Yadif is faster, no artifacts and quality is comparable to TDeint

[Sharktooth]

well, probably it's not worth spending time on a function it is going to be replaced.
however that could be a suggestion for bautodeint... :)

[Sharktooth]

I just updated TIVTC to the latest version a while ago. I have been using it without worries so far, but I dont use the MeGUI script creator much. Did I miss a problem with MeGUI & TIVTC 1.0.1?
could you please try if MeGUI has problems with TIVTC 1.0.1 using the AVS creator?

[Sharktooth]

0.2.6.1006
Commit by Sharx1976:
- Fixed some visual interface glitches
- AVS Creator: Checking "Resize" enables "Suggest Resolution"
- AVS Creator: Checking "Suggest Resolution" automatically checks "Resize"
- (Kurtnoise) fix subtitles streams parsing when we have strings instead of numbers.

[chickenmonger]

The mewiki has changed slightly from what I've seen. What used to be:

http://mewiki.project357.com/wiki/Main_Page

is now

http://mewiki.project357.com/index.php/Main_Page

If this is a permanent change, the internal links in MeGUI should be updated.

Also, here's two more patches for minor visual errors:

Index: MuxProvider.cs
===================================================================
--- MuxProvider.cs (revision 170)
+++ MuxProvider.cs (working copy)
@@ -433,7 +433,7 @@
maxFilesOfType = new int[] { -1, -1, -1, 1 };
base.type = MuxerType.MKVMERGE;
generator = CommandLineGenerator.generateMkvmergeCommandline;
- name = "Mkv muxer";
+ name = "MKV Muxer";
// base.audioInputFilter = "All supported types (*.aac, *.ac3, *.dts, *.mp2, *.mp3, *.mp4, *.ogg)|*.aac;*.ac3;*.dts;*.mp2;*.mp3;*.mp4;*.ogg|RAW AAC Files (*.aac)|*.aac|AC3 Files (*.ac3)|*.ac3|DTS Files (*.dts)|*.dts" +
// "MP2 Files (*.mp2)|*.mp2|MP3 Files (*.mp3)|*.mp3|MP4 Audio Files (*.mp4)|*.mp4|Ogg Vorbis Files (*.ogg)|*.ogg";
// base.videoInputFilter = "All supported types (*.avi, *.mkv, *.mp4)|*.avi;*.mkv;*.mp4|AVI Files (*.avi)|*.avi|Matroska Files (*.mkv)|*.mkv|MP4 Files (*.mp4)|*.mp4";


Index: VobinputWindow.cs
===================================================================
--- VobinputWindow.cs (revision 170)
+++ VobinputWindow.cs (working copy)
@@ -382,7 +382,7 @@
this.projectNameLabel.Name = "projectNameLabel";
this.projectNameLabel.Size = new System.Drawing.Size(100, 13);
this.projectNameLabel.TabIndex = 3;
- this.projectNameLabel.Text = "d2v Project Ouput";
+ this.projectNameLabel.Text = "d2v Project Output";
//
// saveProjectDialog
//


Does anybody know of any current work being done on ContextHelp.xml? That's something even us non-programmers can handle. Also, the mewiki suggests that the preferred way to add a patch is through SF's patch tracker. Is this still the preferred way?

[check]

re: web site, please see my sig or http://forum.doom9.org/showthread.php?p=1042398#1328

[Kurtnoise]

@chickenmonger: done...:)

[Sharktooth]

0.2.6.1007
- (Sharx1976) New changelog format
- (Sharx1976) Fixed 1735676 (Video Output filename can't be changed directly)
- (Kurtnoise) fix wiki link
- (Kurtnoise) fix label typos
- (Kurtnoise) remove hint track option for NDAAC encoder + several tunings
- (Kurtnoise) few tunings for audio encoders

[Atak_Snajpera]

well, probably it's not worth spending time on a function it is going to be replaced.

By what? At the moment in terms of speed and quality Yadif is unbeaten.

[chickenmonger]

By what? At the moment in terms of speed and quality Yadif is unbeaten.

I think Sharktooth is talking about choosing to not integrate Yadif into MeGUI's current auto-deinterlacer, as there are tentative plans to replace the current auto-deinterlacer with Bautodeint instead. As Bautodeint is also AviSynth based, Yadif should be able to be integrated into it instead.

[berrinam]

I certainly want to add yadif to MeGUI. I already use it myself, using AVS templates in MeGUI. The automatic deinterlacing will still use the TIVTC package, because they provide filters such as TIsCombedTIVTC, but yadif should be offered as a possible filter if the source is detected as interlaced.

[Sharktooth]

I think Sharktooth is talking about choosing to not integrate Yadif into MeGUI's current auto-deinterlacer, as there are tentative plans to replace the current auto-deinterlacer with Bautodeint instead. As Bautodeint is also AviSynth based, Yadif should be able to be integrated into it instead.
exactly

@kurtnoise: thank you for your help with megui :)

[Sharktooth]

0.2.6.1009
- (Kurtnoise) fixed 1660566 (Audio Streams were discarded from command line in the Adaptive Muxer).
- (Kurtnoise) [AVS Creator] Add yadif.dll deinterlacer (also added to AutoUpdate)
- (Kurtnoise) [AVS Creator] Re-order deinterlacers, to prefer TDeint over TDeint+EEDI2, and yadif over TDeint
- (Kurtnoise) [MainForm] : some refactoring in the Help Menu.
- (Kurtnoise) added a TabControl for Program Paths.
- (Kurtnoise) updated MediaInfo.dll & MediaInfoWrapper.dll (0.7.4.4 to 0.7.5.3)
- (Kurtnoise) move Settings & Update items to Options Menu.

@kurtnoise: i saw you added yadif but yadif is an avisynth plugin... it is a nonsense to have a path for yadif.dll when we already have an avisynth plugins path.
it should be removed from the settings too since there is a special section in the upgrade.xml named:
<AviSynthFile type="tree" displayname="AviSynth plugins">
that includes ALL the avisynth plugins for the autoupdate. all files placed there will be automatically copied to the avisynth plugins directory stored in the settings.
the changes to to updatewindow.cs and settingsform.cs have be reverted and yadif.dll path removed from the settingsform.cs
Look at the upgrade.xml (http://megui.org/auto/upgrade.xml) file megui parses for the updates, it will make you understand better.
just adding:
<yadif type="file">
<filepath version="0.9">yadif09.zip</filepath>
</yadif>
in that section of the upgrade.xml file, will make megui download the yadif09.zip and unpack it in the avisynth plugins folder
so, i've built 0.2.6.1009 without fixing the yadif stuff since it's 5:00 AM and i need to sleep, but before fixing other bugs please have a look at the yadif stuff.

[buzzqw]

yadif should have a specific path for load since is a LoadCplugin..

in automkv (avaiable in next update) i added a cplugin folder for adding and loading all avisynth_C plugins. If cplugin folder is present and *.dll found i will load it with loadCplugin.. else skip

just my 0.02€

BHH

[berrinam]

Actually, I added yadif (and re-ordered the deinterlacers) -- you probably just misread the SVN log. Anyway, as buzzqw said, it's a C plugin, so it can't be put in the AVS plugins folder. This is why I put it in a MeGUI program files folder. If we will support more C plugins, then it might be worth doing what buzzqw does with automkv.

[Sharktooth]

Oops.... so where should yadif be added in the upgrade.xml?
EDIT: Nevermind, found it.

EDIT: There is a problem in the program paths browse buttons. they do not open the dialog.

[Kurtnoise]

EDIT: There is a problem in the program paths browse buttons. they do not open the dialog.
fixed...:o

[bob0r]

I compiled a fresh new megui, but when i run a clean install, updater keeps asking for this:

Trying server: http://megui.org/auto/stable/
Retrieving update file from server...
File downloaded successfully...
Loading update data...
Update data loaded successfully...
Finished parsing update file...
There are 1 files that can be updated.
Updating libs. File 1/1.
Error: libs could not be found on the server
Update completed.
0 files were completed successfully
1 files had problems.

Easy fix i assume...

[Sharktooth]

does it work now?
also where i can find the megui NSIS installer script you use?

[bob0r]

It works but uhm, aren't the libs i compiled newer and possibly needed??

http://x264.nl/megui.nsi

Edit:
Also why does the "new updates available" pop-up, pop up behind the main windows?

[Sharktooth]

Trying server: http://megui.org/auto/stable/
use the development auto-update server (look in the settings) :)

EDIT: is it ok if i add the installer script to megui svn? ... if so, who's the author?

[bob0r]

Uhm, you are the author?
former x264 installer script? :)

[bob0r]

Uhm, on the update server, isn't it a bad thing to use old LIBS for 0.2.6.1010+ ? Won't this create conflicts?

[Sharktooth]

LOL! ok.:)
however the libs are fine. there will be no conflict.

[bob0r]

Hmm, ok, good to know, 0.2.6.1010 added to x264.nl with new installer and some files removed that were no longer used!

Please fix the New Updates Available Pop-UP popping up behind the main window issue... it has annoyed me from day one :p


..... now all we need is a: MEGUI LOGO!

[Sharktooth]

eh...

[Atak_Snajpera]

AviSource won't open Avis with MJPEG compression, MPEG2 and so on. In case of error MeGUI should switch to DirectShowSource()

[Sharktooth]

That's tricky... however it will be able to do that if you have the respective VFW decoders installed and working (in ffdshow VFW config enable MPEG in AVI and MJPEG)

[Atak_Snajpera]

I've already fixed that in my GUI but I use Delphi so I cannot help you further

[Sharktooth]

it's not necessary. also it's tricky coz megui workflow codebase is more complex.

[Sharktooth]

0.2.6.1011
- (Sharktooth) [OneClick] Audio Track 2 is disabled by default unless "Show Advanced Options" is checked.
- (Sharktooth) [Autoupdate] Check if yadif.dll path was set before trying to update it...
also available here: http://sourceforge.net/project/showfiles.php?group_id=156112

[Sharktooth]

i've put the latest CD's build in the auto-update (dev) server. Please test if it works correctly.

[bob0r]

0.2.6.1011

1: you put start menu shortcut to point to: "C:\Program Files\trunk\dist\bigdist\megui.exe"
2: The Updates Available pop-up still pop ups behind the main window.
3: you cannot set yadif.dll path, because when you browse for it, you need the actual file.
Just set one default path for all none set program files?
%installdir%/tools would be a good place to dumb stuff :)

- Muxer/avimux_gui.exe also has no path set
- Audio/neroAacEnc.exe also has no path set
- Audio/besplit.exe also has no path set

Maybe just set default path to C:\Program Files\megui\tools\
Or C:\Program Files\megui\tools\<program name>\ for each .dll or .exe


icon for installer:
http://x264.nl/x264.ico (you already have it seems)
http://x264.nl/x264.bmp the logo inside the installer, use for dimensions to create your own! (now it looks ugly/weird)

[Sharktooth]

installer should be fixed.
i will put a new build up...
however i dont really know why the autoupdate pop-up just pops "under"...

[nk]

I can't see preview with new version of MeGUI)0.2.6.1011), becase of MediaInfoWrapper.dll.

If I use old version of MediaInfoWrapper.dll, I can see preview.

[Sharktooth]

0.2.6.1012
- (Sharktooth) [Autoupdate] Removed yadif.dll path check since it was impossible to set the path without already having yadif.
- (Sharktooth) Various Installer fixes.

@bobor: the installer stuff is located here: http://megui.svn.sourceforge.net/viewvc/megui/NSIS%20Installer%20script/

[Sharktooth]

I can't see preview with new version of MeGUI)0.2.6.1011), becase of MediaInfoWrapper.dll.

If I use old version of MediaInfoWrapper.dll, I can see preview.
are you sure? it works pretty well here.
are you on XP or Vista?

[bob0r]

@bobor: the installer stuff is located here: http://megui.svn.sourceforge.net/viewvc/megui/NSIS%20Installer%20script/

Hmm cool, maybe better to remove ANY spaces on SVN for any file or dir, for my auto scripts its very annoying :)

Just add _ or . or just remove spaces :cool:


I have added 0.2.6.1012 to x264.nl, if developement will be continuous again, ill have a script auto update once a day.
The more testers the better!

[nk]

are you sure? it works pretty well here.
are you on XP or Vista?

Vista. If it happens only on my environment, maybe something wrong with my envirnment.

This problem also happend at old version (I forgot version number, but not recent).

Additional Information:

MediaInfoWrapper(0.7.5.3 maybe latest version) does not properly work on my environment.
0,7.4.4 works fine.

If I open some avs file for video, an error dialog pops. It says wrong color space. But avs file's
color space is YV12.comverttoyv12() does not help me:mad:

[MarcioAB]

Is there any chance to see adaptive Q parms (--aq-strength and --aq-sensitivity) on MeGUI ?

Who knows why "adaptive Q" is not official in x264 (IMHO it should be) but anyway: it works great (at least for me).
It deserves a much better space in "Quantizers" Advanced tag than a "Custom Commandline Options" in Zones tag.

Thank you.

[Sharktooth]

@MarcioAB: NO. i already explained it in another thread and i also explained how to use those options with megui.
http://forum.doom9.org/showthread.php?t=129813
please dont crosspost.

@nk: thanks, i'll try to investigate the problem but i havent vista for testing...