MeGUI: General Questions and Troubleshooting Thread

[Zathor]

Originally Posted by rhaz

Latest update 2834 broke DGIndex file indexer (DVD as source), you cannot set custom path or filename anymore.

Fixed:

2835 [FileIndexer]          fixed output file selection (regression of 2834)

[rhaz]

Thanks for quick fix. Yes, I was on x64 build.

[hello_hello]

Originally Posted by Zathor

I can only say that I could reproduce it. When the redist files are missing you get exactly the problem you have. With the files it is gone for me. So maybe you are missing something else? Could you try the dependency walker on avisynth.dll?

Dependency Walker says:

Warning: At least one module has an unresolved import due to a missing export function in a delay-load dependent module.

There's two dlls marked in red. They are MPR.dll and SHLWAPI.dll.

Only thing is, Dependency Walker says the same thing whether I check Avisynth 2.6 or Avisynth+, and Avisynth 2.6 works.

Maybe the next step is to "install" Avisynth+ to check it works that way. I'll try to do it tomorrow and report back.

[LigH]

MeGUI can use either the AviSynth DLL installed in your system, or the "fallback" AviSynth+ DLL it ships in its own tool selection. Dependency Walker will not know that, it will probably see only the AviSynth plugin DLL's but not the avisynth.dll MeGUI would use first, so it can only find the system32\avisynth.dll as base.

[Groucho2004]

Originally Posted by LigH

Dependency Walker will not know that, it will probably see only the AviSynth plugin DLL's but not the avisynth.dll MeGUI would use first, so it can only find the system32\avisynth.dll as base.

I don't think you know how Dependency Walker works.
You select a DLL or EXE and it will tell you which dependencies on system or other DLLs exist depending on the linker options used when building the binary.
It has no idea about Avisynth or its plugin subsystem.

[hello_hello]

LigH,
when I open MeGUI's Avisynth plus, there's more dlls in the dependency tree than there are when I open Avisynth 2.6.

Most obvious are the extra runtime files. The very beginning and end of the dependency tree for Avisynth 2.6 looks like this:

[ ] c:\windows\system32\AVISYNTH.DLL
[ ] c:\windows\system32\KERNEL32.DLL
[ ] c:\windows\system32\NTDLL.DLL
[ ] c:\windows\system32\ADVAPI32.DLL
[ ^ ] c:\windows\system32\KERNEL32.DLL
[F^ ] c:\windows\system32\NTDLL.DLL


[D ] c:\windows\system32\WINSTA.DLL
[ ^ ] c:\windows\system32\KERNEL32.DLL
[F^ ] c:\windows\system32\NTDLL.DLL
[ ^ ] c:\windows\system32\NETAPI32.DLL
[ ^ ] c:\windows\system32\NTDLL.DLL
[ ^ ] c:\windows\system32\RPCRT4.DLL
[ ^ ] c:\windows\system32\USER32.DLL

For Avisynth+ in an old MeGUI folder without the required runtime files it lists the dlls in the system32 folder:

[ ] c:\megui\AVISYNTH.DLL
[ ] c:\windows\system32\AVIFIL32.DLL
[ ] c:\windows\system32\MSVCRT.DLL
[ ^ ] c:\windows\system32\KERNEL32.DLL
[F^ ] c:\windows\system32\NTDLL.DLL


[ ] c:\windows\system32\API-MS-WIN-CRT-FILESYSTEM-L1-1-0.DLL
[F^ ] c:\windows\system32\UCRTBASE.DLL
[ ] c:\windows\system32\API-MS-WIN-CRT-LOCALE-L1-1-0.DLL
[F^ ] c:\windows\system32\UCRTBASE.DLL
[ ] c:\windows\system32\API-MS-WIN-CRT-UTILITY-L1-1-0.DLL
[F^ ] c:\windows\system32\UCRTBASE.DLL
[ ] c:\windows\system32\API-MS-WIN-CRT-CONVERT-L1-1-0.DLL
[F^ ] c:\windows\system32\UCRTBASE.DLL
[ ] c:\windows\system32\API-MS-WIN-CRT-TIME-L1-1-0.DLL
[F^ ] c:\windows\system32\UCRTBASE.DLL

And for the same Avisynth+ in the current MeGUI tools/avs folder with the required runtime files, it shows those dlls specifically:

[ ] c:\program files\megui\tools\avs\AVISYNTH.DLL
[ ] c:\windows\system32\AVIFIL32.DLL
[ ] c:\windows\system32\MSVCRT.DLL
[ ^ ] c:\windows\system32\KERNEL32.DLL
[F^ ] c:\windows\system32\NTDLL.DLL


[ ] c:\program files\megui\tools\avs\API-MS-WIN-CRT-FILESYSTEM-L1-1-0.DLL
[F^ ] c:\program files\megui\tools\avs\UCRTBASE.DLL
[ ] c:\program files\megui\tools\avs\API-MS-WIN-CRT-LOCALE-L1-1-0.DLL
[F^ ] c:\program files\megui\tools\avs\UCRTBASE.DLL
[ ] c:\program files\megui\tools\avs\API-MS-WIN-CRT-UTILITY-L1-1-0.DLL
[F^ ] c:\program files\megui\tools\avs\UCRTBASE.DLL
[ ] c:\program files\megui\tools\avs\API-MS-WIN-CRT-CONVERT-L1-1-0.DLL
[F^ ] c:\program files\megui\tools\avs\UCRTBASE.DLL
[ ] c:\program files\megui\tools\avs\API-MS-WIN-CRT-TIME-L1-1-0.DLL
[F^ ] c:\program files\megui\tools\avs\UCRTBASE.DLL

