MeGUI development

[chros]

Bugs:
- anamorphic mode and overcrop 16 in avisynth creator: megui should give always the same SAR values (I don't know how the SAR values are calculated from this DAR) with different cropping settings (now it's almost always different)
- you should update DGIndex to 1.5 RC2, because the current b10 has the colorimetry "bug" (all dvds are treated as BT.709, it uses the "1" matrix instead of "5")

requests:
- can you make the open dialog is "file droppable" in avisynth creator and in d2v creator (like on the main form) ?
- can you make a checkbox to apply or not apply DRC with AC3 and DTS sources on the main form (NIC sources) (and other sources, where it's appropriate) ? Now, megiu always apply DRC with the DRC=1 parameter ...

Thanks

[Sharktooth]

feature requests and bug reports should be posted on the appropriate trackers on the MeGUI project page on sourceforge.
thanks.

[chros]

feature requests and bug reports should be posted on the appropriate trackers on the MeGUI project page on sourceforge.
OK. Submitted ...

[Mutant_Fruit]

I applied few of them...I've no time for the moment for extra reviews. Maybe this weekend.
Just wondering what the outlook is for the patches on the issue tracker.

Also, to give a heads up on what i'm working on now: There are issues in mono's implementation of SettingsBase and/or ApplicationSettingsBase which prevent MeGUI from starting up. I'm working on fixing that.

There are also issues with the serializer which prevents mono from opening settings which were serialized on .NET as opposed to with mono. I'm creating a testcase for that to submit to mono.

[Kurtnoise]

Before reviewing X-plateform patches, I'm starting with patches which fix bugs...



@Sharktooth: could be great to update the bugs/patches trackers on SF...you know that I can't do it myself. ;)

[Sharktooth]

eh... im trying to find the time...

EDIT: i updated your permissions on MeGUI trackers.

[Mutant_Fruit]

And we have a winner :)

I'm just getting a few more patches ready for MeGUI, once all those are in you'll be cross platform. As for how you'll actually encode on linux, well, that's another issue altogether. I don't know too much about media on linux, but it should be possible to hook into gstreamer to do the heavy lifting.


http://img112.imageshack.us/img112/5045/meguilinuxme3.th.png (http://img112.imageshack.us/my.php?image=meguilinuxme3.png)

[mroz]

And we have a winner :)

I'm just getting a few more patches ready for MeGUI, once all those are in you'll be cross platform. As for how you'll actually encode on linux, well, that's another issue altogether. I don't know too much about media on linux, but it should be possible to hook into gstreamer to do the heavy lifting.


http://img112.imageshack.us/img112/5045/meguilinuxme3.th.png (http://img112.imageshack.us/my.php?image=meguilinuxme3.png)

Um, isn't MeGUI so heavily reliant on AviSynth that removing this dependance would effectively require a rewrite?

As to Avisynth under linux, aiui v2 isn't stable under Wine & v3 is not only pre alpha, but pretty much stalled too.

Or am I missing something?

Avisynth is still one of the big reasons I use Windows rather than linux.

[Mutant_Fruit]

As to Avisynth under linux, aiui v2 isn't stable under Wine & v3 is not only pre alpha, but pretty much stalled too.
I thought AviSynth 2.5x under wine worked fine? Maybe not the latest 2.5x, but there are versions which do run...

EDIT: Quick google: http://bugs.winehq.org/show_bug.cgi?id=1707 Result: AviSynth is known to work under Wine.

[mroz]

Good news if true. I've not tried it - only read on several occasions that while it 'works', it isn't stable.

This thread is almost equally old: http://forum.doom9.org/showthread.php?t=81793&page=2

It implies 2.5.2 worked then. I don't know if there's been any progress with more recent versions since.

However going back to 2.5.2 isn't an option for me. I rely on MT & I think that's only 2.5.7 atm.

...Hm, more recently there's: http://forum.doom9.org/showthread.php?p=746967#post746967 with 2.56 mostly working.

But throughout there are descriptions of various aspects not working properly (two being subtitling & anything involving implicit clip variables). I can really do without a further source of bugs that need working around; I usually manage to generate enough problems on my own without further help ;)

[Adub]

I have heard rumors that 2.5.7 is working with wine, but I can't test it myself. Just yet, atleast. I may do a fresh install this weekend.

[Gusar]

I've been doing a lot of encoding with Avisynth in wine with no problems whatsoever. Avisynth versions 2.5.7 and 2.5.8 Alpha 2 with wine versions 0.9.42 and onward. No subtitling, but I did use Mrestore and unDEFTmatcher which are quite complicated scripts. And if those work, probably everything works.

[Sharktooth]

@Mutant_Fruit: great job bro:)

[mroz]

