AVSMeter 3.0.9.0

[StvG]

2.8.2/2.8.1 - were fine.

Now I have c:\windows\system32\avisynth.dll for x86_64 (avsmeter64) and I can test x86 (avsmeter) too without changing the dll path.

With c:\windows\syswow64\avisynth.dll only x86 works, for x86_64 (avsmeter64) -

AVSMeter (x64) cannot load a 32 Bit avisynth.dll.

[Groucho2004]

I think I fixed it. Taurus, StvG, please try this build.
Edit: New release

[StvG]

It's fine here.

Thanks for your tools.

[Groucho2004]

v2.8.4

• Regression from v2.8.3: Revert to "MapAndLoad" WinAPI function
• Added switch "-v". In combination with "avsinfo", this switch adds a list of internal/external functions and DLL dependencies to the log file.

Taurus, StvG, please try this release and let me know if it fixes both issues ("cannot load avisynth.dll" and AVSMeter quitting after pre-scan).
TIA.

[Taurus]

Yes, this is also on Win7 64bit.
Just tested:
Version 2.8.2 is doing fine.
Btw.: The dropbox link you gave me throws an 404 Error! (Can't find the page).

[Taurus]

Version 2.8.4 is fine now!
Thank you!

[Groucho2004]

v2.8.5

• Fixed a long standing exception handling bug

[FranceBB]

Thank you for the new version. ^_^

[Groucho2004]

v2.8.6

• Minor fixes/cosmetics
• Documentation updates/corrections

[tormento]

I have some troubles running AVSMeter64 with -gpu switch.

I have GPU-Z running in the background but I get 0% usage:

d:AVSMeter64.exe sacrificio_KNLMeansCL_pf6.avs -gpu

AVSMeter 2.8.6 (x64) - Copyright (c) 2012-2018, Groucho2004
AviSynth+ 0.1 (r2728, MT, x86_64) (0.1.0.0)

Number of frames:                 1750
Length (hh:mm:ss.ms):     00:01:12.990
Frame width:                      1920
Frame height:                     1032
Framerate:                      23.976 (24000/1001)
Colorspace:                       YV12

Frames processed:               1750 (0 - 1749)
FPS (min | max | average):      1.306 | 714286 | 14.06
Process memory usage (max):     447 MiB
Thread count:                   72
CPU usage (average):            50.8%

GPU usage (average):            0%
GPU memory usage (Dedicated):   0 MiB

Time (elapsed):                 00:02:04.483

Windows 10_x64, latest NVIDIA drivers on GTX 760

[Groucho2004]

Originally Posted by tormento

I have some troubles running AVSMeter64 with -gpu switch.

I have GPU-Z running in the background but I get 0% usage

Does GPU-Z itself show correct values?

[tormento]

Originally Posted by Groucho2004

Does GPU-Z itself show correct values?

Shame on me.

GPU-Z was set to integrated Intel since a previous test.

[Groucho2004]

v2.8.7

• Error handling improvements
• Cosmetics
• Changed some error messages

[Groucho2004]

v2.8.8

• Timer tweaks (less overhead)
• Re-phrased some error messages
• Refactoring

[FranceBB]

Thank you. ^_^

[Groucho2004]

v2.8.9

• Updated documentation
• Updated dates (2018 -> 2019)

[StvG]

Is that error "Script runtime is too short for meaningful measurements" expected? The script is:

BlankClip(length=20000,pixel_type="yuv420p10")

[videoh]

Try a higher number of frames:

BlankClip(...,length=10000) # for example

Probably the default of 240 is too small.

[StvG]

But I have "length=20000". Even with one/two "0" more, I have the same error. Also with width=1920*2,height=1080*2, no changes.

[Groucho2004]

Originally Posted by StvG

But I have "length=20000". Even with one/two "0" more, I have the same error. Also with width=1920*2,height=1080*2, no changes.

With my i5 2500K CPU I get ~4,500,000 fps with that script. 20,000 frames @ 4,500,000 fps is about 4.4 ms. Minimum runtime in AVSMeter is 500 ms. Try more zeros (but not too many, max value for length is 2^31 - 1 or 2,147,483,647).