MeGUI Feature Request Thread

[Doom9]

geez.. doing the whole movie is in the same league as using esa me ;) But I agree that everything should be runnable at idle priority.

[ChronoCross]

geez.. doing the whole movie is in the same league as using esa me ;) But I agree that everything should be runnable at idle priority.

That's why I made the some people are anal retentive about quality testing statement in the x264 and megui discusion threads about esa lol

[berrinam]

@ChronoCross: If you're willing to subject yourself to such long analysis, would you perhaps be willing to share your results with me? My last commit added diagnostics to Source Detection, so it shares much more information about what it's doing now. I wonder how much more accuracy you get by doing 100% as opposed to 1%.

If you're interested, I simply ask that when you analyse something, analyse it both at 100% and then at 1%, and show me the results. The idea is that they should be the same, but who knows?

[ChronoCross]

yeah sure. I'll run it now.

[fogbav]

Automatic Encoding All .TS Files and MPG Files from A Directory ans Subdirs ... Encode Video with fixed PRofile XXX AC3 with fixed Audio Profile YYY and all MP2 Tracks with Audio Profile ZZZ ...

Would be very usefull for all Dbox2 Owners recording streams to a special Folder an get them compressed when they are at work ..8)

Tagging working Folders make it possible to encode from different PCs so 2 or more "Encodings" can happen trough a Network share to the "recording folder"

[berrinam]

I'm not Doom9, but I'm pretty sure that I know what his response is going to be: no way. It requires a huge amount of organisation and has so many ways that the user could stuff it up, and what are the benefits? It saves a tiny amount of time in user setup (of course, the user could set it up with the one click encoder in MeGUI anyway, which is already very easy) for some few people who havze Dbox2s.

[fogbav]

Hmm ... sad to here this ... i programmed some lines with kixtart and everything work very well with all command lines put up in some "spagetti code" programming ... 8)

ts -> ProjectX -> Xvid/mp4 (over ini file - configure Codec +passes)-> Audio --> AAC 5.1 and AAC v2 with winamp codec -> Mp4box -> delete org files ...

but my programming know how is not the best ... so I thought it was a good idea to request this to the profis here in this way ...

Maybe a can spend some time with AUTOIT to transfer all files to the "one Click" encoder in megui and get my autoenconding ...

I have a time eating job and 2 kidz so the only way to get space free on my HD is to programm something that is doing the job for me ... and .. everything exists in Megui / StaxRip etc ...

anyway ... thanks

FoGBaV

[dimzon]

time eating job and 2 kidz so the only way to get space free on my HD is to programm something that is doing the job for me ...
Or teach Your wife how to use MeGUI ;)

[ChronoCross]

Request: A Button that allows for megui to always be shown in the tray.

[berrinam]

Request: A Button that allows for megui to always be shown in the tray.
Why?

Also, do you have any news on the Source Detector? Just to jog your memory:

@ChronoCross: If you're willing to subject yourself to such long analysis, would you perhaps be willing to share your results with me? My last commit added diagnostics to Source Detection, so it shares much more information about what it's doing now. I wonder how much more accuracy you get by doing 100% as opposed to 1%.

If you're interested, I simply ask that when you analyse something, analyse it both at 100% and then at 1%, and show me the results. The idea is that they should be the same, but who knows?
yeah sure. I'll run it now.
If you haven't got any results, then never mind for the moment, because I'm planning on slightly modifying the Source Detector again, so that it uses tritical's IsCombedTIVTC, which is more accurate than DeComb's IsCombed.

[berrinam]

A feature request of my own:

Add extensive commandline implementation for MeGUI. Although it is meant to be a front-end and nothing else should need to run it, commandline support could lead to integration into the shell, meaning you could right-click on a media file and select 'Open With MeGUI' or 'OneClickEncode with MeGUI', etc.

[stax76]

Add extensive commandline implementation for MeGUI. Although it is meant to be a front-end and nothing else should need to run it, commandline support could lead to integration into the shell, meaning you could right-click on a media file and select 'Open With MeGUI' or 'OneClickEncode with MeGUI', etc.

Maybe you like my CLI architecture, it has a nifty parser as well as a command engine like Visual Studio, the command engine is powered by attributes and reflection and drive both, the menus and the CLI. Adding a new CLI switch is as simple as adding a new method:


<Command("Show Message Box", Nothing)> _
Public Sub ShowMsgBox( _
<Name("Message"), Description("The message may contain macros."), Editor(GetType(MacroStringTypeEditor), GetType(UITypeEditor))> _
ByVal message As String, _
<Name("Title"), Description("The title may contain macros."), DefaultValue("StaxRip"), Editor(GetType(MacroStringTypeEditor), GetType(UITypeEditor))> _
ByVal title As String, _
<Name("Icon"), DefaultValue(GetType(MsgIcon), "Info")> _
ByVal icon As MsgIcon)

Msg.Show(Macro.Solve(message), Macro.Solve(title), icon)
End Sub


After adding the method the command is now available at the menus (http://www.planetdvb.net/staxrip/screenshots/038.png) as well as at the command line:

StaxRip.exe -ShowMessageBox:a_string,"a string in quotes",Info

That means no manual commandline parsing and all types with a TypeConverter will work which include primitive types (IConvertible) and enums and lots of other framework types like Point, Size etc.

As you can see it uses the syntax of the .NET framework tools, the syntax rocks from both, user and development (parsing) perspective. The parser is not case sensitive and supports '/' as prefix like: /showmessagebox:arg,arg2...

[berrinam]

What do other people think about this: ability to customise scripts used for Source Detection.

Basically, this would mean that instead of having two scripts hard-coded into MeGUI, these two scripts would be accessible via the Source Detector settings. The scripts could be edited by the user and MeGUI would accept them as long as they returned the correct variables within AviSynth.

Pros:
-Customisability -- it could make it easier for the user to change the Comb detection (or something else) to a more accurate method. For instance, my next update will include a change from IsCombed to IsCombedTIVTC, which is much more accurate.

Cons:
-More work for me.
-Many more ways to stuff up.
-Mainstream users probably won't have a clue/won't wont to experiment with these scripts anyway, so for most people it is just a useless feature.

I'm leaning towards not doing it, because it's more work for me and I can't see much in the way of tangible benefits. If someone can give me a good reason to allow it, though, I'll consider going the whole way and giving the user complete control over these scripts.

[Sharktooth]

uhm... naah.

[ChronoCross]

same....by being able to customize it, it means you have enough knowledge of IVTC just to do it manaully anyway.

[Bathrone]

Im just learning MeGUI and AVC encoding so apologies for any user errors :) Also, love the work so far on MeGUI and x264 :)

How about extending the mux capabilities to be able to demux as well? And be able to mux in more streams like an additional audio one after the file has been done.

And with the D2V creation, being able to put start and end points rather than having to go into DGIndex to set it if the user doesnt want to transcode the whole thing.

I wonder too if there is a way to prevent user's changing Sharktooth's profiles by mistake?

[ChronoCross]

I wonder too if there is a way to prevent user's changing Sharktooth's profiles by mistake?

You can't currently change the profiles. If you make a change tp the profile it's simply made to the settings. if you reselect the same profile whatever you changed will change back to what the profile is.

[berrinam]

How about extending the mux capabilities to be able to demux as well? And be able to mux in more streams like an additional audio one after the file has been done.You should use a dedicated muxing tool to do this -- YAMB for MP4, or mkvToolnix for Matroska.

And with the D2V creation, being able to put start and end points rather than having to go into DGIndex to set it if the user doesnt want to transcode the whole thing.That's really just video cutting. It's not so important to do it in DGIndex, as long as it is done somewhere before the encoding is done. This cutting will eventually be implemented in Avisynth, but it will probably be a while from now, so you'll just have to be patient until then.

I wonder too if there is a way to prevent user's changing Sharktooth's profiles by mistake?
You can't currently change the profiles.That's obviously not right. How would anyone manage if they couldn't changing them. I think I know what you mean, though. If you select a profile in the main window, then press config, modify it and press ok, then you won't have changed Sharktooth's profile. However, you shouldn't rely on this, because this is in fact a documented bug.

In fact, there was a feature called Safe Profile Alteration, but I believe it has been removed from MeGUI because it was a hassle and not particularly useful to us. It would be a good idea to check the settings to see if it is actually there, but if it isn't, then it's just up to the user not to fiddle with what they don't understand.

[dimzon]

You should use a dedicated muxing tool to do this -- YAMB for MP4, or mkvToolnix for Matroska.
Maybe we can add support for this into MeGUI? Why not?

[berrinam]

Maybe we can add support for this into MeGUI?What, specifically, do you mean by this?
Why not?What does it add to MeGUI's purpose, which is to be a frontend for encoding?

