AVSMeter 3.0.9.0

[StainlessS]

There is no switch "-avsinfo", just the command "avsinfo"
Yeh, me done dat lotsa times.

[gispos]

Not sure what you're getting at. There is no switch "-avsinfo", just the command "avsinfo". If you specify "avsinfo" together with a script on the command line, AVSMeter throws an error.

That is the problem, why no switch for avsinfo? The user enters the parameters for the program in the edit field and the file name is automatically transferred. So that's standard for other programs

Now I have to guess, is the user using AvsMeter? and I have to replace the filename with 'avsinfo' and not use any other parameter.

I had to use extra characters that are used as information as to whether the file name has to be replaced by avsinfo. It's awkward and confusing.

Command? Why? Nonsense, use parameters (switches).

Just add -avsinfo as a parameter

Default Error
https://i.postimg.cc/DfcX35Gj/Parameter-Error.jpg (https://postimages.org/)

Not standard for it to work
https://i.postimg.cc/yYdk4Ksx/Parameter.jpg (https://postimages.org/)

Menu name | parameters for the program
The file name is transferred automatically. And that works for everyone ... except AvsMeter

[Groucho2004]

Command? Why? Nonsense, use parameters (switches)."-avsinfo" used to be a switch.

Even though I don't appreciate your snippyness, I'll think about bringing it back.

I wonder what other users think about it.

[videoh]

I don't appreciate your snippyness I don't appreciate your dorkiness.

[Groucho2004]

I don't appreciate your dorkiness.Eat my shorts.

[StainlessS]

I dont appreciate your eating habits.

[gispos]

"-avsinfo" used to be a switch.

Even though I don't appreciate your snippyness, I'll think about bringing it back.

I wonder what other users think about it.

Sorry if I have expressed my wishes a little overzealous.
I know my English is not the best, but I've tried so many times to bring the problem to you ... and that excited me:)

God forgive me, hopefully you too

[Groucho2004]

v3.0.4.0

"avsinfo" is now again a switch ("-avsinfo")
Removed custom avisynth.dll dialog selection from the command line
Removed custom plugin directory dialog selection from the command line

[gispos]

v3.0.4.0

"avsinfo" is now again a switch ("-avsinfo")

nice, thanks :)

[gispos]

A little hint ( well-meant! :)). After recognizing the argument '-avsinfo' it is not necessary to check whether an avs file has been passed.
How does the user benefit from receiving an error message for every argument that does not match?
It is user-friendly to simply ignore unused arguments.

As written 'File names are often automatically passed along with the arguments'

[Groucho2004]

A little hint ( well-meant! :)). After recognizing the argument '-avsinfo' it is not necessary to check whether an avs file has been passed.
How does the user benefit from receiving an error message for every argument that does not match?
It is user-friendly to simply ignore unused arguments.

As written 'File names are often automatically passed along with the arguments'How would the program know what the user intended?
Let's say the command line is "AVSMeter test.avs -avsinfo", either the script name or the parameter was added by mistake. Which one to ignore?

[StainlessS]

HMmmm, so your software cannot tell what user intended ... seems a little unreliable.

[Groucho2004]

HMmmm, so your software cannot tell what user intended ... seems a little unreliable.Not to worry, the mind-reading module is already in the works.

[gispos]

How would the program know what the user intended?
Let's say the command line is "AVSMeter test.avs -avsinfo", either the script name or the parameter was added by mistake. Which one to ignore?
The filename is not a switch. You have to set priorities.
And with -avsinfo it's even easier, because -avsinfo is your main switch that sets your program to another mode.

So why check a series of switches that this mode cannot do anything with.

If you had 2 main switches, let's say 3 different modes, you could argue about whether the switch set first in the parameter list is used (which I would do) or whether an error message appears.

[videoh]

For a command that included an avs script and -avsinfo, I would expect the program to first print the avsinfo and then do the script processing. Am I missing something?

[gispos]