I haven't had a chance to install Avisynth+ yet. The PC's still finishing some encodes.
Plus I don't want to discover this is an XP issue.
Although I guess MeGUI's refusal to use the portable Avisynth+ doesn't matter too much. If I want to use Avisynth+ I can install it instead of Avisynth 2.6.

I'm not missing a required application or system path am I?

The application directory
[ ] C:\WINDOWS\system32\
The 32-bit system directory
[ ] C:\WINDOWS\system32\
The 16-bit system directory (Windows NT/2000/XP/2003/Vista/+)
[ ] C:\WINDOWS\system\
The system's root OS directory
[ ] C:\WINDOWS\
The application's registered "App Paths" directories
The system's "PATH" environment variable directories
[ ] C:\WINDOWS\system32\
[ ] C:\WINDOWS\
[ ] C:\WINDOWS\System32\Wbem\
[ ] C:\WINDOWS\system32\WindowsPowerShell\v1.0\
[ ] C:\Program Files\Common Files\Acronis\SnapAPI\

[LigH]

Hmm, so maybe not? ... I imagined it recursively, with plugin DLL's having a dependency to an avisynth.dll ... my mistake then.

[Groucho2004]

Originally Posted by LigH

Hmm, so maybe not? ... I imagined it recursively, with plugin DLL's having a dependency to an avisynth.dll ... my mistake then.

Some plugins, although very few, have avisynth.dll as a dependency (I have no idea why, though).

[LigH]

I imagined the core might share common features plugins may use, so they don't have to implement it separately, and maybe even query some AviSynth version-dependent attributes. But I never implemented any plugin.

[Groucho2004]

Originally Posted by LigH

I imagined the core might share common features plugins may use, so they don't have to implement it separately, and maybe even query some AviSynth version-dependent attributes.

You have to look at it from the client (x264, VDub, whatever) that requests frames from Avisynth. It loads Avisynth.dll and then initializes IScriptenvironment which will cause Avisynth to enumerate all internal and external (plugins in the auto-load directories) functions. Additional functions can be loaded on the script level with "LoadPlugin()" for example.

And yes, a plugin, once properly initialised, can use any internal Avisynth function and (I think) any function from other loaded external plugins.

[hello_hello]

When you open an IFO or a stand-alone chapters file with MeGUI's Chapter Creator and select xml as the chapter output file, there's a drop down box for selecting a frame rate. Maybe I'm silly, but changing the frame rate doesn't appear to do anything. I thought maybe it'd apply some sort of time-stretch to match a change in video duration. That's probably the only time changing the frame rate when saving a txt or xml chapters file makes sense anyway, as if the video duration doesn't change the chapters would remain at the same point in time.

If you select qpf as the output file, the frame rate option does have an effect, although the assumption seems to be the video duration is unchanged and therefore the frame numbers being saved to the qp file change accordingly. Possibly handy if you're applying IVTC or Bob deinterlacing, but other than that?

What'd be nice would be the ability to select both an input and output frame rate, allowing the time stretching of chapters. Much like ChapterGen does.

When saving a qp file, the frame rate option could continue to work the way it currently does. If you wanted to apply PAL slowdown to a source (for example) you could time-stretch the chapters and save a new chapters file, then use it as the source for creating a matching qp file.

Cheers.

[tppytel]

Originally Posted by hello_hello

Maybe I'm silly, but changing the frame rate doesn't appear to do anything.

Funny... I just bumped into this today myself while slowing down a progressive PAL video to film rate, something I don't usually have reason to do.

Either the drop-down frame rate selector shouldn't be there for xml files, or it should time-stretch the chapters appropriately.

[maxks]

Hi guys, i have this problem...

I want re-encode a Bluray with Megui but i dont know what happened.

I need your help.

[LigH]

Try less Unicode characters in paths. Restricting to latin characters is much safer.

And read the forum rules again. Pirated moviez are not welcome here.

[Zathor]

Originally Posted by hello_hello

What'd be nice would be the ability to select both an input and output frame rate, allowing the time stretching of chapters. Much like ChapterGen does.

When saving a qp file, the frame rate option could continue to work the way it currently does. If you wanted to apply PAL slowdown to a source (for example) you could time-stretch the chapters and save a new chapters file, then use it as the source for creating a matching qp file.

I am working on it. There will be a second FPS selector for the input frame rate. If you have chapters set with static timecodes (you do not know the input FPS for sure = txt/xml or manually added chapters) changing the input frame rate will not change the time codes. However input an output frame rate are always used to determine the stretch factor. Changing the input frame rate will always change also the output FPS so that it does match (to avoid an unwanted time stretch).

[hello_hello]

Originally Posted by Zathor

I am working on it. There will be a second FPS selector for the input frame rate. If you have chapters set with static timecodes (you do not know the input FPS for sure = txt/xml or manually added chapters) changing the input frame rate will not change the time codes. However input an output frame rate are always used to determine the stretch factor. Changing the input frame rate will always change also the output FPS so that it does match (to avoid an unwanted time stretch).

Awesome! Thanks.

[LigH]

x265 v2.8 released (stable, +1 is only the version tag)

[Melan]

Whether there is a possibility so that you add the options "File Title" and "Global Tags" to MKV Muxer?

[olif]

Hi,

is it possible to create a video "web optimized" right now?

And can you recommend a manual for all the settings in the AVS? There are a lot, but some of them are old or not actual.

Thanks.

[LigH]

A "web optimization" depends mainly on the desired container format, and mainly refers to an early position of keyframe index chunks in the container, already before the video content is available. The MP4 container (via MP4Box as multiplexer) supports H.264/AVC or H.265/HEVC video content and is usually generated in "web optimized" order per default, IIRC. The MKV container would support this as well, especially in the WebM subformat, but MeGUI does not generate its supported video formats (VP8 / VP9).