I know it's lame of me to ask rather than test it myself, but I don't have a recent linux install atm. Any chance one of you could try a script which uses MT & SetMTMode()? Also if possible MVTools? If neither of those break it, that'd be an amazing sign & make it a workable alternative. Ooh, a headless quad box for dedicated encoding, that would be nice; linux is so much easier to automate tasks under. Sorry - just the first thoughts that went through my head. It's mostly empty space in there, so they're hard to stop before they drop out the other side.

[Mutant_Fruit]

However going back to 2.5.2 isn't an option for me. I rely on MT & I think that's only 2.5.7 atm.

Well, if the choice is between:
A) Nothing and,
B) Something but without MT

I think the choice is obvious ;) Sure we'll see how it goes anyway. I'm not quite sure how everything will hook in with the linux counterparts yet. AutoUpdate will have to be altered to cope, launching commandline apps may have to be altered. I don't really know ;)

[mroz]

It's certainly a great achievement, don't get me wrong. I'm just being selfish & thinking purely about my own applications. Personally I couldn't live without MT for my slow scripts & they're the kind I'd want to hand off to a headless linux box.

Either way though it's a good sign for future cross platform development of MeGUI :cool:

[Sharktooth]

if you're going to use linux bins for commandline tools it will be a PITA...
as long as you use wine, paths and stuff will be ok in linux...

[Kurtnoise]

i updated your permissions on MeGUI trackers.
I don't think so...or I'm blind.

When I click on "Admin" link, I get this error message : "You do not have admin status on any trackers for this project"...


@Mutant_Fruit: could you post also the MonoDevelop File project in the patches tracker ? thanks...:)

[Mutant_Fruit]

could you post also the MonoDevelop File project in the patches tracker ?

MonoDevelop can load .sln files, so there's no need for separate solution files (luckily). There are one or two small issues with the .sln files with the references, but all you have to do is remove the existing reference then add it back in again and everything's ok. I believe it's a case sensitivity issue, nothing important though. I'll put i a fix for that whenever i bother seeing what exactly the issue is ;)

if you're going to use linux bins for commandline tools it will be a PITA...
as long as you use wine, paths and stuff will be ok in linux...
What exactly would the issue be with linux bins? Assuming the commandline options are the same, you should just have to change the 'path' referenced in the MeGUI settings to point to the linux bin. Then it should work fine... right?

I've already submitted a patch to MeGUI to use Path.Combine() for combining all paths, so there shouldn't be an issue there.

EDIT: Bear in mind i know nothing about encoding in linux ;)

[Sharktooth]

I don't think so...or I'm blind.

When I click on "Admin" link, I get this error message : "You do not have admin status on any trackers for this project"...

log off and re-log back on.

What exactly would the issue be with linux bins?
The issue is not all tools are available as linux native binaries (DGIndex for example...)

[Mutant_Fruit]

Kurtnoise:

The patch to fix the calculator was applied incorrectly ;)

Line 212 in calculator.cs should be:

this.nbFrames.Maximum = new decimal(new int[] {
10000000,
10000000,
10000000,
0});


For applying patches on windows, this should do the job:
http://gnuwin32.sourceforge.net/downlinks/patch-bin-zip.php

[Mutant_Fruit]

The issue is not all tools are available as linux native binaries (DGIndex for example...)

Ah, gotcha. But for tools which have native linux versions, wouldn't it be better if we used the native version as opposed to the wine version?

[Sharktooth]

not necessarily. wine is not an emulator... it's more like a wrapper. also having separate binaries on the auto-update server could be problematic.

[Bigmango]

Hi,

I seem to get the same bug someone got in this thread:
http://forum.doom9.org/showthread.php?p=1055817&highlight=megui+tahoma#post1055817

Megui has always been running fine, but sine I have installed the SP1 for vista I get a fatal error window when starting megui.

The fatal error is about the font Tahoma not supporting the style "regular", followed by a stack trace System.Drawing.Font.CreateNativeFont() ..... etc.... in Megui.MainForm

So, I can't start megui anymore...:confused:


EDIT: ok, I found the problem. For some reason the tahoma.ttf has disapeared from my fonts folder. Copying the font file back into the folder fixed the problem.

[Mutant_Fruit]

This is just a subtle nudge about those patches on the issue tracker ;)

[Mutant_Fruit]

http://sourceforge.net/tracker/index.php?func=detail&aid=1892357&group_id=156112&atid=798478
http://sourceforge.net/tracker/index.php?func=detail&aid=1892350&group_id=156112&atid=798478
http://sourceforge.net/tracker/index.php?func=detail&aid=1888263&group_id=156112&atid=798478

If i can at least get those three into SVN I could continue the effort of changing the 1 or 2 remaining areas of code that affect MeGUI usability on non-windows platforms...

I hope i'm not being too annoying at this stage ;)

[Sharktooth]

do you want SVN access?
seriously, i cant dedicate any time to megui dev right now. however, if you want i can add you as a project developer with full SVN access.

[Mutant_Fruit]

Sure, that'd be fine with me. The changes can always be reverted if someone disagrees with em, tis the beauty of SVN, though i doubt anyone will.

