Error avisinth help pls

[terminator3]

When I am going to use the line darken toon it gives me an error, there is no function named "linedarken_toon" can you help me? thanks

script:
Mpeg2Source("C:\Users\xx\Desktop\55a.d2v")

import("C:\Program Files (x86)\AviSynth+\plugins\SAA.avs")

import("C:\Program Files (x86)\AviSynth+\plugins\fastlinedarken.avsi")


import("C:\Program Files (x86)\AviSynth+\plugins\FastLineDarken 1.3 MT MOD.avs")


crop( 8, 2, -2, -2)


BicubicResize(704,528,0,0.75)

awarpsharp2(thresh=128, blur=3, type=0, depth=16, chroma=4)

linedarken_toon(sstrength=180, sdboost=2.0, srange=0, warpdepth=8, fast=false)
ConvertToYV2()





I am using avisinth + but with normal plugins, I also tried mt and the same thing happens

[StainlessS]

I dont touch cartoons so have no idea, but maybe you need this:- https://forum.doom9.org/showpost.php?p=993939&postcount=2

[terminator3]

I dont touch cartoons so have no idea, but maybe you need this:- https://forum.doom9.org/showpost.php?p=993939&postcount=2

now it appears to me, there is no function called "awarsharp"

before it works for me on the other computer, I don't understand why not now

[kedautinh12]

now it appears to me, there is no function called "awarsharp"

Download awarpsharp

[terminator3]

Download awarpsharp

I have it downloaded


http://imgfz.com/i/hneYy3K.png

[StainlessS]

Maybe post output of this(Avisynth InfoTool) :- https://forum.doom9.org/showthread.php?t=176079

[terminator3]

Maybe post output of this(Avisynth InfoTool) :- https://forum.doom9.org/showthread.php?t=176079

https://pastebin.com/bgx6JNtu

https://i.postimg.cc/523xDS6F/Captura.png

[Groucho2004]

https://pastebin.com/bgx6JNtuThat's not the whole log. the first section is missing (Avisynth version, etc.)

[terminator3]

That's not the whole log. the first section is missing (Avisynth version, etc.)

https://pastebin.com/6YBHtWJU

[StainlessS]

You really need to cleanup your plugins directory, its totally full o' shit in there, you should not just dump everything in plugins,
there is source code and all sorts of crap.
Also, You only choose one of each plugin, these are all alternative versions of the same plugin,

C:\Program Files (x86)\AviSynth+\plugins\Repair.dll [2005-07-31]
C:\Program Files (x86)\AviSynth+\plugins\RepairS.dll [2005-07-31]
C:\Program Files (x86)\AviSynth+\plugins\RepairSSE2.dll [2005-07-31]
C:\Program Files (x86)\AviSynth+\plugins\RepairSSE3.dll [2005-07-31]

The first one is CPP only, 'S' one is static linked, ie no CPP runtimes dll required, the SSE2 and SSE3 specific instruction versions.
It is basically pot-luck which one will be used. [I usually use SSE2 versions]

Read the output of Avisynth InfoTool, it lists the many problems you have. Suggest move everything out of plugins dir,
and move back only the plugins you need. Dump all the rubbish files (as noted in your infotool log), and choose
which of the alternatives you want.

Where you have v2.58 and v2.60 version plugs, suggest keep the v2.60 plugs.

EDIT:
I am using avisinth + but with normal plugins, I also tried mt and the same thing happens

Actually, your log says v2.60 standard, not +.
[Avisynth info]
VersionString: AviSynth 2.60, build:Feb 20 2015 [03:16:45]
VersionNumber: 2.60
File / Product version: 2.6.0.5 / 2.6.0.5

[terminator3]

You really need to cleanup your plugins directory, its totally full o' shit in there, you should not just dump everything in plugins,
there is source code and all sorts of crap.
Also, You only choose one of each plugin, these are all alternative versions of the same plugin,

C:\Program Files (x86)\AviSynth+\plugins\Repair.dll [2005-07-31]
C:\Program Files (x86)\AviSynth+\plugins\RepairS.dll [2005-07-31]
C:\Program Files (x86)\AviSynth+\plugins\RepairSSE2.dll [2005-07-31]
C:\Program Files (x86)\AviSynth+\plugins\RepairSSE3.dll [2005-07-31]

The first one is CPP only, 'S' one is static linked, ie no CPP runtimes dll required, the SSE2 and SSE3 specific instruction versions.
It is basically pot-luck which one will be used. [I usually use SSE2 versions]

