Welcome to Doom9's Forum, THE in-place to be for everyone interested in DVD conversion. Before you start posting please read the forum rules. By posting to this forum you agree to abide by the rules. |
![]() |
#6241 | Link | |||
HeartlessS Usurer
Join Date: Dec 2009
Location: Over the rainbow
Posts: 6,286
|
Zathor,
I have been experiencing some problems with both stable and developer for some months (WXP32SP3). On checking Changelog, see this Code:
- Windows Vista and older is not supported 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. Quote:
Quote:
EDIT: Found this on sourceforge Quote:
__________________
I sometimes post sober. StainlessS@MediaFire ::: AND/OR ::: StainlessS@SendSpace "Some infinities are bigger than other infinities", but how many of them are infinitely bigger ??? Last edited by StainlessS; 12th June 2018 at 09:18. |
|||
![]() |
![]() |
![]() |
#6243 | Link | ||
Registered User
Join Date: Feb 2014
Posts: 245
|
Quote:
Quote:
|
||
![]() |
![]() |
![]() |
#6244 | Link |
German doom9/Gleitz SuMo
Join Date: Oct 2001
Location: Germany, rural Altmark
Posts: 5,755
|
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? |
![]() |
![]() |
![]() |
#6245 | Link |
Join Date: Mar 2006
Posts: 4,021
|
Misinterpretation? All the characters in the path names are valid.
__________________
Groucho's Avisynth Stuff | AVSMeter | Avisynth Info Tool | Universal Avisynth Installer |
![]() |
![]() |
![]() |
#6247 | Link | |
Registered User
Join Date: Mar 2011
Posts: 3,800
|
Quote:
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. |
|
![]() |
![]() |
![]() |
#6249 | Link | |
German doom9/Gleitz SuMo
Join Date: Oct 2001
Location: Germany, rural Altmark
Posts: 5,755
|
Quote:
or maybe I misunderstood the meaning of the term "access error"? |
|
![]() |
![]() |
![]() |
#6250 | Link |
Join Date: Mar 2006
Posts: 4,021
|
That's one possibility.
__________________
Groucho's Avisynth Stuff | AVSMeter | Avisynth Info Tool | Universal Avisynth Installer |
![]() |
![]() |
![]() |
#6251 | Link |
Join Date: Mar 2006
Posts: 4,021
|
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?
__________________
Groucho's Avisynth Stuff | AVSMeter | Avisynth Info Tool | Universal Avisynth Installer |
![]() |
![]() |
![]() |
#6252 | Link | |
Registered User
Join Date: Mar 2011
Posts: 3,800
|
Quote:
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. |
|
![]() |
![]() |
![]() |
#6253 | Link |
German doom9/Gleitz SuMo
Join Date: Oct 2001
Location: Germany, rural Altmark
Posts: 5,755
|
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.
|
![]() |
![]() |
![]() |
#6254 | Link | |
Join Date: Mar 2006
Posts: 4,021
|
Quote:
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.
__________________
Groucho's Avisynth Stuff | AVSMeter | Avisynth Info Tool | Universal Avisynth Installer |
|
![]() |
![]() |
![]() |
#6255 | Link | ||
Registered User
Join Date: Nov 2009
Posts: 2,399
|
Quote:
Quote:
|
||
![]() |
![]() |
![]() |
#6257 | Link | |
Registered User
Join Date: Nov 2009
Posts: 2,399
|
Quote:
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. |
|
![]() |
![]() |
![]() |
#6258 | Link | |
Registered User
Join Date: Nov 2009
Posts: 2,399
|
Quote:
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. |
|
![]() |
![]() |
![]() |
#6259 | Link |
Join Date: Mar 2006
Posts: 4,021
|
Probably not break but there are plugins that are not supported by AVS+ (CPP 2.0 and C 2.0).
__________________
Groucho's Avisynth Stuff | AVSMeter | Avisynth Info Tool | Universal Avisynth Installer |
![]() |
![]() |
![]() |
#6260 | Link |
Registered User
Join Date: Mar 2011
Posts: 3,800
|
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.
|
![]() |
![]() |
![]() |
Thread Tools | Search this Thread |
Display Modes | |
|
|