Log in

View Full Version : loading avsi scripts in Avisynth plugins folder but...


unclescoob
30th March 2019, 00:08
....when I try to open the function, I get a message stating that it's "unable to load d2v file." I'm trying to add LimitedSharpenFaster to my plugins folder. I went to the Avisynth page where the script is available, opened the script, right-clicked and saved it as an .avsi file in my plug-ins folder. I also loaded the .dll files required for this function. What's Avisynth's problem THIS time? I swear, Avisynth gets more and more delicate, bitchy, demanding, and whiny time after time.

Heaven forbid you properly load something in the plugins folder and it actually um...WORKS?

Go ahead, I'm waiting for a response telling me that I have to go around the world chasing 78 codecs and install it in everyone's mother's folder.

wonkey_monkey
30th March 2019, 01:04
"Unable to load d2v file" sounds like a source filter problem. mpeg2source, perhaps?

But rather than play guessing games...

:script:

hello_hello
30th March 2019, 02:59
Yeah, it sounds like the plugins are loading but the location of the d2v file you created when indexing with DGIndex is wrong in the script, assuming you previously indexed with DGIndex. Either that or the d2v index file won't load because the video you indexed is no longer in the same location, so DGDecode can't open the d2v file successfully.

Groucho2004
30th March 2019, 12:30
Just as wonkey_monkey suggested, post your (complete) script. It could also help to run the Avisynth Info Tool (https://forum.doom9.org/showthread.php?t=176079) and post the log file (Save Info...).

I swear, Avisynth gets more and more delicate, bitchy, demanding, and whiny time after time.It can be, but most problems are usually avoidable by reading the documentation (http://avisynth.nl/index.php/Main_Page).

unclescoob
30th March 2019, 14:46
My plug-ins folder is attached here as a jpeg.

Here's my script:
LoadPlugin("C:\Program Files (x86)\AviSynth\plugins\DGDecode.dll")
LoadPlugin("C:\Program Files (x86)\AviSynth\plugins\mvtools2.dll")
LoadPlugin("C:\Program Files (x86)\AviSynth\plugins\IT.dll")
LoadPlugin("C:\Program Files (x86)\AviSynth\plugins\TIVTC.dll")
MPEG2Source("C:\Users\Desktop\Index Files\movie index files\VTS_01_1.d2v", cpu=0)

LimitedSharpenFaster()

Evidently, I must have come across the documentation at least a little bit, wouldn't you say Groucho?

unclescoob
30th March 2019, 15:01
[QUOTE=unclescoob;1870417]My plug-ins folder is attached here as a jpeg.

Here's my script:
LoadPlugin("C:\Program Files (x86)\AviSynth\plugins\DGDecode.dll")
LoadPlugin("C:\Program Files (x86)\AviSynth\plugins\mvtools2.dll")
LoadPlugin("C:\Program Files (x86)\AviSynth\plugins\IT.dll")
LoadPlugin("C:\Program Files (x86)\AviSynth\plugins\TIVTC.dll")
MPEG2Source("C:\Users\Desktop\Index Files\movie index files\VTS_01_1.d2v", cpu=0)

LimitedSharpenFaster()

Evidently, I must have come across the documentation at least a little bit, wouldn't you say Groucho?

unclescoob
30th March 2019, 16:07
Sorry about the double

StainlessS
30th March 2019, 17:53
You can delete your double post if required, just click on EDIT, give optional reason for delete, and click DELETE.

Also, just to remove LimitedSharpenFaster from equation, can temp comment out that line.

Have you moved the VOB directory at all (will need to re-DGIndex for correct path/s in d2v file, or look in d2v to see the used path/s, its just a text file)

EDIT: You can also delete the "sorry about the double" post if required.

hello_hello
30th March 2019, 18:06
Here's my script:
LoadPlugin("C:\Program Files (x86)\AviSynth\plugins\DGDecode.dll")
LoadPlugin("C:\Program Files (x86)\AviSynth\plugins\mvtools2.dll")
LoadPlugin("C:\Program Files (x86)\AviSynth\plugins\IT.dll")
LoadPlugin("C:\Program Files (x86)\AviSynth\plugins\TIVTC.dll")
MPEG2Source("C:\Users\Desktop\Index Files\movie index files\VTS_01_1.d2v", cpu=0)

LimitedSharpenFaster()

Are you aware that for standard Avisynth plugins, you don't need to load them in a script with LoadPlugin if they're in the Avisynth plugins folder?

Are you sure the path for the d2v file is correct? I'm just a lowly XP user, so I'm not terribly familiar with newer Windows, but shouldn't it be:

"C:\Users\USERNAME\Desktop\Index Files\movie index files\VTS_01_1.d2v"

StainlessS
30th March 2019, 18:15
but shouldn't it be:
Brilliant catch HH, methinks you got it. :)

Groucho2004
30th March 2019, 18:42
My plug-ins folder is attached here as a jpeg.

Here's my script:
LoadPlugin("C:\Program Files (x86)\AviSynth\plugins\DGDecode.dll")
LoadPlugin("C:\Program Files (x86)\AviSynth\plugins\mvtools2.dll")
LoadPlugin("C:\Program Files (x86)\AviSynth\plugins\IT.dll")
LoadPlugin("C:\Program Files (x86)\AviSynth\plugins\TIVTC.dll")
MPEG2Source("C:\Users\Desktop\Index Files\movie index files\VTS_01_1.d2v", cpu=0)

LimitedSharpenFaster()

Evidently, I must have come across the documentation at least a little bit, wouldn't you say Groucho?Attachments take forever to be approved (you may see it but we don't) and showing us a picture of your plugins directory is rather useless. So, as already mentioned, check if the path to your d2v file is correct and if it still throws that error, use the tool I mentioned and post the log file.

