MeGUI: bug reports and feature requests

[LouieChuckyMerry]

Maybe it's because my PC's old and it's a slow script and it's been a while since I encoded any 1080p video, but I don't recall such a large delay time between MeGUI starting encoding and realising it had started encoding. The progress window is really slow to respond to changes in encoding speed, so maybe it's related to that (I wish it was responsive enough to show you sudden changes in encoding speed instead of slow enough to show you something that probably happened 20 minutes ago).

This was what I meant though. 100 frames have been encoded and the job queue still hasn't caught up (job5 running).
I'm using an old XP compatible version of LSmash, but even so, this feels like something new.

PS. I just ran a short encode (100 frames) of the same video, only without any filtering aside from resizing in the script, and when it'd finished encoding the job queue still showed "waiting". When I tried deleting the job from the queue manually, MeGUI found a new excuse to crash. :)

https://s22.postimg.cc/bxwqle201/waiting.gif

I paid extra attention when I started my most recent encode and, although it does seem a bit slower to get going, it changed from "waiting" to "processing" as it should. My system is Win 7 64 bit with 12GB RAM. How much RAM do you have? Perhaps it's simply an XP and-or RAM issue?

[VoodooFX]

Try remux your mkv source with MkvToolNixGUI before, and repeat the MeGUI recode.

Remuxing with MkvToolNix v23 didn't helped, only removing Portuguese subs solved error.

[Zathor]

Yes, here is log (after oneclick error I aborted audio job):
https://pastebin.com/gNijDJmS

btw I get same error " 4 is not valid for 'index' " when I edit x265 preset in oneclick and try to save it(clicking around presets error sometimes disappears, still I dunno why or when).

As you are able to reproduce it:
http://megui.org/megui_debug.7z
extract the content of eitehr the 32 or the 64 folder (depending on your MeGUI build), reprocude the error, close MeGUI & upload the log.

[VoodooFX]

As you are able to reproduce it:
http://megui.org/megui_debug.7z
extract the content of eitehr the 32 or the 64 folder (depending on your MeGUI build), reprocude the error, close MeGUI & upload the log.

Here you go:
https://pastebin.com/ixWEYDP1

[Zathor]

LouieChuckyMerry / hello_hello: Could you please try 2860? It should now properly detect that the included portable AviSynth is not used. Please try also if the MeGUI setting "log debug information" changes a thing (with the next restart).

Here you go:
https://pastebin.com/ixWEYDP1
Thanks, will have a look in the next days.

[Statick]

request:

I'd really like a way of accessing the input filename from within the OneClick encoder AVISynth script

specifically I want to access the .d2v file generated, which is always named after the input filename, and reference this in the script. something like %input_filename% would do the job, like this:

tfm(d2v="%input_filename%.d2v")

I'm sure there are other paramters that would be useful if exposed this way, but this is the only one I'm after!

Currently I have to edit the AVISynth profile for every single video I encode, which for several hundred videos is extremely long-winded and error prone

[hello_hello]

LouieChuckyMerry / hello_hello: Could you please try 2860? It should now properly detect that the included portable AviSynth is not used. Please try also if the MeGUI setting "log debug information" changes a thing (with the next restart).

Thanks for the effort!
Now you've made me feel bad for being the bearer of bad news.

[Warning] AviSynth Information
-[Information] AviSynth Wrapper
--[Information] Version: 1.0.2847.0
--[Information] Date: 06-05-2018
--[Information] Interface: 3
-[Information] AviSynth
--[Information] File Version: 2.6.0.6
--[Information] File Date: 31-03-2015
--[Information] File Name: Avisynth 2.6
--[Information] File Path: c:\windows\system32\avisynth.dll
--[Information] AviSynth Version: AviSynth 2.60, build:Mar 31 2015 [16:38:54]
--[Information] AviSynth+: false
--[Information] AviSynth MT: false
--[Information] AviSynth Status: active
-[Warning] AviSynth portable
--[Information] File Version: 0.1
--[Information] File Date: 28-03-2018
--[Information] File Name: AviSynth+ 0.1 (r2664, MT, i386)
--[Information] File Path: c:\program files\megui\avisynth.dll
--[Warning] AviSynth Status: inactive - portable AviSynth build cannot be used. The loaded DLL is: c:\windows\system32\avisynth.dll

PS It makes no difference if the "log debug info" option is enabled/disabled.

[LigH]

c:\program files\megui\avisynth.dll

is probably protected by the UAC: Windows doesn't allow manipulation of files in this directory branch without Administrator access rights.

That's why we keep recommending not to install MeGUI there, over and over ... or you would have to disable the UAC, which is a security risk.

[Statick]

is probably protected by the UAC: Windows doesn't allow manipulation of files in this directory branch without Administrator access rights.

That's why we keep recommending not to install MeGUI there, over and over ... or you would have to disable the UAC, which is a security risk.

I have "run this program as administrator" selected and it seems to solve all such problems, albeit that I have to click the "yes" prompt every time I open the program. I could be missing something though.

[StainlessS]

Zathor,
I have been experiencing some problems with both stable and developer for some months (WXP32SP3).
On checking Changelog, see this

- Windows Vista and older is not supported

The only problem I'm having is using MeGUI_AutoEncode_Batcher, which uses AutoIt code to add avs scripts to the Auto Encode queue.
Problem arises when Preview Window is opened (after avs script load) and the batcher clicks close Button (little x close alias ALT/F4).
Seems that the problem arises due to close button being clicked before MeGUI is ready, ie MeGUI is still doing its multiple scanning
of Avs script and has not as yet presented the clip graphic in the preview window, when close button is clicked it crashes MeGUI.
(the Batcher is un-affected).

I have been putting off posting this problem report, in hope of it disappearing, but update earlier today and then saw changelog.
I've tried adding in a 10 second delay after Preview Window appears, and that fixes my problem, and so I have to assume
that problem could also affect systems after VISTA, if user clicks ALT/F4 close button before MeGUI has finished whatever it does
during its multiple script scanning period.

Adding avs scripts by hand is no problem for me with current versions, but I like to use the batcher.
I was not at all aware until a short while ago (checking Changelog) that XP is no longer supported (in theory),

What is the latest version MeGUI that is supported for XP (I see no such dropping of support note in changelog).

Developer MeGUI 2860, stable 2836.

Thanks in advance.

