AVSMeter 3.0.9.0

[Music Fan]

Thanks !

[Groucho2004]

v2.9.9.1
- Increased range for AVISYNTH_INTERFACE_VERSION detection

[FranceBB]

- Added GPU power consumption sensor readout

That's great. So, if I use the new version of ffms2 or DGIndexNV and run a script through AVSMeter, it should detect my old NVIDIA Quadro K4000 and tell me how much I'm using it, right?
That's cool.
I get the feeling that we're somehow moving into a sort of avisynth_neo approach and I really like that.

[Groucho2004]

So, if I use the new version of ffms2 or DGIndexNV and run a script through AVSMeter, it should detect my old NVIDIA Quadro K4000 and tell me how much I'm using it, right?Correct. Keep in mind that it only measures the total power consumption. So, if there's something else running using the GPU heavily, the reading will be rather useless. The same goes for GPU usage and GPU memory usage.

[FranceBB]

Correct. Keep in mind that it only measures the total power consumption. So, if there's something else running using the GPU heavily, the reading will be rather useless. The same goes for GPU usage and memory usage.

Oh, I see, got it.

[pinterf]

Thanks!

[tormento]

Could be possible to check every plugin for compatibility with newer pinterf AVS+ iteration?

P.S: CPU power consumption too would be nice.

[pinterf]

Those plugins will probably appear at the non-usable list at the bottom of avsmeter avsinfo output

[Groucho2004]

Those plugins will probably appear at the non-usable list at the bottom of avsmeter avsinfo outputSo far I only found KNLMeansCL that produces an error message.

[Groucho2004]

Could be possible to check every plugin for compatibility with newer pinterf AVS+ iteration?As pinterf mentioned, there should be an error message.

CPU power consumption too would be nice.I looked into that some time ago, couldn't find a suitable library. I'll have another look.

[tormento]

As pinterf mentioned, there should be an error message.

Ok but I’d like to test my plugin folder instead of having to use them one by one.

[Groucho2004]

Ok but I’d like to test my plugin folder"AVSMeter avsinfo" will do exactly that. You can even use the switch "-c" to specify any directory with plugins you want.

You can also use the Avisynth Info Tool.

[tormento]

"AVSMeter avsinfo" will do exactly that.
You are telling me that is already capable of find AVS+ 3.x compatible plugins?

[Groucho2004]

You are telling me that is already capable of find AVS+ 3.x compatible plugins?It should. AVSMeter calls 'LoadPlugin()" on every plugin which should reveal incompatibilities (It does with the old KNLMeansCL). If you find one that does not work with AVS+ 3.5.2 and AVSMeter doesn't complain, let me know.

[tormento]

I looked into that some time ago, couldn't find a suitable library. I'll have another look.
AFAIK both MSI Afterburner and HwInfo can provide values, at least thru RivaTuner Server. I am not a programmer but you can easily find some documentation about needed APIs.

[Groucho2004]

HwInfoThat API is not free.

... MSI Afterburner... RivaTuner Server ...No thanks.

[Groucho2004]

v2.9.9.2
- Updated AVS headers
- Updated libcpuid

[FranceBB]

v2.9.9.2
- Updated AVS headers
- Updated libcpuid

Thank you! :)

[DiablosDemon]

Hello Grocho I can't seem to get the AVSMeter64 to install. I have the 32bit version working. I installed as administrator. What do you think is happening to not let this install OR what am I doing wrong(this is the most likely problem)? When I install all I get is a flash on the screen. I really do like the meter works great with 32bit but I want to try some of the 64bit scripts. Thanks. Using Powershell, message below.