[Sharktooth]

well, we should discuss a couple of things then.
now it's almost 5AM and i really need to sleep.

[Mutant_Fruit]

I'll PM you my email address then, unless you want to discuss stuff here...

EDIT: You seem to be out of PM space ;) alan.mcgovern@gmail.com will do it.

[Sharktooth]

sorry, i missed your reply.
ok, let's discuss it here, maybe there are others interested.
megui repository is divided into several tags and branches.
the tags directory contains the megui stable version.
while the trunk contains the current development version.
branches dir contains parallel development projects (like megui x264farm version).
1st and most important thing is every fix must be ported to both the stable and dev versions. new features only in trunk (dev), except, changes in the codecs or other 3rd party software commandlines or API.
also we usually discuss breaking changes and new features.
any question?

EDIT: btw, i added you...

[bob0r]

@Sharktooth:

You can use this .exe for megui update (rename to x264.exe :p):
http://forum.doom9.org/showthread.php?p=1108916#post1108916

In the future it will go on request or monthly updates or something (AQ, git(svn) or not, will always be part of the .exe)

[Sharktooth]

already up :)

[bob0r]

Fixed x264.exe 748 online:
http://forum.doom9.org/showthread.php?p=1109544#post1109544

[Kurtnoise]

The patch to fix the calculator was applied incorrectly ;)
IIRC, the last patch for this has been posted after the closing. Anyway, it's fixed now.


@Sharktooth: could be great to update some packages (mkvtoolnix, ffmpeg, mencoder, mp4box, DGIndex (https://sourceforge.net/tracker/index.php?func=detail&aid=1889482&group_id=156112&atid=798476))...I'm updating MediaInfo library and his wrapper.

[Sharktooth]

DGIndex needs fixing in the megui code.
The build in auto-update is the latest working build that the actual code supports.
however tomorrow ill update some packages.

[Kurtnoise]

DGIndex needs fixing in the megui code.
oO really ? I need to check this because I've made a quick test with the RC3 and it works like a charm. :)

[Mutant_Fruit]

@SharkTooth: Thanks for that. I'm heading over to france in a few hours. I'll be back late on thursday, so i'll probably ping ye some time on friday or over the weekend if i have any questions/problems.

Thanks.

[Sharktooth]

@M_F: you're welcome.

@Kurtnoise: IIRC, something changed on dgindex about audio tracks selection.
EDIT: look here -> https://forum.doom9.org/showthread.php?p=1063355#post1063355

[Kurtnoise]

mmh...you're right. I just tested d2v file creation. I'll have a look asap.

[Sharktooth]

Berrinam is still MIA?

[Kurtnoise]

Hi,

Should I rebuild the old x264 config (to have zones, extra commands, etc...) for the dev branch or we wait the berrinam's back ?

[Kurtnoise]

Berrinam is still MIA?
falling in love maybe...:D

[Sharktooth]

Hi,

Should I rebuild the old x264 config (to have zones, extra commands, etc...) for the dev branch or we wait the berrinam's back ?
lets wait few other days. if he's still MIA we can either:
1- Revert to the old profiles code
2- Complete the profiles refactor adding the missing zones and custom CLI options fox x264
3- Go ahead without zones and add custom CLI options only.

[Kurtnoise]

ok...shouln't be too complicated anyway.


btw, last night I checked the new DGindex stuff for audio streams extraction and it seems to be more complicated than I thought. We need to run a special command first to create a logfile to have each tracks IDs, then read those datas from the file and put them in the current DGindex command...so, great. :-/

I'll see what can I do for this part....

[Sharktooth]

eh, i had a look at it some time ago and i gave up since i had not enough time to get it working.

[buzzqw]

@Kurtonise13

yea, confirm; i use the same approach on automkv
First check if stream is mpeg2 (mediainfo) if yes, lauch dgindex in info mode, parse the log and add the audio tracks to list
If video is mpeg4, run dgavcdec demuxing all audio tracks and indexing the file, then add audio to list

BHH

[Kurtnoise]

btw, last night I checked the new DGindex stuff for audio streams extraction and it seems to be more complicated than I thought. We need to run a special command first to create a logfile to have each tracks IDs, then read those datas from the file and put them in the current DGindex command...so, great. :-/

I'll see what can I do for this part....
There is also an alternative: using the track IDs supply by the DVDDecrypter stream infos file. :) Several parts in the current code use this. But an issue remains if we use this way : when users don't have a such file. So, the right trick seems to use the logfile created by DGindex. What do you think ?

[Sharktooth]

DVD Decrypter is dead and in some countries even illegal.
Sadly, we should not rely on it anymore but that means rewriting some code...
Buzzqw method is the right way to go (yeah italians do it better:p) but as i said, it needs some time and will to rewrite some parts of megui.

[stax76]

I extract all streams and rename the files replacing the index with language code and name extracted from IFO.