EDIT: Batcher:- https://forum.doom9.org/showthread.php?t=163343

EDIT:
From current Changelog of both Stable and Development.
Known Problems:
- Windows Vista and older is not supported

from Full Changelog
2077 [Progress Window] lower also I/O and memory priority when priority below normal (requires Windows Vista or newer). Feature request #3468249
Is this the first one that does NOT support XP ?

EDIT: Found this on sourceforge
Known Problems: - Windows XP and older is not supported [2624]
So maybe 2525 last supported stable (despite me not knowing that neither development nor stable not supported since March 2015).

[tuanden0]

mkvmerge update version 24.0.0

[LouieChuckyMerry]

LouieChuckyMerry / hello_hello: Could you please try 2860? It should now properly detect that the included portable AviSynth is not used. Please try also if the MeGUI setting "log debug information" changes a thing (with the next restart).

Version 2860 seems to properly detect that the included AviSynth is not used; ticking "Log debug information" does change something: [Information] AviSynth+: false in the log became [Information] AviSynth+: true. However, now I receive an access error for loading ConvertStack.dll, and if I # that line of my script out I receive an access error for the next line, and so on. Here's the script:

# Set DAR in encoder to 16 : 9. The following line is for automatic signalling
global MeGUI_darx = 16
global MeGUI_dary = 9
SetMemoryMax(1024)
LoadPlugin("F:\[0]StandAloneApps\MeGUI-2500(core)2443(data)0.3.5(libs)[Portable]\Tools\Avs\plugins\ConvertStacked.dll")
LoadPlugin("F:\[0]StandAloneApps\MeGUI-2500(core)2443(data)0.3.5(libs)[Portable]\tools\lsmash\LSMASHSource.dll")
LWLibavVideoSource("D:\Temp\[0000]ReEncTemp\[1080p]AlohaBobbyAndRose[S]{1975}[1080p]\OriginalVideo,OriginalAudio.mkv")
SMDegrain(TR=3,ThSAD=700,RefineMotion=True,Plane=0,Chroma=False,Lsb=True,Lsb_Out=True)
F=DitherPost(Mode=-1)
S=F.FastLineDarkenMod()
D=MT_MakeDiff(S,F).Dither_Convert_8_To_16()
Dither_Add16(Last,D,Dif=True,U=2,V=2)
GradFun3(Radius=16,Lsb_In=True,Lsb=True)
Trim(11111,11666)
Dither_Out()
ConvertFromStacked(Bits=16)
Prefetch(7)

My system is Win 7 64 bit, UAC has been disabled since I opened the package, and portable MeGUI is on a RAMDisk, F:\.

[LigH]

Sounds like a misinterpretation of the confusingly bracketed path names... is there any reason to interpret them?

I would guess if you simplified the path and file names as much as possible, there may be no issue?

[Groucho2004]

Sounds like a misinterpretation of the confusingly bracketed path names... is there any reason to interpret them?

I would guess if you simplified the path and file names as much as possible, there may be no issue?
Misinterpretation? All the characters in the path names are valid.

[LouieChuckyMerry]

Sounds like a misinterpretation of the confusingly bracketed path names... is there any reason to interpret them?

I would guess if you simplified the path and file names as much as possible, there may be no issue?

I've been using those path names with SEt's AviSynth MT for some years without issue. Would AviSynth+ be different that way?

[hello_hello]

is probably protected by the UAC: Windows doesn't allow manipulation of files in this directory branch without Administrator access rights.

That's why we keep recommending not to install MeGUI there, over and over ... or you would have to disable the UAC, which is a security risk.

Fortunately, I'm in a UAC free zone (still running XP).

How do people put up with the crap? I plugged a USB hard drive into my ex's laptop the other day, to copy some stuff to the laptop drive, and UAC had to bother me to ask permission to access it. More than once, I think.

[videoh]

It's easy to turn off completely if you don't like it.

[LigH]

Misinterpretation? All the characters in the path names are valid.

So, do you see any better reason for

now I receive an access error for loading ConvertStack.dll, and if I # that line of my script out I receive an access error for the next line, and so on

or maybe I misunderstood the meaning of the term "access error"?

[Groucho2004]

maybe I misunderstood the meaning of the term "access error"?That's one possibility.

[Groucho2004]

I'm curious about the "portable mode" in Megui.
I suppose this option will load the included avisynth.dll instead of the DLL that was installed in System32/SysWow64.

What about the plugins that were installed with Avisynth which are referenced in the registry? The only way I can see to avoid these being used is to have an explicit "LoadPlugin()" call for each plugin used in the script, right?

[hello_hello]

I'm curious about the "portable mode" in Megui.
I suppose this option will load the included avisynth.dll instead of the DLL that was installed in System32/SysWow64.

That's the theory, although it still isn't working correctly for me.

What about the plugins that were installed with Avisynth which are referenced in the registry? The only way I can see to avoid these being used is to have an explicit "LoadPlugin()" call for each plugin used in the script, right?

Would it be preferable for MeGUI not to use auto-loading plugins? If it didn't, when Avisynth is installed other programs could open scripts that rely on auto-loading plugins but they'd fail to open in MeGUI.

[LigH]

I believe (strongly, like I read it before) that MeGUI redirects the auto-load directory during its activity. AviSynth may have an API to change the location read from the registry after the initialization of its interface.

[Groucho2004]

I believe (strongly, like I read it before) that MeGUI redirects the auto-load directory during its activity. AviSynth may have an API to change the location read from the registry after the initialization of its interface.
There are two ways of which I'm aware to disable auto-loading from directories referenced in the registry:
1. Use ClearAutoloadDirs() (requires AVS+)
2. Remove the registry entries (quite drastic)

Maybe Megui is using one of these methods. I'm too lazy to dig through the code so maybe the developer(s) can shed some light.

[Zathor]

Zathor,
I have been experiencing some problems with both stable and developer for some months (WXP32SP3).
On checking Changelog, see this

- Windows Vista and older is not supported

The MeGUI core still does work with XP (and Vista), however the external tools may not and most important I will not spend time to test anything with XP/Vista and I will not fix any issues which arise only on those OS. I simply do not have the time.