For a command that included an avs script and -avsinfo, I would expect the program to first print the avsinfo and then do the script processing. Am I missing something?

You can do it that way, but you don't have to do it that way
That seems to me to be too complicated.

Prioritizing switches - the only correct way to proceed

[videoh]

The user has explicitly asked for both!

And who are you to declare what is "the only correct way"?

[Groucho2004]

There are at least 30 error conditions under which AVSMeter throws an error. I'm not going to remove that one. The program returns "-1" in case of an error (otherwise "0"). Get your command line in order and check for the program's return value. Then you can decide for yourself what to ignore.

[Groucho2004]

For a command that included an avs script and -avsinfo, I would expect the program to first print the avsinfo and then do the script processing. Am I missing something?Running a script and gathering extended Avisynth info (-avsinfo) are 2 different operating modes. I'd rather have them separate. There is for example a switch "-info" which simply returns a scripts properties. Users have accidentally used -avsinfo instead of -info before which just creates confusion. So, using -avsinfo together with a script name makes no sense and should be pointed out to the user.

[gispos]

Sorry, but what videoh asks is nonsense and makes the whole topic absurd.
Groucho you have one main switch, so it can not be difficult to ignore the filename and all unnecessary arguments.

[FranceBB]

Not to worry, the mind-reading module is already in the works.

https://i.imgur.com/zp6VAqK.png

[Groucho2004]

Sorry, but what videoh asks is nonsense and makes the whole topic absurd.The problem is that you think what you're asking makes sense.

[gispos]

The problem is that you think what you're asking makes sense.
There are enough examples.
if you use arguments with ffmpeg that are not needed they are ignored. Nobody says 'No you can't do that'

But I'm out of here now.

[videoh]

There are enough examples.
if you use arguments with ffmpeg that are not needed they are ignored. Nobody says 'No you can't do that' And there are enough examples of applications that do report bad options.

But I'm out of here now. Is that a threat or a promise? A fit of pique?

[gispos]

Is that a threat or a promise? A fit of pique?
Yesterday you insulted Groucho and today you insulted me. What's wrong with you?
What had started as a harmless discussion took an uncomfortable turn. That's why.

And there are enough examples of applications that do report bad options.
And because some do it wrong, you don't have to do it the same way.

I regret having raised this issus here. I should have known better that this only brings trouble.
My bad.

[wonkey_monkey]

gispos, if I may interject, it's your unwavering insistence that you're right and everyone else is wrong that has likely rubbed people up the wrong way here. videoh and Groucho2004 have given good reasons for not doing as you suggest.

That said, I stll haven't got a clue what you're trying to achieve. What other program is trying to pass a filename to avsmeter when you don't want it to?

[StainlessS]

Thats what I like about science, there's never only one correct answer.

:)

[Groucho2004]

v3.0.5.0

Added command line switch "-p". This pauses the program at the end and returns after pressing a key.
Modified some error messages

[videoh]

My bad. You finally got something right. Congratulations!

[stax76]

I would like to request Windows 10 long path support by adding a manifest, since the prefix workaround don't work there are probably buffers used with MAX_PATH size limitation.

Invalid argument: "\\?\C:\iiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiii\iiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiii\Jupiter !_temp\Jupiter !_new_temp.avs"

https://github.com/staxrip/staxrip/wiki/Windows-10-long-path-support

https://docs.microsoft.com/en-us/windows/win32/fileio/naming-a-file

[Groucho2004]

I would like to request Windows 10 long path support by adding a manifest, since the prefix workaround don't work there are probably buffers used with MAX_PATH size limitation.Can you try this (http://www.mediafire.com/file/zvng46oicnj8t72/AVSMeter_3.0.6.0.7z/file) version?

[stax76]

Thanks for the support Groucho. It does not work yet, maybe still a buffer issue because even the prefix workaround does not work. It's not having a manifest according to Resource Hacker. You can find example manifests on our wiki page:

https://github.com/staxrip/staxrip/wiki/Windows-10-long-path-support#manifests

