AVSMeter 3.0.9.0

[Groucho2004]

AVSMeter is a CLI (command line interface) tool which measures the speed/efficiency of Avisynth scripts and checks if Avisynth and its plugin sub-system are set up and working correctly.

Features:

• "Running" scripts with virtually no overhead, displaying clip info, CPU/GPU usage / memory usage and the minimum, maximum and average frames processed per second. Measuring how fast Avisynth can serve frames to a client application (x264, VirtualDub) and establishing CPU/GPU/memory usage helps with optimizing scripts and tracking down crashes, slowdowns and bottlenecks.
• Performing a thorough test of the Avisynth installation and associated plugins, checking if external dependencies are installed, etc.

Screen shots:

Command line usage:

AVSMeter script.avs [switches] or AVSMeter -avsinfo [switches]

Switches:
  -avsinfo            Displays extended Avisynth info
  -info   [-i]        Displays clip info
  -log    [-l]        Creates log file
  -csv                Creates csv file
  -gpu                Displays GPU/VPU usage (requires GPU-Z)
  -range=first,last   Sets frame range
  -timelimit=n        Sets time limit (seconds)
  -hp                 Sets process priority to high
  -o                  Omits script pre-scanning
  -lf                 Adds internal/external functions to the avsinfo*.log file
  -p                  Pauses the program at the end and returns after pressing a key.



Note:
For normal operation, i.e. testing the speed of a script, the "-o" switch should not be used,
otherwise the accuracy of the FPS/TPF measurements will be reduced, particularly for fast scripts.

For all features to work properly, run this program with administrative user rights.

System requirements:
Avisynth 2.6x, Avisynth+

Recent changes:

v3.0.9.0
- Updated libcpuid (Intel Rocket Lake, AMD Ryzen Milan)



Download
GPU-Z (needed when using the "-gpu" switch)

Video tutorial by Andrew Swan

[lansing]

Where are all the posts?

[Groucho2004]

Originally Posted by lansing

Where are all the posts?

I deleted the old thread a while ago. The old posts are not really relevant any more since so many things were changed/fixed.

[Groucho2004]

v2.6.1

• The list of plugin functions in the log file (-avsinfo -log) now points out duplicates (functions with the same name in different DLLs) by adding "[DUPLICATE]" to the function name(s)

[StainlessS]

Originally Posted by Groucho2004

v2.6.1

• The list of plugin functions in the log file (-avsinfo -log) now points out duplicates (functions with the same name in different DLLs) by adding "[DUPLICATE]" to the function name(s)

Very handy, ta very much.

[Groucho2004]

v2.6.2

• Fixed a problem caused by the 50 plugin limit in "classic" Avisynth

[VS_Fan]

It is flagging with the [DUPLICATE] suffix only one of the instances of duplicated functions, both in 32 and 64 bits:

• 32 bits: deblock_Deblock [DUPLICATE] _vs_ DGDecode_Deblock (Not flagged)
• 64 bits: deblock_Deblock (Not flagged) _vs_ MPEG2DecPlus64_Deblock [DUPLICATE]
  

It is useful this way, but could be better/clearer flagging all of the duplicated instances.

[StainlessS]

Originally Posted by VS_Fan

It is flagging with the [DUPLICATE] suffix only one of the instances of duplicated functions, both in 32 and 64 bits:

• 32 bits: deblock_Deblock [DUPLICATE] _vs_ DGDecode_Deblock (Not flagged)
• 64 bits: deblock_Deblock (Not flagged) _vs_ MPEG2DecPlus64_Deblock [DUPLICATE]
  

It is useful this way, but could be better/clearer flagging all of the duplicated instances.

Fair point, but perhaps DUPLICATED could be better description where flagging all instances.

[Groucho2004]

The duplicate detection ignores the plugin (file) name, so it just checks the "short" function names which is the whole point of this feature.

[Groucho2004]

v2.6.3

• Fixed: Updating very old ini files didn't work
• Removed report of duplicate plugin functions temporarily
• Some minor fixes/cosmetics

[Groucho2004]

v2.6.4

• New/updated code for reporting duplicate plugin functions

Reporting of duplicate plugin functions is now integrated in the "Plugin error/warnings" section and lists all plugins that export functions with the same name.
Example:

[Plugin errors/warnings]
___________________________________________________________________________________________________

Duplicate plugin function "nnedi3":
    e:\apps\videotools\avisynthrepository\avsplus_x86\plugins\nnedi3.dll
    e:\apps\videotools\avsplugins\autoload\nnedi3.dll
___________________________________________________________________________________________________

Duplicate plugin function "nnedi3_rpow2":
    e:\apps\videotools\avisynthrepository\avsplus_x86\plugins\nnedi3.dll
    e:\apps\videotools\avsplugins\autoload\nnedi3.dll
___________________________________________________________________________________________________

Cannot load file 'E:/Apps/VideoTools/AVSPlugins/AutoLoad/IBob.dll'. Platform returned code 126:
The specified module could not be found.

