Avisynth_c.dll revisited

[Katie Boundary]

A terrible fate has befallen Defiant, my desktop of the past several years, and I've had to build a new one. this means I've had to reinstall everything, which means that I'm running into problems that I figured out how to solve several years ago and then forgot how I solved. In this case, Avisynth_c.dll is giving me headaches. Thanks to my previous two threads on the subject, I know that I shouldn't put it in the plugin autoload directory unless I need to load some Avisynth 2.0 C plugins and use STDcall for all the 2.5 C plugins. However, when it's NOT in the plugin autoload directory, vdub and Tsunami give me 3 error messages saying "The program can't start because avisynth-c.dll is missing from your computer. Try reinstalling the program". But then after clicking through all of those, everything works fine.

So how do I get rid of these errors without ruining my ability to actually use the loadcplugin command?

[Groucho2004]

Did you try this?

[StainlessS]

You can auto install C plugins, eg

InitExternalPlugins.avsi (my current init script)

fn1 ="C:\NON-INSTALL\DGMpgDec\DGDecode.DLL"
Exist(fn1) ? LoadPlugin(fn1) : NOP

fn2= "C:\NON-INSTALL\DGAVCDec\DGAVCDecode.dll"
Exist(fn2) ? LoadPlugin(fn2) : NOP

#fn3= "C:\Program Files\AviSynth\plugins\FFMS_C\ffms2.dll"                # FFMpegSource C Plugin
#Exist(fn3) ? LoadCPlugin(fn3) : NOP

fn4= "C:\Program Files\AviSynth\plugins\FFMS2000_CPP\ffms2.dll"           # FFMpegSource CPP Plugin
#Exist(fn4) ? LoadPlugin(fn4) : NOP
Exist(fn4) ? LoadPlugin(fn4) : RT_DebugF("FFMS2000_CPP: NOT FOUND") # added in BLUE

#fn5= "C:\Program Files\AviSynth\plugins\FFMS_CPP\ffms2_26.dll"            # FFMpegSource CPP Plugin
#Exist(fn5) ? LoadPlugin(fn5) : NOP

fn6= "C:\Program Files\AviSynth\plugins\LSMASH_CPP\LSMASHSource.dll"      # L-Smash CPP
Exist(fn6) ? LoadPlugin(fn6) : NOP

[Katie Boundary]

Originally Posted by Groucho2004

Did you try this?

No, I did not try a solution to a completely different and only tangentially related problem.

Originally Posted by StainlessS

You can auto install C plugins

Okay but will that work with C 2.5 plugins if avisynth_c.dll (which is for C 2.0 plugins) is in the autoload directory? And how would i modify it for my needs? I've never seen "avsi" files before so I can't make heads or tails of your code.

[FredThompson]

put avisynth_c.dll in a different directory in your path.

[Katie Boundary]

Okay, I found the answer. The secret is to install the x86 version of the Microsoft Visual C++ Runtime, 2010. This will also eliminate the error messages relating to vcruntime140.dll, msvcr100.dll, etc., which is what I was actually trying to solve when I figured this out.

Originally Posted by FredThompson

put avisynth_c.dll in a different directory in your path.

And how, exactly, is that supposed to make the "I can't find avisynth_c.dll" error messages go away?

[Groucho2004]

Originally Posted by Katie Boundary

No, I did not try a solution to a completely different and only tangentially related problem.

Your question was:

Originally Posted by Katie Boundary

So how do I get rid of these errors without ruining my ability to actually use the loadcplugin command?

The link I gave you showed you the solution to that problem.

I don't know why I even bother...

[Katie Boundary]

Originally Posted by Groucho2004

Your question was:

The link I gave you showed you the solution to that problem.

I don't know why I even bother...

Your proposal said "move avisynth_c.dll out of the auto-load directory"

Not having that file in the autoload directory was part of what was causing the problem to begin with.

[Groucho2004]

Originally Posted by Katie Boundary

Your proposal said "move avisynth_c.dll out of the auto-load directory"

Not having that file in the autoload directory was part of what was causing the problem to begin with.

So, you're getting an error from VDub even when you explicitly load avisynth_c.dll before your C2.0 plugin(s)?

How about posting the script that gives you trouble?

[Groucho2004]

Also, run AVSMeter with the switches "-avsinfo -log" and post the avsinfo_x86.log file.

[Katie Boundary]

Originally Posted by Groucho2004

So, you're getting an error from VDub even when you explicitly load avisynth_c.dll before your C2.0 plugin(s)?

I'm not using any "C2.0" plugins.

[Groucho2004]

Originally Posted by Katie Boundary

I'm not using any "C2.0" plugins.

In that case no program should complain about a missing avisynth_c.dll.
You could most likely locate your Avisynth problem by following my advice in my last post (#10).

[Katie Boundary]

I just reinstalled windows and avisynth on a newly acquired laptop and I'm seeing a lot of these old problems again. This time, however, the avisynth_c.dll error persists even after installing all the MS VC++ runtimes.

Originally Posted by Groucho2004

In that case no program should complain about a missing avisynth_c.dll.

And yet they do.

[Groucho2004]

Originally Posted by Katie Boundary

I just reinstalled windows and avisynth on a newly acquired laptop and I'm seeing a lot of these old problems again. This time, however, the avisynth_c.dll error persists even after installing all the MS VC++ runtimes.

Installing these runtimes will not help with anything related to avisynth_c.dll.

Originally Posted by Katie Boundary

I'm not using any "C2.0" plugins.

Originally Posted by Groucho2004

In that case no program should complain about a missing avisynth_c.dll.

Originally Posted by Katie Boundary

And yet they do.

Only C2.0 plugins complain about a missing avisynth_c.dll.



Anyway, run the Avisynth Info Tool and post the log (Save Info...).

[StainlessS]

Originally Posted by Groucho2004

Run the Avisynth Info Tool and post the log (Save Info...).

You know with 100% surety, that she aint gonna do it. EDIT: It aint Ghetto enough, bitchin' is though, apparently. [still, nice to see she finally saw sense and installed all runtimes]

[Groucho2004]

Originally Posted by StainlessS

nice to see she finally saw sense and installed all runtimes]

Not that it matters much but how do you know she installed all of them?

[StainlessS]

Originally Posted by Katie Boundary

I just reinstalled windows and avisynth on a newly acquired laptop and I'm seeing a lot of these old problems again. This time, however, the avisynth_c.dll error persists even after installing all the MS VC++ runtimes.

You guessin' that she's tellin' porkies ?

[Groucho2004]

Originally Posted by StainlessS

You guessin' that she's tellin' porkies ?

This post makes me think that she installs things randomly. I doubt very much that she knows the whole list of MS C++ runtimes.

[StainlessS]

Arh well, as they say, arrogance is bliss.

[Katie Boundary]

Are there any MS Visual C++ runtimes other than 2008, 2010, 2012, 2013, and 2015/7 (2017 is just a slightly updated 2015), all in both x86 and x64 flavors? Those are the ones that I have.