MeGUI: bug reports and feature requests

[Zathor]

Ah, ok. It should not harm at all if the input filter is returning a 8 bit video.

[LigH]

@Betsy25:

It has always been recommended not to install MeGUI inside of a directory which is guarded by the UAC, it won't have permissions to write files there. The legacy of pre-Vista development.

[doomleox999]

Why MeGUI x64 keeps asking me to update AviSynth plugins even though they are up to date?



I'm also having this problem:



The only workaround I found is to add "ConvertBits(16)" to the end of the script.

[Lyle_JP]

New bug with 2891 and AVISynth Script Creator. Now, even though I have "Nvidia Resizer" unchecked when using DGIndexNV, it is still doing a source resize in the script, along with the resize filter I asked for. Example:

LoadPlugin("C:\Program Files (x86)\MeGUI_x86\tools\dgindexnv\DGDecodeNV.dll")
DGSource("D:\Princess Bride old\Princess Bride.dgi",fieldop=0, resize_w=1120, resize_h=608)
#deinterlace
crop(2, 16, -2, -24)
Spline36Resize(1120,608) # Spline36 (Neutral)
LoadPlugin("C:\Program Files (x86)\MeGUI_x86\tools\avisynth_plugin\UnDot.dll")
Undot() # Minimal Noise

The bolded part should not be there with the Nvidia Resizer option unchecked. This behavior just started with 2891

[pommesmatte]

Originally Posted by Lyle_JP

New bug with 2891 and AVISynth Script Creator. Now, even though I have "Nvidia Resizer" unchecked when using DGIndexNV, it is still doing a source resize in the script, along with the resize filter I asked for.

The bolded part should not be there with the Nvidia Resizer option unchecked. This behavior just started with 2891

I'm also seeing this. And I don't even use resize anywhere.

I crop in Avisynth and the resulting file has the correct playback aspect ratio BUT the wrong Pixel height.

Workaround for me this far is either removing the resize options manually from the script or do the cropping in DGIndexNV.

By the way: Why AVS Script Creator (optinally) doesn't put the cropping parameters in the DGSource statement? Wouldn't that be the far better procedure?

[Zathor]

Originally Posted by doomleox999

[B]Why MeGUI x64 keeps asking me to update AviSynth plugins even though they are up to date?

Thanks for the report. Could you please upload a full log (I do need the "Versions" part)? Also what happens if you update the plugins? Will it always come back? If yes, please upload your AutoUpdate.xml
Link to the bug report: https://sourceforge.net/p/megui/bugs/936/
EDIT: fixed (see bug report)

Also update to 2891 which should fix the color space issue.

[Zathor]

Originally Posted by pommesmatte

By the way: Why AVS Script Creator (optinally) doesn't put the cropping parameters in the DGSource statement? Wouldn't that be the far better procedure?

Currently working on that while fixing the resize bug. In my eyes this cannot be optional as the cropping must happen before the resize so it must be in the DGSource() call ==> if resize is enabled with DGSource, also the cropping has to happen there. Only issue is that for AVS cropping mod2 is fine while DGSource() does need mod4 so I have to increase to the next mod4 value = overcropping.

[Zathor]

2893 [OneClick]             fixed fatal error in some cases (regression of 2882). bug #937
2892 [AVS Script Creator]   added an option in the profile to use the DGIndexNV crop & resize filter if possible
                            if resize with DGIndexNV is enabled also cropping will be done that way (mod4 is forced for crop values)
                            fixed always applying the resize parameters to DGSource() (regression of 2891)

[pommesmatte]

Awesome! Works great thus far!

EDIT: There seems to be a bug left with the overcropping. The crop uses mod4 (134,138,142...), but if e.g. 138 top and bottom is chosen, in DGSource it becomes 140, but in the resulting video stream, there is a black border left on the bottom.
Maybe something to do with those 1088 height thing?

[doomleox999]

Originally Posted by Zathor