Dependencies that could not be loaded:
  avisynth_c.dll

Note: C 2.0 Plugins are not supported by Avisynth+
___________________________________________________________________________________________________

[Groucho2004]

v2.6.5

• Added hint for error 127 (proc not found / procedure could not be found)
• Minor fixes/cosmetics

[george84]

C:\Users\Walter\Downloads\AVSMeter265>"AVSMeter.exe" C:\Users\Walter\Documents\SMIL\BSG23\testsuite\OLED\ColorCheck\PhotoDirList2020Plus.xml.smil.avs -log

AVSMeter 2.6.5 (x86) - Copyright (c) 2012-2017, Groucho2004
AviSynth+ 0.1 (r2508, MT, i386) (0.1.0.0)

Exception 0xC0000005 [STATUS_ACCESS_VIOLATION]
Module: C:\Users\Walter\Downloads\AvisynthUniversalInstaller_2017-09-02\AvisynthRepository\AVSPLUS_x86\plugins\Shibatch.dll
Address: 0x6570A393

C:\Users\Walter\Downloads\AVSMeter265>SHIFT

C:\Users\Walter\Downloads\AVSMeter265>"AVSMeter.exe" -avsinfo

AVSMeter 2.6.5 (x86) - Copyright (c) 2012-2017, Groucho2004

VersionString: AviSynth+ 0.1 (r2508, MT, i386)
VersionNumber: 2.60
File / Product version: 0.1.0.0 / 0.1.0.0
Interface Version: 6
Multi-threading support: Yes
Avisynth.dll location: C:\WINDOWS\SysWOW64\avisynth.dll
Avisynth.dll time stamp: 2017-06-29, 09:00:22 (UTC)
PluginDir2_5 (HKLM, x86): C:\Users\Walter\Downloads\AvisynthUniversalInstaller_2017-09-02\AvisynthRepository\AVSPLUS_x86\plugins
PluginDir+ (HKLM, x86): C:\Users\Walter\Downloads\AvisynthUniversalInstaller_2017-09-02\AvisynthRepository\AVSPLUS_x86\plugins


[CPP 2.6 / 32 Bit Plugins]
C:\Users\Walter\Downloads\AvisynthUniversalInstaller_2017-09-02\AvisynthRepository\AVSPLUS_x86\plugins\ConvertStacked.dll
C:\Users\Walter\Downloads\AvisynthUniversalInstaller_2017-09-02\AvisynthRepository\AVSPLUS_x86\plugins\DirectShowSource.dll
C:\Users\Walter\Downloads\AvisynthUniversalInstaller_2017-09-02\AvisynthRepository\AVSPLUS_x86\plugins\ImageSeq.dll
C:\Users\Walter\Downloads\AvisynthUniversalInstaller_2017-09-02\AvisynthRepository\AVSPLUS_x86\plugins\Shibatch.dll
C:\Users\Walter\Downloads\AvisynthUniversalInstaller_2017-09-02\AvisynthRepository\AVSPLUS_x86\plugins\TimeStretch.dll
C:\Users\Walter\Downloads\AvisynthUniversalInstaller_2017-09-02\AvisynthRepository\AVSPLUS_x86\plugins\VDubFilter.dll

C:\Users\Walter\Downloads\AVSMeter265>SHIFT

Above violation occurs on a script of 1400 lines. The script displays well in AvsPmod which gives Video Information correctly (CS = RGB24)

Problem is not important for me.

[Groucho2004]

Originally Posted by george84

Above violation occurs on a script of 1400 lines. The script displays well in AvsPmod which gives Video Information correctly (CS = RGB24)

What happens when you open/run the script in VirtualDub?

[george84]

Checked with 2 different versions of Vdub. Both crash in shibach.dll.

See attachments

[Groucho2004]

Originally Posted by george84

Checked with 2 different versions of Vdub. Both crash in shibach.dll.

So, it's not just AVSMeter. Can you post the full script and possibly a short clip so we can reproduce this?

[george84]

Will take some time.

[george84]

The crash doesn't occur when I remove following code from script.

SMILrootlayout = Overlay(SMILrootlayout, SMILregion1, x = SMILregion1_left, y = SMILregion1_top, pc_range = false)

left and top are 0.

SMILregion1 is a BlankClip of length=0.

[Groucho2004]

Originally Posted by george84

The crash doesn't occur when I remove following code from script.

A single line from your script doesn't help tracking down the problem. Post it in the AVS+ thread since it obviously isn't a problem with AVSMeter.

[george84]

Originally Posted by Groucho2004

A single line from your script doesn't help tracking down the problem. Post it in the AVS+ thread since it obviously isn't a problem with AVSMeter.

As I said in the beginning everything works fine in AVS+. Only AVSMeter and VDub Crash. AVSPmod does also good preview.
I just wanted to help you track the crash in AVSMeter.

As I also said it is not all important for me. So let it die.