MeGUI development

[Sharktooth]

it was simply not fixed... report the bug in the MeGUI bug tracker

EDIT: i fixed it though, next version will have the fix... so dont report it. thanx.

[Sharktooth]

0.2.6.1021
- (Sharktooth) [Muxers] Fixed the output file dialog (save mode)

small change but it was worth building since you couldnt select the output file in the muxers...
i also edited the .1019 changelog entries to reflect a minor change.
the new build is on the autoupdate.

[Sharktooth]

Has anyone a clue why shutdown doesnt work? Im getting mad...

@kurtnoise: i accepted you MSN invite...

@devs: further work must be aimed ad stabilizing the code, so forget about features and stuff (unless they're small changes, like exposing and adding new codec options or adding some exception handlers... however nothing that can screw the codebase and/or will need further bug fixing) and lets get all bugs squashed. after we reach a stable stage we'll release a stable package and we can concentrate on adding stuff or messing with the code.
Tomorrow ill create stable and unstable branches in the SVN repo, so we can port fixes to the stable version and continue with developing the unstable version until it reaches a stable status.
on the developers front, SF has a nice recruitment service. should i seek for new devs using the service?

@all: i need to know if dgindex 1.5 works correctly with MeGUI. I dont want to break things at this stage, so please extensively test it with ALL kind of sources (progressive, interlaced, telecined...) and report back. thanks.

[berrinam]

Some of the shutdown is simply not running: it was removed at one stage and never made it back in. I have a local version on my computer which fixes that.

EDIT: Committed to SVN.

[berrinam]

I notice that Sharktooth has added bug #1808055 (Encoder commandline options not being shown in the codec config window) to the SF tracker. Yes, it is a bug currently. However, it is not an accident -- I removed it in 1018 when I removed the CommandLineGenerator, as I moved some code around, thinking that command line generation is more appropriate in the individual encoders that it generates a commandline for.

There is of course no reason why it is infeasible to put the commandline back in the video codec config, but is it actually sensible to? My only use for it has been to check that all the buttons and checkboxes are being updated correctly and the commandline is being generated correctly: in short, I have only used it for diagnostic purposes, and not useful for anyone except a developer.

I think we should get rid of it. What do you think?

[mroz]

If you're asking all users, I personally find such information useful & would much prefer if devs feel the way you do, the information be hidden by default but still available via some sort of 'advanced info/features' toggle.

If you'd like to know why I find it useful, that's two fold. If I have a problem it reassures me I'm at fault rather than the gui I'm using, since I get feedback that the gui's doing what I asked. Secondly, it helps me to learn how the tool works & get to know the codec better, which I always find helpful.

If Megui ever turned into nothing more than a one click app with all internal functionality hidden I'd be very sad, however good the results. That said, I love to have such functionality available; I just prefer the freedom to choose how much automation I want, so that my usage patterns can grow as my understanding increases. I love apps that let me do that.

Sorry if I've gone off at a tangent or started ranting. Just wanted to voice my feelings. BTW you shouldn't be surprised how popular Megui's becoming. It's a very nice piece of kit :)

[foxyshadis]

It needs to be showable on that dialog, wherever the code actually is. One of MeGUI's primary target audiences is the sort of people who are likely to copy a configuration straight to a command-line (batch, etc), without running an encode first to get it out of the log. Or check it to quickly determine that they haven't made a mistake. Frankly, I think MeGUI has the best and most complete x264 option GUI out there.

[berrinam]

Hmmm... that comment reminds me of a feature I remember thinking about ages ago: exporting jobs to a batch file. I had thought someone had implemented it, but I can't find it in MeGUI or the changelog. Well, I better put it on the SF tracker.

[berrinam]

0.2.6.1022
- (berrinam) Fixed #1808324 (1 pass encode broken in autoencode)
- (berrinam) Fixed #1808055 (Encoder commandline options is not being shown in the codec config window)
- (berrinam) Fixed #1806911 (Clever anamorphic encoding not working)
- (berrinam) Shutdown when finished re-enabled (including countdown patch from imoon4)
- (berrinam) FPS chooser now says "choose your framerate" not "choose your AR"

