MeGUI development

[b66pak]

NicAudio has been updated (2.0.4):

http://forum.doom9.org/showthread.php?p=1314068#post1314068
_

[Yoshiyuki Blade]

Do keep us updated on your quest. I also interested in using 64 bit version of x264 (on 64 bit MeGUI) if it is reliable and not too hard to setup.

:thanks:

You make a lot of sacrifices in convenience and choices when switching entirely over to 64-bit. I managed to get a test encode running via commandline, but I've had some issues getting MeGUI to properly handle it. I might just do what JEEB said and do some piping... whatever that means :D.

[tebasuna51]

NicAudio has been updated (2.0.4)
Only a bug with lpcm input.
Without syntax changes, everybody can replace the previous version without problems.

[Dark Eiri]

On .1053, when I check the "Turbo" on x264 config, I'm limited to 1 ref-frame. Why is that?

[buzzqw]

because is TURBO ?
if you don't wanto to use turbo .. don't check it

also.. on newer x264 revision the first pass is now ALWAYS Turbo , unless requested as slow-first-pass

BHH

[Dark Shikari]

because is TURBO ?
if you don't wanto to use turbo .. don't check it"Turbo", as defined by what x264 does by default with --pass 1, is not a reasonable speed/quality tradeoff for anything except the first pass of a two-pass encode, so it should only be available for expressly that purpose.

[CpT]

Ok, I've searched for the better part of 2 days and can't find up-to-date info reguarding the One Click encoder and file types.
Is there any way to mod the allowable file types for the input of the one click encoder? eg .mov's.
I do a ton of 100mb source encodes. Thus far I'm getting amazing results with MeGui, like really amazing! :thanks:

But having to set the output Width every time via the script creator "Resize" is really annoying. Yes I'm lazy, but I'm usually doing the convert's while doing a million other things "working".

I see there's a really slick option in the one click setup for Output Resolution Width in the one click encoder setup/conf and would love to be able to use it with .mov sources.

Any ideas or tips would be greatly appreciated! Luv the App guys!:thanks:

[Dark Eiri]

because is TURBO ?
if you don't wanto to use turbo .. don't check it

also.. on newer x264 revision the first pass is now ALWAYS Turbo , unless requested as slow-first-pass

BHH

Guess you didn't get it.

