MeGUI: General Questions and Troubleshooting Thread

[hello_hello]

I don't know if it's a bug or design, but the file indexer won't open any files in a directory/folder containing a sub-folder called VIDEO_TS, instead it insists on opening the contents of the VIDEO_TS folder.

As an example, I have several source files residing on the root of drive "E". Today I copied a VIDEO_TS folder to drive "E", so now the file indexer opens the DVD files whenever I try to open a file on the root of drive "E". Renaming the VIDEO_TS folder to something other than VIDEO_TS fixes the problem.

Thanks.

[HOB]

MeGUI will only check every few hours if there are new builds available. This is in order to prevent that the servers are flooded with requests.

Thanks for the feedback Zathor, most helpful.

[Rat Killer]

Can anyone point me to some instructions on how to do a reasonable conversion from 4k HDR HEVC to SDR? Been using MeGUI for a long time but this one has me stumped. Or is there no real way to do this in a straightforward manner?

[sneaker_ger]

MeGUI doesn't provide a simple way to do this. RipBot does.

https://forum.doom9.org/showthread.php?t=127611

https://forum.doom9.org/showthread.php?t=175125
https://forum.doom9.org/showthread.php?p=1800675
https://github.com/ifb/vapoursynth-tonemap/

[Zathor]

That is correct. AviSynth currently does not seem to provide a way to do HDR-->SDR and therefore MeGUI cannot do much. Other ideas are welcome!

[Tohno_Neil]

It is a little bug,

https://forum.doom9.org/showthread.php?p=1837772

[Zathor]

It is a little bug,

https://forum.doom9.org/showthread.php?p=1837772

Sorry, I do not get it. Please provide a full log.

[Tohno_Neil]

Sorry, I do not get it. Please provide a full log.

I turn to use the stable version,
and I delete all old logs.

And the problem happened again.

avs4x26x.exe
SHA-256:362902E8F0AE8B8B1050CDCB5CAC662DBE0221111C331EF7318B738D5AB94013
E:\drs\Megui\tools\x264\avs4x26x.exe

I don't edit the logs, megui run and crash.

[Zathor]

I don't know if it's a bug or design, but the file indexer won't open any files in a directory/folder containing a sub-folder called VIDEO_TS, instead it insists on opening the contents of the VIDEO_TS folder.

As an example, I have several source files residing on the root of drive "E". Today I copied a VIDEO_TS folder to drive "E", so now the file indexer opens the DVD files whenever I try to open a file on the root of drive "E". Renaming the VIDEO_TS folder to something other than VIDEO_TS fixes the problem.
That is "somehow" intended when a DVD or Blu-ray structure is detected. But you should be able to "cancel" that dialogue and your initialy selected file will be used.

[Zathor]

I turn to use the stable version,
and I delete all old logs.

And the problem happened again.

avs4x26x.exe
SHA-256:362902E8F0AE8B8B1050CDCB5CAC662DBE0221111C331EF7318B738D5AB94013
E:\drs\Megui\tools\x264\avs4x26x.exe

I don't edit the logs, megui run and crash.

And it does work with the other avs4x26x.exe file?
Btw. you can try to disable in the MeGUI settings this option:
"External Program Configuration\Use x64 tools if possible"

Then avs4x26x will not be used and directly the 32bit x264.exe. That way it will be a bit slower but it would be good to see if it will work then.

EDIT: I cannot see in any of your logs that a video encoding is started at all. Are you sure the error is related to that step? I only see the start of an audio encoding.

[hello_hello]

Does the following Avisynth info from MeGUI's log file make sense (MeGUI version 2830)?

--[Information] AviSynth Information
---[Information] AviSynth Wrapper
----[Information] Version: 1.0.2721.0
----[Information] Date: 29-04-2017
----[Information] Interface: 3
---[Information] AviSynth
----[Information] File Version: 2.6.0.6
----[Information] Date: 31-03-2015
----[Information] Name: Avisynth 2.6
----[Information] Version: AviSynth 2.60, build:Mar 31 2015 [16:38:54]
----[Information] AviSynth+: false
----[Information] MT: false
----[Information] Status: inactive
---[Information] AviSynth portable
----[Information] File Version: 0.1
----[Information] Date: 02-03-2018
----[Information] Name: AviSynth+ 0.1 (r2636, MT, i386)
----[Information] Version: AviSynth 2.60, build:Mar 31 2015 [16:38:54]
----[Information] AviSynth+: false
----[Information] MT: false
----[Information] Status: active

