View Full Version : MeGUI development
buzzqw
14th March 2008, 20:32
yes.. if have an ifo.. but with a mpeg stream, not belonging to dvd.. it's hard to tell language
on automkv i use vstrip to determine audio id/languages (on ifo) and then allow dgindex to demux only tracks user selected
BHH
Mutant_Fruit
23rd March 2008, 01:56
This is the current constructor. This throws a null ref exception in Mono because of a a missing null-check which prevents MeGUI from loading:
class JobQueueSettings : ApplicationSettingsBase
{
public JobQueueSettings(IComponent c, string k)
:base(c, k)
{}
}
If i use an alternate base constructor, everything loads up fine
class JobQueueSettings : ApplicationSettingsBase
{
public JobQueueSettings(IComponent c, string k)
:base(k)
{}
}
My understanding of the whole ApplicationSettingsBase stuff isn't good enough to know if that's a safe change or not. If that's a safe change, am i good to commit that? That'll allow MeGUI to run on Mono.
bob0r
23rd March 2008, 06:28
Megui x264 config: RC and ME > Macroblock Options
When you select Adaptive DCT (--8x8dct), --i8x8 should be enabled also, this is a bug. Please fix it :)
Also i8x8 is on by default default: --partitions "p8x8,b8x8,i8x8,i4x4"
Edit:
Also please update --analyse to --partitions. Thanks
Kurtnoise
24th March 2008, 08:37
This is the current constructor. This throws a null ref exception in Mono because of a a missing null-check which prevents MeGUI from loading:
class JobQueueSettings : ApplicationSettingsBase
{
public JobQueueSettings(IComponent c, string k)
:base(c, k)
{}
}
If i use an alternate base constructor, everything loads up fine
class JobQueueSettings : ApplicationSettingsBase
{
public JobQueueSettings(IComponent c, string k)
:base(k)
{}
}
It's fine for me if it doesn't break anything else...
Kurtnoise
24th March 2008, 08:45
Megui x264 config: RC and ME > Macroblock Options
When you select Adaptive DCT (--8x8dct), --i8x8 should be enabled also, this is a bug. Please fix it :)
ok...
Edit:
Also please update --analyse to --partitions. Thanks
both are correct...
Mutant_Fruit
24th March 2008, 16:40
It's fine for me if it doesn't break anything else...
From what i can tell, it's ok to make this change, so i'm going to go ahead and commit this. Let me know if any issues pop up that i've missed. The fix is in revision 479, so things should Just Work (TM) on Linux now. Encoding and all that doesn't work, that needs to be set up, but MeGUI starts up.
bob0r
26th March 2008, 01:53
ok...
both are correct...
Yes, but x264 --help shows --partitions, why not make it match the x264 git code, just logical.
Thanks :)
Kurtnoise
26th March 2008, 10:49
why ? lazyness probably..;)
Anyway, if you check the current x264 code (formely common.c), you can see that it's still there fortunately...
bob0r
26th March 2008, 12:21
why ? lazyness probably..;)
Anyway, if you check the current x264 code (formely common.c), you can see that it's still there fortunately...
YES i know that, pengvado left it there because he is such a nice guy :)
I just say: It would be better if you renamed it just to match Current x264 settings when you type x264 --help.
Clarity > Sanity!
P.S.
If you fixed the i8x8 issue, please update the stable version on the updater.... Okay Sahrktooth?
Sharktooth come on irc tonight 00:00-04:00 or tomorrow please, got something to run by you :)
Sharktooth
26th March 2008, 16:35
ill see what i can do
Kurtnoise
26th March 2008, 21:49
@bob0r: it's done...
bob0r
27th March 2008, 01:51
@bob0r: it's done...
Muchas gracias!
Sharktooth
27th March 2008, 15:02
0.2.6.1046 is up on the autoupdate and on sourceforge.
this should be the last 0.2.x release until something new comes out...
bob0r
31st March 2008, 06:28
@Sharktooth
Can you please update MeGUI with the proper DVD target sizes:
373MB 1/12 DVD
559MB 1/8 DVD
746MB 1/6 DVD
1119MB 1/4 DVD
1493MB 1/3 DVD
2239MB 1/2 DVD
The new x264 tv rules 2008 will also include these.
Edit:
Also add the AQ GIT x264 build to megui asap :D
http://forum.doom9.org/showthread.php?p=1119815#post1119815
Tacio
31st March 2008, 18:31
and what about 0.3.0.1004? any chance for update? :)
Sharktooth
1st April 2008, 02:25
https://forum.doom9.org/showthread.php?p=1119781#post1119781
~bT~
1st April 2008, 04:07
^ so no more updates Sharktooth? :(
poisondeathray
1st April 2008, 04:13
^ so no more updates Sharktooth? :(
Please say it isn't so :(
I just wanted to say many people appreciate your work Sharktooth, and the efforts of the whole development team.
73ChargerFan
1st April 2008, 05:29
Let me also extend my deepest thanks to Sharktooth and everyone else behind MeGUI. I've been struggling with learning to encode in my spare time for a year and a half, and I couldn't have gotten anywhere without MeGUI. Command line operations and tools just aren't my thing.
So, thank you.
bob0r
1st April 2008, 06:49
Hell we do need your great work.... keep it going Shark!!
Please update megui profile and x264.exe, we all need to be AQified! :D
IRC me for good feelings :p
mroz
1st April 2008, 23:31
Oh bugger.
Not much I can add. Each of the devs will be missed if they choose to leave. They've all done great work. There are /many/ happy Megui users who never post or make their appreciation known in other ways.
The devs could choose to ignore overly critical or irrational users, but it's not always easy & one might well feel that one shouldn't have to.
I would hope that such reasons wouldn't be the principal cause of anyone leaving, as that would be a sad waste, but that's down to each dev.
Doom9
2nd April 2008, 19:35
You know, back in the day when I was running the megui show, there were a couple of times where I was pretty darned close to just throwing the towel because I was so sick and tired of people constantly bitching about something I invested large part of my free time of over one year. Imagine working for a charity and instead of being grateful, the people you help constantly give you grief. At some point you've just had it.
Try to see it from a different perspective: if you're reasonably proud of your product, if somebody comes along and screams bug, without doing anything even remotely related to proper verification, basically they call your work defective even though it isn't. That's not a compliment you're looking for. The least bit of courtesy you should show every freeware developer is proper research before calling something defective. Unless you are sure something is broken, don't call it broken. Similarly, if the answer is no, leave it at that, even if you do not understand the reasons. Your time would be better spent learning to code and make the change yourself if you find it worthwhile (and being a community project changes are still subject to approval before being committed into the mainline code.. that's how it works for open source projects in general) - rarely should you insist if you are really certain that the person on the other end just didn't understand your idea (often, images can help in such a case.. words can be misconstrued a lot more easily). Similarly, if people take away your time with trivial things.. it is just a waste of your time and you could do more useful things in the meantime. Accumulate just a few minutes of wasted time each day.. it eats away at you.
P.S. Every so often I also encounter people that treat me in a way where I feel it would be better if I just closed down the site and moved on to something different. You get used to the obvious insults, but every now and then somebody really finds that hole in your body armor and really thrusts the blade in - and it takes a lot to come back from that. Just as in real life, some things really get to you - the other party might not even realize their mistake since we don't have facial expression and body language online. The reaction might be too strong - but in the end we're all human and each and everybody reacts differently.. haven't you ever said or done something in the heat of the moment that you wouldn't have done if you had spent an hour cooling off (doing sports, smashing something until you can no more, etc.)?
bob0r
3rd April 2008, 10:53
Well whatever the future may hold, i love megui, and apparently so do thousands of other users.
0.01% LOUD complaining people
99.99% silent happy users
MeGUI + x264 is an absolute killer combination for proper video encoding!!!
@sharktooth
Thanks for adding x264 808M (ghost edition :D) to megui!!
See you soon cowboy..... FFFFINISH HIM!
Kurtnoise
4th April 2008, 14:23
well, I'm still there...coz I would like to implement and update several things this weekend.
rack04
4th April 2008, 14:52
well, I'm still there...coz I would like to implement and update several things this weekend.
Hip Hip Hurray! Thanks for your continued effort in developing this great program.
~bT~
4th April 2008, 14:57
@ Kurtnoise13
thank you sir!!!
trex
4th April 2008, 15:06
@ Kurtnoise13
I have been the more silent forum member here so far but I want to let you know that MeGUI is my favorite encoding UI.
I would love to see it further developped in the future.
:)
Best, trex
Mutant_Fruit
4th April 2008, 15:07
Just a quick update as to the status of the Mono port.
At the moment I'm tied up with no free time to spend on MeGUI. Monsoon, the GUI for the bittorrent library I develop has recently been accepted (http://monotorrent.blogspot.com/2008/04/there-was-meeting-yesterday-for.html) to the Suse linux distribution. I have two weeks before feature freeze, and 4-6 weeks before commit-freeze.
So i probably won't be doing too much of anything else between now and then. I've a lot to be working on ;)
As to the recent debackle that the MeGUI devs had, i think this link may be helpful. I watched it a few days ago and it's definitely changed my outlook on how to deal with bugreports/contributors to opensource projects:
http://video.google.nl/videoplay?docid=-4216011961522818645
Theliel
4th April 2008, 19:49
My English isn't good enough for explain the gratitude and respect that (i'm sure) the most of us have with Shark and Kurtnoise.
It's true that sometimes all of us can be very... arrogant? or we write incoherent post or... but all your work are unquestionable and very important for all of video coding World, and the same words for others members like our friend Loren and others, that make all of this possible, in all grades
mroz
5th April 2008, 04:50
@Kurtnoise13: Great to know you're still active :)
@Mutant_Fruit: Seriously informative vid from the SVN guys - I've just watched the whole thing, despite meaning only to take a brief look. Most of the projects whose development I track could benefit from applying those ideas.
Sharktooth
5th April 2008, 13:39
Mutant_fruit: that's why we asked to use the megui trackers on SF. so we can have more control and a "centralized view".
ill ask the mods to close all the topics regarding megui except this one.
~bT~
5th April 2008, 13:58
^ closing all topics wouldnt be right. there will be 20 new threads created each day for minor megui issues..
Kurtnoise
5th April 2008, 15:59
beta testers needed to test the new AQ part (http://www.mediafire.com/?1xd3mh6rxen)...Zones has been reintroduced but doesn't work yet.
@devs: I switched the B-Frames part to the Main tab to introduce AQ in the Advanced one. Is it ok ? what do you think about that ?
bob0r
5th April 2008, 16:24
Where would you like reports of cosmetical fixes and stuff like --filter = --deblock and --analyse = --paritions in the future?
Cosmetical fixes like:
x264 config > RC and ME > Quant options:
Mixed Reference frames
Mixed Reference Frames
f > F
x264 config > RC and ME > Misc:
Encoder interlaced
Encoder Interlaced
i > I
.... and many more small none consistency examples in the Advanced tab :)
Want me to name them all? :)
so all the less important stuff....
Kurtnoise
5th April 2008, 17:36
Where would you like reports of cosmetical fixes and stuff like --filter = --deblock and --analyse = --paritions in the future?
Cosmetical fixes like:
x264 config > RC and ME > Quant options:
Mixed Reference frames
Mixed Reference Frames
f > F
x264 config > RC and ME > Misc:
Encoder interlaced
Encoder Interlaced
i > I
.... and many more small none consistency examples in the Advanced tab :)
Want me to name them all? :)
so all the less important stuff....
sure...http://sourceforge.net/tracker/?group_id=156112&atid=798476
tebasuna51
6th April 2008, 03:11
@dev's
I suggest replace the NicAudio.dll by NicAudio.dll v2.0 (http://www.codeplex.com/NicAudio).
The NicAc3Source function is improved to solve some bugs detected:
- changes in 'dsurmod' (http://forum.doom9.org/showthread.php?p=1071652#post1071652)by mroz
- problems with some 'acmod' values (http://forum.doom9.org/showthread.php?p=976506#post976506) by Raven2x using MeGui.
- and mroz Dual mono MeGui bug (http://sourceforge.net/tracker/index.php?func=detail&aid=1865246&group_id=156112&atid=798476)
Some changes in AviSynthAudioEncoder.cs are needed:
case ".mpa":
case ".mpg":
case ".mp2":
// script.AppendFormat("NicMPASource(\"{0}\"){1}", audioJob.Input, Environment.NewLine);
// break;
case ".mp3":
script.AppendFormat("NicMPG123Source(\"{0}\"){1}", audioJob.Input, Environment.NewLine);
break;
The NicMPASource function don't exist in v2.0 because is replaced with NicMPG123Source with support for VBR (also for mp2).
NicMPG123Source updated to new version (http://forum.doom9.org/showthread.php?p=1102957#post1102957) (mpg123-lib of the LAME project)
And I suggest use also RaWavSource (included in NicAudio v2.0) for wav (WAVE_FORMAT_EXTENSIBLE header supported) and also other uncompressed formats always supporting files > 4GB.
See the Kurtnoise MeGui Feature request (http://sourceforge.net/tracker/index.php?func=detail&aid=1830524&group_id=156112&atid=798479):
case ".wav":
case ".w64":
case ".aif":
case ".au":
case ".caf":
case ".bwf":
script.AppendFormat("RaWavSource(\"{0}\", 2){1}", audioJob.Input, Environment.NewLine);
break;
Finally the Bass libraries can avoid the problem of use DirectShow filters to decode some common formats like aac, ogg, flac, wma, ...
Most users have DirectShow configured to stereo output (and other settings for the audio equipment attached to the PC), not aproppriate for transcoding tasks.
The new version 2.4 and some changes in BassAudio.dll (AviSynth interface) seems guarantee correct decoding for:
case ".ogg": // (1) = BassAudio.dll 2.4, Bass.dll 2.4 required
case ".mp1": // (1)
case ".aac": // (1) + bass_aac.dll 2.4
case ".m4a": // (1) + bass_aac.dll 2.4
case ".mp4": // (1) + bass_aac.dll 2.4
case ".wma": // (1) + bass_wma.dll 2.4
case ".flac": // (1) + bass_flac.dll 2.4
// case ".alac": // (1) + bass_alac.dll 2.4
// case ".wv": // (1) + bass_wv.dll 2.4
// case ".ofr": // (1) + bass_ofr.dll 2.4 + OptimFROG.dll
// case ".ape": // (1) + bass_ape.dll 2.4
// case ".tta": // (1) + bass_tta.dll 2.4
// case ".cda": // (1) + bass_cda.dll 2.4
// case ".mpc": // (1) + bass_mpc.dll 2.4
// case ".spx": // (1) + bass_spx.dll 2.4
script.AppendFormat("BassAudioSource(\"{0}\"){1}", audioJob.Input, Environment.NewLine);
break;
The commented lines are options untested and, maybe, unnecesaries to MeGui.
BassAudio.dll 2.4 can be obtained from this post (http://forum.doom9.org/showthread.php?p=1112359#post1112359) and can be distributted with MeGui (Author Dimzon, modified by me), Bass.dll and the others can be free downloaded, for non-commercial use, from http://www.un4seen.com/bass.html
Kurtnoise
6th April 2008, 07:38
@dev's
I suggest replace the NicAudio.dll by NicAudio.dll v2.0 (http://www.codeplex.com/NicAudio).
you read in my mind...;) it's my plan for today.
Finally the Bass libraries can avoid the problem of use DirectShow filters to decode some common formats like aac, ogg, flac, wma, ...
Most users have DirectShow configured to stereo output (and other settings for the audio equipment attached to the PC), not aproppriate for transcoding tasks.
maybe...but personally, I'm more interested by the FFmpegSource filter. :)
tebasuna51
6th April 2008, 10:22
maybe...but personally, I'm more interested by the FFmpegSource filter. :)
Of course, many people are interested in ffmpeg project, but is usable actually for audio decode?
From ffmpegsource help:
"Note that the audio cache will always be created when opening files with audio and that it will be huge since it stores all audio as raw signed 16/24/32 bit pcm, unsigned 8 bit pcm or as float, using flac to compress it is also possible to reduce the size by half."
If we need a 3.67 MB FFmpegSource.dll to decode an aac to a huge uncompressed wav maybe is better use faad before. Work with files > 4GB?
BassAudio, Bass, Bass_aac, Bass_flac, Bass_wma dll's are 0.34 MB and don't need write huge files in disk.
Maybe in the future we can use ffmpeg to decode/encode everything (also EAC3, MLP, TrueHD, ...) but now I recommend use BassAudio for BeHappy. :rolleyes:
Kurtnoise
6th April 2008, 10:30
Agreed...just hoping that this part will be improved in the future.
coz some new stuff from FFmpeg (aac decoder, dts encoder, eac3 decoder, etc...) is going to be introduced...
Atak_Snajpera
6th April 2008, 22:30
I suggest replace the NicAudio.dll by NicAudio.dll v2.0.
Do not use it (2.0) for MP3 and MP2 decoding. I had corrupted sound after conversion. BassAudio works very well :)
tebasuna51
7th April 2008, 00:46
Do not use it (2.0) for MP3 and MP2 decoding. I had corrupted sound after conversion. BassAudio works very well :)
Please use this thread (http://forum.doom9.org/showthread.php?t=135876) or http://www.codeplex.com/NicAudio to report NicAudio 2.0 bugs.
Maybe you can upload some samples with the problem. I can't see differences with my samples.
check
7th April 2008, 14:20
Gosh, look what you miss when you're gone for a few weeks :)
Anway, I thought I'd give an update here on how popular the MeGUI autoupdate cache is. If you want these quarterly updates out of the dev thread let me know.
General Summary
This report contains overall statistics.
Figures in parentheses refer to the 7-day period ending 07-Apr-2008 18:00.
Successful requests: 1,445,741 (115,081)
Average successful requests per day: 14,591 (16,440)
Successful requests for pages: 380,049 (30,967)
Average successful requests for pages per day: 3,835 (4,423)
Failed requests: 10,124 (2,872)
Redirected requests: 193 (4)
Distinct files requested: 380,136 (31,060)
Distinct hosts served: 106,080 (11,591)
Corrupt logfile lines: 42
Unwanted logfile entries: 1,709,881
Data transferred: 533.99 gigabytes (42.49 gigabytes)
Average data transferred per day: 5.39 gigabytes (6.07 gigabytes)
tebasuna51
9th April 2008, 03:33
Do not use it (2.0) for MP3 and MP2 decoding. I had corrupted sound after conversion. BassAudio works very well :)
The bug in the new version of mpg123-lib don't affect to Megui/BeHappy but yes to Bepipe.
The new MPASource.dll from WarpEnterprises (http://forum.doom9.org/showthread.php?p=1123600#post1123600) is also affected.
A bugfix release of NicAudio.dll (v2.0.1) are available.
Sharktooth
9th April 2008, 12:53
beta testers needed to test the new AQ part (http://www.mediafire.com/?1xd3mh6rxen)...Zones has been reintroduced but doesn't work yet.
@devs: I switched the B-Frames part to the Main tab to introduce AQ in the Advanced one. Is it ok ? what do you think about that ?
i thought a different design:
http://www.webalice.it/f.corriga/x264/x264config.png
AQ options can be placed in the down-left corner in the empty space.
That will also avoid to rewrite the b-frames controls code... ;)
Oh, btw, in the picture above it should be "Quantizers ratio" (not quantization ratio) :(
Kurtnoise
9th April 2008, 20:14
well...it's ok for me but (yeah, there is a but ;))
Honestly, it depends on what we want to do : just an update to have AQ or improve this part completely...I think that the UI for video encoders, at least, must be completely redesigned. If you don't mind I'll put something online this weekend about that but the discussion is open of course. :)
Sharktooth
9th April 2008, 21:56
i see ppl discussing about the profiles and much less about the settings.
fact is ppl dont like to mess with settings since most of them dont know what those mean, plus the golden programmer rule: if it aint broke, dont fix it
however if you feel to make changes, there's no problem on my side but if you do it, ensure it works properly before committing any changes or ppl (as you saw) will moan like bitches.
a new 0.3.x build is needed too coz a shitload of stuff was added/fixed/changed but never tested, so i will wait your changes before making a new one.
Kurtnoise
10th April 2008, 16:59
all new stuff that I added in the dev branch has been tested properly and it works fine...;)
About the changes in the UI : i'll post some builds online (or patches...as you want) before to commit something. don't worry.
bob0r
10th April 2008, 22:54
Hmm it seems i forgot to press Submit after Preview, so here goes again:
@Sharktooth
Can you please update new x264 816 modified:
http://forum.doom9.org/showthread.php?p=1124122#post1124122
--threads auto now auto-enables --thread-input, so especially usefull for windows (avs) megui users....
(75 to 95fps SD video)
(9 fps to 15fps HD video)
Sharktooth
11th April 2008, 03:42
megui already does that when threads = auto or threads > 1
however i'll update it as soon as i find a minute :)
Kurtnoise
11th April 2008, 13:02
--threads auto now auto-enables --thread-input, so especially usefull for windows (avs) megui users....
what does it mean ? we need to change the command line ?
vBulletin® v3.8.11, Copyright ©2000-2025, vBulletin Solutions Inc.