If I uncheck Turbo, it adds "--slow-first-pass" to the CLI. If I check it, it removes --slow-first-pass, but adds --ref 1. Before .1053, checking turbo would keep me with the ref quantity I wanted (--ref 3, which is now the default, so it shouldn't add anything to the CLI), and still would do a fast first pass. That's the issue. I want to use turbo only as the first pass, which is how MeGUI used to do it before.

[Underground78]

When --slow-firstpass is not used ref is always --ref 1 :

814 /* Set faster options in case of turbo firstpass. */
815 if( b_turbo && b_pass1 )
816 {
817 param->i_frame_reference = 1;
818 param->analyse.b_transform_8x8 = 0;
819 param->analyse.inter = 0;
820 param->analyse.i_me_method = X264_ME_DIA;
821 param->analyse.i_subpel_refine = X264_MIN( 2, param->analyse.i_subpel_refine );
822 param->analyse.i_trellis = 0;
823 }

so I'm not sure it's a real issue ...

[pitc]

where can i get the latest version of megui??

[Dark Eiri]

When --slow-firstpass is not used ref is always --ref 1 :

814 /* Set faster options in case of turbo firstpass. */
815 if( b_turbo && b_pass1 )
816 {
817 param->i_frame_reference = 1;
818 param->analyse.b_transform_8x8 = 0;
819 param->analyse.inter = 0;
820 param->analyse.i_me_method = X264_ME_DIA;
821 param->analyse.i_subpel_refine = X264_MIN( 2, param->analyse.i_subpel_refine );
822 param->analyse.i_trellis = 0;
823 }

so I'm not sure it's a real issue ...

On the second pass too? I can understand why it would decrease to 1 on the first pass, but should it limit it to 1 on the final pass too?

[Underground78]

but should it limit it to 1 on the final pass too?

If it does then it's a bug.

[Dark Eiri]

It's been doing it in all of the 2pass presets. They use the "Automated 2 pass" setting. So when Turbo is checked, I can't set the 2nd pass settings by myself. It locks the ref-frame setting and others. If I uncheck the Turbo, I can customize every single setting, but --slow-firstpass is added. The correct behaviour, or at least what MeGUI used to do, would be using the Turbo settings for the 1st pass and the settings I specified for the second pass.

[prOnorama]

It's been doing it in all of the 2pass presets. They use the "Automated 2 pass" setting. So when Turbo is checked, I can't set the 2nd pass settings by myself. It locks the ref-frame setting and others. If I uncheck the Turbo, I can customize every single setting, but --slow-firstpass is added. The correct behaviour, or at least what MeGUI used to do, would be using the Turbo settings for the 1st pass and the settings I specified for the second pass.

Ah so it wasn't me, I noticed this as well. If I check "Turbo" in a profile I can't change values like # of Ref Frames, Trellis, Partitions, ME Algorithm anymore (greyed out to Hexagon, Subp Refinement 2, like the first pass), so the 2nd pass is set to these values as well now.

[CpT]

It's been doing it in all of the 2pass presets. They use the "Automated 2 pass" setting

That explains a lot. Thanks... Couldn't for the life of me figure out why I was getting decent fps during the 2nd pass.:rolleyes:

[Raere]

It looks like when you select 'automated 2-pass' and turbo, the x264 config window sets itself as if you have selected '2-pass first pass'. The old behavior was that with turbo, the first pass would be set up already behind the scenes, and you were only changing the settings for the second pass. Right now it grays out certain options because it thinks you don't need to change them for a turbo first pass. It looks like it's a bug, and the window needs to go back to its old behavior of only setting up for the second pass. You can do both passes manually (2-pass first pass, 2-pass second pass) as two separate jobs to get around this. Or, you can downgrade back to .1052, which is still on the Sourceforge page. I haven't looked at the code, but it looks like that's where the problem lies.

[hajj_3]

is a 64bit megui being developed at the moment or not? It might help speed up a 64bit avisynth being created then all we would need would be 64bit filters.

[Kurtnoise]

guys, I have some time on my hand and I'm on a brand new Win7 64bit install and eager to try out the whole 64 bit thing. I realize there was an aborted attempt to get the 64bit thing to fly.. any pointers as to what to look at to continue that work?
One thing to fix (http://forum.doom9.org/showthread.php?t=148654) otherwise that works (http://forum.doom9.org/showthread.php?p=1308100#post1308100)...

[morphinapg]

Not sure if this has been mentioned, but when I uncheck Turbo, the motion estimation mode combo box doesn't re-enable.

[Gannjunior]

Hi,

will be megui able to load multiple batch files where every file is a separated encoding? (for example drag in 100 files, assign all the same preset and start the encoding? )

thnks,
ciao!

[ser2]

Megui bugreport (version 1053).
There is a bug in Video preview window at AVS script creator:
1. Press '+' to zoom preview to 2x
2. Press 1x to return preview to normal size.
3. Now if I press again + it scales to 3x, nor 2x! Now if I press 1x and '+' again it zoom to 4x! Seems like button 1x does not reset zoom variable.

[Underground78]

Seems like button 1x does not reset zoom variable.

Yep, exactly ... Little patch to fix this bug :

Index: gui/VideoPlayer.cs
===================================================================
--- gui/VideoPlayer.cs (révision 1344)
+++ gui/VideoPlayer.cs (copie de travail)
@@ -240,7 +240,8 @@
/// <param name="e"></param>
void originalSizeButton_Click(object sender, EventArgs e)
{
- resize((int)file.Info.Width, showPAR.Checked);
+ zoomWidth = (int)file.Info.Width;
+ resize(zoomWidth, showPAR.Checked);
}
private void zoomInButton_Click(object sender, EventArgs e)
{

On a side note, I had to modify MeGUI.csproj to successfully compile Megui with compile-msbuild.bat because some files seem not to exist anymore. I'm not really sure of what I've done but here the patch in case it could be useful :

Index: MeGUI.csproj
===================================================================
--- MeGUI.csproj (révision 1344)
+++ MeGUI.csproj (copie de travail)
@@ -834,11 +834,6 @@
<Compile Include="AssemblyInfo.cs">
<SubType>Code</SubType>
</Compile>
- <Compile Include="Properties\Resources.Designer.cs">
- <AutoGen>True</AutoGen>
- <DesignTime>True</DesignTime>
- <DependentUpon>Resources.resx</DependentUpon>
- </Compile>
<Compile Include="Properties\Settings.Designer.cs">
<AutoGen>True</AutoGen>
<DesignTimeSharedInput>True</DesignTimeSharedInput>
@@ -1111,11 +1106,6 @@
</EmbeddedResource>
<EmbeddedResource Include="pause.ico" />
<EmbeddedResource Include="play.ico" />
- <EmbeddedResource Include="Properties\Resources.resx">
- <Generator>ResXFileCodeGenerator</Generator>
- <LastGenOutput>Resources.Designer.cs</LastGenOutput>
- <SubType>Designer</SubType>
- </EmbeddedResource>
</ItemGroup>
<ItemGroup>
<None Include="app.config" />

[rtjnyoface]

This might seem like an extraneous request but would it be possible to get the font in the status window darker? There are many times when I have difficulty reading it. Like I said it might seem extraneous but even people peeping at my pc while it's encoding have had difficulty seeing the time remaining and such. This is but a small request and I understand if other things are given priority, especially since you're doing this stuff for free.

I guess it says something about your work when requests are fixing small errors in zooming and being asked for a darker font in a specific window;)

[Kurtnoise]

You mean something like this ?

http://uppix.net/8/7/f/b8467925eddfcfb4dfe10887201f3.png (http://uppix.net/8/7/f/b8467925eddfcfb4dfe10887201f3.html)

[Jawed]

This might seem like an extraneous request but would it be possible to get the font in the status window darker? There are many times when I have difficulty reading it. Like I said it might seem extraneous but even people peeping at my pc while it's encoding have had difficulty seeing the time remaining and such. This is but a small request and I understand if other things are given priority, especially since you're doing this stuff for free.
I'm afraid you are facing an uphill struggle here:

http://forum.doom9.org/showthread.php?p=1213232#post1213232

make sure to read all the follow-up posts.

I even suggested a fix.

Jawed

[stax76]

It uses WinAPI standard controls/values used by thousands of applications, the problem is your LCD or your configuration. RipBot264 has serious issues regarding unreadable stuff, maybe it assumes a large resolution which I don't have.

[Jawed]

MeGUI uses standard controls in a non-standard way.

Windows has a concept of "make a control hard to read to indicate to the user that this information is irrelevant". This is being misused in this case, because the information being shown is highly relevant.

Jawed

[Atak_Snajpera]

RipBot264 has serious issues regarding unreadable stuff, maybe it assumes a large resolution which I don't have.
I assume that everybody has good well calibrated MAT lcd monitor. I don't care about rest.

[stax76]

Windows has a concept of "make a control hard to read to indicate to the user that this information is irrelevant". This is being misused in this case, because the information being shown is highly relevant.

I'm not sure about this, in the latest StaxRip beta I use readonly text boxes as well as cue hints in text controls often and it's not hard to read on my 1024x768 Samsung analog monitor. What about VirtualDub and DGIndex, don't they also use readonly text boxes in the status display?

I assume that everybody has good well calibrated MAT lcd monitor. I don't care about rest.

That's exactly what I assumed because RipBot264 targets HD users mostly which are likely to have a good LCD. Not that I'm concerned but would it be such a problem to support older/cheaper hardware?

[Jawed]

Greyed-out text, deliberately defined by Microsoft to indicate that the text is not meant to be read, should never ever ever be used by an application for text that is meant to be read.

It's irrelevant how readable any developer thinks it is, the UI specifically reserves greyed-out text for text that is not meant to be read.

Jawed

[Kurtnoise]

It's irrelevant how readable any developer thinks it is, the UI specifically reserves greyed-out text for text that is not meant to be read.
blame constructor then instead of any developer...

[stax76]

It seems MeGUI don't use just readonly text boxes since readonly text boxes have black and not grey text, I'm confused.

edit (overlap): maybe it's grey because of the flatstyle used?

[Jawed]

As I already explained before, that's because you are using the wrong kind of control. You should be using a label.

A text box is a kind of control used for entering data. A label is a kind of control for showing data. A label can never be edited by the user.

That's why, by default, a text box is accompanied automatically by a label control (when added to a form), which the developer uses to put a description of the function of the text box. The text in this label can not be edited by the user, so does not need locking, and is therefore highly readable.

Jawed

[Kurtnoise]

It seems MeGUI don't use just readonly text boxes since readonly text boxes have black and not grey text, I'm confused.

yes it does...but this is dependant of the OS used. In the case of Progress Window, the textboxes are disabled (so...grey-out) but are readable.

[stax76]

Ah, it's disabled, I agree then text should be black like in VirtualDub, DGIndex, StaxRip etc.

[Kurtnoise]

better ?

textboxes as read-only:
http://uppix.net/2/0/0/7315f34b1625a00df6aace5f97331.png (http://uppix.net/2/0/0/7315f34b1625a00df6aace5f97331.html)

textboxes disabled:
http://uppix.net/8/7/f/b8467925eddfcfb4dfe10887201f3.png (http://uppix.net/8/7/f/b8467925eddfcfb4dfe10887201f3.html)

[Betsy25]

Actually, I agree. In the end, they are used as status indicators, which purpose are to be kept visible. You can think about any kind of status indicators, the most known perhaps the installation progress windows of the main windows installers, they aren't greyed, because the user wants the see the progress at any time it is running, so for me, these should not be greyed out, after all the MeGui status windows do run for hours and hours and especially then, users are interested in taking a keep once in a while how far the process is.

So my conclusion : Better readability, the first shot is better, regarding the Time indicators, these are (for most) the most important parts, so bolding them wouldn't be a bad idea either.

[stax76]

@Kurtnoise

Read only text boxes allow focus, text selection etc., I think it's OK but not perfect. Better would be using a label and apply border style using WinAPI overriding CreateParams or using ControlPaint class to paint a border. Maybe there are easier solutions.

[Kurtnoise]

I decided to stick as "Vdub" style (like 1st picture) for the moment...

[stax76]

If you want to prevent focus/selection a easy solution is using labels and drawing a border:


Private Sub TestForm_Paint(ByVal sender As Object, ByVal e As PaintEventArgs) Handles Me.Paint
For Each i In New Label() {Label1, Label2}
Dim r = i.Bounds
r.Inflate(1, 1)
ControlPaint.DrawBorder3D(e.Graphics, r)
Next
End Sub


Another way:


Public Class StatusLabel
Inherits Label

Protected Overrides ReadOnly Property CreateParams() As CreateParams
Get
Dim ret = MyBase.CreateParams
ret.ExStyle = ret.ExStyle Or Native.WS_EX_CLIENTEDGE
Return ret
End Get
End Property
End Class

Public Class Native
Public Const WS_EX_CLIENTEDGE As Integer = &H200
End Class

[Kurtnoise]

VB ? huh, no thanks...:D

[stax76]

http://codeconverter.sharpdevelop.net/SnippetConverter.aspx

[Kurtnoise]

Thanks...anyway, I think to switch to WPF asap to have a better UI.

[stax76]

Are you sure you want to convert a complex form like your x264 form or mix WPF and WinForms in the same application? I've done some mixing too but only a small piece. I had a WinForms custom control with 350 lines code and replaced it with a WPF version achieving the same thing with only 50 lines code so I have smaller code and a little fun learning WPF. I'm looking forward to use WPF in the player I'm building.

[Kurtnoise]

Honestly I don't know...I've some random ideas but I'm not sure that it's doable or not. If I jump to WPF and succeed, x264 form will change probably...In fact, all forms must be changed. :D

[Theliel]

¿Bug in 0.3.1.1055?

CABAC toggle dont work?

[Kurtnoise]

fixed...redownload or force to reinstall it.

[hajj_3]

got a bug with latest megui, i get the following when closing megui after i manually replaced x264.exe v1235 32bit with x264.exe v1146 32bit:

http://i28.tinypic.com/r8h0mb.jpg

also in "update" it shows the version as v1135 still instead of reading the x264.exe to see what build it is. Hopefully you can fix these 2 bugs shortly, many thanks:)

[stax76]

It's bad practice to show a stack trace to the user, it's bad practice to save to a system directory and it's bad practice to require elevated privileges in order to be able doing so.

[Kurtnoise]

this is not the right place to report this...

got a bug with latest megui,
which is ?


also in "update" it shows the version as v1135 still instead of reading the x264.exe to see what build it is.
what ? no, nothing is parsed to retrieve the version #.

[hajj_3]

0.3.1.1055 is the version of megui i am using.

http://i26.tinypic.com/2zo8z0z.jpg

as you can see in the above screenshot it says that i have x264 v1135 installed but i actually have v1146 as i manually over-wrote the x264.exe in program files\megui\tools\x264. It should report the actual version i'm using.

[Kurtnoise]

this version # is read from the upgrade.xml on the server...whatever you do.

[rtjnyoface]

@kurtnoise

Post 4537

I like the first pic.

[morphinapg]

textboxes as read-only:
http://uppix.net/2/0/0/7315f34b1625a00df6aace5f97331.png

textboxes disabled:
http://uppix.net/8/7/f/b8467925eddfcfb4dfe10887201f3.png

Why use textboxes instead of labels?

[stax76]

Because labels don't have a border unless you draw one or apply a style using pinvoke.

[morphinapg]

Because labels don't have a border unless you draw one or apply a style using pinvoke.

label.BorderStyle = BorderStyle.FixedSingle;

That's what I use in ASXGui

[stax76]

I didn't notice it's that simple, last time I only saw and tested the FlatStyle property and didn't notice the BorderStyle property. Sometime the easiest things are hard to see.

[Octo-puss]

Is MeGUI dead? Just curious.

[RyaNJ]

Is MeGUI dead? Just curious.

Look here (http://forum.doom9.org/showthread.php?t=151159) for a temporary thread until MeGUI is maintained fully again.

[Octo-puss]

What happened btw? I haven't been here for 3 months or something.

[RyaNJ]

I guess the guys working on it are just busy at the moment. If they have time to work on it, they'll probably be back again.

[lnatan25]

http://forum.doom9.org/showthread.php?t=151159

[Claymore]

I have to say thank you for the x-mas update! Seems, that all is fine.

MeGUI ... can't live without it.

greetings