View Full Version : MeGUI development
Romario
29th October 2006, 01:30
What's going on, guys? Nobody says anything about further MeGUI development?
Come on!
berrinam
29th October 2006, 01:39
Romario, don't spam. I replied to your message earlier. You are now being a pain, and if you do this again, I will ask a moderator to strike you.
Sharktooth
29th October 2006, 04:17
all devs are actually quite busy, so dont expect big updates in the near future...
Sharktooth
29th October 2006, 04:30
what are the exact partitions allowed per AVC Levels?
once akupenguin said p4x4 is allowed for 4.1
Megui actually restricts p4x4 for levels higher than 3 and for level 3 with b-frames.
i think this is quite wrong so, can anyone shed some lights on that?
berrinam
29th October 2006, 09:12
Doom9 based the settings on what akupenguin told him. If you know that akupenguin says p4x4 is fine for 4.1, then Doom9 must just have got the details slightly wrong.
Sharktooth
29th October 2006, 15:28
well, is p4x4 ok even for other levels? what ones? and what happens with b-frames?
berrinam
3rd November 2006, 09:03
I don't know. I just trusted what Doom9 did, and I haven't changed anything there.
Sharktooth
3rd November 2006, 14:51
Yes, i know but i need the exact info to fix this:
private bool checkP4x4Enabled(int level, x264Settings settings)
{
if (level != 15 && (level > 7 || (level == 7 && settings.NbBframes != 0)))
return false;
else
return true;
}
Thunderbolt8
3rd November 2006, 15:43
are the deadzone settings actually implented meanwhile, either in the gui or in the profiles ?
Sharktooth
3rd November 2006, 22:57
not yet, but you can use the custom commandline options
Kurtnoise
6th November 2006, 19:12
Hi,
I just started to read megui sources to try to learn C#...but I'm little bit confused by this (in BitrateCalculator.cs) :
private double cbrMP3Overhead = 23.75;
private double vbrMP3Overhead = 40;
private double ac3Overhead = 23.75;
How those values have been calculated ?
Checking alexnoe's page (http://www.alexander-noe.com/video/amg/en_estimate_overhead.html), we can see that :
The following items cause one unit of overhead in AVI-Mux GUI:
* one video frame
* 64 milliseconds of AC3 audio
* 24 milliseconds of MP3-VBR audio
* 1 second of MP3-CBR audio
* 21 milliseconds of DTS audio
(Same values in xvid VFW calculator.)
And for your information :
AC3BlockSize != DTSBlockSize >> DTSBlockSize = MP3BlockSize.
LCAACBlockSize = 1024
HEAACBlockSize = 1024
lcaacoverhead = 21 milliseconds
heaacoverhead = 42 milliseconds
dtsoverhead = 21 milliseconds
Sharktooth
6th November 2006, 19:31
IIRC Doom9 coded the bitrate calc.
xujunzhe
7th November 2006, 04:04
everytime after muxing the audio and video, even after the megui has already did the delay correction, still, a problem, delay about 1sec
I capped to MPEG2 then use megui to convert to mp4
anyone has same problem?
Doom9
7th November 2006, 10:55
@Kurtnoise13: I got those values looking at how GKnot calculates the overhead.. and GKnot seems to be pretty accurate as far as AVI goes (iirc those values are used for avis only.. there is a different calculation in place for mkv based on what robu4x told me. I'd be careful looking at formulas that work for avimuxgui.. it appears to work quite differently (more efficiently) from the "standard" avi muxer
Kurtnoise
7th November 2006, 14:39
I see...I should read GK sources more carefully then. :p
What about extras infos ? Could be great to have them for mkv output...
Last question : megui is compatible with the Framework 3.0 or not ?
Sharktooth
7th November 2006, 15:04
MeGUI is written for .NET 2.0... and it should compile with .NET 3.0.
There could be minor and easy fixable problems though.
bob0r
7th November 2006, 16:16
Forum Search Terms: Microsoft .NET Framework 3.0 Redistributable Package
:D
try for yourself:
http://www.microsoft.com/downloads/details.aspx?familyid=10CC340B-F857-4A14-83F5-25634C3BF043&displaylang=en
x86: http://download.microsoft.com/download/3/F/0/3F0A922C-F239-4B9B-9CB0-DF53621C57D9/dotnetfx3.exe
x64: http://download.microsoft.com:80/download/3/F/0/3F0A922C-F239-4B9B-9CB0-DF53621C57D9/dotnetfx3_x64.exe
Doom9
7th November 2006, 19:04
I wouldn't expect any problems since .NET 3.0 is just .NET 2.0 plus WCF, WPF, WWF and that Infocard thingie. The language enhancements (touted C# 3.0, and LINQ will only come at some later day). It might be that a binary compiled with 3.0 wouldn't run on a 2.0 runtime though. I for one will stick to 2.0 for now until I need any of the new frameworks.
Adub
8th November 2006, 04:46
Sharktooth, I know that you are working on the distributed computing part of megui. Have you looked at omion's new program, to give you some support/ideas?
http://forum.doom9.org/showthread.php?t=117889
Sharktooth
8th November 2006, 04:49
Yes, i even asked to tobias if he's interested in implementing Elder in MeGUI.
It will save me much time...
Sharktooth
9th November 2006, 04:33
@berrinam: what's left to do to complete the refactor?
there are a couple of thing that arent working like the avisynth script creator...
Mutant_Fruit
18th November 2006, 03:07
Heya,
I just thought this might be interesting for making MeGUI support multi-machine encoding.
http://www.monoboss.com/details.html
It's basically a fully fledged framework for adding/removing/tracking nodes with fail detection and recovery. It could more than likely be used to pass pieces of a file out to different computers for encoding etc.
Doom9
18th November 2006, 11:33
Well.. I can't shut up any longer: multi machine / clustered encoding goes WAAAAAAYYY beyond the 80/20 rule. It goes so far you can't even see the line anymore.
Romario
18th November 2006, 18:47
What's 80/20 rule, Doom9?
foxyshadis
19th November 2006, 13:27
Indeed, the only way megui should support clustering should be by calling a program that mimics x264 and passes its arguments on to the real clustering tools, like ELDER and x264farm. Or, at best, a new "codec" that just creates a slightly different command line customized for one of the clustering engines, the way sharktooth wants to add ELDER support.
Romario: http://en.wikipedia.org/wiki/Pareto_principle
Sharktooth
19th November 2006, 14:46
Indeed. I already asked tobias if he wants to implement ELDER in megui.
x264farm is also good though, but only for x264.
check
20th November 2006, 14:13
May I chime in with a reminder about berriman's old proposal to separate the megui job control from the rest of the logic? Something like this would give a completely extensible interface upon which people could build their own frontends for whatever they want. I have something like this written in python currently brewing on my hard drive, but I'd switch to the megui job control backend in a flash, it's far more capable than my efforts.
dimzon
20th November 2006, 14:31
What's 80/20 rule, Doom9?
The misnamed Pareto principle (also known as the 20-80 rule, the law of the vital few and the principle of factor sparsity) states that for many phenomena 80% of consequences stem from 20% of the causes.
Some Sample 80/20 Rule Applications
80% of process defects arise from 20% of the process issues.
20% of your sales force produces 80% of your company revenues.
80% of delays in schedule arise from 20% of the possible causes of the delays.
80% of customer complaints arise from 20% of your products or services. (MeGUI applicable)
As explained example - 80% of MS Word users use only 20% of it's functionality
How can we put the 80-20 principle to good use? The key to 80-20 is not time-management. Don't try to do more. Just do more of the right things.
http://en.wikipedia.org/wiki/Pareto_rule
http://www.gassner.co.il/pareto/
http://www.clickz.com/showPage.html?page=988291
http://www.entrepreneurs-journey.com/428/80-20-rule-pareto-principle/
Sharktooth
20th November 2006, 14:44
Eh... if italians weren't so good... :p
bob0r
21st November 2006, 10:26
We wouldn't have an Enzo Ferrari.
JarrettH
26th November 2006, 22:42
Suggestion!
So I'm trying to encode an xvid using meGUI and one of the xvid profiles. The 1st pass errors out instantaneously. I figured it out quite easily the quant matrices (EQM) for xvid are missing from the autoupdater. The path on the hard drive it points to is extras/eqm_v3hr.xcm. Even if you have xvid installed it doesn't come with the EQM matrices.
:D
Sharktooth
27th November 2006, 05:19
:readguid:
laksman91
27th November 2006, 05:35
i have problem with megui. When i put something to encode (.avs) with x264 and i tried with XVID codecs, for over 24hours i got 0/xxxx Frames analyzed and i dont recieve an FPS i just get "FPS" and Estimated time is N/A
The avs works flawlessly in VDub, i'm leaning towards maybe an error w/ my MeGUI config. ?
Sharktooth
28th November 2006, 19:35
this is not the bugreport thread.
Adub
2nd December 2006, 08:01
Man, and I got all excited because I thought there was an upswing in development.
People, Read the guides, Use Search, and for Good sake, Post in the right forum!
If you have a problem with Megui, post it elsewhere.
Thank you.
miztadux
12th December 2006, 16:55
Hello,
Thanks for all the work you did with this great app....I got a question for people with knowledge of MeGui source code...
I tried to "port" x264 MeGUi profiles by Sharktooth to my transcoding app (a lame homebrewed perl script).
To do so i looked at the MeGui source and tried to extract the bits that translate the profile/settings to a x264 commandline.
I found most of the code was in "CommandLineGenerator.cs", in particular the two methods "x264TriStateAdjustment", "generateX264CLICommandline"...
So basically I ported the "x264Settings" class and the two aforementioned methods in my script, and had the script do:
- load the MeGUI profile in a x264Settings "object" (no more an object in my sloppy code...)
- set "BitrateQuantizer" and "Logfile" to some correct values depending on the source/settings.
- for each pass:
* use a copy of the loaded settings
* set "EncodingMode" to an appropriate value (//comments in generateX264CLICommandline)
* run "x264TriStateAdjustment" on those settings
* run "generateX264CLICommandline" on those settings to get the cmdline
* run the pass...
I'd like to ask if I've missed something that MeGUI does with the profile/settings before feeding them to the "generateVideoCommandline" method, perhaps setting the value of some parameters based on some properties of the source ? (i'm no .net expert and did a sloppy job, i'm pretty sure i did something wrong ;))
In particular, I didn't have much time to test my code, but i saw that x264 displayed a warning like "--vbv-maxbitrate specified but no value for --vbv-buffersize" using the "HQ-Slow" profile...and actually i didn't find where, in the code ,"VBVBufferSize" value would have been changed (except manually in the control panel)...
(VBVBufferSize is "-1" in the profile, so it won't be in the command line as "if (xs.VBVBufferSize > 0)..." )
Sorry for my English (i did the best i could;)) or if this post doesn't belong here.
Thanks for any help....
PS: For now, I completely skipped the "AVCLevels" class, as I though it was only used if "Level" is different from "15" in the profile, but is it used somewhere else in the process ??
nightrhyme
15th December 2006, 01:06
Any word on when the updates on the server will be fixed ?
This is as far as the update procedure goes. have let it hang for an hour.
http://img335.imageshack.us/img335/4563/screen02pr4.jpg
Do we still need NEROAACenc ? because it can't update that either ?
Tried running a job. But it just sits there. No progress.
Sharktooth
15th December 2006, 01:32
There should be an hidden window... try moving around the autoupdate and the megui window...
you should find an import profiles window...
select the profiles you wanna import and go on.
neroaacenc should be update manually. you can turn of the error message by clicking with the rigth mouse button over neroaacentry in the autoupdate...
nightrhyme
15th December 2006, 01:52
Thanx for reply.
Ok I almost got it.
Regarding manual update of neroaacenc:
So I just take the neroaacenc dll from nero directory ? and put where ?
Sharktooth
15th December 2006, 02:17
no.. you need the nero digital aac encoder binary (exe). it's available at nero website for free: http://www.nero.com/nerodigital/eng/Audio.html
place it in the C:\Program Files\megui\tools\neroaacenc folder (or wherever you installed megui)
Sharktooth
16th December 2006, 05:07
SVN update (please do a checkout!):
- Trunk is now 0.2.4.0000 (updated changelog and Assemblyinfo.cs accordingly)
- New tag 0.2.3.2193 in tags dir
check
16th December 2006, 05:19
somewhat related, can people recommend any good online resources on c#? I'm coming from an intermediate level of experience in python, and... that's it :)
shon3i
16th December 2006, 11:02
Nice Shartooth tanks, can you include SSIM check
Sharktooth
16th December 2006, 14:18
It will be included in 0.2.4.x
bob0r
16th December 2006, 21:06
0.2.3.2193 on http://x264.nl
bob0r
16th December 2006, 21:15
What is the workaround for x264 sliceless threads?
I dont see --threads auto in commandline, and selecting threads is disabled. Why is that?
Threads:
auto <default>
1
2
3
...
16
Thats how it should be.
Edit:
Also the help balloon disappears when mouse over on threads.
berrinam
16th December 2006, 23:15
0.2.4.0001
Commit by berrinam:
- Fixed Guide link so it points to http://mewiki.project357.com/wiki/Main_Page
- Fixed bug when loading d2v files into avs creator
- New deinterlacing options in avs creator
In addition, Sharktooth's last commit (0.2.4.0000) involves a lot of change to MeGUI's internals. To the user, it means:
Reworked profile behavior so that it is consistant across MeGUI
Reworked One click encoder's profiles; removed the one click configuration dialog.
Left out the avi muxer since it doesn't seem to work anyway. This omission isn't permanent, though.
berrinam
17th December 2006, 00:07
Oh, and another nice feature is that the One click encoder is more likely to guess and format the name properly when it opens a file.
Adub
17th December 2006, 00:14
All right! good to see you again berrinam. And thanks for the update too.
berrinam
17th December 2006, 05:07
This version should be fit for use:
0.2.4.1002
Commit by berrinam:
- Add 'run command after encoding'
- x264: add support for --no-ssim and --interlaced
vBulletin® v3.8.11, Copyright ©2000-2025, vBulletin Solutions Inc.