PS C:\Users\ME\Desktop\TestAVS> avsmeter64
avsmeter64 : The term 'avsmeter64' is not recognized as the name of a cmdlet, function, script file, or operable
program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
At line:1 char:1
+ avsmeter64
+ ~~~~~~~~~~
+ CategoryInfo : ObjectNotFound: (avsmeter64:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException

[StainlessS]

Where have you put it ?

Go to command line and check that path to directory holding AvsMeter64.exe is set.
ie from command line type 'set'

EDIT:
for me, has this for path

Path=C:\Program Files (x86)\Common Files\Oracle\Java\javapath;C:\Windows\system3
2;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0
\;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Windows\System32\WindowsPowerSh
ell\v1.0\;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Windows\System32\Window
sPowerShell\v1.0\;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\BIN;C:\BINW7;C:
\ProgramData\chocolatey\bin;;C:\Program Files\VSCodium\bin

Above where mine is/are [both x86 and x64] in BLUE
EDIT: I got an awful lot of identical Powershell paths in there, I've deleted the extra ones.

[DiablosDemon]

OK I'm a bonehead It was a while ago I installed the 32bit version and forgot how it was done. I have it in now but still have a slight problem. AVSmeter64 can't create the .ins file. I installed the .ins file that came with the .exe in the same directory. Probably another bonehead moment.

AVSMeter 2.9.9.2 (x64), 2012-2020, (c) Groucho2004

Cannot create "C:\Program Files\AVSmeter64\AVSMeter.ini"

[Groucho2004]

Cannot create "C:\Program Files\AVSmeter64\AVSMeter.ini"Windows won't let you write to "Program Files". Use a different directory, for example what Stainless suggested above or something like "C:\Tools". And don't forget to add that directory to your PATH environment variable.

[DiablosDemon]

Thanks Grocho I did not know windows did that. Working great now. Is the Program files (86) different? This is where I put the 32bit which works great too. :)

C:\Program Files (x86)\AVSmeter\AVSmeter.exe

[Groucho2004]

Is the Program files (86) different? This is where I put the 32bit which works great too. :)I don't know. I have UAC disabled and I'm logged in with admin rights.

[Groucho2004]

v2.9.9.3

Added new color space definitions (CS_RGBP8 and CS_RGBAP8), removed redundant CS_RGBP / CS_RGBAP
Fixed a version resource issue
Updated AVS headers

[StainlessS]

Cheers oh Groucho one :)

[tormento]

@Groucho2004

Isn't possible to list interface version for every plugin?

[Groucho2004]

Isn't possible to list interface version for every plugin?There's no such thing. Avisynth C++ plugins either use the 2.0, 2.5 or 2.6 initialisation which AVSMeter indicates. BTW, 2.0 is ancient and not supported by AVS+.
The AVISYNTH_INTERFACE_VERSION is a property of avisynth.dll, also indicated by AVSMeter.

[tormento]

There's no such thing. Avisynth C++ plugins either use the 2.0, 2.5 or 2.6 initialisation which AVSMeter indicates. BTW, 2.0 is ancient and not supported by AVS+.
The AVISYNTH_INTERFACE_VERSION is a property of avisynth.dll, also indicated by AVSMeter.


I meant compatibility. Perhaps trying to simulate a call to the dll in the possible different interfaces and look what gives error and generate report as maximum supported interface.

[Groucho2004]

I meant compatibility. Perhaps trying to simulate a call to the dll in the possible different interfaces and look what gives error and generate report as maximum supported interface.Sorry, not workable.

[Groucho2004]

v3.0.0.0
- Added check for duplicate functions

This checks for duplicate functions
1. within .avsi files
2. against functions in other .avsi files
3. against internal/plugin functions

Since a new feature was added I guess bumping the major version number is justified.

I would appreciate some testing of the new feature (real.finder, Stainless?).

Have fun.

[ChaosKing]

Thx for adding duplicate function detection.
I think you should show all scripts with duplicate functions.


In avsrepogui I show it like this:

Duplicate Function Name Detection
------------------------------------------------------------
Path of *.avsi files: D:\AvisynthRepository\SCRIPTS
Found 30 potential conflicts:

Function name: bbb
D:\AvisynthRepository\SCRIPTS\a - copy.avsi
D:\AvisynthRepository\SCRIPTS\b - copy.avsi
D:\AvisynthRepository\SCRIPTS\c - copy.avsi

Function name: GreyCenteredToMask_dhh
D:\AvisynthRepository\SCRIPTS\dehalohmod.avsi
D:\AvisynthRepository\SCRIPTS\Zs_RF_Shared.avsi


With avsmeter I can't see in which file the "GreyCenteredToMask_dhh" is found first. In this case it would be dehalomod.avsi, but avsmeter would only show Zs_RF_Shared.avsi (or b & c copy, but not a copy)

[Groucho2004]

Thx for adding duplicate function detection.
I think you should show all scripts with duplicate functions.


In avsrepogui I show it like this:

Duplicate Function Name Detection
------------------------------------------------------------
Path of *.avsi files: D:\AvisynthRepository\SCRIPTS
Found 30 potential conflicts:

Function name: bbb
D:\AvisynthRepository\SCRIPTS\a - copy.avsi
D:\AvisynthRepository\SCRIPTS\b - copy.avsi
D:\AvisynthRepository\SCRIPTS\c - copy.avsi

Function name: GreyCenteredToMask_dhh
D:\AvisynthRepository\SCRIPTS\dehalohmod.avsi
D:\AvisynthRepository\SCRIPTS\Zs_RF_Shared.avsi