The only problem I'm having is using MeGUI_AutoEncode_Batcher, which uses AutoIt code to add avs scripts to the Auto Encode queue.
Problem arises when Preview Window is opened (after avs script load) and the batcher clicks close Button (little x close alias ALT/F4).
Seems that the problem arises due to close button being clicked before MeGUI is ready, ie MeGUI is still doing its multiple scanning
of Avs script and has not as yet presented the clip graphic in the preview window, when close button is clicked it crashes MeGUI.
(the Batcher is un-affected).
I tried to reproduce that but failed. Could you please describe in more detail how do you get it to crash?

[Zathor]

Version 2860 seems to properly detect that the included AviSynth is not used; ticking "Log debug information" does change something: [Information] AviSynth+: false in the log became [Information] AviSynth+: true.
Could you upload please both logs? (versions part is sufficient)

[Zathor]

I'm curious about the "portable mode" in Megui.
I suppose this option will load the included avisynth.dll instead of the DLL that was installed in System32/SysWow64.

What about the plugins that were installed with Avisynth which are referenced in the registry? The only way I can see to avoid these being used is to have an explicit "LoadPlugin()" call for each plugin used in the script, right?

MeGUI does copy in portable mode in every needed folder (encoder directories and the MeGUI root) the needed avisynth.dll + others (devil, redist).

Based on the the avs calls in the exe files - as none of them specifies a path - will based on the default dll search order first search in the local directory before the system ones are searched. So e.g. MeGUI.exe does call avisynthwrapper.dll which will call avisynth.dll

I have added in 2860 the information to the log which module path is used to detect potential issues.

And yes, to avoid any issues with then not autoloaded plugin dlls, there will be LoadPlugin calls for each needed function placed / but only for the ones MeGUI is using so e.g. convertstacked.dll is not loaded. I suggest to use the addautoloaddir() command.

As AVS+ will check for the registry keys and load the system installed plugin DLLs, it may potentially try to load dlls which will break AVS+.Not sure if such DLLs exist.

[Zathor]

Thanks for the effort!
Now you've made me feel bad for being the bearer of bad news.

PS It makes no difference if the "log debug info" option is enabled/disabled.

Thanks, I have only changed the detection method so while the checkbox is not ticked, you should still have the same result. But now it will be detected that not the portable one is used.

When the checkbox is ticked I do have explicit FreeLibrary calls in place to unload avisynth.dll used by avisynthwrapper.dll. This seems to have it changed for LouieChuckyMerry somehow.

[Groucho2004]

As AVS+ will check for the registry keys and load the system installed plugin DLLs, it may potentially try to load dlls which will break AVS+.Not sure if such DLLs exist.Probably not break but there are plugins that are not supported by AVS+ (CPP 2.0 and C 2.0).

[hello_hello]

Compatibility with auto-loading plugins isn't exactly a new problem. If there's auto-loading plugins then it's really up to the user to make sure they're compatible with MeGUI's portable Avisynth, otherwise you can tell MeGUI to use the installed Avisynth instead. It's not really any different from ensuring auto-loading plugins are compatible with the version of Avisynth you have installed.

[StainlessS]

I tried to reproduce that but failed. Could you please describe in more detail how do you get it to crash?

Well, the scripts I use often have a long (a couple of seconds) scan where auto border cropping & auto contrast scanning is done (scans about 40 frames from clip, evenly spread thoughout clip duration, and then the crop/contrast is set.
MeGUI does its own multiple scans of the script during both load and then again when clicking on AutoEncode. So for each of the MeGUI scans, the script does its own scan (occurs at script start up), so MeGUI may be busy for about 10 seconds after script load, and it is during this time that the preview window pops up.
There seems to have been some recent (within about 2 or 3 months) mod to MeGUI source that displays the preview window before the MeGUI multiple scans of script starts, and as the batcher clicks the ALT\F4 close button as soon as the preview window pops up, so when MeGUI blits the graphic to the window, it has already been closed, Bang, Crash Wallop.

Before the problem arose, the window would only show up after MeGUI multiple scans had completed, and so the batcher would not close the window, because it was not there.

That is how it seems to me.

EDIT: Above is not an XP issue, it will occur on any OS (if a batcher is used, or the user is super quick at closing the window, I have not as yet managed to be quick enough to click it manually fast enough to crash it).

[hello_hello]

StainlessS,
out of curiosity, do you have any problems with Avisynth plugins causing MeGUI to crash on XP?

If dither.dll or avspt.dll 1.27.2 are used in a script MeGUI always crashes when closing the preview, while version 1.27.1 is fine. MAA2() also does the same, although I haven't bothered trying to work out which plugin is to blame as I rarely use it.

I'm curious if that's peculiar to my XP installation.

Cheers.

[LouieChuckyMerry]

Could you upload please both logs? (versions part is sufficient)

Long story short, I've been switching between a portable MeGUI, Version 2855, that still works correctly with SEt's MT AviSynth 2.6.0.5 and then updating that to Version 2860 to try and sort out why AviSynth+ doesn't work (then deleting this entire folder and replacing it with the Version 2855 that works when I've something to encode). What I typed in post #6243 was copied-and-pasted from the log (the fact that AviSynth+ was true), but now I can't repeat it :( . The last updating of Version 2855 to Version 2860, then ticking "Log debug information", then restarting now shows [Information] AviSynth+: false. I don't know why. Also, when it stated true I could load my scripts that worked with SEt's MT and they would run but output the acid flashback stacked video with extremely high bit rate and extremely low FPS. Now, I can't even load a SEt script, MeGUI simply crashes. Here's the crash log:

Preliminary log file only. During closing of MeGUI the well formed log file will be written.

