MeGUI Feature Request Thread

[check]

You mean like what's in the tools menu?

[rollow]

OK. I know it may not be a very good idea to start again about Quicktime. But...it would be really great to be able to use QT source in megui. I received a big box of digibeta tapes today, and I need to encode to H264. Not painfully slow, like in QT player, or flaky, like in Squeeze, or ... well let's not even mention Procoder or Compression Master.

Why QT? Because my Decklink Extreme card produces brilliant source files using SDI. Because my clients provide me with .890 Cavena and EBU .stl subs which I convert with Belle Nuit to QTText, so I have total control over subs in my encodings.

Avisynth and the qtreader thingy don't work. Converting to avi is an option, but it doesn't make sense at all. Maybe I'll have to ask my client to send DVD's instead of digibeta's.

[berrinam]

Is there a feature request somewhere there? It seems like you want us to pull some form of QTSource out of thin air, since you don't want us to use AviSynth's

[rollow]

Is there a feature request somewhere there? It seems like you want us to pull some form of QTSource out of thin air, since you don't want us to use AviSynth's

Yes, a feature request indeed. Am not saying you need to pull it out of thin air, just hoping to restart the QT src discussion and being open to help developing it in any way.

[Kurth]

Can you add an option to the MKV Muxer to insert Timecodes.txt I always use VFR for my animes but I cant mux MKV using the MeGUI MKV muxer because it dont have a place to insert the timecodes.

[berrinam]

@Kurth: Will consider it, but MeGUI shouldn't become a full-blown muxing GUI -- that's what the other tools are for.

@rollow: Bring it up in the AviSynth forum. That's where it really belongs.

[foxyshadis]

@rollow: http://forum.doom9.org/showthread.php?t=104293 this is the thread you should follow.

[rollow]

THX a lot!

[jellysandwich]

Is there already an option for automatic minimization to system tray? I can't find it... Where is it exactly?

js

[Audionut]

The option to have megui only notify of NEW updates.

ie: I load megui and tell it what I want to update.
Every time I load megui it tells me that there are updates.

Either the ability to decide what the user has not updated and only notify when those components have been updated.
Or an option to disable checking for updates on components.

[berrinam]

@Audionut: Have you tried selecting the things you don't want to update, right-clicking, and pressing 'ignore updates'? I think that should work.

[Audionut]

Thanks!!

[berrinam]

Hmm..... tricked Doom9 as well.... I would have thought right-clicking was an obvious thing to try.

[Audionut]

I did try and right-click the options on the left.

ie: external programs, avisynth plugins etc.

IMHO it would be alot more handy to be able to disable say avisynth plugins completely, rather than each and every filter.

Thanks.

[shon3i]

@berrinam can you make that updater remove all .backup files, when update finished and everything is fine.

[killerhex]

anyway to make mkv as input

[check]

killerhex, file->open

[cc979]

been doing some hd tests encodes and sometimes the video player is bigger then my screen, could it be possible to have and option to have maxmise to desktop size or have the show show/use par tick box at the top of the window

cheers

[shon3i]

It's possible to make when for example when we choose x264, only x264 profiles shown in profiles, xvid xvid's profiles, etc, aslo for audio profiles

[Sharktooth]

it would be possible if we save the encoder name in the profile.
that would require parsing of profiles on startup too.

[berrinam]

Actually, the codec is already stored. It's completely by choice that we list all of the profiles together on the main form. You should really prefix your profiles with Xvid- or x264- etc.

[Sharktooth]

oh... i missed that.
uhm... i could prefix my profiles but if i rename them the users will get duplicated profiles (due to autoupdate).

[berrinam]

Well, prefixing is only needed if it's important to know the codec. It never bothers me, though, because all of my profiles are prefixed, and yours are all x264, so there's no confusion. When I said, 'you', I meant shon3i

[shon3i]

Well, prefixing is only needed if it's important to know the codec. It never bothers me, though, because all of my profiles are prefixed, and yours are all x264, so there's no confusion. When I said, 'you', I meant shon3i
OK you mean x264_HQ_Slow, XviD_HQ_1CD...

[check]

Can you make tool windows (such as the avisynth creator, muxer, etc etc) not be always on top? Possibly if this was a deliberate design choice, an option for the user in settings? Drivin' me crazy :p

[berrinam]

OK you mean x264_HQ_Slow, XviD_HQ_1CD...Call it whatever you want. I'm just saying that I think it is a good idea to list alll video profiles on the main form, so if you want to know which is which then you will have to keep notes yourself. If not, then prefixes aren't important. I was just making a suggestion.

[shon3i]

Call it whatever you want. I'm just saying that I think it is a good idea to list alll video profiles on the main form, so if you want to know which is which then you will have to keep notes yourself. If not, then prefixes aren't important. I was just making a suggestion.
OK!!!