[stax76]

Project -> Properties -> Linker -> Manifest File


<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<assembly xmlns="urn:schemas-microsoft-com:asm.v1" manifestVersion="1.0">
<assemblyIdentity name="none" version="0.0.0.0"/>
<application xmlns="urn:schemas-microsoft-com:asm.v3">
<windowsSettings>
<longPathAware xmlns="http://schemas.microsoft.com/SMI/2016/WindowsSettings">true</longPathAware>
</windowsSettings>
</application>
</assembly>

[Groucho2004]

It's not having a manifest according to Resource Hacker.
Try this one (http://www.mediafire.com/file/a4aho48y3kfee43/file) (with manifest).

[stax76]

It's still not working I'm afraid.

Error: Invalid argument: "C:\iiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiii\iiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiii\Jupiter !_temp\Jupiter !_new_temp.avs"

[Groucho2004]

It's still not working I'm afraid.Hm, I'll look into it.

[Groucho2004]

v3.0.6.0

Increased some static buffer sizes
Now using LoadlibraryEx with the flag "LOAD_WITH_ALTERED_SEARCH_PATH"

[stax76]

@Groucho2004

Which IDE and which compiler name and version do you use to build avsmeter?


I tried with following:

g++.exe (x86_64-posix-seh-rev0, Built by MinGW-W64 project) 8.1.0

GNU gdb (GDB) 8.1


Guide used:

https://code.visualstudio.com/docs/cpp/config-mingw


Errors



> Executing task: & 'C:\Program Files\mingw-w64\x86_64-8.1.0-posix-seh-rt_v6-rev0\mingw64\bin\g++.exe' -g 'D:\To Do\AVSMeter3060\source\*.cpp' -o 'd:\To Do\AVSMeter3060\source\AVSMeter.exe' <

In file included from D:\To Do\AVSMeter3060\source\AVSMeter.cpp:20:
D:\To Do\AVSMeter3060\source\exception.h: In function 'void SE_Translator(unsigned int, EXCEPTION_POINTERS*)':
D:\To Do\AVSMeter3060\source\exception.h:1859:22: error: no matching function for call to 'std::exception::exception(char [2048])'
throw exception(msg);
^
In file included from C:/Program Files/mingw-w64/x86_64-8.1.0-posix-seh-rt_v6-rev0/mingw64/lib/gcc/x86_64-w64-mingw32/8.1.0/include/c++/exception:38,
from C:/Program Files/mingw-w64/x86_64-8.1.0-posix-seh-rt_v6-rev0/mingw64/lib/gcc/x86_64-w64-mingw32/8.1.0/include/c++/new:40,
from C:/Program Files/mingw-w64/x86_64-8.1.0-posix-seh-rt_v6-rev0/mingw64/lib/gcc/x86_64-w64-mingw32/8.1.0/include/c++/ext/new_allocator.h:33,
from C:/Program Files/mingw-w64/x86_64-8.1.0-posix-seh-rt_v6-rev0/mingw64/lib/gcc/x86_64-w64-mingw32/8.1.0/include/c++/x86_64-w64-mingw32/bits/c++allocator.h:33,
from C:/Program Files/mingw-w64/x86_64-8.1.0-posix-seh-rt_v6-rev0/mingw64/lib/gcc/x86_64-w64-mingw32/8.1.0/include/c++/bits/allocator.h:46,
from C:/Program Files/mingw-w64/x86_64-8.1.0-posix-seh-rt_v6-rev0/mingw64/lib/gcc/x86_64-w64-mingw32/8.1.0/include/c++/string:41,
from D:\To Do\AVSMeter3060\source\common.h:31,
from D:\To Do\AVSMeter3060\source\AVSMeter.cpp:19:
C:/Program Files/mingw-w64/x86_64-8.1.0-posix-seh-rt_v6-rev0/mingw64/lib/gcc/x86_64-w64-mingw32/8.1.0/include/c++/bits/exception.h:63:5: note: candidate: 'std::exception::exception()'
exception() _GLIBCXX_USE_NOEXCEPT { }
^~~~~~~~~
C:/Program Files/mingw-w64/x86_64-8.1.0-posix-seh-rt_v6-rev0/mingw64/lib/gcc/x86_64-w64-mingw32/8.1.0/include/c++/bits/exception.h:63:5: note: candidate expects 0 arguments, 1 provided
C:/Program Files/mingw-w64/x86_64-8.1.0-posix-seh-rt_v6-rev0/mingw64/lib/gcc/x86_64-w64-mingw32/8.1.0/include/c++/bits/exception.h:60:9: note: candidate: 'constexpr std::exception::exception(const std::exception&)'
class exception
^~~~~~~~~
C:/Program Files/mingw-w64/x86_64-8.1.0-posix-seh-rt_v6-rev0/mingw64/lib/gcc/x86_64-w64-mingw32/8.1.0/include/c++/bits/exception.h:60:9: note: no known conversion for argument 1 from 'char [2048]' to 'const std::exception&'
The terminal process "C:\WINDOWS\System32\WindowsPowerShell\v1.0\powershell.exe -Command & 'C:\Program Files\mingw-w64\x86_64-8.1.0-posix-seh-rt_v6-rev0\mingw64\bin\g++.exe' -g 'D:\To Do\AVSMeter3060\source\*.cpp' -o 'd:\To Do\AVSMeter3060\source\AVSMeter.exe'" terminated with exit code: 1.


tasks.json


{
"version": "2.0.0",
"tasks": [
{
"type": "shell",
"label": "C/C++: g++.exe build files",
"command": "C:\\Program Files\\mingw-w64\\x86_64-8.1.0-posix-seh-rt_v6-rev0\\mingw64\\bin\\g++.exe",
"args": [
"-g",
"${workspaceFolder}\\*.cpp",
"-o",
"${fileDirname}\\${fileBasenameNoExtension}.exe"
],
"options": {
"cwd": "${workspaceFolder}"
},
"problemMatcher": [
"$gcc"
],
"group": {
"kind": "build",
"isDefault": true
}
},
{
"type": "shell",
"label": "C/C++: cl.exe build active file",
"command": "cl.exe",
"args": [
"/Zi",
"/EHsc",
"/Fe:",
"${fileDirname}\\${fileBasenameNoExtension}.exe",
"${file}"
],
"options": {
"cwd": "${workspaceFolder}"
},
"problemMatcher": [
"$msCompile"
],
"group": {
"kind": "build",
"isDefault": true
}
}
]
}


launch.json


{
// Use IntelliSense to learn about possible attributes.
// Hover to view descriptions of existing attributes.
// For more information, visit: https://go.microsoft.com/fwlink/?linkid=830387
"version": "0.2.0",
"configurations": [

{
"name": "g++.exe - Build and debug active file",
"type": "cppdbg",
"request": "launch",
"program": "${fileDirname}\\${fileBasenameNoExtension}.exe",
"args": [],
"stopAtEntry": false,
"cwd": "${workspaceFolder}",
"environment": [],
"externalConsole": false,
"MIMode": "gdb",
"miDebuggerPath": "C:\\Program Files\\mingw-w64\\x86_64-8.1.0-posix-seh-rt_v6-rev0\\mingw64\\bin\\gdb.exe",
"setupCommands": [
{
"description": "Enable pretty-printing for gdb",
"text": "-enable-pretty-printing",
"ignoreFailures": true
}
],
"preLaunchTask": "C/C++: g++.exe build files"
}
]
}


MS compiler error

> Executing task: cl.exe /Zi /EHsc /Fe: 'd:\To Do\AVSMeter3060\source\AVSMeter.exe' 'd:\To Do\AVSMeter3060\source\AVSMeter.cpp' <

Microsoft (R) C/C++ Optimizing Compiler Version 19.27.29111 for x86
Copyright (C) Microsoft Corporation. All rights reserved.

AVSMeter.cpp
d:\To Do\AVSMeter3060\source\AvisynthInfo.h(372): warning C4834: discarding return value of function with 'nodiscard' attribute
Microsoft (R) Incremental Linker Version 14.27.29111.0
Copyright (C) Microsoft Corporation. All rights reserved.

/debug
"/out:d:\To Do\AVSMeter3060\source\AVSMeter.exe"
AVSMeter.obj
AVSMeter.obj : error LNK2019: unresolved external symbol __imp__CharToOemA@8 referenced in function __catch$?CalculateFrameInterval@@YAIAAV?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@0@Z$4
AVSMeter.obj : error LNK2019: unresolved external symbol _GetFileVersionInfoSizeA@8 referenced in function "public: class std::basic_string<char,struct std::char_traits<char>,class std::allocator<char> > __thiscall CUtils::GetFileVersion(class std::basic_string<char,struct std::char_traits<char>,class std::allocator<char> >)" (?GetFileVersion@CUtils@@QAE?AV?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@V23@@Z)
AVSMeter.obj : error LNK2019: unresolved external symbol _GetFileVersionInfoA@16 referenced in function "public: class std::basic_string<char,struct std::char_traits<char>,class std::allocator<char> > __thiscall CUtils::GetFileVersion(class std::basic_string<char,struct std::char_traits<char>,class std::allocator<char> >)" (?GetFileVersion@CUtils@@QAE?AV?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@V23@@Z)
AVSMeter.obj : error LNK2019: unresolved external symbol _VerQueryValueA@16 referenced in function "public: class std::basic_string<char,struct std::char_traits<char>,class std::allocator<char> > __thiscall CUtils::GetFileVersion(class std::basic_string<char,struct std::char_traits<char>,class std::allocator<char> >)" (?GetFileVersion@CUtils@@QAE?AV?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@V23@@Z)
AVSMeter.obj : error LNK2019: unresolved external symbol __imp__RegCloseKey@4 referenced in function __catch$?GetInfo@CAvisynthInfo@@QAEHAAV?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@H@Z$13
AVSMeter.obj : error LNK2019: unresolved external symbol __imp__RegEnumKeyExA@32 referenced in function __catch$?TestLoadPlugins@CAvisynthInfo@@AAEXXZ$2
AVSMeter.obj : error LNK2019: unresolved external symbol __imp__RegOpenKeyExA@20 referenced in function __catch$?GetInfo@CAvisynthInfo@@QAEHAAV?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@H@Z$13
AVSMeter.obj : error LNK2019: unresolved external symbol __imp__RegQueryValueExA@24 referenced in function __catch$?GetInfo@CAvisynthInfo@@QAEHAAV?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@H@Z$13
AVSMeter.obj : error LNK2019: unresolved external symbol __imp__MapAndLoad@20 referenced in function "public: int __thiscall CAvisynthInfo::GetInfo(class std::basic_string<char,struct std::char_traits<char>,class std::allocator<char> > &,int)" (?GetInfo@CAvisynthInfo@@QAEHAAV?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@H@Z)
AVSMeter.obj : error LNK2019: unresolved external symbol __imp__UnMapAndLoad@4 referenced in function "public: int __thiscall CAvisynthInfo::GetInfo(class std::basic_string<char,struct std::char_traits<char>,class std::allocator<char> > &,int)" (?GetInfo@CAvisynthInfo@@QAEHAAV?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@H@Z)
AVSMeter.obj : error LNK2019: unresolved external symbol __imp__ImageRvaToVa@16 referenced in function
"public: int __thiscall CAvisynthInfo::GetInfo(class std::basic_string<char,struct std::char_traits<char>,class std::allocator<char> > &,int)" (?GetInfo@CAvisynthInfo@@QAEHAAV?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@H@Z)
AVSMeter.obj : error LNK2019: unresolved external symbol _cpuid_present referenced in function __catch$?TestLoadPlugins@CAvisynthInfo@@AAEXXZ$2
AVSMeter.obj : error LNK2019: unresolved external symbol _cpuid_get_raw_data referenced in function __catch$?TestLoadPlugins@CAvisynthInfo@@AAEXXZ$2
AVSMeter.obj : error LNK2019: unresolved external symbol _cpu_identify referenced in function __catch$?TestLoadPlugins@CAvisynthInfo@@AAEXXZ$2
d:\To Do\AVSMeter3060\source\AVSMeter.exe : fatal error LNK1120: 14 unresolved externals
The terminal process "C:\WINDOWS\System32\WindowsPowerShell\v1.0\powershell.exe -Command cl.exe /Zi /EHsc /Fe: 'd:\To Do\AVSMeter3060\source\AVSMeter.exe' 'd:\To Do\AVSMeter3060\source\AVSMeter.cpp'" terminated with exit code: 1.

[stax76]

I managed to debug with VS, here it does not enter:


if (::GetFullPathName(argv[iArg], MAX_PATH_LEN, szOut, &lpPart))
{
sAVSFile = utils.StrFormat("%s", szOut);
if (!utils.FileExists(sAVSFile))
{
PrintConsole(Settings.bConUseStdOut, COLOR_ERROR, "\nError: File not found: \"%s\"\n", sAVSFile.c_str());
PollKeys();
return -1;
}
else
continue;
}


It's because GetFullPathNameA is used which does not support long path I think, you probably need to call GetFullPathNameW.


In the ANSI version of this function, the name is limited to MAX_PATH characters. To extend this limit to 32,767 wide characters, call the Unicode version of the function (GetFullPathNameW)

[stax76]

Github mirror using Visual Studio and latest cpu lib:

https://github.com/stax76/AVSMeter

[VoodooFX]

"AVSDLL=" in ini doesn't work anymore!? I tried to update from v2.9.4...

In readme I still see:

"-avsinfo"
Displays extended info about the installed Avisynth version and the plugin sub-system. If a custom avisynth.dll is specified in the ini file, info about that file will be displayed.

EDIT:
Last version with "AVSDLL=" working is v3.0.3.0.

[Groucho2004]

"AVSDLL=" in ini doesn't work anymore!? I tried to update from v2.9.4...

In readme I still see:



EDIT:
Last version with "AVSDLL=" working is v3.0.3.0.I removed it but I forgot to remove that reference in the documentation. I suppose you added the entry manually to the ini file because that entry should also not be there.

If you really need that feature I might put it back.

[VoodooFX]

If you really need that feature I might put it back.
That would be nice, this feature I use very often, almost every time I run AVSMeter.

[Groucho2004]

v3.0.7.0
Updated libcpuid (new AMD and Intel CPUs)

The user can specify a custom avisynth.dll in the INI file.
This feature was removed some time ago, now it's back

Info about used command line switches is added to the log files

[VoodooFX]

Thanks for quick update.

[stax76]

StaxRip has a tool auto updater but mediafire is too difficult to automate. :(


Edit:

It's also ridiculous slow currently downloading 50 MB Patman ffmpeg build at 50 KB/s.

[Groucho2004]

v3.0.8.0
- Updated libcpuid (Intel Whiskey Lake-U CPUs, AMD Ryzen Cezanne)
- Updated AVS header files

[amayra]

there a tool for vapoursynth like this one?
or it possible to add vapoursynth support to AVSMeter?

[Groucho2004]

there a tool for vapoursynth like this one?I doubt it.

possible to add vapoursynth support to AVSMeter?Possible - yes. However, these days I'm too busy doing that. Maybe someone else wants to take my code and write a VapourSynth version.

[ChaosKing]

there a tool for vapoursynth like this one?
or it possible to add vapoursynth support to AVSMeter?

For simple benchmarking => use vspipe http://www.vapoursynth.com/doc/vspipe.html
For basic plugin err checking => use vsrepogui https://github.com/theChaosCoder/VSRepoGUI