[foxyshadis]

Do you guys think this is a good idea? Or better to just silently copy settings (jobs etc) to the user profile and work from there?
http://foxyshadis.slightlydark.com/random/meguiperm.png
Of course it only matters when people put it in programs, megui can happily run from documents if people want.

[berrinam]

By default, I think MeGUI should be installed to program files, and it should also work by default, even on Vista (without the user having to answer a question like you posted).

I can't see much point in having per-user settings (jobs/profiles), since it isn't like diary or email software where everyone has a personal account. However, I also don't see anything particularly wrong with it, and if it is the recommended way (or the clean way) of handling things on Vista, then I don't see anything particularly wrong with that. In that case, though, we should perhaps change the behavior for all versions of windows, though.

Of course, downloaded files such as x264, dgindex, should definitely go in program files.

[foxyshadis]

Having something in program files and having it work without user profiles or changing permissions is pretty much an impossibility in Vista (or an XP limited account). You can quietly change permissions, but a randomly appearing admin confirmation/runas box on startup will probably throw people.

Actually, on Vista the situation seems better, everything gets dumped into %Appdata%\Local\VirtualStore\Program Files\megui while you're using the program, I forgot that it has the virtalization. Even in the admin account. Since it would just work, it wouldn't even pop the box above up, the OS takes care of everything as long as it's not turned off. Update still has to be fixed, though, it just spins its wheels now.

The MS and unix standard is that anything that gets modified regularly is per-user. Jobs, logs, and profiles are kind of per-user things anyway, they're yours after all, although it could go either way.

I have a Vista system you can terminal into if you'd like, there's nothing private on it, it's just a terminal client. (I'm still getting used to it, first time I've really played with it in depth.)

[mroz]

2.6.10.21 Adaptive Mux Window bug - chapters can't be added. The Open file dialogue has file types set to:
"Chapter files (*.txt)
Notice the leading quote. This seems to result in no files being listed, consequently chapter txt files can't be selected.

[berrinam]

Please report bugs on the sourceforge bug tracker. There is a link in my signature.

[mroz]

Please report bugs on the sourceforge bug tracker. There is a link in my signature.

Done.

[Sharktooth]

@berrinam: knowing the commandline options will:
1 - let the user know what a megui options translates to the real encoder option
2 - be usefull to spot typos or other kind of errors in command line generation
3 - be usefull when implementing new encoder options

however thanks for re-adding it.

[berrinam]

@berrinam: knowing the commandline options will:
1 - let the user know what a megui options translates to the real encoder optionGood point, although it's not useful for me, because I trust MeGUI to do the entire job for me. Perhaps the "export to batch (https://sourceforge.net/tracker/index.php?func=detail&aid=1808438&group_id=156112&atid=798479)" feature request I added will help alleviate this need in the future?

2 - be usefull to spot typos or other kind of errors in command line generation
3 - be usefull when implementing new encoder optionsAs far as I can see, this is just diagnostics, mainly for the developers. We already have the log for that, don't we?

however thanks for re-adding it.No worries. It seems that, at the moment, it is a very useful thing to have.

[Sharktooth]

0.2.6.1023
- (Kurtnoise) [Muxer] : Chapters Filter fixed.
- (Kurtnoise) [Avisynth Window] : deinterlace checkbox unchecked when Analysis returns "Do Nothing" (to avoid interlaced=true with ColorMatrix())
- (Kurtnoise) [Help Button] : url fixed for the wiki.
- (berrinam) Catch all exceptions in ProgressWindow.UpdateStatus. (It is a non-essential function, so errors should be silently caught). Should probably fix #1760486

[Sharktooth]

0.2.6.1024
- (Sharktooth) Fixed main window (Form1.cs) size (some Audio controls were not shown)
- (Sharktooth) Fixed #1810120 (x264 video configuration dialog problem)
- (Sharktooth) [Update Window] Workaround for #1808878 (Maximize/Minimize states don't work). Disabled Minimize and Maximize buttons.