Thanks for the report. Could you please upload a full log (I do need the "Versions" part)? Also what happens if you update the plugins? Will it always come back? If yes, please upload your AutoUpdate.xml
Link to the bug report: https://sourceforge.net/p/megui/bugs/936/
EDIT: fixed (see bug report)

Also update to 2891 which should fix the color space issue.

I'm using MeGUI x64. It doesn't let me update to 2891. Should I use MeGUI x86? Is there any difference perfomance wise? I have a 64 bits system so I thought I should use MeGUI x64 to, let's say, encode faster, is that the case?

After updating, the problem comes back the next day. Is this what you need?

[pommesmatte]

Originally Posted by doomleox999

I'm using MeGUI x64. It doesn't let me update to 2891.

You have to switch the update server to "development".

Originally Posted by doomleox999

Should I use MeGUI x86? Is there any difference perfomance wise? I have a 64 bits system so I thought I should use MeGUI x64 to, let's say, encode faster, is that the case?

x64 is faster on x64 systems.

[Zathor]

Originally Posted by doomleox999

I'm using MeGUI x64. It doesn't let me update to 2891. Should I use MeGUI x86? Is there any difference perfomance wise? I have a 64 bits system so I thought I should use MeGUI x64 to, let's say, encode faster, is that the case?

Switch to the development server (in Options\Settings\Extra Config).
I still do recommend the x86 version as not all filters are available as x64 versions. However if x64 works for you, then you can continue to use it.

Originally Posted by doomleox999

After updating, the problem comes back the next day. Is this what you need?

That problem has been fixed already, but it will take up to 60 hours before your client gets the new config data from the update server. Also depending on what you do have there, one final update may be required.

[doomleox999]

Originally Posted by pommesmatte

You have to switch the update server to "development".



x64 is faster on x64 systems.

Originally Posted by Zathor

Switch to the development server (in Options\Settings\Extra Config).
I still do recommend the x86 version as not all filters are available as x64 versions. However if x64 works for you, then you can continue to use it.


That problem has been fixed already, but it will take up to 60 hours before your client gets the new config data from the update server. Also depending on what you do have there, one final update may be required.

Thanks for your answers. I did as you say and it works now. However, I have a problem with the development server update, some settings are different or they just disappeared:



Will this be fixed? Should I return to the stable servers? This development update will eventually be in the stable servers right?

[LigH]

Could you please avoid yelling? There is no need to write everything in bold.

[Zathor]

Originally Posted by doomleox999

[B]Thanks for your answers. I did as you say and it works now. However, I have a problem with the development server update, some settings are different or they just disappeared:
Will this be fixed? Should I return to the stable servers? This development update will eventually be in the stable servers right

I got tired of these questions where the settings have been gone to (let us have new ones...):

2894 [Main]                 moved menu items:
                            - "options\update" to "tools\update"
                            - "options\settings" to "options"
                            - "workers\settings" to "options"
                            - "workers\overview" to "view\worker overview"

And yes, this will be at some point also applied to the stable branch.

[LeMoi]

The problem is that you have to go to Doom9 forum and this topic to know about changelog before an update.
Maybe you should find a way to display changelog in the updater window, so that we know what has changed before we agree to the update?

[Zathor]

Originally Posted by LeMoi

The problem is that you have to go to Doom9 forum and this topic to know about changelog before an update.
Maybe you should find a way to display changelog in the updater window, so that we know what has changed before we agree to the update?

To read the changelog after the update has been done should be sufficient (help\changelog).

[doomleox999]

I get that message whenever I load an mkv file to One Click Encoder and I have selected mp4 as output. Is there any way to disable that?

[Glarioo]

Cannot use dgindexnv anymore after an update yesterday.

[Zathor]

Originally Posted by doomleox999

I get that message whenever I load an mkv file to One Click Encoder and I have selected mp4 as output. Is there any way to disable that?

Something must be in your MKV which cannot be muxed into a MP4 by MeGUI.