-[Information] Versions
--[Information] MeGUI: 2860 x86
--[Information] Update Check: development update server
-[Information] Operating System: Windows 7 Premium x64 SP1 (6.1.65536.7601)
-[Information] .NET Framework: 4.0 (4.0.0.0)
-[Information] .NET Framework: 4.7 (4.7.02558)
-[Information] Microsoft Visual C++ 2010 x64: 10.0.40219
-[Information] Microsoft Visual C++ 2010 x86: 10.0.40219
-[Information] Microsoft Visual C++ 2015 x64: 14.0.23506
-[Information] Microsoft Visual C++ 2017 x86: 14.14.26429
-[Information] Redistributables
-[Information] DPI: 100% (96/96)
-[Information] Resolution: 1600x900
-[Information] Primary Screen: True
-[Information] Monitor 1
--[Information] System Information
-[Information] Update detection
-[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.05.0.0 (08-05-2018)
-[Information] SevenZipSharp: 0.64.3890.29348 (02-01-2011)
-[Information] 7z: 9.20 (18-11-2010)
--[Information] Component Information
--[Information] [14 Jun 18 16:55:30] Using cached update config and server: http://megui.org/auto/
-[Information] Version: 1.0.2847.0
-[Information] Date: 06-05-2018
-[Information] Interface: 3
-[Information] AviSynth Wrapper
--[Information] [14 Jun 18 16:55:30] No package requires an update
-[Information] File Version: 2.6.0.5
-[Information] File Date: 20-02-2015
-[Information] File Name: Avisynth 2.6
-[Information] File Path: c:\windows\system32\avisynth.dll
-[Information] AviSynth Version: AviSynth 2.60, build:Feb 20 2015 [03:16:45]
-[Information] AviSynth+: false
-[Information] AviSynth MT: true
-[Information] AviSynth
--[Information] AviSynth Information
-[Information] MediaInfoWrapper
--[Information] [14 Jun 18 16:55:38] sessions open: 1, id: 109528: File: File: D:\Temp\[0000]ReEncTemp\[1080p]Zoolander2[S]{2016}[1080p]\ReEncZoo[1,100]-TrimTest.avs
-[Information] AviSynthWrapper
--[Information] [14 Jun 18 16:55:38] sessions open: 1, id: 106226: D:\Temp\[0000]ReEncTemp\[1080p]Zoolander2[S]{2016}[1080p]\ReEncZoo[1,100]-TrimTest.avs

[Zathor]

Long story short, I've been switching between a portable MeGUI, Version 2855, that still works correctly with SEt's MT AviSynth 2.6.0.5 and then updating that to Version 2860 to try and sort out why AviSynth+ doesn't work (then deleting this entire folder and replacing it with the Version 2855 that works when I've something to encode). What I typed in post #6243 was copied-and-pasted from the log (the fact that AviSynth+ was true), but now I can't repeat it :( . The last updating of Version 2855 to Version 2860, then ticking "Log debug information", then restarting now shows [Information] AviSynth+: false. I don't know why. Also, when it stated true I could load my scripts that worked with SEt's MT and they would run but output the acid flashback stacked video with extremely high bit rate and extremely low FPS. Now, I can't even load a SEt script, MeGUI simply crashes. Here's the crash log:
Do you have ticked the "always use the included avisynth" checkbox?
And when it crashes, what error message do you get?

[Zathor]

Well, the scripts I use often have a long (a couple of seconds) scan where auto border cropping & auto contrast scanning is done (scans about 40 frames from clip, evenly spread thoughout clip duration, and then the crop/contrast is set.
MeGUI does its own multiple scans of the script during both load and then again when clicking on AutoEncode. So for each of the MeGUI scans, the script does its own scan (occurs at script start up), so MeGUI may be busy for about 10 seconds after script load, and it is during this time that the preview window pops up.
There seems to have been some recent (within about 2 or 3 months) mod to MeGUI source that displays the preview window before the MeGUI multiple scans of script starts, and as the batcher clicks the ALT\F4 close button as soon as the preview window pops up, so when MeGUI blits the graphic to the window, it has already been closed, Bang, Crash Wallop.

Before the problem arose, the window would only show up after MeGUI multiple scans had completed, and so the batcher would not close the window, because it was not there.

That is how it seems to me.

EDIT: Above is not an XP issue, it will occur on any OS (if a batcher is used, or the user is super quick at closing the window, I have not as yet managed to be quick enough to click it manually fast enough to crash it).

Again, I would need more details to be able to reproduce it. E.g. can you share the script? Is there an error in the log?

[StainlessS]

E.g. can you share the script? Is there an error in the log?

Share Script, well not really, consists of maybe a dozen scripts, some quite significant in length, and a bucket load of plugins.
Error in the log, not concerning the error, just (from memory) a "MeGUI has crashed" style message box.

I was wrong, preview window does not show before MeGUI double scanning (based on below test script), but I seem to recall
that it does show the window borders with plain grey where graphic would be, and then crash before graphic blitted to the window.

I have not been able to reproduce the crash with a short test script, below, but if I put in a Sleep(10000) command ie sleep for 10 seconds
into the Batcher code, before close ALT/F4 close button then it does not crash.

Test script that failed to prompt the crash

Colorbars(Pixel_type="YV12").ShowFrameNumber.KillAudio
SAMPLES=2048 # Enought to have a longish timeout
FC=Framecount
Step=FrameCount/SAMPLES
RT_DebugF("Script Open Scan commence",name="Crash.avs: ")
#GScript("""
z=0.0
For(i=0,FC-1,Step) { # Time Waster
current_frame=i
z=z+AverageLuma
}
#""")
RT_DebugF("Scan complete, returning clip",name="Crash.avs: ")
Return Last


DebugView result

00000001 0.00000000 RemoveDirt 0.9 # AutoLoaded plugins
00000002 1.12014675 SSETools 0.1
00000003 1.18845010 RT_DebugF: Init_ExternalPlugins
00000004 1.20852351 RT_DebugF: .\FFMS2000_CPP\ffms2.dll LOADED
00000005 1.23122072 Crash.avs: Script Open Scan commence
00000006 27.22969246 Crash.avs: Scan complete, returning clip # End of scan 1 before Preview
00000007 27.60651970 RemoveDirt 0.9
00000008 28.72829628 SSETools 0.1
00000009 28.79436684 RT_DebugF: Init_ExternalPlugins
00000010 28.81436348 RT_DebugF: .\FFMS2000_CPP\ffms2.dll LOADED
00000011 28.83756065 Crash.avs: Script Open Scan commence
00000012 54.90752029 Crash.avs: Scan complete, returning clip # End of scan 2 Preview shows after this (crashes after this usually)
00000013 57.81261444 RemoveDirt 0.9
00000014 58.93026733 SSETools 0.1
00000015 58.99621582 RT_DebugF: Init_ExternalPlugins
00000016 59.01642990 RT_DebugF: .\FFMS2000_CPP\ffms2.dll LOADED
00000017 59.03916550 Crash.avs: Script Open Scan commence
00000018 85.08772278 Crash.avs: Scan complete, returning clip # End of AutoEncode scan


I shall try to find a fix within the Batcher, maybe try a 1 second delay, see if that works.

Anyway, sorry for bothering you, and nice work in reducing the MeGUI pre-scan count to 2 before Preview (was some time ago about 7),
and 1 scan for the AutoEncode (was about 5 I think).
EDIT: The crash seems to happen more often on a P4 3.0 GHz (with HyperThreading) than on my Quad Core Duo 2.4 GHz.

EDIT:
StainlessS,
out of curiosity, do you have any problems with Avisynth plugins causing MeGUI to crash on XP?
Never had any problems with MeGUI and other dll's at all (although I dont usually use dither and the other dll which I'm not familiar with).
EDIT: I assume that your 'avspt.dll' should actually be 'avstp.dll', which I do have (but dont offhand know what it does, something to do with dither I think).