MeGUI seems to be saying it's using Avisynth+ and not using it at the same time. Is it an XP thing?

Checking Avisynth.dll in the MeGUI folder reveals the following:
AviSynth+ 0.1 (r2636, MT, i386)
So that seems okay, but no Avisynth+ specific functions seem to be working, so I suspect MeGUI is still using the installed Avisynth 2.6. When I renamed Avisynth.dll in the MeGUI folder to Avisynth.old, MeGUI could still open scripts even though it's configured to use the portable Avisynth+

Cheers.

[StainlessS]

HH, have you got an Avisynth.dll in system32/SysWOW64 ?

[LigH]

@StainlessS: The upper "legacy" AviSynth version with "inactive" status is the one probably installed in the Windows system; the lower "AviSynth portable" version is the one shipped with MeGUI.

Indeed, surprising that it is reported as neither plus nor MT. As if that was continued from the previous report.

[hello_hello]

HH, have you got an Avisynth.dll in system32/SysWOW64 ?

I'm still on XP, so it's in the C:\WINDOWS\system32 folder.

MeGUI used to switch between the installed Avisynth and it's portable version, but doesn't seem to do so now.

I usually use Avisynth 2.6 anyway. The only reason I started to think about it was due to this thread (https://forum.doom9.org/showthread.php?t=175355).

I thought maybe it was something peculiar to my PC as I tried a few older versions of MeGUI, telling it to use the included Avisynth and tested it's ability to open this script:
BlankClip(color=color_red)
and they opened it successfully, which I assume they shouldn't be able to, but then I tried MeGUI 2584 and the portable Avisynth+, it resulted in:
"I don't know what 'color_red' means",
so it appears it is using the portable Avisynth+.

The old version of the log file isn't as informative though.

[Information] Versions
-[Information] [31/03/18 8:04:17 PM] MeGUI: 2584
-[Information] [31/03/18 8:04:17 PM] Operating System: Windows XP Professional x86 SP3 (5.1.196608.2600)
-[Information] [31/03/18 8:04:17 PM] .NET Framework: 4.0 (4.0.30319)
-[Information] [31/03/18 8:04:18 PM] AviSynth: 2.6.0.6 (31-03-2015) (inactive)
-[Information] [31/03/18 8:04:18 PM] AviSynth+ portable: 0.1 (29-06-2017) (active)
-[Information] [31/03/18 8:04:18 PM] AvisynthWrapper: 1.0.2721.0 (29-04-2017)
-[Information] [31/03/18 8:04:18 PM] Haali Matroska Splitter: 1.13.138.14 (14-04-2013)
-[Information] [31/03/18 8:04:18 PM] Haali DSS2: (14-04-2013)
-[Information] [31/03/18 8:04:18 PM] ICSharpCode.SharpZipLib: 0.85.5.452 (07-08-2008)
-[Information] [31/03/18 8:04:18 PM] MediaInfo: 0.7.97.0 (29-06-2017)
-[Information] [31/03/18 8:04:18 PM] MediaInfoWrapper: 0.7.61.0 (06-01-2013)
-[Information] [31/03/18 8:04:18 PM] MessageBoxExLib: 1.0.2218.28317 (19-12-2008)
-[Information] [31/03/18 8:04:18 PM] SevenZipSharp: 0.64.3890.29348 (02-01-2011)
-[Information] [31/03/18 8:04:18 PM] 7z: 9.20 (18-11-2010)

I was just replacing MeGUI.exe in an old installation folder for testing and I'm not sure that's the best way to do it. Maybe it's Avisynthwrapper related. I wouldn't know. I'm short on time at the moment, but I can dig out some older MeGUI's tomorrow for testing if Zathor needs me to.

[Weirdo]

Reading in the release notes that the DPI issues have been fixed but I'm seeing no changes. From version's 2828 video player, W10 Pro, 125% custom DPI. Pressing the buttons usually makes the preview so large that it's unusable and needs to be closed/reopened.

https://i.imgur.com/sufyVDU.png

[mr2legs]

My first post and request for help. I have just upgraded to meGUI 2828 and there now seems to be no indexer to deal with avi (DivX5) files preparatory to conversion to AVC (mkv or mp4) files. Error message receive No Indexer Found. Has this functionality been removed or do I need to download additional components/files?

Thanks in advance.

[hello_hello]

mr2legs,
I don't know why it's telling you no indexer was found, but DirectShowSource and AviSource are disabled be default now. You can re-enable them in MeGUI's options. How are you opening the AVIs?

Changelog 2774 --> 2808
Features/Changes:
[AVS Script Creator] DirectShowSource/AVISource are disabled by default and have to be enabled in the MeGUI settings

[Zathor]

Reading in the release notes that the DPI issues have been fixed but I'm seeing no changes. From version's 2828 video player, W10 Pro, 125% custom DPI. Pressing the buttons usually makes the preview so large that it's unusable and needs to be closed/reopened.
https://i.imgur.com/sufyVDU.png
That is true, I did no changes for the video player. That part of MeGUI is (even more than the others) a piece of ... and hard to maintain. Could you please post your log file (versions block) and which size your video has?

My first post and request for help. I have just upgraded to meGUI 2828 and there now seems to be no indexer to deal with avi (DivX5) files preparatory to conversion to AVC (mkv or mp4) files. Error message receive No Indexer Found. Has this functionality been removed or do I need to download additional components/files?

As written by hello_hello we would need more details. In general both l-smash and ffms can still index AVI files.
EDIT: If you however try to open the AVI directly in the AVS Creator this is blocked by default (and even if not advisable can be reenabled).

Does the following Avisynth info from MeGUI's log file make sense (MeGUI version 2830)?
No, it does not. However I could not reproduce it. What happens when you only run a script with version() in it?

[hello_hello]

No, it does not. However I could not reproduce it. What happens when you only run a script with version() in it?

For MeGUI 2584 it shows Avisynth+ 0.1 etc when it's using the included Avisynth.

For MeGUI 2830 (and a couple of slightly older versions I tested), it shows Avisynth 2.6 even when MeGUI is set to use the portable Avisynth+.

I did try version() initially but it showed Avisynth 2.6 either way and I wasn't sure if Avisynth+ actually showed different version information. I forgot to try it again with MeGUI 2584.

Maybe it's an XP thing, although I can't imagine why.

[Zathor]

Checking Avisynth.dll in the MeGUI folder reveals the following:
AviSynth+ 0.1 (r2636, MT, i386)
So that seems okay, but no Avisynth+ specific functions seem to be working, so I suspect MeGUI is still using the installed Avisynth 2.6. When I renamed Avisynth.dll in the MeGUI folder to Avisynth.old, MeGUI could still open scripts even though it's configured to use the portable Avisynth+Cheers.
What happens if you use the old MeGUI version which does report proper results and update the AviSynth package to the one included on the update server?

[Weirdo]

Could you please post your log file (versions block) and which size your video has?
Video was 1920x1080.

-[Information] Versions
--[Information] MeGUI: 2828 x86
--[Information] Update Check: stable update server
--[Information] System Information
---[Information] Operating System: Windows 10 Pro 1709 x64 (10.0.16299.309)
---[Information] .NET Framework: 4.0 (4.0.0.0)
---[Information] .NET Framework: 4.7 (4.7.02556)
---[Information] DPI: 125% (120/120)
---[Information] Monitor 1
----[Information] Resolution: 1680x1050
----[Information] Primary Screen: True

[hello_hello]

What happens if you use the old MeGUI version which does report proper results and update the AviSynth package to the one included on the update server?

I made a copy of my current MeGUI 2830 folder and replaced MeGUI.exe with version 2584. When I ran the updater it appeared to want to "upgrade" the portable version to Avisynth 2.6.
I didn't update it though, and when I tested, it was correctly using the portable Avisynth+.

-[Information] Versions
--[Information] [01/04/18 5:23:56 PM] MeGUI: 2584
--[Information] [01/04/18 5:23:56 PM] Operating System: Windows XP Professional x86 SP3 (5.1.196608.2600)
--[Information] [01/04/18 5:23:56 PM] .NET Framework: 4.0 (4.0.30319)
--[Information] [01/04/18 5:23:56 PM] AviSynth: 2.6.0.6 (31-03-2015) (inactive)
--[Information] [01/04/18 5:23:56 PM] AviSynth+ portable: 0.1 (02-03-2018) (active)
--[Information] [01/04/18 5:23:56 PM] AvisynthWrapper: 1.0.2721.0 (29-04-2017)

If anything, I suspect the problem may have started when the Avisynth version information displayed in the log file was updated. I recall initially thinking it didn't seem right, but I didn't give it any further thought at the time as I normally use the installed Avisynth 2.6. Of course, that could simply be coincidence.

I'll try some different versions of MeGUI later on, maybe starting with a fresh installation of MeGUI, and if I discover anything interesting I'll report back.

[hello_hello]

I hope this doesn't turn out to be an XP issue.

After testing a bunch of old MeGUI versions, I found the last MeGUI that'll use the portable Avisynth+ is version 2624.
The next older version I have is 2620 and it also uses the portable Avisynth+. The next newer MeGUI I have is 2627 and it does not.

Could it have anything to do with this?

2627 [Main] detects during startup if AviSynth can be used
automatic fallback to the portable AviSynth
2626 [AvisynthWrapper] updated to recent avisynth.h (requires AviSynth 2.6)
improved error handling
added x64 support

For fun, I rebooted to fairly virgin copy of XP on another drive. I use it so rarely it still has Avisynth 2.5.8 installed. MeGUI 2830 went into a never ending re-installation cycle trying to install Avisynth+. All the required files appeared to be copied to the tools/avs folder, except for Avisynth.dll. I tried copying it to the tools/avs directory myself, but MeGUI deleted it when it was restarted, then went back to wanting to re-install it. The info in the log file got a bit funkier. Avisynth.dll was being copied to the MeGUI folder.

[Error] AviSynth Information
-[Information] AviSynth Wrapper
--[Information] Version: 1.0.2721.0
--[Information] Date: 29-04-2017
--[Information] Interface: 3
-[Information] AviSynth
--[Information] File Version: 2.5.8.5
--[Information] Date: 21-12-2008
--[Information] Name: Avisynth 2.5
--[Information] Version: AviSynth 2.58, build:Dec 22 2008 [08:46:51]
--[Information] AviSynth+: false
--[Information] MT: false
--[Information] Status: Installed AviSynth build is out of date.
-[Error] AviSynth portable
--[Information] File Version: 0.1
--[Information] Date: 02-03-2018
--[Information] Name: AviSynth+ 0.1 (r2636, MT, i386)
--[Error] Status: Installed AviSynth build cannot be used.
--[Information] Status: inactive
-[Error] AviSynth: not found

[Error] Update detection
-[Information] [01/04/18 8:48:14 PM] Using cached update config and server: http://megui.tmebi.de/test/
-[Information] [01/04/18 8:48:15 PM] There is 1 package which can be updated: AviSynth portable
-[Information] [01/04/18 8:48:15 PM] There is 1 package which can be updated: AviSynth portable
-[Information] [01/04/18 8:48:15 PM] updating package AviSynth portable as it is missing or outdated
-[Error] [01/04/18 8:48:23 PM] Component not found: C:\Program Files\MeGUI\tools\avs\AviSynth.dll

When I tried the same thing again with MeGUI 2632 the re-installation loop didn't happen, but it seemed to install Avisynth 2.6.0.6 as the portable version instead of Avisynth+. I'm a bit dubious as to whether it's actually using the portable version though. As version() wouldn't tell me anything I deleted Avisynth.dll from both the MeGUI and the tools/avs folders, yet MeGUI still happily opened a script (I think I tried that test after switching back to the XP with Avisynth 2.6 installed).

[LigH]

Despite all the warnings not to install MeGUI in "C:\Program files" (because the UAC will block attempts of updating files except MeGUI is started "as Administrator") ...

[gonca]

Did Windows XP have UAC?

[LigH]

Oops, no, I thought I closed this without sending my reply when I read this as well. :o

[gonca]

Its been a while since I used XP, wasn't sure myself anymore

[mr2legs]

mr2legs,
I don't know why it's telling you no indexer was found, but DirectShowSource and AviSource are disabled be default now. You can re-enable them in MeGUI's options. How are you opening the AVIs?

Thank you for your very swift reply.

The problem appears to be that the avi in question uses the DivX5 codec. I have tried other such files to the same effect - No Indexer. There is no problem with XVid avis which are indexed with LSmash or FFMS without difficulty. There are so few instances of DIVX5 around these days that this probably won't be that much of a hinderance. These are old files that I inherited. Interestingly The Solveig Splitter can split XVid avis but not DivX5 avis.

You suggested I enable DirectShowSource which I did and AVIsource to which I could find no options in MeGUI settings.

The principal reason I wanted to do all this was to add some chapters which AVIs do not support so a conversion to MKV or MP4 would be a first stage. Fortunately the somewhat less than sophisticated "AVC - All Video Converter" (freeware) was able to work with DivX5 and did a reasonable one-pass re-encode (DivX5 to Matroska).

I have converted many XVid avis with MeGUI in the past and I thought I had converted DivX too (with both codecs using the .AVI extension one tends to treat them as interchangeable) but perhaps there has never been an index for DivX.

If you can illuminate any of the above points then I should be grateful but if not it seems it is not the end of the world and thank you for looking at my problem.

[hello_hello]

mr2legs,
Until Zathor returns, maybe try changing the FourCC of an AVI to Xvid with MPEG4 Modifier (https://www.videohelp.com/software/MPEG4-Modifier) to see if MeGUI will index it. That's a wild guess by the way, as I've got nothing else. You might need to post your log file.


You suggested I enable DirectShowSource which I did and AVIsource to which I could find no options in MeGUI settings.

Enabling DirectShowSource enables them both.

The principal reason I wanted to do all this was to add some chapters which AVIs do not support so a conversion to MKV or MP4 would be a first stage.

Do you "need" to re-encode the video? If not you can remux MKVs while adding chapters/subtitles without re-encoding using MKVToolNixGUI (https://www.videohelp.com/software/MKVToolNix). If you do, it might pay to change the FourCC to Xvid first anyway. Some hardware players won't play DivX video. One of the Bluray players in this house will while the other won't (only I can't remember which is which off the top of my head). Changing the FourCC fixes that.
And you can also try remuxing an AVI as MKV to see if MeGUI will then index the MKV, so you can use it as the source.

[Zathor]

Reading in the release notes that the DPI issues have been fixed but I'm seeing no changes. From version's 2828 video player, W10 Pro, 125% custom DPI. Pressing the buttons usually makes the preview so large that it's unusable and needs to be closed/reopened.

This hopefully is now fixed in 2833.

[Zathor]

Thank you for your very swift reply.

The problem appears to be that the avi in question uses the DivX5 codec. I have tried other such files to the same effect - No Indexer. There is no problem with XVid avis which are indexed with LSmash or FFMS without difficulty. There are so few instances of DIVX5 around these days that this probably won't be that much of a hinderance. These are old files that I inherited. Interestingly The Solveig Splitter can split XVid avis but not DivX5 avis.

You suggested I enable DirectShowSource which I did and AVIsource to which I could find no options in MeGUI settings.

The principal reason I wanted to do all this was to add some chapters which AVIs do not support so a conversion to MKV or MP4 would be a first stage. Fortunately the somewhat less than sophisticated "AVC - All Video Converter" (freeware) was able to work with DivX5 and did a reasonable one-pass re-encode (DivX5 to Matroska).

I have converted many XVid avis with MeGUI in the past and I thought I had converted DivX too (with both codecs using the .AVI extension one tends to treat them as interchangeable) but perhaps there has never been an index for DivX.

If you can illuminate any of the above points then I should be grateful but if not it seems it is not the end of the world and thank you for looking at my problem.

Do you mind to upload short sample file?

[HOB]

Fantastic!
Just updated to MeGUI v2833 and DGindexNV 2053(20180402) and the audio file IS being placed right where it should be.

Once again...THANK YOU very much! :D

[videoh]

You're welcome and thanks for the status update, HOB. It took good coordination with Zathor, to whom thanks.

Now I have to port the changes to DGDecIM.

[HOB]

You're welcome and thanks for the status update, HOB. It took good coordination with Zathor, to whom thanks.

Now I have to port the changes to DGDecIM.

videoh

In the times we're living in it's very rewarding to see people working TOGETHER to make things work right.

You and Zathor have made a very positive impression on me...I thank you for getting this program to work but even more I thank you for reminding me there are still humans out their who deserve our respect...

Thank you both!

[Zathor]

Does the following Avisynth info from MeGUI's log file make sense (MeGUI version 2830)?
MeGUI seems to be saying it's using Avisynth+ and not using it at the same time. Is it an XP thing?

Reason are missing redist files for Visual C++ 2017. I have updated now the redist package. Could you please try it again?

[hello_hello]

Reason are missing redist files for Visual C++ 2017. I have updated now the redist package. Could you please try it again?

Bummer. It's still the same.
I did have the Visual C++ 2017 redistributable installed. The latest nnedi3 requires it, and it's working. The only oddity I noticed was it wasn't showing up in Add/Remove Programs, but all the same "api-ms-win" files were in the system32 folder. I re-installed it to make sure (it now shows up in Add/Remove Programs) but nothing has changed. I tried MeGUI 2830 without letting it update the runtime files, and then I updated the runtime files and MeGUI to version 2834. Same result either way. Avisynth is still showing as version 2.6 for the portable Avisynth.

Thanks.

[Information] Log
-[Information] Versions
--[Information] MeGUI: 2834 x86
--[Information] Update Check: development update server
--[Information] System Information
---[Information] Operating System: Windows XP Professional x86 SP3 (5.1.196608.2600)
---[Information] .NET Framework: 4.0 (4.0.30319)
---[Information] DPI: 100% (96/96)
---[Information] Monitor 1
----[Information] Resolution: 1920x1080
----[Information] Primary Screen: False
---[Information] Monitor 2
----[Information] Resolution: 1152x864
----[Information] Primary Screen: True
--[Information] Component Information
---[Information] Haali Media Splitter: 1.13.138.14 (14-04-2013)
---[Information] Haali DSS2: (14-04-2013)
---[Information] ICSharpCode.SharpZipLib: 0.85.5.452 (07-08-2008)
---[Information] MediaInfo: 18.03.1.0 (26-03-2018)
---[Information] SevenZipSharp: 0.64.3890.29348 (02-01-2011)
---[Information] 7z: 9.20 (18-11-2010)
--[Information] AviSynth Information
---[Information] AviSynth Wrapper
----[Information] Version: 1.0.2721.0
----[Information] Date: 29-04-2017
----[Information] Interface: 3
---[Information] AviSynth
----[Information] File Version: 2.6.0.6
----[Information] Date: 31-03-2015
----[Information] Name: Avisynth 2.6
----[Information] Version: AviSynth 2.60, build:Mar 31 2015 [16:38:54]
----[Information] AviSynth+: false
----[Information] MT: false
----[Information] Status: inactive
---[Information] AviSynth portable
----[Information] File Version: 0.1
----[Information] Date: 28-03-2018
----[Information] Name: AviSynth+ 0.1 (r2664, MT, i386)
----[Information] Version: AviSynth 2.60, build:Mar 31 2015 [16:38:54]
----[Information] AviSynth+: false
----[Information] MT: false
----[Information] Status: active
-[Information] Update detection
--[Information] [04/04/18 2:10:02 PM] Using cached update config and server: http://megui.tmebi.de/test/
--[Information] [04/04/18 2:10:03 PM] No package requires an update

[Zathor]

Bummer. It's still the same.
I did have the Visual C++ 2017 redistributable installed. The latest nnedi3 requires it, and it's working. The only oddity I noticed was it wasn't showing up in Add/Remove Programs, but all the same "api-ms-win" files were in the system32 folder. I re-installed it to make sure (it now shows up in Add/Remove Programs) but nothing has changed. I tried MeGUI 2830 without letting it update the runtime files, and then I updated the runtime files and MeGUI to version 2834. Same result either way. Avisynth is still showing as version 2.6 for the portable Avisynth.

Thanks.

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?

[rhaz]

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

Click Output and try doing any changes or just click Open it gives you error File not found, which doesn't make sense at all. You're not opening a file, you're saving a .d2v file ready for a job. It works if you click Queue, but that's not a solution for a DVD with multiple PGCs, you want to give custom paths and names.

update: on top of that, you cannot go back to Stable update server from Developmental, saving/exiting/restarting the application always resets to Developmental server.

[Zathor]

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

Click Output and try doing any changes or just click Open it gives you error File not found, which doesn't make sense at all. You're not opening a file, you're saving a .d2v file ready for a job. It works if you click Queue, but that's not a solution for a DVD with multiple PGCs, you want to give custom paths and names.


Thanks, will be looking into that.

update: on top of that, you cannot go back to Stable update server from Developmental, saving/exiting/restarting the application always resets to Developmental server.
Are you using the x64 build of MeGUI? Then this is to be expected as there is no stable build yet.

[Zathor]

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]

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]

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]

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]

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 (https://www.videohelp.com/software/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.