[Doom9]

c't asked to put megui on the DVD for one of their upcoming issues.
I took the liberty of approving the request.. I put "Doom9 community" as author and noted that users should come here for support and that avisynth is a prerequisite.

[Adub]

Who is c't?

[mroz]

My guess (http://en.wikipedia.org/wiki/C't).

[Sharktooth]

@Doom9: also tell them MeGUI is in beta stage too, so there could be some bugs.

[berrinam]

0.2.6.1025
- (berrinam) Fixed #1812162 (Up & down buttons in queue are mixed up)
- (berrinam) [Adaptive Mux Window] Fixed some incorrect mux-path-finding which caused a crash -- the window thought it could mux something that it couldn't.
- (berrinam) Filetypes are better determined, by also looking at the extension. This may fix #1808882.
- (berrinam) Fixed xvid AR signalling. (Use PAR not DAR)
- (berrinam) Fix #1808573 (Not able to import xvid profiles anymore)
- (berrinam) Fix #1812842 (ITU 4:3 is wrong)

[berrinam]

0.2.6.1026
- (berrinam) Fixed #1746055 (Video profile selection error)
- (berrinam) Fixed #1749810 (For each level have max bitrate for main and high profiles)
With this commit, there are no bugs in the SF bug tracker that I can reproduce other than Vista issues and the large font issue. If anyone has forgotten to post bugs, please do it now.

Also, I think that both the Vista and the large font problems are likely to require bigger changes than simple one-liners. Given that, do you think it would be a good idea to wait a week or so, and then release 0.2.6.1026 as a stable version?

@foxyshadis: Are you still working on the Vista stuff? What's the news? I think that we should move the jobs, profiles, and MeGUI settings to "my documents" in the future, but I'm not sure how that will work for people who want to run multiple instances of MeGUI at once, with different job queues (it's something I do all the time, as I have multiple copies of MeGUI for development, and one copy for encoding). Perhaps My Documents/megui should have a separate subdirectory for each version of megui installed on the computer, with either a registry key or an .ini file in each subdirectory to say which subdirectory belongs to which copy of megui. Thoughts?

[Bigmango]

If anyone has forgotten to post bugs, please do it now.

Posted "Core auto-update does not work".

[berrinam]

I tried debugging MeGUI on a Vista computer today, and I believe I solved the file-opening problem.

The old MediaInfoWrapper had a PInvoke call

[DllImport("MediaInfo.dll")]
internal static extern int MediaInfo_Count_Get(IntPtr Handle, [MarshalAs(UnmanagedType.U4)] MediaInfoStreamKind StreamKind, int StreamNumber);

// and later

private string GetSpecificMediaInfo(MediaInfoStreamKind KindOfStream, int trackindex, string NameOfParameter)
{
return MediaInfo.MediaInfo_Get(this.Handle, KindOfStream, Convert.ToUInt32(trackindex), NameOfParameter, MediaInfoInfoKind.Text, MediaInfoInfoKind.Name);
}

And when that was called, it occasionally (on the longer strings) crashed with an Access Violation. I replaced it with

[DllImport("MediaInfo.dll", CharSet = CharSet.Unicode)]
internal static extern IntPtr MediaInfo_Get(IntPtr Handle, [MarshalAs(UnmanagedType.U4)] MediaInfoStreamKind StreamKind, uint StreamNumber, string Parameter, [MarshalAs(UnmanagedType.U4)] MediaInfoInfoKind KindOfInfo, [MarshalAs(UnmanagedType.U4)] MediaInfoInfoKind KindOfSearch);

// and later

private unsafe string GetSpecificMediaInfo(MediaInfoStreamKind KindOfStream, int trackindex, string NameOfParameter)
{
IntPtr p = MediaInfo.MediaInfo_Get(this.Handle, KindOfStream, Convert.ToUInt32(trackindex), NameOfParameter, MediaInfoInfoKind.Text, MediaInfoInfoKind.Name);
char* p2 = (char*)p.ToPointer();
string s = "";
while (*p2 != '\0')
{
s += *p2;
++p2;
}
return s;
}

Which appears to fix it. The thing I don't get is, I thought the PInvoke Marshaller converted the string exactly as I did. Obviously not, though, as it crashed whereas this code works.

Does anyone know what's up with this?

--

Anyway, I have committed the updated library and I will upload it to AutoUpdate, so that this bug is hopefully fixed.

EDIT: It appears what I fixed was only part of the problem. Apparently there are also problems with DirectShow, which I haven't looked at yet.

[foxyshadis]

If you want I'll go ahead and do that tomorrow then, I wasn't sure what you were going to decide so I held off. I can set it to look for settings.xml in the MeGUI folder first, then the user's folder. Hm. Have it check for a <UseUserSettings>0</> tag and continue on to load/save to the user profile if not found? That way it can automatically propagate seamlessly unless you have the magic word.

I'm not expert in thinking about these issues, obviously.

[fields_g]

1026 not on the update server yet? Would love to try to find more bugs for you. Thanks for cleaning out the bug tracker!

[Sharktooth]

Posted "Core auto-update does not work".
coz the core was not updated on the autoupdate...
however it's coming ;)

[Sharktooth]

i updated the changelog as follows:

0.2.6.1026
- (berrinam) Fixed #1746055 (Video profile selection error)
- (berrinam) Fixed #1749810 (For each level have max bitrate for main and high profiles)
- (berrinam) Fixed #1715064 (Crash under Vista when loading avisynth script)
and uploaded the new build on the autoupdate server.

[Bigmango]

coz the core was not updated on the autoupdate...
however it's coming ;)

Nope, still not working. :(

I was in v0.2.6.1024. Autoupdate has now downloaded core 0.2.6.1025 + libs 0.2.6.1026. Then it asks to restart, and asks for admin priviledge (good !).

then it restarts.... but still with v.0.2.6.1024, and it asks me to update again.... same loop.

[fields_g]

I work at an evil corporation that has imposed Active Directory over us employees. Anyway... I don't have admin rights or install rights permanently. I installed MeGUI and have been able to do the updates until now. I believe that this must have something to do with the above talk about vista asking for admin.

Error: Access to registry key 'HKEY_LOCAL_MACHINE\Software\MeGUI' denied.

Any hope?

[Sharktooth]

Nope, still not working. :(

I was in v0.2.6.1024. Autoupdate has now downloaded core 0.2.6.1025 + libs 0.2.6.1026. Then it asks to restart, and asks for admin priviledge (good !).

then it restarts.... but still with v.0.2.6.1024, and it asks me to update again.... same loop.
Completely uninstall MeGUI AND delete the installation folder then reinstall it. I'll post a .1026 installer in few minutes on MeGUI's SF project page.

[berrinam]

In SVN revision 269, I added a test suite using NUnit (http://www.nunit.org/), the idea being that a number of bug reports can be expressed as tests, and this way we can hope to avoid more regressions as we accumulate more and more tests. I hope no-one minds the NUnit dependency; it is very light-weight, as simply being able to compile it only requires a single 76KB dll, nunit.framework.dll, which is included in the SVN.

Note that, in order to compile the test suite, you need to run compile-all.bat once first.

To run the tests, you need to install NUnit. After compiling the testsuite project, you can then run the tests either by double-clicking on the compiled testsuite.dll (NUnit registers with the filetype *.dll) or by running the NUnit GUI and opening the testsuite.dll file. All the tests should pass, which means that they should all end up green.

To find out how to write tests, see the documentation, and also the test I've already written as an example.

If, for some reason, you don't like NUnit, we can always revert.

[Maccara]

In SVN revision 269, I added a test suite using NUnit (http://www.nunit.org/), the idea being that a number of bug reports can be expressed as tests, and this way we can hope to avoid more regressions as we accumulate more and more tests. I hope no-one minds the NUnit dependency; it is very light-weight, as simply being able to compile it only requires a single 76KB dll, nunit.framework.dll, which is included in the SVN.


Excellent. I'm a fan of JUnit/NUnit myself. If you're using VS for the development, I can also recommend TestDriven.NET (http://www.testdriven.net/) (supports NUnit amongst others) which makes it easier to run/prepare NUnit tests from VS GUI directly. Free for non-commercial use.
(some might prefer this over the barebones NUnit framework, so the transition wouldn't be so painful :))

[Theliel]

umm, no more crash under vista :)
thank berrinam, work fine now.

[Sharktooth]

0.2.6.1027
- (Kurtnoise) [AviSynth Creator] : fixed Save Event for Vista OS.
- (Kurtnoise) change constant variables to shut down the PC correctly.
- (Kurtnoise) Cosmetic - fixed typos.
- (Kurtnoise) [AudioEncodingComponent]: remove the tab selected instead of the last one (#1814772)
- (berrinam) Fix #1813777 (Autocrop problem)
- (berrinam) Fixed #1814193 (AutoEncode with >1 audio track -> each audio track muxed twice)

[Kurtnoise]

#1715064,
#1728897,
#1808882,
#1814766,
#1813769

can be closed imo. To clean the bugs tracker...;)

[berrinam]

Closed 1808882, 1814766, 1728897. As far as I'm aware, fixing the Vista MediaInfo crash didn't fix the Vista DirectShow problems: can someone verify or refute this?

And 1813769 hasn't been fixed yet, has it? I know it's a duplicate, but is that a problem?

[Sharktooth]

what about #1816518. update works here...

[Kurtnoise]

As far as I'm aware, fixing the Vista MediaInfo crash didn't fix the Vista DirectShow problems: can someone verify or refute this?
I'll check this today...

And 1813769 hasn't been fixed yet, has it? I know it's a duplicate, but is that a problem?
it has been fixed...cannot reproduce the bug myself anymore.

what about #1816518. update works here...
That's strange indeed...I started to look at this yesterday but cannot find the bug/a fix.

[berrinam]

it has been fixed...cannot reproduce the bug myself anymore.Have you ever been able to reproduce it? I haven't, but I am pretty sure it was introduced in around 0.2.6.1018, and I'm not aware of any changes since then which would have fixed it, so I would expect it is still a problem.

[Bigmango]

Completely uninstall MeGUI AND delete the installation folder then reinstall it. I'll post a .1026 installer in few minutes on MeGUI's SF project page.

Ok, I have uninstalled megui and reinstalled a clean install of version 0.2.6.1026.

But now I can't test it anymore because the update versions are messed up. The latest versions are now older than the currently installed version:

- core: existing version: 0.2.6.1026 ; latest version: 0.2.5.107
- data: existing version: 0.2.4.1038 ; latest version: 0.2.4.1038

But in my previous install everything was at version 0.2.6.xxx.

So, bug #1813653 was closed; but what I see as a user is that the situation is even worse than it was before, because before the data was updating correctly to versions 0.2.6.xxx (or maybe it was 0.2.5, but definitely not 0.2.4) and the core was downloading new versions even though it failed to install them. But now it doesn't even see the new versions anymore, so I can't test if the core update works.

[Carpo]

http://mirror01.x264.nl/x264/megui-0.2.6.1022.exe - try that version and select the dev update server

[mini-moose]

hi

been playing around with megui recently and a few things I noticed/wanted to suggest in case they weren't brought up yet :

1) AVS script editor - I've loaded a .dv2 for an 50fps mpg and chose analyze.
the suggested solution was tdecimate(CycleR=2) which brings the encoded result to 30fps instead of 25fps as it should be from a pal source. tdecimate(cycle=2) would have achieved the correct result I believe.
On the main editor page I've selected PAL but I guess it doesn't influence the analyzing tool. I assume the analyzer is meant more for those who are not very experienced but thought I'd mention it anyway.

2) Bitrate Calculator/AutoEncode - one of the available sizes to choose from is 1/4 DVD / 1120mb. personally I liked the 1100mb on previous versions better as it leaves a little room for sizing errors.

3) Updates - on all the versions I've tried I always get an error when updating avc2avi : Error: Could not unzip avc2avi. Aborting...

4) MKV - something I thought might be useful for some who are used to virtualdub's "Save segmented avi" : maybe adding an option to split the encoded video file (before muxing i.e without audio) into parts. In other words have the video file output into smaller files while 2nd pass is ongoing.

5) splitting muxed file - I'm not sure if this is the place to suggest mkvmerge features or not but anyhow...I think it would be cool to have a splitting option that would not necessarily split the whole file into little bits but also an option to choose a certain segment to split from the full file. e.g 02:45 till 05:11. sometimes people might wanna save a certain clip from within a video.

I hope some of that makes sense and apologies if I have repeated issues discussed before or showed some lack of understanding of the tool's features. as I said I just recently started using it so I have not had the chance to explore it in full.

tnx

[Kurtnoise]

Have you ever been able to reproduce it? I haven't, but I am pretty sure it was introduced in around 0.2.6.1018, and I'm not aware of any changes since then which would have fixed it, so I would expect it is still a problem.
No, I'm not able to reproduce it. So...

1) AVS script editor - I've loaded a .dv2 for an 50fps mpg and chose analyze.
the suggested solution was tdecimate(CycleR=2) which brings the encoded result to 30fps instead of 25fps as it should be from a pal source. tdecimate(cycle=2) would have achieved the correct result I believe.
On the main editor page I've selected PAL but I guess it doesn't influence the analyzing tool. I assume the analyzer is meant more for those who are not very experienced but thought I'd mention it anyway.
Analysis tool is mainly dedicated to interlace stuff not framerate...

2) Bitrate Calculator/AutoEncode - one of the available sizes to choose from is 1/4 DVD / 1120mb. personally I liked the 1100mb on previous versions better as it leaves a little room for sizing errors.
Select Size...-> 1100 MB

