MeGUI Feature Request Thread

[berrinam]

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 .
I don't understand you. What do you mean by "stream data pipeline"?

EDIT: I read your earlier post and Googled it. I found this result:

(From http://www.virtualdub.org/docs_faster )
What do the Performance settings do?

Short answer: leave them alone.
...
Stream data pipelining controls the number of audio and video buffers in flight in VirtualDub's pipeline; this is the companion to the AVI output buffering setting. One buffer is used for one video frame, or one video frame's worth of audio data. Again, this value rarely speeds anything up if you're doing a slow operation like recompression, and raising it can have extremely bad consequences -- setting 256 buffers on a 640x480, 24-bit uncompressed RGB file could conceivably cause VirtualDub to allocate 235MB of memory. Increasing it on a direct stream copy operation with a highly compressed input could help, but that tends to already be speedy with the defaults.

So, that issue is not to do with MeGUI, it's x264's problem, and I would also say it isn't a problem -- x264 is just slow, because it is very powerful

[jmk]

i like that megui now calculates the --sar value for x264 according to what you put in into the "sample aspect ratio" in the config dialogue.

but would it somehow be possible to have a checkbox that disables the automatic calculation and passes the values that i input into those fields to x264 as the --sar values instead? (like it used to be...).


thx,
jmk

btw: i am using v0.2.3.2118

[Doom9]

according to what you put in into the "sample aspect ratio" in the config dialogue.it hardly does that.. rather it fills those values, but only if you tell it to. Unless you configure megui to signal dar in the avisynth script creator or one click encoder, whatever you configured in the two sar fields in the x264 configuration will be applied (and by default that's 1:1 so nothing will be set).

[berrinam]

it hardly does that.. rather it fills those values, but only if you tell it to. Unless you configure megui to signal dar in the avisynth script creator or one click encoder, whatever you configured in the two sar fields in the x264 configuration will be applied (and by default that's 1:1 so nothing will be set).
Actually, those fields are treated as DAR, Display Aspect Ratio (the labels might be wrong, though). This means that MeGUI does in fact convert them to sar just before encoding. I made it that way because I made a general decision that DAR is more useful than SAR. I think it is worth allowing either.

[thuongshoo]

I don't understand you. What do you mean by "stream data pipeline"?

EDIT: I read your earlier post and Googled it. I found this result:


So, that issue is not to do with MeGUI, it's x264's problem, and I would also say it isn't a problem -- x264 is just slow, because it is very powerful
"stream data pipeline" , is a fucntion , .Perhaps you don't understand "function" .:D
yes ,
Stream data pipelining controls the number of audio and video buffers in flight in VirtualDub's pipeline
So can you do the same in Megui ?
I want to have a function which named "Stream data pipeline" , controls the number of audio and video buffers in flight in Megui's pipeline :D
Virtualdub have 3 function concerns with "pipeline" , you can view the picture which I posted .
Virtualdub uses x264vfw while Megui uses x264.exe ,so I don't know whether Megui can boost speed as Virtualdub :D
Again, this value rarely speeds anything up if you're doing a slow operation like recompression, and raising it can have extremely bad consequences
yes , I agree with Averly Lee but it is not bad function completely . If I use 256 buffers (maximum) , output file can be bad but I use less 256 buffers , Virtualdub is ok .Adding , Virtualdub using .Avi as output container , it is said that .Avi is not a good container for x264
The speed actually increase if I increase "AVI buffer" .I use Virtualdub and the speed is often 16 frame/s while is only 2 frame/s for Megui

[berrinam]

I still don't completely understand what it does, however, I feel confident enough to say, "It has nothing to do with MeGUI". Make a feature request either to the Avisynth devs or the x264 devs for that.

As far as the actual processing goes, MeGUI does nothing. It just sits and watches x264 and Avisynth do all the work, and reports back with how much they've done.

[Doom9]

You don't seem to understand how megui works. Megui has no pipelines.. it doesn't read video data.. x264.exe reads video data, encodes and writes video data.. it's all in one tool. All megui does is give parameters to x264.exe and display the status as reported by x264.exe.

[thuongshoo]

You don't seem to understand how megui works. Megui has no pipelines.. it doesn't read video data.. x264.exe reads video data, encodes and writes video data.. it's all in one tool. All megui does is give parameters to x264.exe and display the status as reported by x264.exe.
yes .Thank for explaining . Before I also guess that Megui is only actually a Gui ,dont do anything , transcoding is job of encoder . Perhaps this is a advantage of x264.exe

[thuongshoo]

wrote by thuongshoo
Perhaps this is a advantage of x264.exe
I'm sorry !
Perhaps this is a disadvantage of x264.exe :D

[Richard Berg]

I'm not sure you understand how x264 (or VDub for that matter) work either. x264's backend will always be slower than disk I/O, so adding buffers would just be a waste of memory. It loads Avisynth, which does have PVideoFrames (equivalent to one of VDub's pipelines), but since it's a nonlinear editor the allocation is much much more complex than VDub. There's no way to fit the concept of a static # of pipelines into Avisynth: the number of frames and clips in the system is dynamic, and it also has an aggressive cache. The closest equivalent would be the SetMemoryMax function, but as the name implies, that's a maximum rather than a static #.

All of these programs are open source. If you come up with any workable ideas, submit a patch.

[thuongshoo]

Megui convert file by x264.exe and Avisynth . It is good .I have a mpeg-2 which can't be transcoded by Virtualdub but Megui can do well . I'm very surprise .
Averly Lee says that Using a large buffer make VD encode while it waits for disk I/O .
Oh ! all thing is theory . If increasing AVI buffer and pipeline , processing speed will increase . Have you try to do this with VD ?
VD uses x264vfw.dll while Megui uses x264.exe
Maybe we can't do this in MEgui because it use Avisynth . I guess that . I don't dare say because I'm a pro programmer :D

[denise]

difference setting between x264 MeGUI and x264vfw VD ---> difference speed.

Use MP4 box -aviraw video to extract raw h264 from .avi that made by VD . Mux new .264 and .aac in to .mp4 as you desire.

[foxyshadis]

Heavy pipelining is only useful for huge disk operations, on the order of tens of megabytes read and written a second. Capture and direct stream processing fall into this, heavy final encoding does not. x264 already uses asynch i/o afaik, which provides a big boost, and pipelining doesn't gain much over that.

He discusses it in this entry (http://www.virtualdub.org/blog/pivot/entry.php?id=31):

If your render operation is projected to take 14 hours and its speed is better measured in SPF than FPS, just leave the buffering settings alone. Tweaking them isn't likely to speed anything up.

[thuongshoo]

wrote by thuongshoo
because I'm a pro programmer
oh ! shock ! shock ! I'm sorry
because I'm not pro programmer :D

To denise : thank you ! I will try
To foxyshadis : I will read it .My english is n ot good so I need time to understand it .

[Kayaker]

I'd love to have vorbis sound suppont in MeGUI.

Until you resolve the avisynth sound support for Vorbis would it possible to add at least muxing of Vorbis sound with mkvmege ?

Cos mkverge is perfectly capable of doing so.

Thanks a lot for the BEST encoding GUI.

[Bathrone]

Just a useability suggestion on the UI - buttons could be made inactive until they can be actually used. e.g. Not having the job tab start button enabled until a job exists in the que.

Thanks to all involved in MeGUI, a great app that Im sure is setting the stage for our AVC future.

[Kostarum Rex Persia]

Hi guys, I have one reasonable suggestion for future MeGUI builds?

Instead supporting ONLY AVS input, devs should introduce direct work with AVI. MPG and other video files, without need for AVS script.

That's because most people doesn't need filters in AviSynth, so direct work with MPG and AVI files would be nice.

http://img438.imageshack.us/img438/6660/suggest9wo.jpg

Any good thoughs, devs. I don't need AviSynth scripts very often, I just want to encode in MP4 or MKV container directly, without AVS scripts.

[chipzoller]

I don't need AviSynth scripts very often, I just want to encode in MP4 or MKV container directly, without AVS scripts.

I agree this would be nice. Most of the time I don't NEED scripts but have to make them anyway.

[ChronoCross]

It does have a meinimize to tray already.

View --> minmize to tray

[foxyshadis]

There's nothing nice about his request, all that needs to change is the drag-drop (and file open) handlers need to be extended to accept and handle directshow types (mkv, mp4, mov, wmv, etc). And, possibly, avisynth input renamed to video input, except then we'd get the exact opposite requests from people asking for an avisynth input.

[ChronoCross]

Not to mention demultiplexing issues, Remuxing control, container capabilites(in temrs of handling audio and video streams).

There is a whole lot to consider if Megui were to start accepting all types of files.

[chipzoller]

It does have a meinimize to tray already.

View --> minmize to tray

My bad...never seen it under 'view'

[foxyshadis]

Well, the video just gets sent to a directshowsource call, so if that fails you just pop up a dialog saying "No system splitter or decoder available for this format! Please install [haali's and ffdshow|realplayer|WMP codecs]."

If you get beyond that into multiple streams, subtitles, chapters, etc, you're in for a world of pain for not much gain. ;_;

[berrinam]

Ok, done! You can now open any video source that works with DirectShowSource in a number of ways:
Go to the AviSynth script creator and open it there
Drag it onto MeGUI, which will open it in the AviSynth script creator
Use File->Open, which will also open it in the AviSynth script creator

At the moment, the only supported filetypes for DirectShow are *.avi, *.mp4, *.mkv, and *.rmvb. Everything else is accessible through the 'All files' filter. If someone wants to givve a me a better list of file extensions for DSS-loadable files, please go ahead.

[Kostarum Rex Persia]

Yuo don't inderstand my point berrinam. We, common users, want to open video files directly, without AVS interfering. I hate to make AVS script every time.

[ChronoCross]

Yuo don't inderstand my point berrinam. We, common users, want to open video files directly, without AVS interfering. I hate to make AVS script every time.

your an idiot. do you have any idea how much would be required to build a directshow decoder directly into megui??? Seriously man....it's best to do your decoding through avisynth. it allows us to deal with things better as the framework is already finished.

[dimzon]

your an idiot. do you have any idea how much would be required to build a directshow decoder directly into megui??? Seriously man....it's best to do your decoding through avisynth. it allows us to deal with things better as the framework is already finished.
maybe we can create AVS script impicitly without showing any avs-creation GUI

[ChronoCross]

true. but I think what KRP is asking for is basically virtualdub. Where the video file is handled implicitly where the end of encoding all the stuff is done already.

That would mean that megui would have to be able to differentiate between all tracks(video, audio, subs) Their given track names and other info be able to wrap that in avisynth with no user input, and then figure out how to keep them into the next container with the same attribs.

Considering all the things that can go wrong in this process(audio compatibility, video changes and whatnot) there would have to be a substantial amount of time put in to get every possible situation and prereq for each container both input and output.

[cc979]

@berrinam cheers for clear log button,
just noticed the resize disable nice touch - but maybe a idea to turn on resize automaticly if crop is used and its not a mod of 8/16(not remember which)

[shon3i]

maybe we can create AVS script impicitly without showing any avs-creation GUI
For example something like AutoGK

[berrinam]

@cc979: I dunno.... if I turned resizing off, I wouldn't want it to turn back on when I selected my cropping. You have a point, though.

@all: Yep, I am considering doing that implicit avs creation. There needs to be some way to smoothly integrate the two, so if people can come up with some ideas, that would be great.

The way that I thin the implicit avs creation would work would not be like AutoGK, as shon3i said, but simply a single input line. So, if you load a video file, then MeGUI creates an avs that has a DirectShowSource call (or AviSource, etc), with no resizing or cropping. If you want to configure it yourself, then you (somehow) tell MeGUI to open this with the AviSynth script creator, and if you want AutoGK-style automated script generation, you use the One Click Encoder (this could do with some extension, to support directshowsource files for input -- perhaps using the MediaInfo lib for track information).

[cc979]

@berrinam ... if autocrop is used and resizer is disabled maybe increase the crop so it is a mod of 16 or re-enable the resize or give a choice

depends on the encode maybe

[Romario]

your an idiot. do you have any idea how much would be required to build a directshow decoder directly into megui??? Seriously man....it's best to do your decoding through avisynth. it allows us to deal with things better as the framework is already finished.

Beside your bad maners:( , I support KRP request for direct opening of video files in future MeGUI builds. Common users needs that.

[ChronoCross]

your basically the same person so whatever. Besides ignoring the technical reasons for this MeGUI is NOT Virtualdub. Re-read a few of my posts and you'll understand why implementing it will be not worth the effort.

[foxyshadis]

If you need a virtualdub for newer formats, please, use avidemux! It was made to be a virtualdub-style editor for them. MeGUI is just an encoder that levarages smart algorithms and the power of avisynth to make your encoding easier, but it will never be an NLE.

[Doom9]

Here's the only thing that makes sense from a programmer's perspective: relax the filter to other types. If the file selected has the extension .avs, everything works as normal. If the extension is .avi, megui writes a new avs named yourmovie.avi.avs containing:
avisource("yourmovie.avi")
and loads that avs. The avs is written in the same directory as the avi.
If the extension is anything else, the avs written has the same naming system, but instead contains
directshowsource("yourmovie.extension")

But for megui, there's only avs and anything that goes beyond that would be a major effort - that time is better invested into something else.
Also keep in mind a directshowsource call without fps is dangerous.. but it's the only thing that can be done because we can't just get fps info from an arbitrary file unless either writing parsers for X different containers, or start messing with directshow (render the file and hopefully the fps can be gotten from that).
But in the input window, you still only have avs shown, and you cannot use the typing facility to manually put a non avs filename there.. that would already turn things too complicated again.

[berrinam]

Here's the only thing that makes sense from a programmer's perspective: relax the filter to other types. If the file selected has the extension .avs, everything works as normal. If the extension is .avi, megui writes a new avs named yourmovie.avi.avs containing:
avisource("yourmovie.avi")
and loads that avs. The avs is written in the same directory as the avi.
If the extension is anything else, the avs written has the same naming system, but instead contains
directshowsource("yourmovie.extension")This system is what I plan to implement (however, not with AviSource. avisource has problems with non-VfW decoders). It shouldn't be hard (the infrastructure is already there in the AviSynth script creator, which I extended in my last commit to support arbitrary filetypes using DSSource), and MeGUI's error checking for video should avoid some problems (well, it will detect AviSynth errors, which includes problems with not signalling fps, as well as mod16 and colorspace problems), so it can't really stuff MeGUI up.

EDIT: Done. It is a very stupid script generator, and it won't deal with any problems like flipped video. If you run into them that's your problem -- use the Avisynth script creator which is designed to deal with all of that.

[faxmactor]

"Shutdown when finished" is going onto my mind :mad:

I don't think there's any user who wants to go on with the shutdown when he aborts a job manually. :(

Besides that, a timed interception possibility would be useful, just in case. (Encodes packed with filters take so long that one might forget that the option has been set.)

:thanks:

[shon3i]

I can't belive MeGUI finally looks like a big app for multiformat encoding, all greetings to MeGUI devs, but you miss only one big thing. That's thing is 5.1 audio encoding. I know MeGUI supports 5.1 encoding for both BeSweet and AviSynth, but encoders is very bad. Nero and FAAC need bitrate like AC3 to sounds normaly. So only one encoder is good for 5.1 HE encoding and we know is that Coding Tehnologies (Winamp). Thanks to Dimzon and his encAACPlus.exe comandline encoder, encoding is very sipmply. New Nero encoder shall to be out in few months which all bugs in 5.1 encoding is cleared but until now you can add support for CT becouse is aslo good in stereo encoding. CT now support both LC and HE profiles, aslo LC encoder support 8-320kbs, HE 8-320kbs, 6ch HE 96-213kbs which all bitrates good for 1cd rips especialy 96-128, and 128-213 is good for 2 or more cd's, aslo LC supports 6ch. Thanks

EDIT: Encoding via BeSweet have no sense, so clear your agony and remove it form MeGUI

[dimzon]

I can't belive MeGUI finally looks like a big app for multiformat encoding, all greetings to MeGUI devs, but you miss only one big thing. That's thing is 5.1 audio encoding. I know MeGUI supports 5.1 encoding for both BeSweet and AviSynth, but encoders is very bad. Nero and FAAC need bitrate like AC3 to sounds normaly. So only one encoder is good for 5.1 HE encoding and we know is that Coding Tehnologies (Winamp). Thanks to Dimzon and his encAACPlus.exe comandline encoder, encoding is very sipmply. New Nero encoder shall to be out in few months which all bugs in 5.1 encoding is cleared but until now you can add support for CT becouse is aslo good in stereo encoding. CT now support both LC and HE profiles, aslo LC encoder support 8-320kbs, HE 8-320kbs, 6ch HE 96-213kbs which all bitrates good for 1cd rips especialy 96-128, and 128-213 is good for 2 or more cd's, aslo LC supports 6ch. Thanks
AFIAK this feature (CT AAC encoder support) is in TODO list. Unfortunally there are huge work (refactiring) to do before it and we (Doom9 and I) are too busy IRL now

[shon3i]

@dimzon thanks anyway. When you back to url can you start working on this. I am not sure but i don't now how nero distribute their new aac codec, Ivan told that will be new distribution and maybe limitation over encoding.

[cc979]

@berrinam
just had time to do some testing (0.2.3.2129 20 April 2006)

good job on the mod16 stuff :) :thanks:

just a little feature when encoding an .avs maybe have script preview window, incase some forget which what they are encoding

[chipzoller]

I would like to request the addition of MP3 audio support in MP4 muxing operation. I realize AAC is the favored choice and perhaps the better one, but nonetheless if MP3 is supported in the container format, I think megui should be able to do it, and this shouldn't be a big deal to add.

[berrinam]

I agree, but this will probably have to wait until the refactor is committed.

[Doom9]

@berrinam: if not already done, all that needs to be done to support that is adding the mp3 audio type as supported audio type.. I may have even already done it. Then of course there's the matter of making the mux windows muxer aware to they allow you to select input types that the muxer supports..

[chipzoller]

Also, another request....
I think perhaps it's time megui had its own icon. It seems to be in a worthy enough state :)

Or is this feature in the works?

As always, many thanks for the outstanding program.

[Morte66]

Small ease of use request: when using file dialogues to open souce audio files for encoding, please treat Avisynth files (.avs) as an audio format along with .ac3, .dts etc. I create quite a few combined audio/video scripts to retime PAL movies to 24fps, so I often have avisynth as an audio source.

[ChronoCross]

That however would be undetectable as to you having audio in the avs script. so it would be pointless.

you can't encode audio and video together and change the audio format. just won't work. Audio must be encoded separately.

if you had a completely separate avs for audio it would be another matter.

[Morte66]

* confused *

I do mean to encode the audio separately. Perhaps I should give an example. Say I have externally created an avisynth script called deadwood3.avs which has 24fps audio and video streams:

LoadPlugin("C:\Program Files\DGMPGDec\dgdecode.dll")
loadplugin("C:\Program Files\avisynth 2.5\plugins\NicAudio.dll")
video=mpeg2source("C:\MyDox\My Videos\Staging\Deadwood 3\VTS_01_1.d2v",cpu=4)
audio=nicac3source("VTS_01_1 T01 3_2ch 448Kbps DELAY 0ms.ac3",2)
audiodub(video,audio)
AssumeFPS(24,1,true)
SSRC(48000,false)

I open it once as a video source and again as a sound source, maybe using "AutoEncode" to do the mux as well, to get 2 or 3 related jobs. I open it as video as normal on th emain input tab, no problem. Then I in the main input tab I click on the "..." button to the right of the audio input filename. That launches the "Select your audio input" dialogue. In the bottom drop-list on that dialogue, labelled "Files of type", I can choose "Supported audio formats" {default}, "AC3 audio", "DTS audio", "MPEG audio", "WAV audio", and "All Files (*.*). At them moment, I have to choose "All Files" to open an avisynth file like deadwood3.avs as my source sound file. I would like to see "Avisynth Audio" added to the list of audio file types, and for it to fall within "Supported audio formats" so that avisynth files appear when I first launch the "Select your audio input" dialogue. {edit} It would also be quite useful if the audio input box on the main Input tab accepted avs files via drag and drop, like it accepts ac3 etc.

[I'm referring to versions 0.2.3.2065 and 0.2.3.2127, if that matters. I've encoded over 100 files this way, generally to x264/FAAC.]

[ChronoCross]

why don't you just encode the AC3 Seperately? you can do the same SSRC transform in the audio config dialog. Your method seems strangely wrong to me.