[hello_hello]

Never had any problems with MeGUI and other dll's at all (although I dont usually use dither and the other dll which I'm not familiar with).
EDIT: I assume that your 'avspt.dll' should actually be 'avstp.dll', which I do have (but dont offhand know what it does, something to do with dither I think).

Interesting. I just re-installed an old image of XP because the one I was using was nearly five years old and started blue-screening the other day, but the problem still exists. I might have to re-install XP from scratch to see what happens. Or just bite the bullet and download Linux Mint and never look back.

Yes, it should have been avstp.dll. It comes with the dither plugin. Something about internal plugin multi-threading, from memory.

Cheers.

[LouieChuckyMerry]

Do you have ticked the "always use the included avisynth" checkbox?

D'oh! Good thing you're the developer, Zathor, and Happy Friday :) . Anyway, now that you've pointed out the obvious, here are the version logs you requested earlier, all from portable MeGUI on a RAMDisk, F:\.

NOTE: At first, after updating and ticking "Always use included AviSynth" then restarting, the log would still show ----[Information] AviSynth+: false. However, after a bit of checking, it turns out that ffmpeg wasn't updating because the package was disabled. Once I manually updated ffmpeg, from Version 3.4 to Version 4.0, and restarted the log shows ----[Information] AviSynth+: true. This is probably why there was an issue before, with the one time true but other time false, because I remember manually updating ffmpeg the first time but I didn't update it the second time.

First, Version 2855 working well with SEt's MT AviSynth:

[Information] Log
-[Information] Versions
--[Information] MeGUI: 2855 x86
--[Information] Update Check: Disabled
--[Information] System Information
---[Information] Operating System: Windows 7 Premium x64 SP1 (6.1.65536.7601)
---[Information] .NET Framework: 4.0 (4.0.0.0)
---[Information] .NET Framework: 4.7 (4.7.02558)
---[Information] Redistributables
----[Information] Microsoft Visual C++ 2010 x64: 10.0.40219
----[Information] Microsoft Visual C++ 2010 x86: 10.0.40219
----[Information] Microsoft Visual C++ 2015 x64: 14.0.23506
----[Information] Microsoft Visual C++ 2017 x86: 14.14.26429
---[Information] DPI: 100% (96/96)
---[Information] Monitor 1
----[Information] Resolution: 1600x900
----[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.05.0.0 (08-05-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.2847.0
----[Information] Date: 06-05-2018
----[Information] Interface: 3
---[Information] AviSynth
----[Information] File Version: 2.6.0.5
----[Information] Date: 20-02-2015
----[Information] Name: Avisynth 2.6
----[Information] Version: AviSynth 2.60, build:Feb 20 2015 [03:16:45]
----[Information] AviSynth+: false
----[Information] MT: true
----[Information] Status: active
---[Information] AviSynth portable
----[Information] File Version: 0.1
----[Information] Date: 28-03-2018
----[Information] Name: AviSynth+ 0.1 (r2664, MT, i386)
----[Information] Status: inactive
-[Information] Update detection
--[Information] [15 Jun 18 09:18:34] Automatic update is disabled
--[Information] [15 Jun 18 09:18:34] Using cached update config and server: http://megui.tmebi.de/test/
--[Information] [15 Jun 18 09:18:34] There is 1 package which can be updated: MeGUI

Second, the previous version updated and with "Always use included AviSynth" ticked:

[Warning] Log
-[Warning] Versions
--[Information] MeGUI: 2860 x86
--[Information] Update Check: development update server
--[Information] System Information
---[Information] Operating System: Windows 7 Premium x64 SP1 (6.1.65536.7601)
---[Information] .NET Framework: 4.0 (4.0.0.0)
---[Information] .NET Framework: 4.7 (4.7.02558)
---[Information] Redistributables
----[Information] Microsoft Visual C++ 2010 x64: 10.0.40219
----[Information] Microsoft Visual C++ 2010 x86: 10.0.40219
----[Information] Microsoft Visual C++ 2015 x64: 14.0.23506
----[Information] Microsoft Visual C++ 2017 x86: 14.14.26429
---[Information] DPI: 100% (96/96)
---[Information] Monitor 1
----[Information] Resolution: 1600x900
----[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.05.0.0 (08-05-2018)
---[Information] SevenZipSharp: 0.64.3890.29348 (02-01-2011)
---[Information] 7z: 9.20 (18-11-2010)
--[Warning] AviSynth Information
---[Information] AviSynth Wrapper
----[Information] Version: 1.0.2847.0
----[Information] Date: 06-05-2018
----[Information] Interface: 3
---[Information] AviSynth
----[Information] File Version: 2.6.0.5
----[Information] File Date: 20-02-2015
----[Information] File Name: Avisynth 2.6
----[Information] File Path: c:\windows\system32\avisynth.dll
----[Information] AviSynth Version: AviSynth 2.60, build:Feb 20 2015 [03:16:45]
----[Information] AviSynth+: false
----[Information] AviSynth MT: true
----[Information] AviSynth Status: active
---[Warning] AviSynth portable
----[Information] File Version: 0.1
----[Information] File Date: 28-03-2018
----[Information] File Name: AviSynth+ 0.1 (r2664, MT, i386)
----[Information] File Path: f:\[0]standaloneapps\megui-2500(core)2443(data)0.3.5(libs)[portable]\avisynth.dll
----[Warning] AviSynth Status: inactive - portable AviSynth build cannot be used. The loaded DLL is: c:\windows\system32\avisynth.dll
-[Information] Update detection
--[Information] [15 Jun 18 09:31:42] Using cached update config and server: http://megui.org/auto/
--[Information] [15 Jun 18 09:31:43] No package requires an update

Finally, the previous but with "Log debug information" ticked, too:

[Information] Log
-[Information] Versions
--[Information] MeGUI: 2860 x86
--[Information] Update Check: development update server
--[Information] System Information
---[Information] Operating System: Windows 7 Premium x64 SP1 (6.1.65536.7601)
---[Information] .NET Framework: 4.0 (4.0.0.0)
---[Information] .NET Framework: 4.7 (4.7.02558)
---[Information] Redistributables
----[Information] Microsoft Visual C++ 2010 x64: 10.0.40219
----[Information] Microsoft Visual C++ 2010 x86: 10.0.40219
----[Information] Microsoft Visual C++ 2015 x64: 14.0.23506
----[Information] Microsoft Visual C++ 2017 x86: 14.14.26429
---[Information] DPI: 100% (96/96)
---[Information] Monitor 1
----[Information] Resolution: 1600x900
----[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.05.0.0 (08-05-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.2847.0
----[Information] Date: 06-05-2018
----[Information] Interface: 3
---[Information] AviSynth
----[Information] File Version: 2.6.0.5
----[Information] File Date: 20-02-2015
----[Information] File Name: Avisynth 2.6
----[Information] File Path: c:\windows\system32\avisynth.dll
----[Information] AviSynth Version: AviSynth 2.60, build:Feb 20 2015 [03:16:45]
----[Information] AviSynth+: false
----[Information] AviSynth MT: true
----[Information] AviSynth Status: inactive
---[Information] AviSynth portable
----[Information] File Version: 0.1
----[Information] File Date: 28-03-2018
----[Information] File Name: AviSynth+ 0.1 (r2664, MT, i386)
----[Information] File Path: f:\[0]standaloneapps\megui-2500(core)2443(data)0.3.5(libs)[portable]\avisynth.dll
----[Information] AviSynth Version: AviSynth+ 0.1 (r2664, MT, i386)
----[Information] AviSynth+: true
----[Information] AviSynth MT: true
----[Information] AviSynth Status: active
-[Information] Update detection
--[Information] [15 Jun 18 09:38:28] Using cached update config and server: http://megui.org/auto/
--[Information] [15 Jun 18 09:38:28] No package requires an update

[StainlessS]

I might have to re-install XP from scratch to see what happens. Or just bite the bullet and download Linux Mint and never look back.

Yes, it should have been avstp.dll. It comes with the dither plugin. Something about internal plugin multi-threading, from memory.

If you use WususOfflineUpdate, then be aware that M$ seems to have deliberately broken it a bit (for a new install of XPSP3).
So, if you have an old version of Wusus [EDIT: Offline Update], use that before trying to update with a newer one.
Otherwise it seems that you have to go through updates in date order and install manually (about a hundred or so), and then it will work ok.

Mint is pretty good, but I'm not sure, I may switch to Fedora (or LMDE).

Yep, I thought that plugin was something to do with multi-threading, now I know.

[manolito]

If you use WususOfflineUpdate, then be aware that M$ seems to have deliberately broken it a bit (for a new install of XPSP3).
So, if you have an old version of Wusus, use that before trying to update with a newer one.

No, this time it is not Microsoft's fault. WSUSOffline( NOT Wusus) v. 9.21 is the very last version which can retrieve Win XP updates, it is still available at the author's website:
http://download.wsusoffline.net/wsusoffline921.zip

Just for fun I tested it again, and it still downloads all the latest WinXP updates from the Microsoft servers without errors.


Cheers
manolito

[LigH]

WSUS = Windows Server Update Services (https://en.wikipedia.org/wiki/Windows_Server_Update_Services)

If you have a workgroup or domain with Windows server(s), you can let it download update packages once or the local network, and set up workstation PCs to download their update packages from your local server instead of Microsoft servers.

[StainlessS]

it still downloads all the latest WinXP updates from the Microsoft servers without errors.
Yes, but will get 'stuck' if trying to update a brand new XP32SP3 install.
One of the problems indicated below (I've experienced more than one prob)

2018-05-07 20:00:02:359 832 12c PT +++++++++++ PT: Synchronizing server updates +++++++++++
2018-05-07 20:00:02:359 832 12c PT + Offline serviceId = {8FFD129A-DD86-4A5D-933C-5F9985975929}
2018-05-07 20:00:02:359 832 12c PT WARNING: Cached cookie has expired or new PID is available
2018-05-07 20:00:37:031 832 12c Agent WARNING: Failed to evaluate Installed rule, updateId = {2190702A-4B98-4A80-90FF-0C6DB43C13CC}.200, hr = 8024E001
2018-05-07 20:01:30:515 832 12c PT +++++++++++ PT: Synchronizing extended update info +++++++++++
2018-05-07 20:01:30:515 832 12c PT + Offline serviceId = {8FFD129A-DD86-4A5D-933C-5F9985975929}
2018-05-07 20:01:30:515 832 12c OfflSnc WARNING: Failed to add file to the FileLocationList with 0x80240013
2018-05-07 20:02:13:640 832 12c OfflSnc WARNING: Failed to add file to the FileLocationList with 0x80240013
2018-05-07 20:02:13:640 832 12c OfflSnc WARNING: Failed to add file to the FileLocationList with 0x80240013
2018-05-07 20:02:13:640 832 12c OfflSnc WARNING: Failed to add file to the FileLocationList with 0x80240013
2018-05-07 20:02:13:640 832 12c OfflSnc WARNING: Failed to add file to the FileLocationList with 0x80240013
2018-05-07 20:02:13:640 832 12c OfflSnc WARNING: Failed to add file to the FileLocationList with 0x80240013
2018-05-07 20:02:13:640 832 12c OfflSnc WARNING: Failed to add file to the FileLocationList with 0x80240013
2018-05-07 20:02:13:640 832 12c OfflSnc WARNING: Failed to add file to the FileLocationList with 0x80240013
2018-05-07 20:02:13:640 832 12c OfflSnc WARNING: Failed to add file to the FileLocationList with 0x80240013
2018-05-07 20:02:13:656 832 12c OfflSnc WARNING: Failed to add file to the FileLocationList with 0x80240013
2018-05-07 20:02:13:656 832 12c OfflSnc WARNING: Failed to add file to the FileLocationList with 0x80240013
2018-05-07 20:02:13:656 832 12c OfflSnc WARNING: Failed to add file to the FileLocationList with 0x80240013
2018-05-07 20:02:13:656 832 12c OfflSnc WARNING: Failed to add file to the FileLocationList with 0x80240013
2018-05-07 20:02:13:656 832 12c OfflSnc WARNING: Failed to add file to the FileLocationList with 0x80240013
2018-05-07 20:02:13:656 832 12c OfflSnc WARNING: Failed to add file to the FileLocationList with 0x80240013
2018-05-07 20:02:13:656 832 12c OfflSnc WARNING: Failed to add file to the FileLocationList with 0x80240013
2018-05-07 20:02:13:656 832 12c OfflSnc WARNING: Failed to add file to the FileLocationList with 0x80240013
2018-05-07 20:02:13:656 832 12c OfflSnc WARNING: Failed to add file to the FileLocationList with 0x80240013
2018-05-07 20:02:13:656 832 12c OfflSnc WARNING: Failed to add file to the FileLocationList with 0x80240013
2018-05-07 20:02:13:656 832 12c OfflSnc WARNING: Failed to add file to the FileLocationList with 0x80240013
2018-05-07 20:02:13:656 832 12c OfflSnc WARNING: Failed to add file to the FileLocationList with 0x80240013
2018-05-07 20:02:13:656 832 12c OfflSnc WARNING: Failed to add file to the FileLocationList with 0x80240013
2018-05-07 20:02:13:656 832 12c OfflSnc WARNING: Failed to add file to the FileLocationList with 0x80240013
2018-05-07 20:02:13:656 832 12c OfflSnc WARNING: Failed to add file to the FileLocationList with 0x80240013
2018-05-07 20:02:13:656 832 12c OfflSnc WARNING: Failed to add file to the FileLocationList with 0x80240013
2018-05-07 20:02:13:656 832 12c OfflSnc WARNING: Failed to add file to the FileLocationList with 0x80240013
2018-05-07 20:02:13:656 832 12c OfflSnc WARNING: Failed to add file to the FileLocationList with 0x80240013
2018-05-07 20:02:13:656 832 12c OfflSnc WARNING: Failed to add file to the FileLocationList with 0x80240013
2018-05-07 20:02:13:656 832 12c OfflSnc WARNING: Failed to add file to the FileLocationList with 0x80240013
2018-05-07 20:02:13:656 832 12c OfflSnc WARNING: Failed to add file to the FileLocationList with 0x80240013
2018-05-07 20:02:13:656 832 12c OfflSnc WARNING: Failed to add file to the FileLocationList with 0x80240013
2018-05-07 20:02:13:656 832 12c OfflSnc WARNING: Failed to add file to the FileLocationList with 0x80240013
2018-05-07 20:02:13:703 832 12c OfflSnc WARNING: Failed to add file to the FileLocationList with 0x80240013
2018-05-07 20:02:13:718 832 12c OfflSnc WARNING: Failed to add file to the FileLocationList with 0x80240013

Goes on for hours like that before I quit, tried a number of things including updating the agent, I unfortunately did not keep the old version I had [EDIT: the complete download version from v9.2.1 from about 6 months ago].

EDIT:
this time it is not Microsoft's fault. WSUSOffline( NOT Wusus) v. 9.21
Last version is actually v9.2.4 (which I have, the actual old file you need is I think the wsusscn2.cab file).

[manolito]

Yes, but will get 'stuck' if trying to update a brand new XP32SP3 install.

Alright, I misunderstood your previous post, I thought you were saying that the download from the M$ servers was broken.

But I still believe that something must be wrong at your end, I spent some hours trying to reproduce your errors, but I couldn't, everything works just fine here.


This is what I did:

Dowloaded WSUSOfflineInstaller 9.24 (thanks for the hint), downloaded the updates and put the whole stuff on a USB stick.

Formatted the target partition (to FAT32)

Did a clean install of WinXP 32 SP3 Professional Corporate Edition. This installation CD had been slipstreamed to include SP3, but otherwise no tweaks like NLite or injecting SATA (AHCI) drvers.

Ran the UpdateInstaller from the previously created USB stick. Except for a few updates which were skipped because they were blacklisted all of the 134 updates were installed without issues, no errors like the ones you posted. (The small number of only 134 is because I deselected all the dotNet stuff.)

What does that mean?
Obviously your WinXP language is English while mine is German. I do not believe that this could make a difference.

What about your WinXP installation CD? Did you apply any fancy tweaks to it?


Whatever, at least for me the WSUSOffline app still works nicely for WinXP.


Cheers
manolito

[StainlessS]

Was slipstreamed SP2, and then SP3, into standard setup disk (pro GOLD, ie SP0), (but with Internet Explorer 8.0 [no idea why, I dont use it at all]
and also WMP 11.0 [dont use that either], nothing else I think).
I also set up a load of stuff including Visual Studio 2008, before using WSUSOffline,
Thanks Mani, I'll give it another go with WSUS updates applied first.

EDIT: To Below,
I updated the XP downloaded updates again via W10 Home, and noticed an error message (only in console window, not logged to log file),
that some *.txt md5 hash files were giving an "Access Denied" error message.
So having noticed this, I decided to download the entire update set again (with 9.2.4 about 5GB for chosen stuff [XP32+64]), and re-tried
the XP targetting, (I install all DotNet, from 1.1, 2.0, 3.5 [includes v3.0] and 4.0), but NOT CPP files, no remote desktop, no
Silverlight, no updated certificate things. [EDIT: + Powershell 2.0]
Installed just fine, 159 updates in total. Still got the "Failed to add file" type errror messages in windowsUpdate.log (not the
WSusOfflineUpdate.log), but only 30 seconds worth, and did not really take any more time than it should have.
All hunky dory now, my downloads were just messing up due to MD5 hash stuff. :)

EDIT: I saw no indication to what file/files the "Failed to add file" stuff referred to.

[manolito]

Did another test, this time "the works". Source CD was WinXP 32 SP3 Pro Corporate (SP3 slipstreamed into an earlier CD), and also injected the Intel IASTOR AHCI drivers. Of course the AHCI drivers were not used because my computer only has an IDE HDD interface, and the BIOS does not know a thing about SATA or AHCI.

For the update installation this time I selected everything except the WMP update. (dotNet, IE8, VC redist, DirectX) The dotNet stuff slowed down the update to a crawl (the whole dotNet update stuff is a major PITA IMO, whoever programmed this crap at Microsoft should be sent to a Singapore prison and receive at least 20 cane strokes on the bare).

But still, everything went well, all updates were installed without any error messages. So I feel that I am well prepared for a fresh install of WinXP...


Cheers
manolito

(Tomorrow it's off to Scotland, I won't post for the next 2 weeks...)

[Zathor]

2863 [AviSynth] changed default value of "always use the included AviSynth" to enabled
unload avisynthwrapper during startup detection to ensure that the portable build is used if required
2862 [Xvid] improved workaround to be able to use Xvid in portable AviSynth mode
2861 [OneClick] fixed an out of bounds error. bug #919

[Zathor]

The only problem I'm having is using MeGUI_AutoEncode_Batcher, which uses AutoIt code to add avs scripts to the Auto Encode queue.
Problem arises when Preview Window is opened (after avs script load) and the batcher clicks close Button (little x close alias ALT/F4).
Seems that the problem arises due to close button being clicked before MeGUI is ready, ie MeGUI is still doing its multiple scanning
of Avs script and has not as yet presented the clip graphic in the preview window, when close button is clicked it crashes MeGUI.
(the Batcher is un-affected).

That should be fixed with 2865:

2865 [AviSynth] improved error handling
2864 [L-SMASH Indexer] added high bit depth support

[StainlessS]

That should be fixed with 2865:

Thanx Z, much obliged, I'll give it a try soon. (I was testing some stuff to detect change from inital central dialog box average color, in any pixel,
or if some timeout occurred).

Manolito, added edit four posts earlier.

[hello_hello]

2863 [AviSynth] changed default value of "always use the included AviSynth" to enabled
unload avisynthwrapper during startup detection to ensure that the portable build is used if required

MeGUI (2865) doesn't always copy Avisynth.dll to the MeGUI folder when it's being told to use the included Avisynth.

When Avisynth.dll in the system32 folder is version 2.6, MeGUI does not copy Avisynth.dll to the MeGUI folder, and if I copy it there myself before starting MeGUI, it's removed when MeGUI starts.

--[Warning] AviSynth Information
---[Information] AviSynth Wrapper
----[Information] Version: 1.0.2847.0
----[Information] Date: 06-05-2018
----[Information] Interface: 3
---[Information] AviSynth
----[Information] File Version: 2.6.0.6
----[Information] File Date: 31-03-2015
----[Information] File Name: Avisynth 2.6
----[Information] File Path: c:\windows\system32\avisynth.dll
----[Information] AviSynth Version: AviSynth 2.60, build:Mar 31 2015 [16:38:54]
----[Information] AviSynth+: false
----[Information] AviSynth MT: false
----[Information] AviSynth Status: active
---[Warning] AviSynth portable
----[Information] File Version: 0.1
----[Information] File Date: 28-03-2018
----[Information] File Name: AviSynth+ 0.1 (r2664, MT, i386)
----[Information] File Path: c:\program files\megui\avisynth.dll
----[Warning] AviSynth Status: inactive - portable AviSynth build cannot be used. The loaded DLL is: c:\windows\system32\avisynth.dll

When I replace Avisynth.dll in the system32 folder with Avisynth+, MeGUI does copy Avisynth.dll to the MeGUI folder. I'm pretty sure it's actually using it, as when it's using the dll in the system32 folder the dll is normally locked and can't be deleted until I close MeGUI, but I can delete it.


--[Information] AviSynth Information
---[Information] AviSynth Wrapper
----[Information] Version: 1.0.2847.0
----[Information] Date: 06-05-2018
----[Information] Interface: 3
---[Information] AviSynth
----[Information] File Version: 0.1
----[Information] File Date: 28-03-2018
----[Information] File Name: AviSynth+ 0.1 (r2664, MT, i386)
----[Information] File Path: c:\windows\system32\avisynth.dll
----[Information] AviSynth Version: AviSynth+ 0.1 (r2664, MT, i386)
----[Information] AviSynth+: true
----[Information] AviSynth MT: true
----[Information] AviSynth Status: inactive
---[Information] AviSynth portable
----[Information] File Version: 0.1
----[Information] File Date: 28-03-2018
----[Information] File Name: AviSynth+ 0.1 (r2664, MT, i386)
----[Information] File Path: c:\program files\megui\avisynth.dll
----[Information] AviSynth Version: AviSynth+ 0.1 (r2664, MT, i386)
----[Information] AviSynth+: true
----[Information] AviSynth MT: true
----[Information] AviSynth Status: active

This time with Avisynth.dll removed from the system32 folder before starting MeGUI (Avisynth.dll is copied to the MeGUI folder and MeGUI can open scripts).

---[Information] AviSynth
----[Information] AviSynth Status: not installed
---[Information] AviSynth portable
----[Information] File Version: 0.1
----[Information] File Date: 28-03-2018
----[Information] File Name: AviSynth+ 0.1 (r2664, MT, i386)
----[Information] File Path: c:\program files\megui\avisynth.dll
----[Information] AviSynth Version: AviSynth+ 0.1 (r2664, MT, i386)
----[Information] AviSynth+: true
----[Information] AviSynth MT: true
----[Information] AviSynth Status: active

Hopefully this isn't an XP-specific thing. :)

Cheers.

[Zathor]

The fix in 2863 was intended for the issue LouieChuckyMerry had. He conformed that it was working when "show debug information" was enabled so I have enabled that now by default for that part. However I noticed that I changed it a bit and I do not know if it therefore still works as expected.

MeGUI calls AviSynth not directly (it uses avisynthwrapper.dll for that) but that does not change much. By default when searched for the AviSynth.dll it should open the one in the calling directory and then in the system directories (more details here: https://msdn.microsoft.com/en-us/library/windows/desktop/ms682586).

For you it seems that when the 2.6 from the system32 is loaded this is still used even when the avisynth.dll is now in the calling folder. But interestingly with AVS+ it seems to work.

The workaround implemented for LouieChuckyMerry did force an unload (and load) of avisynth.dll and avisynthwrapper.dll which seems to have fixed that for him.

If the wrong avs is used, could you please try to encode an avs file with version() inside e.g. with x264 to see which version is used there?

[Zathor]

MeGUI (2865) doesn't always copy Avisynth.dll to the MeGUI folder when it's being told to use the included Avisynth.

Could you please try these two builds?
http://megui.org/debug.7z

fix: may fix the change intended with 2863
force: force portable avisynth (will not try to detect system installed one)