3) Updates - on all the versions I've tried I always get an error when updating avc2avi : Error: Could not unzip avc2avi. Aborting...
yes, known issue.

4) MKV - something I thought might be useful for some who are used to virtualdub's "Save segmented avi" : maybe adding an option to split the encoded video file (before muxing i.e without audio) into parts. In other words have the video file output into smaller files while 2nd pass is ongoing.
what about splitting feature ?

5) I think it would be cool to have a splitting option that would not necessarily split the whole file into little bits but also an option to choose a certain segment to split from the full file. e.g 02:45 till 05:11. sometimes people might wanna save a certain clip from within a video.
ok...just put the request in SourceForge.

[Bigmango]

http://mirror01.x264.nl/x264/megui-0.2.6.1022.exe - try that version and select the dev update server


Arf, I forgot to select the dev update server after reinstalling :rolleyes:

The update works fine now :thanks:

[mini-moose]

Quote:
Originally Posted by "Kurtnoise13"
Analysis tool is mainly dedicated to interlace stuff not framerate...


just thought I would mention it cause it did suggest the wrong
command after analysing,

Quote:
Originally Posted by "Kurtnoise13"
what about splitting feature ?

the splitting feature seems to be only for the final muxed file unless I couldn't find a split feature for the vid only. what I mean is similar to the split feature in vdub. i.e one can set the output video file to be split while encoding and not while muxing.

[Sharktooth]

Ok, I have uninstalled megui and reinstalled a clean install of version 0.2.6.1026.

But now I can't test it anymore because the update versions are messed up. The latest versions are now older than the currently installed version:

- core: existing version: 0.2.6.1026 ; latest version: 0.2.5.107
- data: existing version: 0.2.4.1038 ; latest version: 0.2.4.1038

But in my previous install everything was at version 0.2.6.xxx.

So, bug #1813653 was closed; but what I see as a user is that the situation is even worse than it was before, because before the data was updating correctly to versions 0.2.6.xxx (or maybe it was 0.2.5, but definitely not 0.2.4) and the core was downloading new versions even though it failed to install them. But now it doesn't even see the new versions anymore, so I can't test if the core update works.

Data should be 0.2.4.1038. Everyone has "data" version 0.2.4.1038... coz it's the lastest. So everything is OK.