MeGUI Problem (fatal error - could not load file or assembly)

ect5150 · 13th February 2016, 01:50

Hey guys! Having problems I can't seem to track down myself - so I turn to the experts!

Let me preface the issue by saying I haven't touched any encoding since about the beginning of November. Decided to encode something the other day and MeGUI won't even load a script without getting a fatal error. Apparently MeGUI updated a few issues, but that's about the only major change on the system that was made (that I actively recall outside of installing a video game or two).

Reinstalled AVISynth and MeGUI from scratch, but I still get the same issues as seen here:

The error above is a trying to load the following script:

Code:

LoadPlugin("D:\Video\Programs\MeGUI\tools\lsmash\LSMASHSource.dll")
LWLibavVideoSource("D:\Video\Images\SGATE\T2_Video - -muxed.mkv.lwi")

crop(0, 140, 0, -140)
Suptitle(".\T5_Subtitle - English.sup")

I have noticed that when I remove the last line (the Suptitle function), it will load as expected. No issues. Apparently this is an AVISynth plugin problem for me? I have other similar scripts and more complicated scripts - all with the same issue. If it needs a function that exists within my AVISynth directory, I get the above error message.

I should mention, the script plays just fine (with any lines of code) in MPC-HC as well as AVSP (as seen here)

Any help or ideas would be greatly appreciated - and thank you in advance!

hello_hello · 13th February 2016, 11:48

I can confirm the problem running MeGUI 2627 on XP. I don't understand it.

I tried putting msvcp100.dll and msvcr100.dll in all the logical locations. I'm not sure which helped, but I put copies in the MeGUI folder (which MeGUI kindly removes every time it starts up) in the Avisynth plugins folder (with SupTitle.dll and SupCore.dll) and also in the same folder as the script and subtitle file. That initially allowed me to use SupTitle() in a script and preview it, but MeGUI would offer the same error if I then tried to use the Tools or Options menu, even after the script was closed. Eventually I gave up and removed all extra copies of msvcp100.dll and msvcr100.dll, only to discover the problem's gone. I can now use SupTitle() in a script without error and MeGUI's menus still work. Go figure......

It'll probably go back to the way it was after I reboot. I was always able to open a script containing SupTitle() with MPC-HC without an issue, so it seems like it is an MeGUI problem.

ect5150 · 14th February 2016, 00:11

For me, it's not just SupTitle() that causes the problem. But if there are others getting the error, then I guess it's time for the command line until the problem is fixed?

der_andi · 24th September 2016, 14:44

I have the same problem now. Runnig Win7 x64.

Scripts with SupTitle can be loaded, but I cannot access the x264 settings or most of the dialogs from the menu. Enqueuing the script works. Haven't tested an actual encode run yet.

It is of no use to just close the script or "Reset" the GUI. The error stays. Only restarting the GUI makes the settings accessible again, as long as no SupTitle'd script is loaded.

In the log files, there seems to be missing a "MeGUI.resources.dll" in the avisynth_plugin folder, but I am very sure that there was never such a file in it.

I also didn't change anything in the MeGUI program folder. It literally happened over night. Scripts without SupTitle do not produce this problem.

Any idea, how this can be fixed?

locotus · 24th September 2016, 16:49

Don't know if it may be related or no, but the last
windows 10 update erase both dll Hello-Hello is talking
about.

Actually, up to now, I haven't had any problem with Megui,
but did have it with some other programs that uses them
like DLNow Video Downloader.

Hope this could be helpful.

der_andi · 24th September 2016, 17:59

Any Windows 10 related solutions or proposals may not work with Windows 7. I also tried to supply all the logical places (System32, SysWOW64, avisynth_plugin) with the msvcp100.dll and msvcr100.dll. I also removed all of those. In the system folders, they reappear on their own. Nothing worked.

I got a new copy of MeGUI from sourceforge and disabled anti-virus before that. Maybe it is detecting a false-positive in the MeGUI software. In the end, all that did not help. The error persists. The strangest thing of all is, that I did not touch ANYTHING. Something else must have happend and broke it.

Zathor · 3rd October 2016, 12:09

https://sourceforge.net/p/megui/bugs/850/

I can reproduce it but I cannot fix it. It seems to be an incompatibility between AviSynth 2.6 and the way MeGUI reads the AVS content. Only workaround from my side would be to completly disable the in memory reading of AVS files (thus disabling previews, audio encoding, media information, ...) which I will not do for obvious reasons.

Use 2.5.x and it should work. As the author of the program lost the source code it is very unlikely that a proper plugin for 2.6 will appear.