In particular, what advantage is there in integrating it into MeGUI as opposed to running it as a separate, already-working tool? It's good having primitive muxing in MeGUI, because it means that entire encodes can be managed automatically. But unless demuxing can be somehow integrated into an automated workflow in MeGUI, then it saves the user basically no work by our putting it in MeGUI, but it takes a lot of work for us to replicate YAMB's code (or mkvmergegui's, which is even more powerful).

[dimzon]

In particular, what advantage is there in integrating it into MeGUI as opposed to running it as a separate, already-working tool? It's good having primitive muxing in MeGUI, because it means that entire encodes can be managed automatically. But unless demuxing can be somehow integrated into an automated workflow in MeGUI, then it saves the user basically no work by our putting it in MeGUI, but it takes a lot of work for us to replicate YAMB's code (or mkvmergegui's, which is even more powerful).

MkvMerge has it's own GUI so I doesn't propose to implement yet another Matrosska muxer

But YAMB is "third-party" tool. I really think it's better to invite Kurtnoise to join in MeGUI development and move all YAMB functionality into MeGUI... YAMB is not stable until MP4BOX is beta. So Kurtnoise must perform adaptation sometimes for ne MP4BOX version. In other case we must support muxing part of code too... So joining MeGUI and YAMB we will get all code in one place, it's much easy to support

[berrinam]

In other case we must support muxing part of code too... So joining MeGUI and YAMB we will get all code in one place, it's much easy to support
It's not really going to be such a big hassle to change MP4Box code in MeGUI -- all of the relevant code should be contained in the one generateMP4BoxCommandline function. However, integrating YAMB into MeGUI could be a fair bit more work, and there is still no benefit for the user. Also, it just makes MeGUI even more bloated.

[dimzon]

However, integrating YAMB into MeGUI could be a fair bit more work, and there is still no benefit for the user. Also, it just makes MeGUI even more bloated.
I doesn't think is too hard to implement it. And I really dislike to use too much applications at once - so I prefer to add additional functionality to MeGUI. And other users doe't like it too. Really you need different applications to encode / mux / split / extract MP4. In opposit way VirtualDub perform everything in one application. This (usability/comfort) is one of reason why users prefer x264 VfW and AVI container. Anycase this work can be done/planned with lowest priority...

[berrinam]

I can partly understand your reasons for wanting it.... just two final questions:
What exactly do you have in mind for it?
If we are going to put the level of flexibility with editing that VDub allows into MeGUI (which I think is a good idea for SOME application; not necessarily MeGUI), then wouldn't it be better to go the whole way and support matroska cutting as well. Once the GUI is done, the generation of the commandlines are trivial by comparison, as long as the code is well-designed.

[Doom9]

In fact, there was a feature called Safe Profile Alteration, but I believe it has been removed from MeGUI because it was a hassle and not particularly useful to us.No, it's still there, but I noticed that it hasn't been updated when a codec's option get updated. And profiles are updated just fine.. just switch between two of them in a codec configuration dialog.

but it takes a lot of work for us to replicate YAMB's codeDid you say lot? You probably mean LOOOOOOOOOOOOTS.. it would add another dimension to the "ideal mux path" finding (and the ideal encoder output finding.. that's already two dimensions too many).. and that code is making me insane as it is.

[dimzon]

it would add another dimension to the "ideal mux path" finding
Why? Maybe Your code have suboptimal architecture? Anycase we must wait until Your commit...

[berrinam]

A few things to consider:

If MeGUI is meant to target an audience that knows nothing about video encoding (that's what I imagine the One Click Encoder is for), then it might be worthwhile adding some kind of 'quality' scheme, as a %, like other commercial programs do (wmeconder, for example). This would basically be implemented as a codec-specific mapping from a quality % to quantizer or crf-type mode.

Add extra support for Drag'n'Drop in the other windows. So, in a mux window, you could drag all the inputs in.

Also, I wonder how useful the 'and close' feature in the D2V creator and One Click Encoder is. Perhaps it would be better if it were checked by default, because the default behavior ATM is that pressing Queue/Go gives no indication that anything has happened. In fact, MeGUI has several quirks like this that make it confusing for the new user.

[kurt]

Feature Request for xvid_encraw: cqm support with squid_80's build should work (maybe in cvs too?) - could this also be included in MeGUI?

and what about adding a custom commandline option in the xvid encoder dialog? (this feature exists for x264 under zones)

thx in advcance
(sorry, if this has been asked before)

[Doom9]

Feature Request for xvid_encraw:all of the options of squid's build are already supported in the code on my harddisk.. but it's other parts that are extremely broken so it will take weeks if not month before the whole thing is usable again. Add to that that I'm under constant deadline pressure at work so at home I really don't feel like writing more code.

[kurt]

ok, Doom - thx for the clarification and there's no need to rush :)

[cc979]

is it possible, on the log screen to have a clear log function because would quicker than reloading it, easier to kept track of things on multible encodes and it would save you from re-opening files too

[berrinam]

is it possible, on the log screen to have a clear log functionYep, it's possible.
because would quicker than reloading it, easier to kept track of things on multible encodes and it would save you from re-opening files tooI don't understand what you are saying.

[cc979]

i must have been really tired, i meant it would be easier to clear the log screen - than reloading megui with opened avs files - so you could make profile changes quickly on test encodes and at a quick clear log encode and see problems quicker

cheers

[cc979]

after reading thru the dev section and seeing all talk macros, magic numbers and things with saved settings and that

could it be possible to save the script from the main screen in some sort of xml file with all the settings, SAR, DAR included so you can encode stuff later and not worry and possibly with option to re-save it as as .avs script

[cc979]

just curious do the anime presets in Convolution3DYV12.dll work ok, i have added them to the ScriptServer.cs file seems ok

[Ogig]

(Didn't know whether to post in bug thread or here, hope it's the right place.)

When using the Avisynth Script Generator I noticed that 720 is the maximum width. Is there a reason for this limitation ?

[GmorG McRoth]

I'm not sure if somone else mentioned it already (If so, I'm with him), but could it be possible to change color of font in status window? currently is unreadable in most of windows themes I like to use. Screen shot (http://gmorg.mcroth.googlepages.com/window.jpg)

[berrinam]

When using the Avisynth Script Generator I noticed that 720 is the maximum width. Is there a reason for this limitation ?Yep -- your source is only 720 pixels wide, and there's no point in upsizing unless you use a very advanced upsizer like iiP, in which case MeGUI can give you no help.

I'm not sure if somone else mentioned it already (If so, I'm with him), but could it be possible to change color of font in status window? currently is unreadable in most of windows themes I like to use. Screen shot (http://gmorg.mcroth.googlepages.com/window.jpg)
No. The font works well in the standard Windows themes, and there have been many other people posting skinned screenshots with no troubles like that. I don't know, but I'm pretty sure that MeGUI skins properly, so if there's something up, I would say there is something wrong with your font. And it simply requires way too much work to make every font skinnable. Perhaps dimzon can contribute his experience with HTMLayout (http://forum.doom9.org/showthread.php?p=806360#post806360) to helping your problem, but other than that, I would say it is way too much work.

[berrinam]

i must have been really tired, i meant it would be easier to clear the log screen - than reloading megui with opened avs files - so you could make profile changes quickly on test encodes and at a quick clear log encode and see problems quickerI can't really see the benefits, but I don't imagine it would be too much work, either, so I've added it to the list. I'm also considering a different approach to the log (see my next post no, don't. I changed my mind) which may mean this isn't necessary.
could it be possible to save the script from the main screen in some sort of xml file with all the settings, SAR, DAR included so you can encode stuff later and not worry and possibly with option to re-save it as as .avs scriptWhat is there to store other than SAR/DAR?

[dimzon]

Perhaps dimzon can contribute his experience with HTMLayout (http://forum.doom9.org/showthread.php?p=806360#post806360) to helping your problem

Actually I want test IUI paradigm and HTMLayout in BeHappy and (if success) propose it to MeGUI ;) Actually current MeGUI look and feel is too complex for novice.

[berrinam]

Two AviSynth-related ideas:

Cropping can be done by the resizer. This is undoubtedly faster, and I think it also allows for mod1 cropping, which is much better than at the moment. To integrate this into the script creator (which I think we should), the templates would need to be reorganised, because there is no guarantee that they are going to be consecutive. I propose the addition of another tag, <resize-crop>, which will insert the resizer with cropping if relevant.

According to foxyshadis, ColorMatrix() is a good idea on most sources, as DVDs tend to use Rec.701 and MPEG-4 uses Rec.601 (I have no idea about the numbers or what they mean, I'm just taking it on trust). More importantly, DGDecode hints the stream, so that ColorMatrix() will autodetect the right thing to do. So it won't be bad in any cases. I think, then, that ColorMatrix should be checked by default, not unchecked.

I said I was going to propose another idea about the log. I've changed my mind -- I don't like it.

Actually I want test IUI paradigm and HTMLayout in BeHappy and (if success) propose it to MeGUI ;)Yes, sure. I was just saying that this might be a solution sometime in the future.

Actually current MeGUI look and feel is too complex for novice.I totally agree. MeGUI still needs a lot of work, but it is very promising.

@dimzon: Would you be willing to implement this:
Be able to choose the sampling rate for audio
Description: See quake74's post (http://forum.doom9.org/showthread.php?p=764825#post764825)
Status : Nobody is working on it.

[dimzon]

@dimzon: Would you be willing to implement this:
No problem - but I'm waiting Doom9 refactoring first (to drop out BeSweet support). Actually current Doom9 refactoring is a huge bottleneck for development...

[GmorG McRoth]

No. The font works well in the standard Windows themes, and there have been many other people posting skinned screenshots with no troubles like that. I don't know, but I'm pretty sure that MeGUI skins properly, so if there's something up, I would say there is something wrong with your font. And it simply requires way too much work to make every font skinnable. Perhaps dimzon can contribute his experience with HTMLayout (http://forum.doom9.org/showthread.php?p=806360#post806360) to helping your problem, but other than that, I would say it is way too much work.

I know I have no right to complain, It is free software. I was just asking for improvement. I have little to no programming knowlage, I was thinking that changing font color is not a big deal, but if you say, its much to rewrite, to change one font, it's indeed bigger chore than it's worth. I attach, for your consideration screenshots of other skins.

windows default:
XP Blue (http://gmorg.mcroth.googlepages.com/XPblue.jpg)
XP Olive (http://gmorg.mcroth.googlepages.com/XPolive.jpg)
XP Silver (http://gmorg.mcroth.googlepages.com/XPsilver.jpg)
Windows Classic (http://gmorg.mcroth.googlepages.com/ClassicWindows.jpg)
Windows Classic High Contrast (http://gmorg.mcroth.googlepages.com/Classicwindowshighcontrast1.jpg) (works best XD)

Custom Thames:
Lamina RC (http://gmorg.mcroth.googlepages.com/LaminaRC.jpg)
ReLuna - Bluetiful (http://gmorg.mcroth.googlepages.com/RElunaBluetiful.jpg)
ReLuna - Em3lent (http://gmorg.mcroth.googlepages.com/window.jpg)
Sustenance - Slate (http://gmorg.mcroth.googlepages.com/Sustenance-Slate.jpg)

I hope I did not taken too much of your time.

[foxyshadis]

The problem is more that it uses the disabled text color than that it uses grey, making it harder to read than it needs to be. Do they have to be disabled textboxes instead of captions?

[Ogig]

Yep -- your source is only 720 pixels wide, and there's no point in upsizing unless you use a very advanced upsizer like iiP, in which case MeGUI can give you no help.

What about anamorph encoded content. See http://forum.doom9.org/showthread.php?t=106987 for details.

[berrinam]

What about anamorph encoded content. See http://forum.doom9.org/showthread.php?t=106987 for details.What about it? Just check 'Retain full resolution and set SAR in encoder' and then you're done. Still no need to upsize.

[thuongshoo]

I have just tried to use Megui . Speed of it isn't quick .Only 2 frm/s . Can you add "stream data pipeline " ?
http://img117.imageshack.us/img117/9162/pipeline7xs.th.png (http://img117.imageshack.us/my.php?image=pipeline7xs.png)
thanks !

[Doom9]

megui has very limited influence on speed.. it does nothing complex with the stdout from the encoder. And those settings would affect an encoder.. megui is just a control software, it has no influence on buffers within an encoder software.

Actually current Doom9 refactoring is a huge bottleneck for development...I posted the sources on Thursday so that you can help speed up the process ;)

@GmorG McRoth: If you can show me that MeGUI violates Microsoft suggested design guidelines by using read-only textboxes, this is a problem of whomever designed those skins and any other software using read-only textboxes will run into the exact same problem.. so the skin's bad, not the software. I have never liked skinnable software and anything that doesn't adhere to the platforms normal look and design.. breaking style makes it a lot harder for users to get to know a certain software.

[GmorG McRoth]

@Doom9 I don't know microsoft design guidelines, also I had no idea that they were "disabled textboxes" untill foxyshadis said so. For me grey text on grey background is design flaw so I tried to bring it to developers atention. As I see it's mostly microsoft foult for making "disabled textboxes" font color setting hiden somewhere in system (or in skin file). Ill try to fix this on my side then.

Thanks for MeGUI by the way it's great software despite this one thing.

[thuongshoo]

I'm not a programmer . If using x264.exe , can we make function "stream data pipeline" ?
Virtualdub can't use aac encoder and make .mp4 . What's a pity .