Read the output of Avisynth InfoTool, it lists the many problems you have. Suggest move everything out of plugins dir,
and move back only the plugins you need. Dump all the rubbish files (as noted in your infotool log), and choose
which of the alternatives you want.

Where you have v2.58 and v2.60 version plugs, suggest keep the v2.60 plugs.

EDIT:


Actually, your log says v2.60 standard, not +.
I already got it, in the end it was a failure of the awarsharp version, a question, I have put all the x86 plugins, if I want to make it x64, would I have to search all of them in x64? or is the normal Avisinth not ready? or would I have to put the mt?

[StainlessS]

I already got it, in the end it was a failure of the awarsharp version, a question, I have put all the x86 plugins, if I want to make it x64, would I have to search all of them in x64? or is the normal Avisinth not ready? or would I have to put the mt?
Above is a little unclear, but I think this is the answer you want,
x64 Avisynth/+ requires ALL x64 plugins, (x86 only x86 plugins, x64 only x64 plugins).
You can however have x86 and x64 versions installed side by side, where each has its own plugins as set in the system registry.


On Wikii

x86 plugs
http://avisynth.nl/index.php/External_filters

x64 plugs
http://avisynth.nl/index.php/AviSynth%2B_x64_plugins

[terminator3]

Above is a little unclear, but I think this is the answer you want,
x64 Avisynth/+ requires ALL x64 plugins, (x86 only x86 plugins, x64 only x64 plugins).
You can however have x86 and x64 versions installed side by side, where each has its own plugins as set in the system registry.


On Wikii

x86 plugs
http://avisynth.nl/index.php/External_filters

x64 plugs
http://avisynth.nl/index.php/AviSynth%2B_x64_plugins

But when it comes to coding, how do I know that you are using the plugins of version + 64?

[StainlessS]

But when it comes to coding, how do I know that you are using the plugins of version + 64?

VirtualDub x86 loading avs script uses/requires avisynth x86 and x86 avisynth plugins, VirtualDub x64 loading avs script uses/requires avisynth x64 and x64 avisynth plugins,
MeGUI x86 requires x86 avisynth & x86 avisynth pluigins, MeGUI x64 requires x64 avisynth & x64 avisynth pluigins,
etc.

NOTE,
Avisynth x86 AUTOMATICALLY loads CPP plugin dll's from the avs x86 plugins directory, you do not need LoadPlugin call for dll's in Plugins dir,
same for x64 dll's and Plugins dir.
[Avisynth+ auto loads C plugins too, dont need LoadCPlugin]

AVSI scripts in Plugins directory are AUTOMATICALLY Imported, you do NOT need Import of avsi files in the plugins directory.
[Avisynth+ auto loads avs scripts too]

Groucho2004 SysInfo:- https://forum.doom9.org/showthread.php?t=176131
This plugin returns info about OS/CPU*/Memory/Screen/Avisynth

System related functions:

string SI_OSVersionString()
Returns Operating System info

float SI_OSVersionNumber()
int SI_OSBuildNumber
float SI_OSServicePack
bool SI_IsOS64Bit
bool SI_IsWin10
bool SI_IsWin7
bool SI_IsWin8
bool SI_IsWin81
bool SI_IsWinServer2003
bool SI_IsWinServer2008
bool SI_IsWinServer2008R2
bool SI_IsWinServer2012
bool SI_IsWinServer2012R2
bool SI_IsWinVista
bool SI_IsWinXP
Convenience functions for the running OS

string SI_CPUName()
Returns the CPU brand string + code name

int SI_NumberOfCPUs()
Returns the number of physical CPUs in the system

int SI_PhysicalCores()
Returns the total number of physical cores in the system. If multiple CPUs
are in the system, the sum of physical cores of all CPUs is returned.

int SI_LogicalCores()
Returns the total number of logical cores in the system. If multiple CPUs
are in the system, the sum of logical cores of all CPUs is returned.

string SI_CPUExtensions()
Returns supported CPU extensions/Instruction sets.

bool SI_HasAVX
bool SI_HasAVX2
bool SI_HasAVX512
bool SI_HasFMA3
bool SI_HasFMA4
bool SI_HasMMX
bool SI_HasSSE
bool SI_HasSSE2
bool SI_HasSSE3
bool SI_HasSSE41
bool SI_HasSSE42
bool SI_HasSSSE3
Convenience functions for supported CPU extensions

