LoadPluginEx, Dust5 and the current AVS CVS

[FredThompson]

Has anyone successfully used loadpluginex to load dustv5 with the current CVS build?

It won't work for me.

[Dreassica]

No probs here with the combo, works for me.

[Dark-Cracker]

apparently there is a problem with the latest version of warpsharp.dll file (all the function bundle in this file doesn't work) and avisynth 2.5.2 .try using a previous version of warpsharp.dll .

Bye.

[FredThompson]

available where?

[unplugged]

Originally posted by FredThompson
available where?
http://www.avisynth.org/~warpenterprises/files/warpsharp_25_dll_20030121.zip

Site: http://www.avisynth.org/~warpenterprises/

[FredThompson]

That is the one which isn't working. Do you know where to find previous versions?

[Wilbert]

Did you installed msvcp70.dll, as indicated in Q3.5?

[FredThompson]

I have multiple instances of 50 and 60 70, all have copies in WINNT/System32 (Win2K.)

What is "Q3.5"?

[North2Polaris]

Originally posted by FredThompson
I have multiple instances of 50 and 60 70, all have copies in WINNT/System32 (Win2K.)

What is "Q3.5"?

I believe that "Q3.5" refers to the AviSynthFaq at:

http://www.avisynth.org/index.php?page=AviSynthFaq

[FredThompson]

Oh, I see it, it's the last line in that huge list. Boy, that's hard to spot. The section might benefit from a table...

[Richard Berg]

With the version linked in Q3.5, I get "LoadPlugin: cannot load c:\pf\avisynth2\plugins\old\LoadPluginEx.dll". I definitely have the MS runtime installed.

Curiously, the one linked by WarpEnterprises works; this seems to be the reverse of what everyone else is reporting, but so be it.

[toshi]

The latest version of warpsharp (warpsharp_2003_0705.cab) needs msvcp71.dll & msvcr71.dll.

[Wilbert]

Where can I find those?

[toshi]

Let's use Google:)
You'll find this page (http://www.geocities.co.jp/SiliconValley-PaloAlto/2382/) soon.

[cweb]

That warpsharp (the one in that cab) does not work for me (it's as if it isn't an avisynth plugin). It looks very odd to me.

[toshi]

Originally posted by cweb
That warpsharp (the one in that cab) does not work for me (it's as if it isn't an avisynth plugin). It looks very odd to me.
I cannot understand what you mean. How did you try it?

P.S
Latest warpsharp.dll is for Avisynth 2.5. When you use it on
Avisynth 2.0, You need using LoadPluginEx.dll

[d'Oursse]

keep in mind that once you load Loadpluginex.dll, each following Loadplugin requires an avisynth v2.0 plugin.
I succeed in using dustv5 (wonderful plugin, thanks Steady !) with avisynth 2.5 (in french...):
http://atlas2.tgv.net/~media-video/forum2/viewtopic.php?t=2614&start=0&postdays=0&postorder=asc&highlight=

[DoW]

The last version of the warpsharp package (I think May was when it was made) had some problems and was unusable. The new one warpsharp_2003_0705.cab works, but you also need the 71.cab file from the webpage Warpsharp (http://www.geocities.co.jp/SiliconValley-PaloAlto/2382/), which contains msvcp71.dll and msvcr71.dll, which go in your system32 dir.

[Ark]

I've the same problem:

I've the warpsharp package linked here (http://www.geocities.co.jp/SiliconValley-PaloAlto/2382), but it won't work!

I can't find this "msvcp71.dll" anywhere, in this warpsharp package there isn't!

[Arachnotron]

I can't find this "msvcp71.dll" anywhere, in this warpsharp package there isn't!
That is a MS Visual Studio (C/C++) .Net 2003 Runtime dll file.

Don't know the official MS link for it, but a google usually turns up something.

[Wilbert]

I can't find this "msvcp71.dll" anywhere, in this warpsharp package there isn't!
Q3.6 Last item ...

[Ark]

Originally posted by Wilbert
Q3.6 Last item ...

..that points me to this page (http://www.avisynth.org/index.php?action=edit&page=WinNT) ... :( ... :confused:

And other links of the same answer seems to have nothing to do with this..

Sorry for stressing all of you but this problem really makes me crazy!:eek:

[North2Polaris]

http://download.nvidia.com/developer/NVTextureSuite/DLLs.zip

[AmiRage]

http://www.geocities.com/wilbertdijkhof/71.cab

It's the last item of Q3.5 ...

[Ark]

North2Polaris, AmiRage: thanks! :)

Edit: i've tried it and it works :), thanks again!

[ThunderCrush]

This is absolutely too funny! have a package and don't even include the
MSVCP71.dll file!

I now know why many people don't use avisynth!
not because it is hard to use, its because it is so disorganized and the quality and important information is so scattered around it is unbelievable!! And they ones who have it down just say go to Q3.5 with out saying anything more.


I appreciate everything everyone does, And there are some real geniuses that do things for nothing! My solute to them,but if someone plans on making a package please include files that may not be standard. There is no need to be searching all over the net for files that you need to make a package work.


I found the MSVCP71.dll file here!
http://www.dll-files.com/cgi-bin/cgiwrap/dll-files/topdown/download.pl?file=msvcp71.zip==

MSVCR71.dll file here!
http://www.dll-files.com/cgi-bin/cgiwrap/dll-files/topdown/download.pl?file=msvcr71.zip==

You need both the MSVCP71 and MSVCR71 dll files
put them in your windows/system directory folder.

Once I get this avisynth stuff down to just useable, I will be making a organized tutorial for beginners like myself.

I believe many here on doom9 have forgot what it was like to be a newbie, Days wasted just searching for stuff that could fit all in a few html pages/

Its all fine and dandy to say read Q.3.5 but if you dont check the links that don't work then reading Q.3.5 doesn't mean crap! and like one Gent said way at the bottom of the page!! It is really too funny!!

[Arachnotron]

This is absolutely too funny! have a package and don't even include the MSVCP71.dll file!

I may be wrong, but AFAIKR the microsoft EULA prohibits redistributing this file.

[ThunderCrush]

You maybe right, I don't know stuff about that, but the next best thing would be a read me text with the package, with a link and discription on how to set it up.

This package is very useful, and one that is a must to have and I am very greatful for it!
A small detail readme text file like needing these two files and please do a search on google because of rights and then put them in your windows/systems folder would be perfect.

[Wilbert]

I may be wrong, but AFAIKR the microsoft EULA prohibits redistributing this file.
Really?

@ThunderCrush,

A small detail readme text file like needing these two files and please do a search on google because of rights and then put them in your windows/systems folder would be perfect.
Like you said, you can find all at the bottom of Q3.5. I will include a text file in that package. Is that enough?

This is absolutely too funny! have a package and don't even include the MSVCP71.dll file!
They removed it from their (japanese) website a while ago. I will ask WarpEnterprises to add a link. That should be enough.

[Arachnotron]

Originally posted by Wilbert
Really?

I looked it up; it is a bit unclear, but i 'think' it is allowed.

The version in the VC .net 2003 toolkit cannot be redistributed:

(from redist.txt)Inclusion of these static libraries as compiled into your program is acceptable; you may not, however, redistribute the static libraries standalone - on their own.

This includes msobj71.dll, mspdb71.dll, msvcp71.dll and msvcr71.dll

However, the redist.txt from Visual c++ .net 2003 standard edition states:
The following list reflects all files available with Microsoft Visual Studio for redistribution; if you have acquired a Microsoft developer tool product other than Visual Studio, such as Visual Basic, Visual C#, Visual J# or Visual C++, the files available for redistribution with these other products are specific to such product and as such will be a subset of the following list.

Visual C++ Runtime Files

The following merge modules have been provided for use when redistributing the Visual C++ runtime files. Redistributing the merge modules is the recommended method for the redistribution of these files.
<snip>
mfc71chs.dll
mfc71cht.dll
mfc71jpn.dll
mfc71kor.dll

vc_user_stl71_rtl_x86_---.msm
msvcp71.dll

So I guess it is ok?

[Leak]

Originally posted by Arachnotron
(from redist.txt)Inclusion of these static libraries as compiled into your program is acceptable; you may not, however, redistribute the static libraries standalone - on their own.

This includes msobj71.dll, mspdb71.dll, msvcp71.dll and msvcr71.dll

No, it doesn't. DLLs are by their very definition Dynamically Linked Libraries. Static libraries have .lib as their extension and are linked directly into the final executable, thus not requiring any external files.

Not even MS is so dumb as to prohibit redistribution of files that are required to run any executable made for dynamic linking... ;)

np: Jah Wobble & Deep Space - Five Beat Part II) (Five Beat)

[stickboy]

Disallowing redistribution of dynamically-linked libraries provided by a development environment would be totally pointless. The purpose of the development environment is to allow people to write software that they can distribute. If developers could not redistribute necessary but non-ubiquitous components such as msvcr71.dll, why would anyone ever use them at all?

[Arachnotron]

:o ok, sorry I brought this up. I'll be good now :)