13th February 2016, 01:50	#1 \| Link
ect5150 Registered User Join Date: Dec 2006 Posts: 39	MeGUI Problem (fatal error - could not load file or assembly) Hey guys! Having problems I can't seem to track down myself - so I turn to the experts! Let me preface the issue by saying I haven't touched any encoding since about the beginning of November. Decided to encode something the other day and MeGUI won't even load a script without getting a fatal error. Apparently MeGUI updated a few issues, but that's about the only major change on the system that was made (that I actively recall outside of installing a video game or two). Reinstalled AVISynth and MeGUI from scratch, but I still get the same issues as seen here: The error above is a trying to load the following script: Code: LoadPlugin("D:\Video\Programs\MeGUI\tools\lsmash\LSMASHSource.dll") LWLibavVideoSource("D:\Video\Images\SGATE\T2_Video - -muxed.mkv.lwi") crop(0, 140, 0, -140) Suptitle(".\T5_Subtitle - English.sup") I have noticed that when I remove the last line (the Suptitle function), it will load as expected. No issues. Apparently this is an AVISynth plugin problem for me? I have other similar scripts and more complicated scripts - all with the same issue. If it needs a function that exists within my AVISynth directory, I get the above error message. I should mention, the script plays just fine (with any lines of code) in MPC-HC as well as AVSP (as seen here) Any help or ideas would be greatly appreciated - and thank you in advance!

24th September 2016, 16:49	#5 \| Link
locotus Registered User Join Date: Nov 2005 Posts: 112	Don't know if it may be related or no, but the last windows 10 update erase both dll Hello-Hello is talking about. Actually, up to now, I haven't had any problem with Megui, but did have it with some other programs that uses them like DLNow Video Downloader. Hope this could be helpful. Last edited by locotus; 24th September 2016 at 19:56. Reason: Mismatch the other program name.

Thread Tools	Search this Thread
Show Printable Version Email this Page	Search this Thread: Advanced Search
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

13th February 2016, 11:48	#2 \| Link
hello_hello Registered User Join Date: Mar 2011 Posts: 4,829	I can confirm the problem running MeGUI 2627 on XP. I don't understand it. I tried putting msvcp100.dll and msvcr100.dll in all the logical locations. I'm not sure which helped, but I put copies in the MeGUI folder (which MeGUI kindly removes every time it starts up) in the Avisynth plugins folder (with SupTitle.dll and SupCore.dll) and also in the same folder as the script and subtitle file. That initially allowed me to use SupTitle() in a script and preview it, but MeGUI would offer the same error if I then tried to use the Tools or Options menu, even after the script was closed. Eventually I gave up and removed all extra copies of msvcp100.dll and msvcr100.dll, only to discover the problem's gone. I can now use SupTitle() in a script without error and MeGUI's menus still work. Go figure...... It'll probably go back to the way it was after I reboot. I was always able to open a script containing SupTitle() with MPC-HC without an issue, so it seems like it is an MeGUI problem.

14th February 2016, 00:11	#3 \| Link
ect5150 Registered User Join Date: Dec 2006 Posts: 39	For me, it's not just SupTitle() that causes the problem. But if there are others getting the error, then I guess it's time for the command line until the problem is fixed?

24th September 2016, 14:44	#4 \| Link
der_andi Registered User Join Date: Jul 2006 Posts: 26	I have the same problem now. Runnig Win7 x64. Scripts with SupTitle can be loaded, but I cannot access the x264 settings or most of the dialogs from the menu. Enqueuing the script works. Haven't tested an actual encode run yet. It is of no use to just close the script or "Reset" the GUI. The error stays. Only restarting the GUI makes the settings accessible again, as long as no SupTitle'd script is loaded. In the log files, there seems to be missing a "MeGUI.resources.dll" in the avisynth_plugin folder, but I am very sure that there was never such a file in it. I also didn't change anything in the MeGUI program folder. It literally happened over night. Scripts without SupTitle do not produce this problem. Any idea, how this can be fixed?

24th September 2016, 17:59	#6 \| Link
der_andi Registered User Join Date: Jul 2006 Posts: 26	Any Windows 10 related solutions or proposals may not work with Windows 7. I also tried to supply all the logical places (System32, SysWOW64, avisynth_plugin) with the msvcp100.dll and msvcr100.dll. I also removed all of those. In the system folders, they reappear on their own. Nothing worked. I got a new copy of MeGUI from sourceforge and disabled anti-virus before that. Maybe it is detecting a false-positive in the MeGUI software. In the end, all that did not help. The error persists. The strangest thing of all is, that I did not touch ANYTHING. Something else must have happend and broke it.

3rd October 2016, 12:09	#7 \| Link
Zathor Registered User Join Date: Nov 2009 Posts: 2,405	https://sourceforge.net/p/megui/bugs/850/ I can reproduce it but I cannot fix it. It seems to be an incompatibility between AviSynth 2.6 and the way MeGUI reads the AVS content. Only workaround from my side would be to completly disable the in memory reading of AVS files (thus disabling previews, audio encoding, media information, ...) which I will not do for obvious reasons. Use 2.5.x and it should work. As the author of the program lost the source code it is very unlikely that a proper plugin for 2.6 will appear.