unclescoob
30th March 2019, 23:16
Are you aware that for standard Avisynth plugins, you don't need to load them in a script with LoadPlugin if they're in the Avisynth plugins folder?

Yeah, tell me about it. When I had Windows 7, I didn't have to do this. But with this computer, functions won't work unless I do this. Any suggestions on how to fix this? I've tried all I could.

StainlessS
30th March 2019, 23:25
I think I remember that earlier versions of Avs+ did not autoload avsi scripts.
Update to current version (if just avsi problems):- https://github.com/pinterf/AviSynthPlus/releases

EDIT: You could also check using Regedit

HKEY_LOCAL_MACHINE\SOFTWARE\Avisynth

Mine says:

Default C:\VideoTools\AvisynthRepository\AVSPLUS_x64
PluginDir+ C:\VideoTools\AvisynthRepository\AVSPLUS_x64\plugins
PluginDir2_5 C:\VideoTools\AvisynthRepository\AVSPLUS_x64\plugins

And
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Avisynth

Mine says:

Default C:\VideoTools\AvisynthRepository\AVSPLUS_x86
PluginDir+ C:\VideoTools\AvisynthRepository\AVSPLUS_x86\plugins
PluginDir2_5 C:\VideoTools\AvisynthRepository\AVSPLUS_x86\plugins


EDIT:
Did Hello_Hello fix work for you ?

"C:\Users\USERNAME\Desktop\Index Files\movie index files\VTS_01_1.d2v"

Groucho2004
30th March 2019, 23:55
You could also check using RegeditWhy? Is there something wrong with the AVS Info Tool of which I'm not aware? Maybe this thread is a competition how to make things as difficult as possible?

I've tried all I could.Right. Good luck.