With avsmeter I can't see in which file the "GreyCenteredToMask_dhh" is found first. In this case it would be dehalomod.avsi, but avsmeter would only show Zs_RF_Shared.avsi (or b & c copy, but not a copy)Can you post these AVSI's for me to test?

[ChaosKing]

You can just create a copy of your avsi script ;-)
https://filehorst.de/d/drDJGffI

[tormento]

Can you post these AVSI's for me to test?


Parsing this forum for “AVSI” word will make you happy [emoji2]

[ChaosKing]

Too much work, copy paste is always faster :D

@Groucho2004 How are you reading / finding the script functions? Via avisynth interface? I'm using regex to find all script functions... just curious how it is implemented.

[Groucho2004]

How are you reading / finding the script functions?Simple parsing of the .avsi files.

[real.finder]

v3.0.0.0
- Added check for duplicate functions

This checks for duplicate functions
1. within .avsi files
2. against functions in other .avsi files
3. against internal/plugin functions

Since a new feature was added I guess bumping the major version number is justified.

I would appreciate some testing of the new feature (real.finder, Stainless?).

Have fun.

thanks! it work

[Plugin errors/warnings]
_______________________________________________________________________________________________________

Duplicate function in "SCRIPTS\Cdeblend.avsi":
"min"
_______________________________________________________________________________________________________

Duplicate function in "SCRIPTS\ConditionalSmoothBob.avsi":
"function ConditionalVideoSo"
_______________________________________________________________________________________________________

Duplicate function in "SCRIPTS\ConditionalSmoothBob.avsi":
"function ConditionalVideoSo"
_______________________________________________________________________________________________________

Duplicate function in "SCRIPTS\HQDeringmod.avsi":
"tion YtoYUV_Ge"
_______________________________________________________________________________________________________

Duplicate function in "SCRIPTS\HQDeringmod.avsi":
"Function GetCSP_"
_______________________________________________________________________________________________________

Duplicate function in "SCRIPTS\restore24.avsi":
"Evaluate"
_______________________________________________________________________________________________________

Duplicate function in "SCRIPTS\restore24.avsi":
"m4"
_______________________________________________________________________________________________________

Duplicate function in "SCRIPTS\SAA.avsi":
"SAA"
_______________________________________________________________________________________________________

Duplicate function in "SCRIPTS\Signs_Overlay.avsi":
"sign"
_______________________________________________________________________________________________________

Duplicate function in "SCRIPTS\TGMCmod.avsi":
"VCRep"
_______________________________________________________________________________________________________

Duplicate function in "SCRIPTS\Zs_RF_Shared.avsi":
"SharpAAMCmod"
_______________________________________________________________________________________________________

but not perfect

ChaosKing idea about mentions the scripts with duplicate functions is good

[Groucho2004]

Duplicate function in "SCRIPTS\ConditionalSmoothBob.avsi":
"function ConditionalVideoSo"
_______________________________________________________________________________________________________

Duplicate function in "SCRIPTS\ConditionalSmoothBob.avsi":
"function ConditionalVideoSo"
_______________________________________________________________________________________________________

Duplicate function in "SCRIPTS\HQDeringmod.avsi":
"tion YtoYUV_Ge"
_______________________________________________________________________________________________________

Duplicate function in "SCRIPTS\HQDeringmod.avsi":
"Function GetCSP_"[/CODE]

but not perfectAre these the exact error messages? If so, can you post the avsi that produced them?

[real.finder]

Are these the exact error messages? If so, can you post the avsi that produced them?

yes they are

https://www.solidfiles.com/v/N4DmPy6MgMGXx

[Groucho2004]

yes they are

https://www.solidfiles.com/v/N4DmPy6MgMGXx
Thanks. I know what happened there.

[ChaosKing]

Another improvement could be made here. I can see that some plugins are using the same function name. But which plugin is it (or plugins)? I think showing also the dll file name would be great.

[Plugin errors/warnings]
_____________________________________________________________________________________

Duplicate function (Plugin): "AverageChromaU"
_____________________________________________________________________________________

Duplicate function (Plugin): "AverageChromaV"
_____________________________________________________________________________________

Duplicate function (Plugin): "AverageLuma"
_____________________________________________________________________________________

Duplicate function (Plugin): "ChromaUDifference"
...

[StainlessS]

The cdeblend script using min, maybe was written for avs 2.57 (or prior), 2.57 had no min/max funcs.

Think Grunt maybe redefines eg AverageChromaU, maybe adding Offset arg.