int SI_TotalSystemMemory()
Returns the total system memory in MiB

int SI_AvailableSystemMemory()
Returns the available system memory in MiB

string SI_ProcessName()
Returns the name of the current process

int SI_ProcessBitness()
Returns the bitness of the current process

int SI_ModulePath()
Returns the path of the SysInfo plugin.

int SI_ScreenResX()
Returns the horizontal screen resolution

int SI_ScreenResY()
Returns the vertical screen resolution

int SI_ScreenBitsPerPixel()
Returns the screen BPP

int SI_ScreenVRefresh()
Returns the vertical refresh rate of the screen

string SI_GetEnvVar(string "env_var")
Returns the value of the environment variable "env_var"
Example:
Path = SI_GetEnvVar("PATH")
The argument "env_var" is not case-sensitive

string SI_UserName()
Returns the name of the currently logged in user



Avisynth related functions:

string AI_AvsFileVersion
Returns the value of the FileVersion resource property

string AI_AvsProductVersion
Returns the value of the ProductVersion resource property

int AI_AvsPlusBuildNumber
Returns the AVS+ build number

bool AI_IsAvs26
Returns true if the Avisynth VersionNumber is >= 2.6

bool AI_IsAvsPlus
Returns true for Avisynth+

string AI_AvsDLLPath()
Returns the path of the loaded avisynth.dll

string AI_AvsDLLTimeStamp()
Returns the time stamp (last write time) of the loaded avisynth.dll

bool AI_InternalFunctionExists(string "name")
Returns true if an internal function ("name") is available in the current environment
The argument 'name' is not case-sensitive

bool AI_ExternalFunctionExists(string "name")
Returns true if an external (plugin) function ("name") is available in the current environment
The argument 'name' is not case-sensitive

bool AI_FunctionExists(string "name")
Returns true if an internal or external (plugin) function ("name") is available in the current environment
The argument 'name' is not case-sensitive

string AI_AutoLoadPath(string "registry_location")
Returns the Avisynth auto-load directory/directories. Valid arguments for "registry_location" are (case sensitive!):
(See http://avisynth.nl/index.php/AviSynth%2B#New_Functions for info on the origin of these arguments)
USER_PLUS_PLUGINS
MACHINE_PLUS_PLUGINS
USER_CLASSIC_PLUGINS
MACHINE_CLASSIC_PLUGINS


Other functions:

float SysInfoVersion()
Returns SysInfo.dll version number




See SI_ProcessBitness(), returns bitness of Avisynth Process.

[terminator3]

VirtualDub x86 loading avs script uses/requires avisynth x86 and x86 avisynth plugins, VirtualDub x64 loading avs script uses/requires avisynth x64 and x64 avisynth plugins,
MeGUI x86 requires x86 avisynth & x86 avisynth pluigins, MeGUI x64 requires x64 avisynth & x64 avisynth pluigins,
etc.

NOTE,
Avisynth x86 AUTOMATICALLY loads CPP plugin dll's from the avs x86 plugins directory, you do not need LoadPlugin call for dll's in Plugins dir,
same for x64 dll's and Plugins dir.
[Avisynth+ auto loads C plugins too, dont need LoadCPlugin]

AVSI scripts in Plugins directory are AUTOMATICALLY Imported, you do NOT need Import of avsi files in the plugins directory.
[Avisynth+ auto loads avs scripts too]

Groucho2004 SysInfo:- https://forum.doom9.org/showthread.php?t=176131


See SI_ProcessBitness(), returns bitness of Avisynth Process.

Do you know how I could get the most out of the Ryzen 3960x processor with the Avisinth? any command or script or something?

[StainlessS]

Not really, thats kinda like asking

"what is the best ?"

Best what ?

Avs x64 is defo the way to go, IF ALL YOUR REQUIRED PLUGINS ARE IMPLEMENTED for X64.

[terminator3]

Not really, thats kinda like asking

"what is the best ?"

Best what ?

Avs x64 is defo the way to go, IF ALL YOUR REQUIRED PLUGINS ARE IMPLEMENTED for X64.

but surely you are not taking advantage of all the cpu threads

[StainlessS]

You will have to ask specific questions, not
"What is the bestest super duper does everything better than any other script, and does it faster and more precise and makes my coffee and doles out free cigarettes and beer", type question.

Others may be able to answer CPU threads usage questions a lot better than I, I've only recently started using mutlithreading.