StainlessS
30th March 2019, 23:58
Or you could always try the fantastic Groucho2004 AVS Info Tool.
[He's such a needy fellow, in constant need of head patting, but not quite as bad as Feisty2].

Groucho2004
31st March 2019, 00:01
Or you could always try the fantastic Groucho2004 AVS Info Tool.
[He's such a needy fellow, in constant need of head patting, but not quite as bad as Feisty2].Bite me. It has nothing to do with being needy, I just get annoyed when people think they know everything and ignore good advice.

unclescoob
31st March 2019, 00:10
Update to current version

I do have the current version. I have 2.60, the March 31, 2015 build.

Even in 2011, when I had the recent version of the time, this wasn't a problem.

StainlessS
31st March 2019, 00:12
OK then post result from Groucho's tool, and again, did Hello_Hello fix work ?

EDIT: Below has NO USERNAME
MPEG2Source("C:\Users\Desktop\Index Files\movie index files\VTS_01_1.d2v", cpu=0)

unclescoob
31st March 2019, 00:12
Stainless, no offense, but what the hell are you talking about?
Oh yeah, I'll check the paths in a little while and report back. I've been out all day and dealing with exhausting shit, so this is for tonight.

This website is like Videohelp.com: most people are arrogant assholes.

StainlessS
31st March 2019, 00:15
Agreed. Goodbye.

Groucho2004
31st March 2019, 00:30
This website is like Videohelp.com: most people are arrogant assholes.I see you got banned on VH. Having read some of your posts over there, I'm not surprised. With your attitude you'll probably never get your problems sorted (which by the way are solely caused by your astounding ignorance).

unclescoob
31st March 2019, 00:50
Groucho, it's true. I did get banned from VH for my comments. But I guarantee that my posts there would have mostly ended with "thank you" instead of the way they did if people actually were helpful there.

But what you have is the usual gang of narcissistic fucktards who, instead of just giving you a straight answer, choose to use the questions of "ignorant" novices such as myself as yet another opportunity for expressing their arrogant, shitty, and lame attitudes. In the end, it's like they're defecating through the keyboard.

They think that by insulting you and answering your questions with their wise-ass, passive aggressive comments, that they're making themselves look good, but they actually do the opposite...they just make the um..."astounding ignorant" such as myself keep away instead of seeking help.

And then the other fucktards chime in, pretty much cornering the poor fellow (not just referring to my experiences there, believe me), by kissing each other's asses on their knowledge...and the person who asked the question just walks away feeling like an asshole, instead of having his/her question addressed in...layman's terms maybe? is that possible with you people???

They think that by telling the OP to just "read the documentation" and posting links to the Avisynth page, they're doing the person a favor when in fact, YOU, THEY, and I know very well that much of that so-called documentation is VAGUE, full of JARGON, and CARELESSLY EXPLAINED. Do not act like you don't know that, because you do.

It seems like it's no different here. At least in digitalfaq.com, they treat you with basic respect, regardless of your level of understanding of this (ultimately) useless hobby.

unclescoob
31st March 2019, 01:02
Oh and yes, I already know that you are an arrogant asshole. Asshole.

johnmeyer
31st March 2019, 03:33
I was part of one of the several threads at videohelp.com that led to him getting banned. It was the same identical behavior as seen here. It's too bad because I did try to help him in those posts in that other forum, and like some of the good people who did the same thing here, I got kicked in the teeth as thanks for my time.

I thought the advice given here was useful, respectful, and well presented.

Hopefully the moderators will take care of this.

wonkey_monkey
31st March 2019, 10:42
99.9% of people come here, ask for help, get asked to provide more information, provide said information, receive more advice, find a solution to their problem and go away happy. You seem to have annoyed people on two forums now. You should consider the common factor.

So far you seem to have ignored all the posts pointing out that there may be a problem with the path to your .d2v file. It's really, really helpful if you tell people whether or not you've checked these things instead of just continuing to complain that it doesn't work.

The error message you possibly paraphrased (the exact error message would be more helpful) sounds exactly like the error that mpeg2source throws when it can't find the .d2v file at the specified path. Additionally, the path you posted appears not to match the standard Windows path for a user's desktop. Find your .d2v file in Windows Explorer and check the folder path.

There's a knack to both giving and getting help.

Groucho2004
31st March 2019, 12:12
They think that by telling the OP to just "read the documentation" and posting links to the Avisynth page, they're doing the person a favor when in fact, YOU, THEY, and I know very well that much of that so-called documentation is VAGUE, full of JARGON, and CARELESSLY EXPLAINED. Do not act like you don't know that, because you do.The documentation on avisynth.nl is quite good and people with average intelligence and a bit of patience will benefit from it.

You are either too lazy to acquire some basic knowledge about the software you're using or it simply goes over your head.

As for the JARGON - Would you be happy if you went to a doctor for a rectal exam and instead of telling you that you have a malignant growth in your colon he calls it a boo-boo in your poop hole and you're left guessing what that means?

My guess is that you are of the very rare species that not just likes information to be spoon-fed but also in a very specific way (carefully explained, no jargon, ...).