[cc979]

i've just tested creating a xvid.raw then muxed into a .mp4 - plays fine, is it possible get megui to do it automatic

[berrinam]

Ummm.... what are you saying? MeGUI already can encode automatically to mp4, so why do you need to go via raw other than for testing?

[Morte66]

Request: In the AviSynth creation window, on the Filters tab, could we have a single textual indication that deinterlacer analysis is complete? Waiting for "Source is declared " gets you close, but that's not always the end of analysis.

This is for use by GUI automation scripts (e.g. AutoIt (http://www.autoitscript.com/autoit3/)) that load jobs into MeGUI automatically. Unfortunately, AutoIt doesn't want to read the checkbox that enables when analysis is done.

[I've written a script that can be called by Robot4Rip to load it's output d2v/audio into MeGUI and set up the encode/mux. This means the user only needs to be there for the first couple of minutes to choose file names in R4R, and then everything runs unattended. The last hurdle is knowing for sure that the deinterlacer analysis is finished, so the script can move on.]

[Doom9]

@Morte66: why do you even use r4r anymore? All it does that megui doesn't is rip.

[cc979]

Ummm.... what are you saying? MeGUI already can encode automatically to mp4, so why do you need to go via raw other than for testing?

my mistake i only noticed on xvid encoding it has avi/mkv/raw only but autoencode has mp4 output (sorry it was really late)

[Morte66]

@Morte66: why do you even use r4r anymore?

It gets the job done 20 times faster.

All it does that megui doesn't is rip.

And the main thing MeGUI does that R4R doesn't is choose a deinterlacer...



R4R has a "Finalize" stage that will call another program (e.g. my AutoIt batch) and pass it a D2V filename and audio file list as parameters. You can automate the whole backup chain from R4R. MeGUI has no corresponding "Pre-Process" facility to prepare the rips, so you can't can't automate the whole backup chain from MeGUI.

Consider a TV DVD with four titles...

With R4R you insert DVD, click on a PGC, type a filename, and click "Start". Repeat 4 times. Your involvement is over in 2 minutes. Walk away. 30-40 minutes later it finishes the Decrypter/DGIndex/VobSub cycles and calls AutoIt, which calls MeGUI to choose a deinterlacer and queue the encode/mux, but you don't have to be there for that.

Compare that to MeGUI: Open Decrypter, start a PGC rip, wait about 7 minutes. Repeat four times. Set up four MeGUI jobs once the respective rips are done. If you're OK with OCE (no subtitles or PAL->24fps retiming) set up four OCE jobs. Otherwise you go through the AviSynth script creator four times, including the wait for deinterlace analysis, then click "AutoEncode". Overall, you spend 30-50 minutes waiting for things to happen before you can leave the PC.

The total CPU time is essentially the same by either route, but Robot4Rip + AutoIt + MeGUI ties up the user for around one-twentieth as long.

[If you only do progressive encodes with unvarying settings, R4R can just call a simple DOS batch file that uses "echo" statements to write an Avisynth script then shells iTunesEncode (http://www.rarewares.org/files/aac/iTunesEncode46.zip)/x264/mkvmerge. But you have to leave the disc in until it's started the last encode.]

[unskinnyboy]

Is there a way to make the autoupdater to force update? If lets say I accidentally deleted a plugin, autoupdater thinks I still have it because it parses the AutoUpdate.xml and finds the entry there. I could delete/modify AutoUpdate.xml (which I did), but is it possible to add a right-click item called 'Update Anyway' or something such which would ignore <CurrentVersion> and force update the plugin?

[berrinam]

Yes, something in that vein is definitely required, but there are going to be no improvements in this until we have a stable release, and THEN we will implement new features.

[jellysandwich]

It seems like we might need a server mirror for the autoupdate feature...

js

[berrinam]

Request: In the AviSynth creation window, on the Filters tab, could we have a single textual indication that deinterlacer analysis is complete? Waiting for "Source is declared " gets you close, but that's not always the end of analysis.
Version 0.2.3.2170 should have what you want.

[Morte66]

Version 0.2.3.2170 should have what you want.

Thanks.

I, um, can't find where to download MeGUI. This has just made me realise that the "download and install" half of your MeGUI guide is missing since the accident.

[berrinam]

I removed it deliberately, because autoupdate covers everything it did. That's what caused the accident in the first place -- I thought I could just delete the first post and it would be just dandy, but instead it deleted the whole thread.

You can get MeGUI from http://x264.nl but why do you need to? What's wrong with AutoUpdate?

[Morte66]

You can get MeGUI from http://x264.nl but why do you need to? What's wrong with AutoUpdate?

Nothing that I know of, but I haven't got it yet. :)

I generally stick/stuck to the "stable" builds from a page I've lost (I think bob0r's builds), so I'm on 2130. I haven't used x264.nl because it doesn't distinguish between stable and daily builds (or maybe it does, but not in a way that's obvious to me). Anyhow, I'll get the latest x264.nl build to use that feature.

[Doom9]

On top of that Chronocross still has a basic distro here: http://chronocrossdev.com/apps/
That way you get to chose if you really want an installer or not. Removing the manual bits is a good thing imho.. I think those that needed the guide are candiates for the autoupdate, and those that never needed it are free to continue doing things manually so you get the best of both worlds.

[Morte66]

On top of that Chronocross still has a basic distro here: http://chronocrossdev.com/apps/
That way you get to chose if you really want an installer or not. Removing the manual bits is a good thing imho.. I think those that needed the guide are candiates for the autoupdate, and those that never needed it are free to continue doing things manually so you get the best of both worlds.

Sure.

The auto-updater looks pretty nifty, if I can get accustomed to it.

I get the impression that it's putting its updates in the tools tree under the MeGUI install, regardless of the paths configured in the MeGUI options. So if I have DGIndex.exe installed in "c:\Program Files\DGMPDEC", and set MeGUI to use that, MeGUI will put the update in "C:\Program Files\MeGUI\tools\dgindex" and then ignore it. But I guess I could switch my other programs to using DGIndex installed under MeGUI, and use MeGUI as an update service for everything.

[I was keen to have only one copy of DGIndex.exe and DGDecode.dll on my PC, with various video apps pointed to it. I've had plenty of trouble with multiple versions before.]

Anyhow, I'll check it all out properly and decide what to do. As you say, I can choose what I want.

edit p.s. build 2170 is really nice! :)

[Morte66]

Request for the "AviSynth script generator" window:

In the "Clever (TM) anamorphic encoding:", could have an option for "Undercrop to achieve mod16" to go with the existing "Overcrop" option?

This is especially meant for users who (a) encode mod16, (b) don't like to lose any artistic content to cropping, and (c) encode cinemascope material where there might be ~70 black lines above/below the picture. It would also be useful for DVD extras, which often have 16:9 material encoded in 4:3 with borders, or vice versa.

It's especially relevant for unattended encodes, e.g. using OCE, since it will trim the huge borders but ignore normal material.

[Tima]

I'd like to ask about a very important feature for me:

- ability to manually specify proxy settings in MeGUI options

It's important, because i'd like to update MeGUI through fast internet channel, but for some reasons default proxy in my computer is slow..

[foxyshadis]

If you change the path to the tool in megui's settings, autoupdate will save it there. This goes for individual programs as well as avisynth filters (which all go in the specified avisynth folder).

It does make all these .backup files though, which is kind of lame; at least they could be set hidden. (And we could have a <revert> button in the updator!)

[berrinam]

Does anyone think the backup files are necessary, or should I just remove that feature?

[berrinam]

Request for the "AviSynth script generator" window:

In the "Clever (TM) anamorphic encoding:", could have an option for "Undercrop to achieve mod16" to go with the existing "Overcrop" option?

This is especially meant for users who (a) encode mod16, (b) don't like to lose any artistic content to cropping, and (c) encode cinemascope material where there might be ~70 black lines above/below the picture. It would also be useful for DVD extras, which often have 16:9 material encoded in 4:3 with borders, or vice versa.Since you're undercropping, you're going to be losing compressibility because of the borders, so you might as well just encode non-mod16, which will give you the exact cropping as well as slightly better compressibility.

[buzzqw]

@berrinam

remove the backup... if anyone accidentatly remove something can launch again autoupdater

BHH

[Morte66]

Since you're undercropping, you're going to be losing compressibility because of the borders, so you might as well just encode non-mod16, which will give you the exact cropping as well as slightly better compressibility.

There's a long and involved answer to that involving resizing PAL DVD in one dimension only for superior quality on 1024x576 DLP projectors, and non-mod16 crops screwing it up. But I guess it's a bit rarified for MeGUI to support. OK, request withdrawn.

[Morte66]

From the MeGUI changelog:0.2.3.2162
Commit by berrinam:
- Fix AR calculation to be ITU-correct
Any chance of an option to turn this off in the settings?

It's "correct", but it's bad news in some home theatre applications. When you've got an anamorphic PAL DVD and a a plasma/projector/etc display with 1024x576 pixels specifically designed to play it (that's 16/9 * 720/576) , you don't want the player to send 1050x576 or 1024x562. There'd be an extra dimension of resizing somewhere along the line, and that can look pretty bad in setups that weren't built for it.