AVSMeter 3.0.9.0

[StainlessS]

Dont know if you want to investigate this,
Access Violation in AvsMeter v2.7, with only LoadPluginEx2.dll in plugins (AvsMeter -avsInfo).

2nd linked dll here:- http://avisynth.nl/index.php/LoadOldPlugins

dll is UPX'ed, un-Upx'ed dll same result.

Maybe just a bad dll (about 30kb when UPX'ed, about 90kb de-Upx'ed, LoadPluginEx.dll's from 2003 and 2008 both about 60kb).

EDIT: On second thoughts, you might want to ignore this, even caused Access violation in VDub when dll in plugins folder
(no other plugs, and no script, just startup VDFilterMod and close again, crash).


Perhaps that dll should be removed from Wiki, unless anybody can get it to do something useful, without crashing.

EDIT:
Despite this line on wiki

use as a last resort! I don't know exactly which package it came out of, but it works; I believe it requires v7 of the MS C runtime library (msvcr70.dll)

It dont seem to work and does not require any runtime.


EDIT: That was UPX'ed version in dependency walker, so UPX.exe stuff dont need runtimes either, I presume. [EDIT: No, shows uncompressed size]
EDIT: Same with Un-UPX'ed, no deps.

EDIT: Link time stamp in dep walker says 21 Jan 2003, which is about 10 months before the earliest 2003 LoadPluginEx.dll that I've found. (3 Nov 2003)

EDIT: Strangely, with script
# No Crash in MPC-HC or VDubFilterMod

LoadPlugin("D:\LoadPluginEx2.dll")
Return Colorbars

# No Crash in MPC-HC or VDubFilterMod

LoadPlugin("D:\LoadPluginEx2.dll")
LoadPlugin("D:\Dustv5.dll")   # EDIT: Avisynth v2.0 CPP plugin.
Colorbars
Return PixieDust(limit=5,output="RGB32")

EDIT: I used to like PixieDust. EDIT: No I didn't, it was the Peach or PeachSmoother thing I liked, with all of that there orange smoke stuff.

[Groucho2004]

Originally Posted by Groucho2004

v2.7.1

• When using the switch "-avsinfo" in combination with "-log", a "Save as..." dialog will open enabling the user to save the log file
• Minor fixes and refactoring
• Cosmetics

Some users seemed to have trouble finding the log file created with the switches "-avsinfo -log", mainly when not operating directly from the console. The "Save as..." prompt should cure this.

I'm thinking about using "Save as..." dialogs for the other log/csv file options. Any objections?

[Sparktank]

I wouldn't be apposed to that.

Sometimes I just create generic names for scripts to test out new things and dont name them adequately.

[Selur]

@Groucho2004:
Calling:

AVSMeter.exe -range=0,200 -timelimit=60 "H:\Temp\encodingTempSynthSkript_05_34_45_4010.avs"

on

SetMemoryMax(1536)
SetMTMode(5,16) # changing MT mode
LoadCPlugin("G:\Hybrid\32bit\AVISYN~1\ffms2.dll")
LoadPlugin("G:\Hybrid\32bit\AVISYN~1\flash3kyuu_deband.dll")
# loading source: C:\Users\Selur\Desktop\Dragonball.Z.-.001.-.1080p.BluRay.x264.DHD (1)-001.mkv
#  input luminance scale tv
FFVideoSource("C:\Users\Selur\Desktop\DRAGON~1.MKV",cachefile="H:\Temp\05_34_45_4010.ffindex")
# current resolution: 1920x1080
# debanding
SetMTMode(2) # changing MT mode
f3kdb(dither_algo=3,grainY=1,grainC=1,dynamic_grain=true,Y=64,Cb=40,Cr=40)
# scaling
Spline36Resize(1280,720)
distributor()
return last

AVSMeter get's stuck at:

AVSMeter 2.7.1 (x86) - Copyright (c) 2012-2017, Groucho2004
AviSynth 2.60, build:Feb 20 2015 [03:16:45] (2.6.0.5)
Pre-scanning script (F117 / T4.88)

AVSMeter.exe -avsinfo

properly returns:

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

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
Interface Version:          6
Multi-threading support:    Yes
Avisynth.dll location:      G:\Hybrid\32bit\avisynth.dll
Avisynth.dll time stamp:    2015-02-20, 00:18:42 (UTC)



[Plugin warnings]
_________________________________________________________________________________________________________________________________________________________________________________________________________________

No plugin directory references found in the registry.
Plugin auto-loading disabled.
_________________________________________________________________________________________________________________________________________________________________________________________________________________

AVSMeter.exe -info "H:\Temp\encodingTempSynthSkript_05_34_45_4010.avs"

properly returns:

AVSMeter 2.7.1 (x86) - Copyright (c) 2012-2017, Groucho2004
AviSynth 2.60, build:Feb 20 2015 [03:16:45] (2.6.0.5)

Number of frames:                 7289
Length (hh:mm:ss.ms):     00:05:04.012
Frame width:                      1280
Frame height:                      720
Framerate:                      23.976 (24000/1001)
Colorspace:                       i420
Active MT Mode:                      2

AVSMeter.exe "H:\Temp\encodingTempSynthSkript_05_34_45_4010.avs"

also get's stuck:

AVSMeter 2.7.1 (x86) - Copyright (c) 2012-2017, Groucho2004
AviSynth 2.60, build:Feb 20 2015 [03:16:45] (2.6.0.5)
Pre-scanning script (F123 / T4.83)

Cu Selur

[Groucho2004]

Selur,

You're running out of memory. If you remove the "Distributor()" call it will work. "Distributor()" is called in AVSMeter so you're calling it twice which increases the number of threads from ~50 to ~250 (checked with task manager) and therefore increases memory usage significantly.
Also, check the manual ("InvokeDistributor" ini setting).

However, it's odd that Avisynth doesn't throw an out of memory error. I'll look into it.

[Selur]

You are right, without the 'distributor()' call it does not freeze.
Manual site is blocked by MalwareBytes.

[Groucho2004]

Originally Posted by Selur

Manual site is blocked by MalwareBytes.

First time I hear that. The manual is also included in the download.

[Groucho2004]

v2.7.2

• Added new switch "-c". This allows in combination with "-avsinfo" to specify a custom plugin directory.
• "Save as..." dialog for all log/csv files when using "-log" and/or "-csv" switches
• Updated AVS+ headers
• Cosmetics

[Groucho2004]

v2.7.3

• Fixed a bug in the plugin enumeration

[Yanak]

Hello Groucho2004,

updated to the last version and now i see that the "LogFileDateTimeSuffix" & "LogDirectory" options seems gone and we have the save as dialog when using logs like explained 2 posts above.

I was always using a small batch to loop the tests 3 or 5 times to get more accurate results, but now with this change i can't do this anymore, after the first run i need to save manually the file and can't do like before, launching my batch executing the tests looped 3 times on various source files, just fire and forget about it, especially while it could run for a few hours.

Beside going back to 2.7.1 version is there a way to get this working like before, getting log files generated automatically without user interaction needed to save them please ?


btw what is the option "AutoCompleteExtension=0" ? Unless i am missing it there is nothing about it the help file


Also is there a way add an option directly in the program to set the cores affinity to run the program on ?
Most of the times to get more accurate results when running single threaded tests ( or multi threaded ones but using only 4 threads on my 8 available ) i use this command to exclude the core 0 & 1 of the CPU ( those can be used by some other stuff running in the background or by windows and unless it's a tests needing to run on all threads it's better to not run anything on those for accurate results in most benchmarks perfs tests ), this is the cmd line i use :

start /affinity 0xfc avsmeter64 test.avs

0xfc excludes core 0 & 1, 0xfe excludes only core 0 etc, to get the hex value for the cores needed for a 8 cores/ threads CPU you get this :

7 6 5 4 3 2 1 0 < this is the cores , starting by last core and ending by core 0

Then i use a binary scheme , on/off for the cores , example i want all ON beside core 0 & 1, so in binary i end up with this :

1 1 1 1 1 1 0 0 < ON/OFF Binary
gives 11111100 , converted from binary to hex it gives the 0xfc hex parameter

What I'd like to see is an option in the AVSMeter.ini where i could set the Hex value i need to set the affinity of the cores directly there, like "CoreAffinity=0xfc" or "CoreAffinity=0" to not use it / disable it.

Directly inside the program instead of calling it with the command line listed above, not sure if possible or hard to implement or even if you will find this interesting, but who knows, maybe it is easy and possible.

And maybe, if there is a way to get the log created automatically like before, another useful option will be to have the program itself managing how many runs / loops we want to do for a test, again a parameter in the ini file like "LoopTest=3" or "=0" to disable it.

Maybe i'm the only one interested by those possible options and you will find this silly but i take the risk to ask

Thanks a lot

[Groucho2004]

Originally Posted by Yanak

updated to the last version and now i see that the "LogFileDateTimeSuffix" & "LogDirectory" options seems gone and we have the save as dialog when using logs like explained 2 posts above.

I was always using a small batch to loop the tests 3 or 5 times to get more accurate results, but now with this change i can't do this anymore, after the first run i need to save manually the file and can't do like before, launching my batch executing the tests looped 3 times on various source files, just fire and forget about it, especially while it could run for a few hours.

Beside going back to 2.7.1 version is there a way to get this working like before, getting log files generated automatically without user interaction needed to save them please ?

I'll add an ini option to toggle the old behaviour.

Originally Posted by Yanak

btw what is the option "AutoCompleteExtension=0" ? Unless i am missing it there is nothing about it the help file

You can specify an .avs file without extension, i.e. "avsmeter script" instead of "avsmeter script.avs".

Originally Posted by Yanak

Also is there a way add an option directly in the program to set the cores affinity to run the program on ?

I'll think about it but this would be at the bottom of the priority list.

[Yanak]

I understand now the auto complete extension option, should have guessed it, looks logical now that i know

Thank you for bringing the old behavior back with an option in the ini, as for the affinity ( or even a parameter to run loops directly in avsmeter ) this isn't a problem, as long as i can launch my batch file running loops on various inputs and don't have to wait in front of the pc at the end of each run to save the logs it's already nice, one day maybe but not a priority at all

Thank you very much.

[Groucho2004]

v2.7.4

• Added ini option "LogUseFileSaveDialog". See manual for details.
• Brought back ini options "LogDirectory" and "LogFileDateTimeSuffix". See manual for details.

[Yanak]

Thank you very much for bringing those options back and giving the choice to the end user to use it or not.

I made a quick run and the "LogFileDateTimeSuffix=1" option seems to have an issue

avs file : test.avs
LogFileDateTimeSuffix=1 makes this : test [].log

The date & time remains blank apparently

Thank you.

edit "LogUseFileSaveDialog" is set to 0 in my .ini

DisplayFPS=1
DisplayTPF=0
PauseBeforeExit=0
CreateLog=1
CreateCSV=0
LogDirectory=H:
LogFileDateTimeSuffix=1
MonitorGPULoad=0
TimeLimit=-1
AVSDLL=
FrameRange=0,-1
AllowOnlyOneInstance=1
ProcessPriority=2
InvokeDistributor=1
ConUseSTDOUT=0
UseColor=1
DisplayEfficiencyIndex=1
LogEstimatedTime=0
AutoCompleteExtension=0
LogUseFileSaveDialog=0

[Groucho2004]

v2.7.5

• Fixed a couple of bugs (thanks Yanak for reporting the "LogFileDateTimeSuffix" problem)
• Re-organised the ini settings in logical groups

[Yanak]

Seems to work correctly again after a few tests,

Thanks a lot for the quick fix Groucho2004

[`Orum]

First of all I want to thank you for this. I've been looking for something to replace timecodec for a long time.

Second, I was wondering if you would indulge a feature request I have. In my case, I'm interested in seeing only the time it takes between when a script is opened and when the first frame (as in, frame 0) is actually rendered. Not only does -range=0,0 not report anything but the pre-scanning seems to make this entirely impossible in my case (as the second time the script is opened, the cache will have been created, and I'm not interested in seeing performance post-cache creation). Any chance I could see this data in a future release?

p.s. - Also, the program still lists 2017 as the last year of the copyright.

[DJATOM]

I think you can debug such metrics internally. DebugView is your friend there

[`Orum]

Originally Posted by DJATOM

I think you can debug such metrics internally. DebugView is your friend there

Of course one can do that, but then I need to modify the source of every filter I want to time. The idea was just to make things easy.

Right now I'm deliberately introducing an error immediately after the filter I want to time (in order to not time the execution of the whole output), opening that in avs2yuv, and then timing the execution time using a batch script. In short, it's a bit awkward and would be nice to just be able to do avsmeter [-someflag] <script>.

[Groucho2004]

Originally Posted by `Orum

In short, it's a bit awkward and would be nice to just be able to do avsmeter [-someflag] <script>.

Try this older version of AVSMeter:
https://www.videohelp.com/download/AVSMeter198.7z

Use this command line:
"AVSMeter script.avs -f -range=0,0"