EDIT: Grunt


AverageChromaU "ci"
AverageChromaV "ci"
AverageLuma "ci"
BindStr "s"
ChromaUDifference "cci"
ChromaVDifference "cci"
ConditionalFilter "cccs[showx]b[args]s[local]b"
ConditionalFilter "cccs[showx]b[args]s[local]b"
FrameEvaluate "cs[showx]b[after_frame]b[args]s[local]b"
GConditionalFilter "cccs[show]b[args]s[local]b"
GConditionalFilter "cccs[show]b[args]s[local]b"
GFrameEvaluate "cs[show]b[after_frame]b[args]s[local]b"
GRTConfig "[local]b"
GScriptClip "cs[show]b[after_frame]b[args]s[local]b"
GWriteFile "c[filename]ss+[append]b[flush]b[args]s[local]b"
GWriteFileIf "c[filename]ss+[append]b[flush]b[args]s[local]b"
LumaDifference "cci"
RGBDifference "cci"
RGBDifferenceFromPrevious "ci"
RGBDifferenceToNext "ci"
ScriptClip "cs[showx]b[after_frame]b[args]s[local]b"
UDifferenceFromPrevious "ci"
UDifferenceToNext "ci"
UPlaneMax "c[threshold]fi"
UPlaneMedian "ci"
UPlaneMin "c[threshold]fi"
UPlaneMinMaxDifference "c[threshold]fi"
VDifferenceFromPrevious "ci"
VDifferenceToNext "ci"
VPlaneMax "c[threshold]fi"
VPlaneMedian "ci"
VPlaneMin "c[threshold]fi"
VPlaneMinMaxDifference "c[threshold]fi"
WriteFile "c[filenamex]ss+[append]b[flush]b[args]s[local]b"
WriteFileIf "c[filenamex]ss+[append]b[flush]b[args]s[local]b"
YDifferenceFromPrevious "ci"
YDifferenceToNext "ci"
YPlaneMax "c[threshold]fi"
YPlaneMedian "ci"
YPlaneMin "c[threshold]fi"
YPlaneMinMaxDifference "c[threshold]fi"


EDIT: The trailing i's seem to be the 'offset' args, 'Local' was (I think) recently added in avs+, 'args' not implements in avs+ I think.

BindStr() and GRTConfig() are newish to me, never noticed before a day or two ago, not sure if explained in Grunt docs.

EDIT: I think that some of the Grunt args are a little bit naughty, once you use an Optional named arg, all subsequent args should be optional named args, so
YPlaneMinMaxDifference "c[threshold]fi"
the i (which would be offset) following named optional arg threshold should be a named optional arg.
Above, "[threshold]f" is an optional arg named threshold, of type float. 'i' should really be specified something like "[Offset]i".

Maybe Gavino has an 'excuse' for doing it as is, or maybe not :)

[Groucho2004]

I can see that some plugins are using the same function name. But which plugin is it (or plugins)? I think showing also the dll file name would be great.I tried that before, very difficult. On the backburner for now.

[real.finder]

another thing I note in avs 2.6

https://pastebin.com/eB1JiWij

note that LoadPlugin: too many plugins loaded already (max. 50)

[ChaosKing]

Your list looks like mine, so it's Grunt. But what would the name of the other plugin be? You see the dilema :D

EDIT
I tried that before, very difficult. On the backburner for now.
ok, hopefully this can be added one day.

[ChaosKing]

avs 2.6 is like xp, should one really support it?

[Groucho2004]

another thing I note in avs 2.6

https://pastebin.com/eB1JiWij

note that LoadPlugin: too many plugins loaded already (max. 50)Avisynth throws that error when there are too many plugins in the auto-load directory.

[StainlessS]

But what would the name of the other plugin be?
Probably Avisnth.dll, ie builtin.

I note that I've recently been trying GisPos AvsPMod, and was getting a warning for GConditionalFilter duplicate name,
warning disappears when Grunt plugin removed.
Also warning about Beta version, presume is result of recent Groucho compiled grunt, having third part of 4 part version number in
resource file resource as non zero.
https://i.postimg.cc/HWqLmyvy/Untitled-00.jpg (https://postimages.org/)

EDIT: Guessing duplicate function thing about detected by AvsPMod due to the addresses of GConditionalFilter and ConditionalFilter
creator functions being the same, maybe.

EDIT: "This function is Beta" perhaps refers the the AvsPMod function rather than grunt functions.

[Groucho2004]

presume is result of recent Groucho compiled gruntI never compiled Grunt.