Error loading .avs plugins in MeGUI

[Bablu]

Hey there guys,

I have been trying to use all these .avs or .avsi plugins, but it would always give me this error. Check the screen below.

http://img21.imageshack.us/img21/2641/94193008.th.jpg (http://img21.imageshack.us/my.php?image=94193008.jpg)

Ergo, I can't use plugins like Spresso, Srestore, Mrestore or Deblock_qed or anything and neither can I use my favorite filter, Seesaw. :(

Help please!

:thanks:

[Kurtnoise]

Use Import instead of LoadPlugin...


btw, if you have them in your avisynth plugins folder, you don't need to import them.

[rkalwaitis]

Kurtnoise is right, scripts are imported.

[Bablu]

When I use Import then I get this error.
http://img8.imageshack.us/img8/4408/65448087.th.jpg (http://img8.imageshack.us/my.php?image=65448087.jpg)

[rkalwaitis]

are you trying to use the setmtmode?

[Bablu]

No no! I have P4 old machine so, I don't use it.

[Kurtnoise]

maybe some conflicts between plugins...clean up your avisynth plugins folder.

[Bablu]

maybe some conflicts between plugins...clean up your avisynth plugins folder.

Yes I did that 2times and installed everything fresh. Even I reformatted my PC with the original WinXP SP2 pack.


