MeGUI -feature request

[akapuma]

Hello,

i wrote an add-on for GKnot, named agkp (http://forum.gleitz.info/showthread.php?t=22860) (sorry, in german only). Some features:

- creating of avisynth-filter-functions like postprocessing and deinterlacing for an easy use in GKnot
- use mkvmerge as external muxer
- automaticaly converting vfw-compatiblity-x264-streams into native-x264-Streams before muxing into a mkv-container

Now, I want to use the MeGUI for encoding in x264, because I can use all x264-options. Is it possible to create some needed command-line-options into the MeGUI:

- location and name of avs-Skript
- file type (like mkv)
- bitrate

So, my agkp could send this information to MeGUI at the start. I don't want to use the x264.exe, because the user can do all codec-settings in the MeGUI.

Best regards

akapuma

[Doom9]

let me see if I get this: you want to start up MeGUI and already have the video input configured, codec set to AVC, AVC bitrate set to your commandline parameter, output type set to avi/mkv/mp4? What about if the user has a profile configured? They override everything else..

[Sirber]

looks like it...

[akapuma]

Hello,

I have:
- an avs-script
- a bitrate (to get the target size)
- a designated file type

I want to call the MeGUI. Expample:
MeGUI.exe -avs d:\Rekorder\Test\Test.avs -b 850 -ft mkv

The user can do all AVC-Settings in the MeGUI. If a profile is configured, the profile can be used. But it's necessary to override the bitrate-setting, because the bitrate is calculated by GKnot. I think, avs-file and filetype are not part of a user profile.

Is this possible?

Best regards

akapuma

[Sharktooth]

it is useless!!!
call x264.exe with your favourite parameters and make it encode to raw or mp4.
then use mp4box or mkvmerge to mux the audio and other streams.

[stax76]

Don't know if Doom9 would permit this but reflection can work miracles assuming you are coding .NET, you can even hook into private stuff unless there are security attributes and if you are using a .NET language with late binding support like VB .NET or Boo and don't want to add a assembly reference you can avoid a lot clunky reflection as the compiler translates the late binding calls into reflection calls. Here is a example:


Dim asm As [Assembly] = [Assembly].LoadFile("C:\MeGUI.exe")
Dim f As Form = DirectCast(Activator.CreateInstance(asm.GetType("MeGUI.MeGUI")), Form)
f.Show()
Dim fi As FieldInfo = f.GetType.GetField("videoInput", _
BindingFlags.Instance Or BindingFlags.NonPublic)
DirectCast(fi.GetValue(f), TextBox).Text = "test.avs"

[charleski]

It sounds like you want a system that locks down the output format and automatically determines bitrate as well as applying various avisynth filters, but allows the user to play around with different profiles to match their desired quality/speed tradeoff.

I'm sure it would be possible to alter the One Click Encoder in meGUI to do that, though that would be a rather specialised function. MeGUI is, after-all, a GUI, rather than just a parser for other command-line functions.

You could build a simple batch file to do this yourself without using MeGUI at all - just set up the encoding and muxing commandlines for a variety of profiles and put in a menu.

As an example:

@echo off
echo 1 Fast encoding
echo 2 Normal encoding
echo 3 Slow Encoding
echo 4 Come back next week encoding
echo
Set /p answer=Enter choice:
if %answer%==1 goto choice1
if %answer%==2 goto choice2
if %answer%==3 goto choice3
if %answer%==4 goto choice4
goto :EOF
:choice1
echo You chose number 1
echo.
REM insert commands for fast encoding
goto :EOF
:choice2
echo You chose number 2
REM insert commands for normal encoding
goto :EOF
:choice3
echo You chose number 3
REM insert commands for slow encoding
goto :EOF
:choice4
echo You chose number 4
REM insert commands for really slow encoding

[akapuma]

Hello,

it's possible to use a batch or calling the x264.exe. But using the MeGUI is easy to handle.

There are 3 options:

- Using a batch or the x264.exe:
Not comfortable to create the needes x264-parameters. Not possible to check and edit at each call

- Using the MeGUI without modifications and GKnot:
The AVS-script, the bitrate and the filetype must be entered. Not comfortable.

- Using the MeGUI with modifications (parameters) and GKnot and agkp:
Automatic call from the MeGUI. Parameters, calculated by GKnot, are taken by the MeGUI automatically. All other parameters can be easyly checked and edited by the MeGUI.

I think, the third way is the best.

Best regards

akapuma

[charleski]

Well, if you really want to be able to fiddle with the parameters, it should be possible to write a simple program which will edit the XML in the MeGUI Settings files. Then when it runs MeGUI the parameters you want should be in place. Is that the sort of thing you want?

[Edit] BTW, if you're confused by the various x264 parameters, you can just set up a job in MeGUi and check 'Show Commandline', then copy that.

[Doom9]

well, I guess I could do that. But the syntax would be simpler.. like megui.exe input.avs bitrate output-format
where output-format is an integer corresponding to the index of the format dropdown (0=avi, 1=raw, 2=mkv, 3=mp4).

[akapuma]

well, I guess I could do that.Thank you very much.

Best regards

akapuma

[Sharktooth]

well, I guess I could do that. But the syntax would be simpler.. like megui.exe input.avs bitrate output-format
where output-format is an integer corresponding to the index of the format dropdown (0=avi, 1=raw, 2=mkv, 3=mp4).
if you do that please add "profile" too so it will be megui.exe input.avs profile bitrate output-format.
however i still insist on using x264.exe from a batch file... parameters can be passed to a batch file as well and using megui to replace a simple 50bytes .bat is an overkill...

[bond]

if you do that please add "profile" too so it will be megui.exe input.avs profile bitrate output-format.
however i still insist on using x264.exe from a batch file... parameters can be passed to a batch file as well and using megui to replace a simple 50bytes .bat is an overkill... :stupid:

[Randall]

Don't know if Doom9 would permit this but reflection can work miracles assuming you are coding .NET, you can even hook into private stuff unless there are security attributes and if you are using a .NET language with late binding support like VB .NET or Boo and don't want to add a assembly reference you can avoid a lot clunky reflection as the compiler translates the late binding calls into reflection calls. Here is a example:


Dim asm As [Assembly] = [Assembly].LoadFile("C:\MeGUI.exe")
Dim f As Form = DirectCast(Activator.CreateInstance(asm.GetType("MeGUI.MeGUI")), Form)
f.Show()
Dim fi As FieldInfo = f.GetType.GetField("videoInput", _
BindingFlags.Instance Or BindingFlags.NonPublic)
DirectCast(fi.GetValue(f), TextBox).Text = "test.avs"



Yuck! get that VB stuff outta here! :p If you wanna call MeGUI from the command line, you might as well just use x264 from the command line. It defeats the whole purpose of the GUI. :D

[akapuma]

It defeats the whole purpose of the GUI.I am of other opinion.

The MeGui is not able to
- create an avs-script
- to mux

With the parameters, it is possible to other software, to
- create an avs-script
- to calculate the bitrate (although the MeGUI also can do this)
- to mux
and to use the MeGUI
- to check and create the X264-parameters in a graphical environment
- to do automated 2- or 3-passes

Among other things, my software is an interface between GKnot, the MeGUI and mkvmerge. Parameters would make this much easyer.

Best regards

akapuma

[Doom9]

The MeGui is not able to
- create an avs-script
- to muxHuh? You must not be talking about the MeGUI I wrote. I think somebody is forgetting that MeGUI isn't MeGUI-x264 edition. There's an AviSynth script creator, a DGIndex project creator, AVI/MP4/MKV Muxer and to put it all together, a one click mode.

[akapuma]

I think somebody is forgetting that MeGUI isn't MeGUI-x264 edition.You are right. Normally, I use the X264-Edition.

Best regards

akapuma

[Doom9]

so in that case, I suppose there's no sense in making this change anymore, is there? That feature would only be available in the normal edition anyway, not the codec specific ones.

[akapuma]

Hello,

there is a sense in making this change anymore. It would be fine to make this changes in the X264-edition too, because the capable of the X264-edition is enough for my purposes. But the full version with the changes is better as the X264-edition without the changes.

Best regards

akapuma

[Sharktooth]

This change is perfectly useless coz you can use a batch file for both mencoder and x264.
MeGUI is a GUI... not a command line translator!