No luck so far!:(

[rkalwaitis]

And Megui have you reinstalled it? Sometimes I get similar errors. But when I use the MT mode of avisyth.
type your script the way you want it and open it with MPC and see if it will play. If so your plugins and scripts should be okay. Or open you avs file in Virtualdub and see if it works there.

[~bT~]

are you sure u have all the required dll's/plugins for srestore?

[rkalwaitis]

srestore needs masktools2, TIVTC, RemoveGrain, and Average and of course the Srestore.avsi itself. http://avisynth.org/mediawiki/Srestore

maybe your missing the average package. Its hard to get. here is the link. http://forum.doom9.org/showthread.php?t=118430

Fizick posted it.

[Bablu]

And Megui have you reinstalled it? Sometimes I get similar errors. But when I use the MT mode of avisyth.
type your script the way you want it and open it with MPC and see if it will play. If so your plugins and scripts should be okay. Or open you avs file in Virtualdub and see if it works there.
Ohh this I haven't tried. Let me give it a try.
are you sure u have all the required dll's/plugins for srestore?
Yes I believe I have all of them. Btw, Nice to see your post in my thread after so long. How's life and kids?
srestore needs masktools2, TIVTC, RemoveGrain, and Average and of course the Srestore.avsi itself. http://avisynth.org/mediawiki/Srestore

maybe your missing the average package. Its hard to get. here is the link. http://forum.doom9.org/showthread.php?t=118430

Fizick posted it.

Ahh!! I checked that I didn't have masktools2 and Average.

Ok another question, so all these Average and Mastools2 required for Seesaw too?




EDiT:\\ - fugdeee!! It still doesn't work.:(

[rkalwaitis]

SeeSaw does not require Average. It must use MaskTools2 and Removegrain 1.x http://avisynth.org/mediawiki/SeeSaw

[Bablu]

Yupp! I checked and neither does Spresso or Seesaw or none of my .avsi/.avs works. Crap man! I should not have reformatted my PC. It was work fine before. :( I love using Seesaw, Srestore and Spresso, but .... :(

[Betsy25]

I'm just a newb, so perhaps this won't be of much help, but

Is your .avs file in the DOS Text format ?
You can check that with your notepad.

I've seen these errors too when the .avs was in the Unicode format.

Slame that avisynth still doesn't handle Unicode files.

[Bablu]

I'm just a newb, so perhaps this won't be of much help, but

Is your .avs file in the DOS Text format ?
You can check that with your notepad.

I've seen these errors too when the .avs was in the Unicode format.

Slame that avisynth still doesn't handle Unicode files.

It was ANSI encoding format. So, I don't that's the reason.

[rkalwaitis]

Just pretend to complete the avs file and then play it in MPC. Your error will change to a more direct error, and away from a Megui generated error. What error does MPC give you?

[Bablu]

Just pretend to complete the avs file and then play it in MPC. Your error will change to a more direct error, and away from a Megui generated error. What error does MPC give you?

Ok here's the script I did for an example.

Import("C:\Program Files\AviSynth 2.5\plugins\seesaw.avs")
Import("C:\Program Files\AviSynth 2.5\plugins\srestore.avs")
DGDecode_mpeg2source("C:\Documents and Settings\blah!\Desktop\sample.d2v", info=3)
TDeint(mode=1,order=-1)
Srestore()
#crop
#resize
#denoise
a=last
b=a.degrainmedian()
seesaw(a,b,nrlimit=5)

This is what I get on MPC (with Srestore and Seesaw)
http://img410.imageshack.us/img410/5526/snapshot20090321172145.th.png (http://img410.imageshack.us/my.php?image=snapshot20090321172145.png)

without Seesaw and with Srestore = totally fine

http://img9.imageshack.us/img9/2108/snapshot20090321172416.th.png (http://img9.imageshack.us/my.php?image=snapshot20090321172416.png)
Ok, we (you guys) have solved one thing. Srestore is working fine now, but still have problem working out Seesaw, Spresso and others scripts.

[rkalwaitis]

Seesaw is the culprit then or so it seems.

Which version of masktools are you using?

I think seesaw needs masktools2 and the removegrain 1.x package to work properly.

do you have those in you avisyth plugin directory?

ColorMatrix(hints=true, interlaced=true, threads=0) seems to be missing from you script. I dont know if it will make a differnce or not :|

DGDecode_mpeg2source("C:\Documents and Settings\blah!\Desktop\sample.d2v", info=3)
ColorMatrix(hints=true, interlaced=true, threads=0)
TDeint(mode=1,order=-1)


http://avisynth.org/mediawiki/SeeSaw

[Bablu]

Seesaw is the culprit then or so it seems.

Which version of masktools are you using?

I think seesaw needs masktools2 and the removegrain 1.x package to work properly.

do you have those in you avisyth plugin directory?

ColorMatrix(hints=true, interlaced=true, threads=0) seems to be missing from you script. I dont know if it will make a differnce or not :|

DGDecode_mpeg2source("C:\Documents and Settings\blah!\Desktop\sample.d2v", info=3)
ColorMatrix(hints=true, interlaced=true, threads=0)
TDeint(mode=1,order=-1)


http://avisynth.org/mediawiki/SeeSaw

I HAVE every single of them in plugin dir. lol

ColorMatrix doesn't really make difference, I made sure. I even made sure that the Seesaw script/ Spresso script are good.

So I don't know what the hell is wrong with it. Could it be because I have P4 old machine which might no support it?

[Didée]

Exactly which versions of "RemoveGrain*.dll" and "Repair*.dll" are in your /plugins directory?

[rkalwaitis]

well there are different remove grain dlls in the package. some work on different computers and not on others. I would just double check to ensure the right ones are being used. Could be your system. Im not that system savy. You could give your error to the megui page, perhaps they have seen it before. But if you cant play it in mpc, its not megui's fault.

sorry dude, you need a prodigy to help you now.

And he posted while I was typing. Didee can help you. You will have it running in no time.

[Bablu]

Exactly which versions of "RemoveGrain*.dll" and "Repair*.dll" are in your /plugins directory?
Wow! The great Didee. OMG!

Umm!! I don't know which one it is, but I opened Removegrain.cpp and it says on the first line - Removegrain1.0\n

and there's no documentation on Repair.dll other than just dll files. How do I check that?
well there are different remove grain dlls in the package. some work on different computers and not on others. I would just double check to ensure the right ones are being used. Could be your system. Im not that system savy. You could give your error to the megui page, perhaps they have seen it before. But if you cant play it in mpc, its not megui's fault.

sorry dude, you need a prodigy to help you now.

And he posted while I was typing. Didee can help you. You will have it running in no time.

Your help is highly appreciated buddy.

[Reuf Toc]

I suppose Didée wants to know if you use the SSE3 version of RemoveGrain. There is a bug with this version and it is advised to use the SSE2 version.

[Bablu]

I suppose Didée wants to know if you use the SSE3 version of RemoveGrain. There is a bug with this version and it is advised to use the SSE2 version.

Ahh I see!

I have the following:

RemoveGrain.dll
RemoveGrainHDS.dll
RemoveGrainS.dll
RemoveGrainSSE2.dll
RemoveGrainSSE3.dlldeleted it

[~bT~]

^ keep the sse2 version only for removegrain. same goes for other dll's, keep only one version. which version u decide.

[Bablu]

^ I see! Actually the thing is that I never downloaded none of these dll's nor the scripts. It came with Avisynth I installed recently so I never thought that would be the conflict.

Another thing we have solved is Spresso, but Seesaw is still not working.

[~bT~]

^ they never come with avisynth afaik..

[Bablu]

^ I don't think I downloaded this: RemoveDirt_bT.avs; RemoveDirt_cF.avs

lol

[EuropeanMan]

Why use SeeSaw when LSF/LSFmod work better...?

[rkalwaitis]

Seesaw needs the correct remove grain. They are right. You need to have only one not the four of them. I would just try the removegrainSSE2.dll to see if it works.

Installation
The binary package contains four versions of RemoveGrain, two small dynamically linked versions RemoveGrain.dll, RemoveGrainSSE2.dll, RemoveGrainSSE3.dll and the big staticly linked RemoveGrainS.dll. The first one only requires integer SSE (Athlon and Pentium 3 design), the second requires a SSE2 capable cpu (Pentium 4 or Athlon 64) and the third is for Prescott P4s only. If none of these dlls work because of a missing dll, one has either to copy the missing dll to the window's system directory or one has to use RemoveGrainS.dll, which only requires SSE. Please put only one of the three plugins into the Avisynth plugin directory. RemoveGrain supports all color spaces. YV12 is directly supported and YUY2, RGB24, RGB32 are supported in planar form (see the section Color Spaces). Beginning with version 0.6 the auxiliary filter Clense has been added to RemoveGrain.dll and the plugin Repair.dll has been added to the binary package. There are again four versions of this plugin. Though Repair.dll is derived from the same source code, it serves for quite different purposes. This plugin contains the filters Repair and TemporalRepair. All three new filters are described below. Please post questions, problems, comments etc. to the RemoveGrain thread of the doom9 forum rather than sending me email. In particular, I would appreciate reports about artifacts and compression gain of the various modes. These may also help others to select the right mode.

[Bablu]

Seesaw needs the correct remove grain. They are right. You need to have only one not the four of them. I would just try the removegrainSSE2.dll to see if it works.

Installation
The binary package contains four versions of RemoveGrain, two small dynamically linked versions RemoveGrain.dll, RemoveGrainSSE2.dll, RemoveGrainSSE3.dll and the big staticly linked RemoveGrainS.dll. The first one only requires integer SSE (Athlon and Pentium 3 design), the second requires a SSE2 capable cpu (Pentium 4 or Athlon 64) and the third is for Prescott P4s only. If none of these dlls work because of a missing dll, one has either to copy the missing dll to the window's system directory or one has to use RemoveGrainS.dll, which only requires SSE. Please put only one of the three plugins into the Avisynth plugin directory. RemoveGrain supports all color spaces. YV12 is directly supported and YUY2, RGB24, RGB32 are supported in planar form (see the section Color Spaces). Beginning with version 0.6 the auxiliary filter Clense has been added to RemoveGrain.dll and the plugin Repair.dll has been added to the binary package. There are again four versions of this plugin. Though Repair.dll is derived from the same source code, it serves for quite different purposes. This plugin contains the filters Repair and TemporalRepair. All three new filters are described below. Please post questions, problems, comments etc. to the RemoveGrain thread of the doom9 forum rather than sending me email. In particular, I would appreciate reports about artifacts and compression gain of the various modes. These may also help others to select the right mode.
Ahhhh! It's too late here, but will let you know tomorrow mid-day.
Why use SeeSaw when LSF/LSFmod work better...?

I know how much you hate Seesaw, but honestly speaking, I love using Seesaw, lol.

[~bT~]

Why use SeeSaw when LSF/LSFmod work better...?

whats better for you may not be better for others..:rolleyes:

[rkalwaitis]

I use seesaw more than LSFMod. Its one of Didee's best. I use it with Spresso with another denoiser ie Fluxsmooth. You can get some real solid results. And it process at a nice pace too.

[EuropeanMan]

whats better for you may not be better for others..:rolleyes:

True :)

On a side note: Hope you are well. Miss seeing you around...my regards to your family.

I use seesaw more than LSFMod. Its one of Didee's best. I use it with Spresso with another denoiser ie Fluxsmooth. You can get some real solid results. And it process at a nice pace too.

rkal - would your opinion still be the same if SeeSaw is used against interlaced material? From what I have seen & experienced, SeeSaw isn't that great on interlaced vs progressive frames....even IF you deinterlace properly. Sure SS is faster...etc etc. In the final result, what TRULY is so MUCH better about SS than LSF/LSFmod?

[rkalwaitis]

EuropeanMan,

I really do not mess with too much interlaced material. And you are correct interlaced can be a problem for any inexperienced scripter(me). So you are correct, I usually do progressive. Which is nice for SeeSaw and Spresso and my other toys developed by much smarter gents and ladies than me. But I like SeeSaw cause it is meant to be utilized with my denoiser, I choose. The I can of course easily tweak Seesaw to get the most out of my sharpening and denoised clip. I know by some peoples standards it is obsolete (3 years old). But I have gotten really nice results utilizing it. But in the end my clip has to please me. And I have and still do get some nice results with seesaw and do not have to process a clip for 3 days to do it. I think it is important to remember SeeSaw is not designed to make a bad source looks better but merge a denoised source and a modifed sharpened source. With the appropriate selection of denoiser filter, SeeSaw does a good job at a decent fps.


I use it like below.

a = last
b = a.Your Denoiser
SeeSaw(a,b, NRlimit=6, NRlimit2=7, Sstr=1.5, Slimit=5, Spower=5, Sdamplo=6, Szp=16)##to taste
SPresso(limit=2, limitC=0, bias=65, biasC=65, RGmode=4, RGmodeC=4) ##to taste


or maybe

d=last
e=d.RemoveGrain(mode=17).RemoveGrain(mode=1)
SeeSaw(d, e, NRlimit=2, NRlimit2=1, Sstr=1.4, Slimit=7, Spower=2, Sdamplo=8, SdampHi=10, Szp=16, bias=1, sootheT=8)
SPresso(limit=2, limitC=2, bias=76, biasC=76, RGmode=4, RGmodeC=4)

I think it one of Didees most clever thoughts.

I guess in the end the results for me are pleasing to my eye.

[Bablu]

I use seesaw more than LSFMod. Its one of Didee's best. I use it with Spresso with another denoiser ie Fluxsmooth. You can get some real solid results. And it process at a nice pace too.
You and I have the same taste on where to use Spresso and Seesaw. Also, after I learned the proper way to use Fluxsmooth, now I use that quite often and it churns out good result.

rkal - would your opinion still be the same if SeeSaw is used against interlaced material? From what I have seen & experienced, SeeSaw isn't that great on interlaced vs progressive frames....even IF you deinterlace properly. Sure SS is faster...etc etc. In the final result, what TRULY is so MUCH better about SS than LSF/LSFmod?

EuropeanMan,

I really do not mess with too much interlaced material. And you are correct interlaced can be a problem for any inexperienced scripter(me). So you are correct, I usually do progressive. Which is nice for SeeSaw and Spresso and my other toys developed by much smarter gents and ladies than me. But I like SeeSaw cause it is meant to be utilized with my denoiser, I choose. The I can of course easily tweak Seesaw to get the most out of my sharpening and denoised clip. I know by some peoples standards it is obsolete (3 years old). But I have gotten really nice results utilizing it. But in the end my clip has to please me. And I have and still do get some nice results with seesaw and do not have to process a clip for 3 days to do it. I think it is important to remember SeeSaw is not designed to make a bad source looks better but merge a denoised source and a modifed sharpened source. With the appropriate selection of denoiser filter, SeeSaw does a good job at a decent fps.


I use it like below.

a = last
b = a.Your Denoiser
SeeSaw(a,b, NRlimit=6, NRlimit2=7, Sstr=1.5, Slimit=5, Spower=5, Sdamplo=6, Szp=16)##to taste
SPresso(limit=2, limitC=0, bias=65, biasC=65, RGmode=4, RGmodeC=4) ##to taste


or maybe

d=last
e=d.RemoveGrain(mode=17).RemoveGrain(mode=1)
SeeSaw(d, e, NRlimit=2, NRlimit2=1, Sstr=1.4, Slimit=7, Spower=2, Sdamplo=8, SdampHi=10, Szp=16, bias=1, sootheT=8)
SPresso(limit=2, limitC=2, bias=76, biasC=76, RGmode=4, RGmodeC=4)

I think it one of Didees most clever thoughts.

I guess in the end the results for me are pleasing to my eye.

I do agree with European Man to some extent. Some interlaced source are not that bad. Ex: regular TIVTC or pull down using bobber and restore fuction. For such sources, I like to use combo of Fluxsmooth, Spresso and Seesaw.

Yes, seesaw is one of the best by Didee.

Btw, guyssssssssssss!! can we get back to topic and figure a way out?

_______________________________

I have two tests tomorrow and yet I'm stuck with this, lol. Anyways, I tried the installation method that rkal posted, but no luck with that. I removed the plugins and downloaded the once the are compatible for Seesaw, but still ain't working.

[rkalwaitis]

Well did you fix the dll problem with reomovegrain?

[Bablu]

Yes I did. I kept only one removegrainSSE2 which is required for some of the filters and scripts, so do you think if I do everything fresh from the start, it would work?

[Didée]

Fact is that your folder Avisynth/plugins/ probably is polluted.

Next step would be: the cleaning procedure you did with RemoveGrain**.dll, you have also to do with Repair**.dll, ... and while you're at it anyway, with RemoveGrainHD**.dll (if present), with ReduceFlicker**.dll (if present), and with RemoveDirt**.dll (if present).


Note: using Plugin-auto-loading is lazy, but it can also be problematic. Personally I have never used auto-loading. I've my plugins in a separate folder, always manually LoadPlugin() the ones I need, and be surprised or not, I've never ever had such problems. ;)

[rkalwaitis]

Didee may have a valid point. Make seperate folders for your required avsi files and dlls and see if will run. I bet it will.

[Bablu]

Fact is that your folder Avisynth/plugins/ probably is polluted.

Next step would be: the cleaning procedure you did with RemoveGrain**.dll, you have also to do with Repair**.dll, ... and while you're at it anyway, with RemoveGrainHD**.dll (if present), with ReduceFlicker**.dll (if present), and with RemoveDirt**.dll (if present).


Note: using Plugin-auto-loading is lazy, but it can also be problematic. Personally I have never used auto-loading. I've my plugins in a separate folder, always manually LoadPlugin() the ones I need, and be surprised or not, I've never ever had such problems. ;)

Didee may have a valid point. Make seperate folders for your required avsi files and dlls and see if will run. I bet it will.

You know what? That's one smart thinking, why didn't I think of that. Just have my dlls in one folder and scripts in the other.

Thank you so much guys! I'll get back to this thread again after my encoding and tests are over which is going to be tomorrow.

See ya then!

[steptoe]

Or do what I do and once you get a filter/function running create a folder containing all the required filters and functions that may need and create a script that speciically loads each DLL for that set function

Its neat and you guarantee no problems, ever, as you have tested that filter, so again guarantee it will work


It means duplicating filters, BUT you KNOW that it works, and as some filters/functions insist on very specific versions of filters again you KNOW that you are not going to get DLL's overwritten with oldert/newer versions that don't work with that filter

Plus it means you don't have a huge plugin folder that WILL eventually lead to conflicts and can get very confusing if you have a lot of filters or functions you are tseting or even use