AVSMeter 3.0.9.0

[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 ?
I'll add an ini option to toggle the old behaviour.

btw what is the option "AutoCompleteExtension=0" ? Unless i am missing it there is nothing about it the help fileYou can specify an .avs file without extension, i.e. "avsmeter script" instead of "avsmeter script.avs".

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 :p

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]

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 (https://stackoverflow.com/a/6209392). In short, it's a bit awkward and would be nice to just be able to do avsmeter [-someflag] <script>.

[Groucho2004]

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"

[wonkey_monkey]

Out of curiosity/ignorance, what is pre-scanning for?

[Groucho2004]

Out of curiosity/ignorance, what is pre-scanning for?The CPU/GPU usage, memory, and other measurements present a small, but with very fast scripts not negligible overhead which can skew the timing accuracy.

The pre-scan determines the speed of the script and calculates an interval at which measurements are taken. For a slow(ish) script (< 50 fps) the measurements are taken after each frame, for a very fast script (> 1000 fps) it's every 10 frames (or 20 or 50, don't remember exactly, have to look at my code). It's a linear function, the faster the script, the larger the interval.

After the pre-scan the script environment is deleted and avisynth.dll unloaded so any caching that happened during the scan won't influence the main timing results.

[StainlessS]

I look forward to the DavidHorman version of AvsMeter, I'm quite sure thet it would be better/more capable than the G2K4 Effort,
when can we have it ?

EDIT: Well at least Better documented (hehe, no chance).

EDIT: (We do still love you, but you make it hard :) )

[Groucho2004]

I look forward to the DavidHoman version of AvsMeter, I'm quite sure thet it would be better/more capable than the G2K4 Effort,
when can we have it ?

EDIT: Well at least Better documented (hehe, no chance).

EDIT: (We do still love you, but you make it hard :) )
Sometimes it's hard to tell whether you're using your special brand of sarcasm or if you're just back from a long session at your local pub. ;)

[wonkey_monkey]

Yeah... I don't get it either.

[StainlessS]

Also, me neither, methinks sombody logged under my accout, or, maybe I was a bit pissed, guess we will never know.

[`Orum]

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

Use this command line:
"AVSMeter script.avs -f -range=0,0"
Unfortunately this still only gives me the time to read the first frame and not the time between opening the script and when the first frame is retrieved. Well, I'm not sure what value it's actually giving me, but it's definitely not the time it takes between opening and first frame delivery.

I suppose I'll just continue using the batch script for now.

[rco133]

Hi.

Sorry if this is a stupid question. But I just want to make sure that I understand the output of AVSMeter correctly.

If I use AVSMeter and it gives me a result of lets say average 400 FPS.

If I encode using the same AVS file using x264, and the FPS is way lower than the AVSMeter result, for example 150 FPS, then I can be pretty sure that the "bottleneck" is the CPU and there is nothing that can be done in the AVS script to speed up the encode.

Or am I misinterpreting the results from AVSMeter?

If I am, maybe someone can tell me what the result can be used for, other than trying out different Things in the AVS file, and see what change it has on the FPS.

rco133

[Groucho2004]

If I encode using the same AVS file using x264, and the FPS is way lower than the AVSMeter result, for example 150 FPS, then I can be pretty sure that the "bottleneck" is the CPU and there is nothing that can be done in the AVS script to speed up the encode.The bottleneck in this case is x264 considering you're looking at a software processing chain with given hardware.

A script that runs with 400 fps (measured with AVSMeter) is pretty rare since many Avisynth users use all kinds of filters that slow down the speed with which Avisynth serves frames to the encoder. Scripts that run with 5-10 fps are not uncommon and are therefore usually the bottleneck in the chain.

AVSMeter helps to optimize such scripts using different filter parameters, multi-threading optimization, etc.

[StainlessS]

If I use AVSMeter and it gives me a result of lets say average 400 FPS.
If I encode using the same AVS file using x264, and the FPS is way lower than the AVSMeter result, for example 150 FPS

Perhaps the encoder takes some CPU too, whadya think ?

[rco133]

The bottleneck in this case is x264 considering you're looking at a software processing chain with given hardware.

A script that runs with 400 fps (measured with AVSMeter) is pretty rare since many Avisynth users use all kinds of filters that slow down the speed with which Avisynth serves frames to the encoder. Scripts that run with 5-10 fps are not uncommon and are therefore usually the bottleneck in the chain.

AVSMeter helps to optimize such scripts using different filter parameters, multi-threading optimization, etc.

Thank you for the explanation. I don't use any "heavy" filters. Just yadif for deinterlace, and sometimes srestore.

rco133

[mkver]

I think AVSMeter 2.7.5 has a bug in detecting 64bit C plugins. The 64bit version of the FFmpegSource C-plugin (https://www.mediafire.com/file/h052qy7xd74v2ll/ffms2_r1293%2B111-avs%2Bvsp.7z) is put into the "Uncategorized DLLs (64 Bit)" category; I looked a bit into the code and found this (lines 664-671 in AvisynthInfo.h):

if (sName.find("avisynth_c_plugin_init@4") != string::npos)
{
s_Msg = "AVSC25";
break;
}

if (sName.find("avisynth_c_plugin_init") != string::npos)
s_Msg = "AVSC20";

So absence of the @4 decoration is treated as proof that it is a C 2.0 plugin. But in a 64bit dll C functions are not decorated (https://msdn.microsoft.com/en-us/library/56h2zst2.aspx):

Format of a C decorated name

The form of decoration for a C function depends on the calling convention used in its declaration, as shown in the following table. This is also the decoration format that is used when C++ code is declared to have extern "C" linkage. The default calling convention is __cdecl. Note that in a 64-bit environment, functions are not decorated.

AVS+ also checks for _avisynth_c_plugin_init@4 (https://github.com/pinterf/AviSynthPlus/blob/MT/avs_core/core/PluginManager.cpp#L941); I don't know why.
I guess the reason that the FFmpegSource C-plugin is classified as Uncategorized (and not C 2.0) is that there is a "avisynth_c_plugin_init" and a "avisynth_c_plugin_init_s" in the dll. Maybe one should put "s_Msg = "UNCATEGORIZED";" in front of the loop, not in the loop.

[Groucho2004]

I think AVSMeter 2.7.5 has a bug in detecting 64bit C plugins.
Nice catch. Will be fixed in the next release.

[Groucho2004]

2.7.6

Fixed a bug in the 64 bit C-plugin enumeration
Memory tweaks

[Groucho2004]

v2.7.7

Added switch to specify a avisynth.dll other than the one automatically loaded
Updated AVS+ headers
Regression from 2.7.6: Some warnings/notes were not displayed
Refactoring


New switch "-avsdll":

The user can specify the avisynth.dll to be used (a file open dialog lets the user select it). Without this switch AVSMeter will attempt to load avisynth.dll through the standard Windows search hierarchy which is the default behaviour.

[amayra]

thank you for keep this project alive but this is supposed to be open source right ?
you don't include source with last version

[ChaosKing]

With AVSMeter.exe -avsinfo it outputs every plugin line twice.

D:\AvisynthRepository\AVSPLUS_x86\plugins\amDCT.dll [2017-03-05]
D:\AvisynthRepository\AVSPLUS_x86\plugins\amDCT.dll [2017-03-05]
D:\AvisynthRepository\AVSPLUS_x86\plugins\AutoCrop.dll [2005-01-03]
D:\AvisynthRepository\AVSPLUS_x86\plugins\AutoCrop.dll [2005-01-03]

[Groucho2004]

With AVSMeter.exe -avsinfo it outputs every plugin line twice.

D:\AvisynthRepository\AVSPLUS_x86\plugins\amDCT.dll [2017-03-05]
D:\AvisynthRepository\AVSPLUS_x86\plugins\amDCT.dll [2017-03-05]
D:\AvisynthRepository\AVSPLUS_x86\plugins\AutoCrop.dll [2005-01-03]
D:\AvisynthRepository\AVSPLUS_x86\plugins\AutoCrop.dll [2005-01-03]
Post a log file, "avsmeter -avsinfo -log".

[StainlessS]

With AVSMeter.exe -avsinfo it outputs every plugin line twice.
Sounds twice as nice, but not for me it dont.

Log file created with: AVSMeter 2.7.7 (x86)

[OS/Hardware info]
Operating system: Windows XP (x86) Service Pack 3.0 (Build 2600)
CPU brand string: Intel(R) Core(TM)2 Quad CPU Q6600 @ 2.40GHz
CPU features: MMX, SSE, SSE2, SSE3, SSSE3

[Avisynth info]
VersionString: AviSynth+ 0.1 (r2693, 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\system32\avisynth.dll
Avisynth.dll time stamp: 2018-05-29, 16:02:16 (UTC)
PluginDir2_5 (HKLM, x86): C:\Program Files\AviSynth+\plugins
PluginDir+ (HKLM, x86): C:\Program Files\AviSynth+\plugins+

[CPP 2.5 Plugins (32 Bit)]
C:\Program Files\AviSynth+\plugins\AddGrain.dll [0.1.0.0]
C:\Program Files\AviSynth+\plugins\AddGrainC.dll [1.7.1.0]
C:\Program Files\AviSynth+\plugins\Antiflicker.dll [2003-03-04]
C:\Program Files\AviSynth+\plugins\ApplyEvery.dll [2005-07-30]
C:\Program Files\AviSynth+\plugins\AutoGain.dll [1.7.5.0]
C:\Program Files\AviSynth+\plugins\autolevels_0_6_20110109.dll [0.6.0.0]
C:\Program Files\AviSynth+\plugins\avstp_26.dll [1.0.1.0]
C:\Program Files\AviSynth+\plugins\cnr2k.dll [2005-03-13]
C:\Program Files\AviSynth+\plugins\ColorMatrix.dll [2.5.0.0]
C:\Program Files\AviSynth+\plugins\convolution3d.dll [2003-04-22]
C:\Program Files\AviSynth+\plugins\DctFilter.dll [0.0.1.4]
C:\Program Files\AviSynth+\plugins\deblock.dll [1.2.0.0]
C:\Program Files\AviSynth+\plugins\Decomb.dll [2013-02-26]
C:\Program Files\AviSynth+\plugins\DeDup.dll [2004-11-07]
C:\Program Files\AviSynth+\plugins\Deen.dll [2005-07-05]
C:\Program Files\AviSynth+\plugins\deflicker.dll [0.4.0.0]
C:\Program Files\AviSynth+\plugins\degrainmedian.dll [0.8.2.0]
C:\Program Files\AviSynth+\plugins\despot.dll [3.6.1.0]
C:\Program Files\AviSynth+\plugins\dither.dll [2015-07-16]
C:\Program Files\AviSynth+\plugins\eDeen.dll [2003-01-19]
C:\Program Files\AviSynth+\plugins\EEDI2.dll [0.9.2.0]
C:\Program Files\AviSynth+\plugins\eedi3.dll [0.9.2.0]
C:\Program Files\AviSynth+\plugins\GamMac.dll [2017-08-22]
C:\Program Files\AviSynth+\plugins\gradfun2db.dll [2006-03-15]
C:\Program Files\AviSynth+\plugins\GRunT.dll [2008-09-27]
C:\Program Files\AviSynth+\plugins\GScript.dll [2009-12-06]
C:\Program Files\AviSynth+\plugins\HistogramAdjust.dll [2005-11-21]
C:\Program Files\AviSynth+\plugins\hqdn3d.dll [2005-01-25]
C:\Program Files\AviSynth+\plugins\LSMASHSource.dll [2015-02-23]
C:\Program Files\AviSynth+\plugins\MinMaxAudio.dll [2007-09-04]
C:\Program Files\AviSynth+\plugins\mpasource.dll [2008-02-20]
C:\Program Files\AviSynth+\plugins\MSharpen.dll [2003-04-08]
C:\Program Files\AviSynth+\plugins\Msmooth.dll [2005-09-18]
C:\Program Files\AviSynth+\plugins\NicAudio.dll [2012-08-27]
C:\Program Files\AviSynth+\plugins\nnedi.dll [1.3.0.0]
C:\Program Files\AviSynth+\plugins\nnedi2.dll [1.6.0.0]
C:\Program Files\AviSynth+\plugins\QTSource.dll [2006-01-09]
C:\Program Files\AviSynth+\plugins\rawsource.dll [2005-10-13]
C:\Program Files\AviSynth+\plugins\RemapFrames.dll [2005-08-26]
C:\Program Files\AviSynth+\plugins\RemoveDirtSSE2.dll [2005-05-05]
C:\Program Files\AviSynth+\plugins\RemoveGrainHDS.dll [2007-11-26]
C:\Program Files\AviSynth+\plugins\SmoothAdjust.dll [2011-06-06]
C:\Program Files\AviSynth+\plugins\SSE2Tools.dll [2005-04-11]
C:\Program Files\AviSynth+\plugins\STMedianFilter.dll [0.1.0.3]
C:\Program Files\AviSynth+\plugins\TCPDeliver.dll [1.0.0.6]
C:\Program Files\AviSynth+\plugins\TDeint.dll [1.1.0.0]
C:\Program Files\AviSynth+\plugins\TemporalCleaner.dll [0.0.0.2]
C:\Program Files\AviSynth+\plugins\TIVTC.dll [1.0.5.0]
C:\Program Files\AviSynth+\plugins\TNLMeans.dll [1.0.3.0]
C:\Program Files\AviSynth+\plugins\TPRIVTC.dll [2004-09-30]
C:\Program Files\AviSynth+\plugins\TTempSmooth.dll [0.9.4.0]
C:\Program Files\AviSynth+\plugins\TweakColor.dll [2004-04-12]
C:\Program Files\AviSynth+\plugins\UnDot.dll [0.0.1.1]
C:\Program Files\AviSynth+\plugins\VagueDenoiser.dll [0.35.1.0]
C:\Program Files\AviSynth+\plugins\VariableBlur.dll [2012-05-24]
C:\Program Files\AviSynth+\plugins\VScope.dll [2004-05-16]
C:\Program Files\AviSynth+\plugins\VSFilter.dll [1.0.1.1]

[CPP 2.6 Plugins (32 Bit)]
C:\Program Files\AviSynth+\plugins+\ConvertStacked.dll [2018-05-29]
C:\Program Files\AviSynth+\plugins+\DirectShowSource.dll [2018-05-29]
C:\Program Files\AviSynth+\plugins+\ImageSeq.dll [2018-05-29]
C:\Program Files\AviSynth+\plugins+\Shibatch.dll [2018-05-29]
C:\Program Files\AviSynth+\plugins+\TimeStretch.dll [2018-05-29]
C:\Program Files\AviSynth+\plugins+\VDubFilter.dll [2018-05-29]
C:\Program Files\AviSynth+\plugins\ApparentFPS26.dll [2015-12-18]
C:\Program Files\AviSynth+\plugins\AutoAdjust_26.dll [2.0.0.0]
C:\Program Files\AviSynth+\plugins\Average_26_0_94.dll [0.94.0.0]
C:\Program Files\AviSynth+\plugins\avss_26.dll [2.0.0.10]
C:\Program Files\AviSynth+\plugins\CallCmd_x86.dll [1.4.0.0]
C:\Program Files\AviSynth+\plugins\ClipClop26.dll [2017-08-29]
C:\Program Files\AviSynth+\plugins\DePan_26_2_13_1_3.dll [2.13.1.3]
C:\Program Files\AviSynth+\plugins\DePanEstimate_26_2_10_0_2.dll [2.10.0.2]
C:\Program Files\AviSynth+\plugins\dfttest_x86_1.9.4.2.dll [1.9.4.2]
C:\Program Files\AviSynth+\plugins\DirectShowSource_26.dll [2.6.0.3]
C:\Program Files\AviSynth+\plugins\fft3dfilter_26_2_4_0_0.dll [2.4.0.0]
C:\Program Files\AviSynth+\plugins\FrameSel_x86.dll [2.20.0.0]
C:\Program Files\AviSynth+\plugins\fturn-26.dll [2018-03-13]
C:\Program Files\AviSynth+\plugins\masktools2_26_2_2_10_0_Infix.dll [2.2.10.0]
C:\Program Files\AviSynth+\plugins\MDec2_x86.dll [1.2.0.0]
C:\Program Files\AviSynth+\plugins\mvtools2_26_2_7_27_0.dll [2.7.27.0]
C:\Program Files\AviSynth+\plugins\nnedi3_26_0_9_4_48.dll [0.9.4.48]
C:\Program Files\AviSynth+\plugins\Prune26.dll [2015-04-01]
C:\Program Files\AviSynth+\plugins\RgTools_26_0_96.dll [0.96.0.0]
C:\Program Files\AviSynth+\plugins\RoboCrop26.dll [2016-08-25]
C:\Program Files\AviSynth+\plugins\RT_Stats26.dll [2017-10-13]
C:\Program Files\AviSynth+\plugins\SangNom2.dll [2013-11-30]
C:\Program Files\AviSynth+\plugins\SoundOut_26.dll [1.1.0.0]
C:\Program Files\AviSynth+\plugins\TCPDeliver_26.dll [1.0.0.7]
C:\Program Files\AviSynth+\plugins\TWriteAVI.dll [2016-09-26]
C:\Program Files\AviSynth+\plugins\WaterMark2_x86.dll [2017-12-05]
C:\Program Files\AviSynth+\plugins\yadifmod2_26_0_0_4_1.dll [2016-07-04]
C:\Program Files\AviSynth+\plugins\Zebra26.dll [2015-03-31]

[Scripts (AVSI)]
C:\Program Files\AviSynth+\plugins+\colors_rgb.avsi [2016-07-05]
C:\Program Files\AviSynth+\plugins\AutoContrast.avsi [2018-06-02]
C:\Program Files\AviSynth+\plugins\AWB_131201.avsi [2015-08-24]
C:\Program Files\AviSynth+\plugins\ChangeFrameRate.avsi [2016-12-31]
C:\Program Files\AviSynth+\plugins\colors_rgb.avsi [2016-07-05]
C:\Program Files\AviSynth+\plugins\dither.avsi [2015-07-16]
C:\Program Files\AviSynth+\plugins\Favc.avsi [2014-10-16]
C:\Program Files\AviSynth+\plugins\InitExternalPlugins.avsi [2018-04-01]
C:\Program Files\AviSynth+\plugins\MCDegrain.avsi [2016-05-09]
C:\Program Files\AviSynth+\plugins\Misc.avsi [2017-10-08]
C:\Program Files\AviSynth+\plugins\QTGMC-3.32.avsi [2011-05-05]
C:\Program Files\AviSynth+\plugins\RoboSplice.avsi [2018-04-29]
C:\Program Files\AviSynth+\plugins\SelectRanges.avsi [2015-03-30]
C:\Program Files\AviSynth+\plugins\SMDegrain_20160623_mod.avsi [2016-12-04]

[Uncategorized files]
C:\Program Files\AviSynth+\plugins+\colors_rgb.txt [2016-07-05]

[Groucho2004]

thank you for keep this project alive but this is supposed to be open source right ?
you don't include source with last versionI guess I messed around with the batch file that creates the distributable package. Please re-download.

[ChaosKing]

It's a cosmetic bug in your latest version. Same with 32bit.


Log file created with: AVSMeter 2.7.7 (x64)

[OS/Hardware info]
Operating system: Windows 10 (x64) (Build 17134)
CPU brand string: AMD Ryzen 7 1700 Eight-Core Processor
CPU features: MMX, SSE, SSE2, SSE3, SSSE3, SSE4.1, SSE4.2, AVX, AVX2, FMA3, SSE4A, MMXEXT, MOVBE, POPCNT, AES, F16C


[Avisynth info]
VersionString: AviSynth+ 0.1 (r2664, MT, x86_64)
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\SYSTEM32\avisynth.dll
Avisynth.dll time stamp: 2018-03-28, 18:59:27 (UTC)
PluginDir2_5 (HKLM, x64): D:\AvisynthRepository\AVSPLUS_x64\plugins
PluginDir+ (HKLM, x64): D:\AvisynthRepository\AVSPLUS_x64\plugins


[CPP 2.5 Plugins (64 Bit)]
D:\AvisynthRepository\AVSPLUS_x64\plugins\avstp.dll [1.0.3.0]
D:\AvisynthRepository\AVSPLUS_x64\plugins\avstp.dll [1.0.3.0]
D:\AvisynthRepository\AVSPLUS_x64\plugins\ColorMatrix.dll [2.5.0.0]
D:\AvisynthRepository\AVSPLUS_x64\plugins\ColorMatrix.dll [2.5.0.0]
D:\AvisynthRepository\AVSPLUS_x64\plugins\dfttest.dll [1.9.4.0]
D:\AvisynthRepository\AVSPLUS_x64\plugins\dfttest.dll [1.9.4.0]
D:\AvisynthRepository\AVSPLUS_x64\plugins\DGDecode.dll [1.5.8.0]
D:\AvisynthRepository\AVSPLUS_x64\plugins\DGDecode.dll [1.5.8.0]
D:\AvisynthRepository\AVSPLUS_x64\plugins\dither.dll [2015-12-30]
D:\AvisynthRepository\AVSPLUS_x64\plugins\dither.dll [2015-12-30]
D:\AvisynthRepository\AVSPLUS_x64\plugins\EEDI2.dll [0.9.2.0]
D:\AvisynthRepository\AVSPLUS_x64\plugins\EEDI2.dll [0.9.2.0]
D:\AvisynthRepository\AVSPLUS_x64\plugins\flash3kyuu_deband.dll [2015-05-02]
D:\AvisynthRepository\AVSPLUS_x64\plugins\flash3kyuu_deband.dll [2015-05-02]
D:\AvisynthRepository\AVSPLUS_x64\plugins\FluxSmooth.dll [2010-11-30]
D:\AvisynthRepository\AVSPLUS_x64\plugins\FluxSmooth.dll [2010-11-30]
D:\AvisynthRepository\AVSPLUS_x64\plugins\gradfun2db.dll [2010-03-29]
D:\AvisynthRepository\AVSPLUS_x64\plugins\gradfun2db.dll [2010-03-29]
D:\AvisynthRepository\AVSPLUS_x64\plugins\HDRSharp-x64.dll [2016-02-14]
D:\AvisynthRepository\AVSPLUS_x64\plugins\HDRSharp-x64.dll [2016-02-14]
D:\AvisynthRepository\AVSPLUS_x64\plugins\hqdn3d.dll [2010-04-08]
D:\AvisynthRepository\AVSPLUS_x64\plugins\hqdn3d.dll [2010-04-08]
D:\AvisynthRepository\AVSPLUS_x64\plugins\Hqdn3dY-x64.dll [2016-06-21]
D:\AvisynthRepository\AVSPLUS_x64\plugins\Hqdn3dY-x64.dll [2016-06-21]
D:\AvisynthRepository\AVSPLUS_x64\plugins\LeakKernelDeint.dll [1.5.4.0]
D:\AvisynthRepository\AVSPLUS_x64\plugins\LeakKernelDeint.dll [1.5.4.0]
D:\AvisynthRepository\AVSPLUS_x64\plugins\LSMASHSource.dll [2017-02-24]
D:\AvisynthRepository\AVSPLUS_x64\plugins\LSMASHSource.dll [2017-02-24]
D:\AvisynthRepository\AVSPLUS_x64\plugins\Medianx64.dll [2018-02-11]
D:\AvisynthRepository\AVSPLUS_x64\plugins\Medianx64.dll [2018-02-11]
D:\AvisynthRepository\AVSPLUS_x64\plugins\MipSmooth.dll [2007-02-10]
D:\AvisynthRepository\AVSPLUS_x64\plugins\MipSmooth.dll [2007-02-10]
D:\AvisynthRepository\AVSPLUS_x64\plugins\MP_Pipeline.dll [2014-04-06]
D:\AvisynthRepository\AVSPLUS_x64\plugins\MP_Pipeline.dll [2014-04-06]
D:\AvisynthRepository\AVSPLUS_x64\plugins\TDeint.dll [1.1.0.0]
D:\AvisynthRepository\AVSPLUS_x64\plugins\TDeint.dll [1.1.0.0]
D:\AvisynthRepository\AVSPLUS_x64\plugins\TMM.dll [1.0.0.0]
D:\AvisynthRepository\AVSPLUS_x64\plugins\TMM.dll [1.0.0.0]
D:\AvisynthRepository\AVSPLUS_x64\plugins\TNLMeans64.dll [1.0.3.0]
D:\AvisynthRepository\AVSPLUS_x64\plugins\TNLMeans64.dll [1.0.3.0]
D:\AvisynthRepository\AVSPLUS_x64\plugins\TTempSmooth.dll [0.9.4.0]
D:\AvisynthRepository\AVSPLUS_x64\plugins\TTempSmooth.dll [0.9.4.0]
D:\AvisynthRepository\AVSPLUS_x64\plugins\VagueDenoiser.dll [0.35.1.0]
D:\AvisynthRepository\AVSPLUS_x64\plugins\VagueDenoiser.dll [0.35.1.0]
D:\AvisynthRepository\AVSPLUS_x64\plugins\VSFilterMod64.dll [1.0.0.0]
D:\AvisynthRepository\AVSPLUS_x64\plugins\VSFilterMod64.dll [1.0.0.0]
D:\AvisynthRepository\AVSPLUS_x64\plugins\warpsharp.dll [2011-06-14]
D:\AvisynthRepository\AVSPLUS_x64\plugins\warpsharp.dll [2011-06-14]

[CPP 2.6 Plugins (64 Bit)]
D:\AvisynthRepository\AVSPLUS_x64\plugins\AutoAdjust.dll [2.6.0.0]
D:\AvisynthRepository\AVSPLUS_x64\plugins\AutoAdjust.dll [2.6.0.0]
D:\AvisynthRepository\AVSPLUS_x64\plugins\Average.dll [0.94.0.0]
D:\AvisynthRepository\AVSPLUS_x64\plugins\Average.dll [0.94.0.0]
D:\AvisynthRepository\AVSPLUS_x64\plugins\AvsFilterNet.dll [2018-01-07]
D:\AvisynthRepository\AVSPLUS_x64\plugins\AvsFilterNet.dll [2018-01-07]
D:\AvisynthRepository\AVSPLUS_x64\plugins\aWarpSharp.dll [2016-06-24]
D:\AvisynthRepository\AVSPLUS_x64\plugins\aWarpSharp.dll [2016-06-24]
D:\AvisynthRepository\AVSPLUS_x64\plugins\aWarpsharpMT.dll [2.0.0.0]
D:\AvisynthRepository\AVSPLUS_x64\plugins\aWarpsharpMT.dll [2.0.0.0]
D:\AvisynthRepository\AVSPLUS_x64\plugins\ConvertStacked.dll [2018-03-28]
D:\AvisynthRepository\AVSPLUS_x64\plugins\ConvertStacked.dll [2018-03-28]
D:\AvisynthRepository\AVSPLUS_x64\plugins\DCTFilter.dll [0.5.0.0]
D:\AvisynthRepository\AVSPLUS_x64\plugins\DCTFilter.dll [0.5.0.0]
D:\AvisynthRepository\AVSPLUS_x64\plugins\Deblock.dll [2013-12-03]
D:\AvisynthRepository\AVSPLUS_x64\plugins\Deblock.dll [2013-12-03]
D:\AvisynthRepository\AVSPLUS_x64\plugins\DePan.dll [2.13.1.3]
D:\AvisynthRepository\AVSPLUS_x64\plugins\DePan.dll [2.13.1.3]
D:\AvisynthRepository\AVSPLUS_x64\plugins\DePanEstimate.dll [2.10.0.2]
D:\AvisynthRepository\AVSPLUS_x64\plugins\DePanEstimate.dll [2.10.0.2]
D:\AvisynthRepository\AVSPLUS_x64\plugins\DirectShowSource.dll [2018-03-28]
D:\AvisynthRepository\AVSPLUS_x64\plugins\DirectShowSource.dll [2018-03-28]
D:\AvisynthRepository\AVSPLUS_x64\plugins\eedi3.dll [0.9.2.3]
D:\AvisynthRepository\AVSPLUS_x64\plugins\eedi3.dll [0.9.2.3]
D:\AvisynthRepository\AVSPLUS_x64\plugins\ffms2.dll [2016-12-29]
D:\AvisynthRepository\AVSPLUS_x64\plugins\ffms2.dll [2016-12-29]
D:\AvisynthRepository\AVSPLUS_x64\plugins\fft3dfilter.dll [2.4.0.0]
D:\AvisynthRepository\AVSPLUS_x64\plugins\fft3dfilter.dll [2.4.0.0]
D:\AvisynthRepository\AVSPLUS_x64\plugins\grunt-x64.dll [2016-05-17]
D:\AvisynthRepository\AVSPLUS_x64\plugins\grunt-x64.dll [2016-05-17]
D:\AvisynthRepository\AVSPLUS_x64\plugins\ImageSeq.dll [2018-03-28]
D:\AvisynthRepository\AVSPLUS_x64\plugins\ImageSeq.dll [2018-03-28]
D:\AvisynthRepository\AVSPLUS_x64\plugins\KNLMeansCL.dll [2018-01-29]
D:\AvisynthRepository\AVSPLUS_x64\plugins\KNLMeansCL.dll [2018-01-29]
D:\AvisynthRepository\AVSPLUS_x64\plugins\masktools2.dll [2.2.13.0]
D:\AvisynthRepository\AVSPLUS_x64\plugins\masktools2.dll [2.2.13.0]
D:\AvisynthRepository\AVSPLUS_x64\plugins\MedianBlur2.dll [2014-02-10]
D:\AvisynthRepository\AVSPLUS_x64\plugins\MedianBlur2.dll [2014-02-10]
D:\AvisynthRepository\AVSPLUS_x64\plugins\modPlus.dll [2017-10-17]
D:\AvisynthRepository\AVSPLUS_x64\plugins\modPlus.dll [2017-10-17]
D:\AvisynthRepository\AVSPLUS_x64\plugins\msharpen.dll [2013-11-30]
D:\AvisynthRepository\AVSPLUS_x64\plugins\msharpen.dll [2013-11-30]
D:\AvisynthRepository\AVSPLUS_x64\plugins\mvtools2.dll [2.7.31.0]
D:\AvisynthRepository\AVSPLUS_x64\plugins\mvtools2.dll [2.7.31.0]
D:\AvisynthRepository\AVSPLUS_x64\plugins\nnedi3.dll [0.9.4.49]
D:\AvisynthRepository\AVSPLUS_x64\plugins\nnedi3.dll [0.9.4.49]
D:\AvisynthRepository\AVSPLUS_x64\plugins\Plugins_JPSDR.dll [2.0.5.0]
D:\AvisynthRepository\AVSPLUS_x64\plugins\Plugins_JPSDR.dll [2.0.5.0]
D:\AvisynthRepository\AVSPLUS_x64\plugins\ReduceFlicker.dll [2016-05-05]
D:\AvisynthRepository\AVSPLUS_x64\plugins\ReduceFlicker.dll [2016-05-05]
D:\AvisynthRepository\AVSPLUS_x64\plugins\ResampleMT.dll [1.5.3.0]
D:\AvisynthRepository\AVSPLUS_x64\plugins\ResampleMT.dll [1.5.3.0]
D:\AvisynthRepository\AVSPLUS_x64\plugins\RgTools.dll [0.96.0.0]
D:\AvisynthRepository\AVSPLUS_x64\plugins\RgTools.dll [0.96.0.0]
D:\AvisynthRepository\AVSPLUS_x64\plugins\RT_Stats_x64.dll [2017-09-10]
D:\AvisynthRepository\AVSPLUS_x64\plugins\RT_Stats_x64.dll [2017-09-10]
D:\AvisynthRepository\AVSPLUS_x64\plugins\Shibatch.dll [2018-03-28]
D:\AvisynthRepository\AVSPLUS_x64\plugins\Shibatch.dll [2018-03-28]
D:\AvisynthRepository\AVSPLUS_x64\plugins\SmoothAdjust.dll [3.2.0.0]
D:\AvisynthRepository\AVSPLUS_x64\plugins\SmoothAdjust.dll [3.2.0.0]
D:\AvisynthRepository\AVSPLUS_x64\plugins\TCannyMod.dll [2016-07-05]
D:\AvisynthRepository\AVSPLUS_x64\plugins\TCannyMod.dll [2016-07-05]
D:\AvisynthRepository\AVSPLUS_x64\plugins\tcolormask.dll [2013-11-30]
D:\AvisynthRepository\AVSPLUS_x64\plugins\tcolormask.dll [2013-11-30]
D:\AvisynthRepository\AVSPLUS_x64\plugins\TCPDeliver.dll [0.2.0.0]
D:\AvisynthRepository\AVSPLUS_x64\plugins\TCPDeliver.dll [0.2.0.0]
D:\AvisynthRepository\AVSPLUS_x64\plugins\TimeStretch.dll [2018-03-28]
D:\AvisynthRepository\AVSPLUS_x64\plugins\TimeStretch.dll [2018-03-28]
D:\AvisynthRepository\AVSPLUS_x64\plugins\TIVTC.dll [1.0.11.0]
D:\AvisynthRepository\AVSPLUS_x64\plugins\TIVTC.dll [1.0.11.0]
D:\AvisynthRepository\AVSPLUS_x64\plugins\tmaskcleaner.dll [2013-12-24]
D:\AvisynthRepository\AVSPLUS_x64\plugins\tmaskcleaner.dll [2013-12-24]
D:\AvisynthRepository\AVSPLUS_x64\plugins\TMM2.dll [2016-07-05]
D:\AvisynthRepository\AVSPLUS_x64\plugins\TMM2.dll [2016-07-05]
D:\AvisynthRepository\AVSPLUS_x64\plugins\TUnsharp64.dll [0.9.3.0]
D:\AvisynthRepository\AVSPLUS_x64\plugins\TUnsharp64.dll [0.9.3.0]
D:\AvisynthRepository\AVSPLUS_x64\plugins\VapourSource_x64.dll [2016-07-05]
D:\AvisynthRepository\AVSPLUS_x64\plugins\VapourSource_x64.dll [2016-07-05]
D:\AvisynthRepository\AVSPLUS_x64\plugins\VDubFilter.dll [2018-03-28]
D:\AvisynthRepository\AVSPLUS_x64\plugins\VDubFilter.dll [2018-03-28]
D:\AvisynthRepository\AVSPLUS_x64\plugins\vinverse.dll [2013-11-30]
D:\AvisynthRepository\AVSPLUS_x64\plugins\vinverse.dll [2013-11-30]
D:\AvisynthRepository\AVSPLUS_x64\plugins\VSFilter.dll [3.1.0.800]
D:\AvisynthRepository\AVSPLUS_x64\plugins\VSFilter.dll [3.1.0.800]
D:\AvisynthRepository\AVSPLUS_x64\plugins\yadifmod2.dll [2016-07-04]
D:\AvisynthRepository\AVSPLUS_x64\plugins\yadifmod2.dll [2016-07-04]

[Uncategorized DLLs (64 Bit)]
D:\AvisynthRepository\AVSPLUS_x64\plugins\avcodec-57.dll [57.81.100.0]
D:\AvisynthRepository\AVSPLUS_x64\plugins\avcodec-57.dll [57.81.100.0]
D:\AvisynthRepository\AVSPLUS_x64\plugins\avformat-57.dll [57.66.102.0]
D:\AvisynthRepository\AVSPLUS_x64\plugins\avformat-57.dll [57.66.102.0]
D:\AvisynthRepository\AVSPLUS_x64\plugins\avresample-3.dll [3.2.0.0]
D:\AvisynthRepository\AVSPLUS_x64\plugins\avresample-3.dll [3.2.0.0]
D:\AvisynthRepository\AVSPLUS_x64\plugins\avutil-55.dll [55.47.100.0]
D:\AvisynthRepository\AVSPLUS_x64\plugins\avutil-55.dll [55.47.100.0]
D:\AvisynthRepository\AVSPLUS_x64\plugins\libfftw3f-3.dll [2016-07-30]
D:\AvisynthRepository\AVSPLUS_x64\plugins\libfftw3f-3.dll [2016-07-30]
D:\AvisynthRepository\AVSPLUS_x64\plugins\msvcp110.dll [11.0.51106.1]
D:\AvisynthRepository\AVSPLUS_x64\plugins\msvcp110.dll [11.0.51106.1]
D:\AvisynthRepository\AVSPLUS_x64\plugins\msvcr110.dll [11.0.51106.1]
D:\AvisynthRepository\AVSPLUS_x64\plugins\msvcr110.dll [11.0.51106.1]
D:\AvisynthRepository\AVSPLUS_x64\plugins\swscale-4.dll [4.3.101.0]
D:\AvisynthRepository\AVSPLUS_x64\plugins\swscale-4.dll [4.3.101.0]
D:\AvisynthRepository\AVSPLUS_x64\plugins\vcomp120.dll [12.0.21005.1]
D:\AvisynthRepository\AVSPLUS_x64\plugins\vcomp120.dll [12.0.21005.1]
D:\AvisynthRepository\AVSPLUS_x64\plugins\VSScript.dll [2017-01-21]
D:\AvisynthRepository\AVSPLUS_x64\plugins\VSScript.dll [2017-01-21]
D:\AvisynthRepository\AVSPLUS_x64\plugins\XySubFilter.dll [3.1.0.800]
D:\AvisynthRepository\AVSPLUS_x64\plugins\XySubFilter.dll [3.1.0.800]

[Uncategorized files]
D:\AvisynthRepository\AVSPLUS_x64\plugins\MP_Pipeline.dll.slave.exe [2014-04-06]
D:\AvisynthRepository\AVSPLUS_x64\plugins\MP_Pipeline.dll.slave.exe [2014-04-06]
D:\AvisynthRepository\AVSPLUS_x64\plugins\MP_Pipeline.dll.win32 [2014-04-06]
D:\AvisynthRepository\AVSPLUS_x64\plugins\MP_Pipeline.dll.win32 [2014-04-06]
D:\AvisynthRepository\AVSPLUS_x64\plugins\MP_Pipeline.dll.win32.slave.exe [2014-04-06]
D:\AvisynthRepository\AVSPLUS_x64\plugins\MP_Pipeline.dll.win32.slave.exe [2014-04-06]
D:\AvisynthRepository\AVSPLUS_x64\plugins\MP_Pipeline_readme.avs [2014-04-06]
D:\AvisynthRepository\AVSPLUS_x64\plugins\MP_Pipeline_readme.avs [2014-04-06]



[Plugin errors]
______________________________________________________________________________________________________________________

Error loading "D:\AvisynthRepository\AVSPLUS_x64\plugins\AutoOverlay_netautoload.dll"
Cannot load 32 bit DLL with 64 bit Avisynth
______________________________________________________________________________________________________________________

Error loading "D:\AvisynthRepository\AVSPLUS_x64\plugins\AutoOverlay_netautoload.dll"
Cannot load 32 bit DLL with 64 bit Avisynth
______________________________________________________________________________________________________________________



[Internal (core) functions]
AVIFileSource
AVISource
AddAlphaPlane
AddAutoloadDir
AddBorders
AlignedSplice
Amplify
AmplifydB
Animate
Apply
ApplyRange
Assert
AssumeBFF
AssumeFPS
AssumeFieldBased
AssumeFrameBased
AssumeSampleRate
AssumeScaledFPS
AssumeTFF
AudioDub
AudioDubEx
AudioTrim
AutoloadPlugins
AverageB
AverageChromaU
AverageChromaV
........

[Groucho2004]

It's a cosmetic bug in your latest version. Same with 32bit.
It's not just cosmetic. Does it happen with the previous version?

[StainlessS]

PluginDir2_5 (HKLM, x64): D:\AvisynthRepository\AVSPLUS_x64\plugins
PluginDir+ (HKLM, x64): D:\AvisynthRepository\AVSPLUS_x64\plugins


Mine

PluginDir2_5 (HKLM, x86): C:\Program Files\AviSynth+\plugins
PluginDir+ (HKLM, x86): C:\Program Files\AviSynth+\plugins+


ChaosKing, perhaps because both set to same directory.

[Groucho2004]

Mine

PluginDir2_5 (HKLM, x86): C:\Program Files\AviSynth+\plugins
PluginDir+ (HKLM, x86): C:\Program Files\AviSynth+\plugins+


ChaosKing, perhaps because both set to same directory.
Dups like this should be suppressed. That was a bug in a previous version which I thought I fixed.

[Groucho2004]

It's a cosmetic bug in your latest version. Same with 32bit.
Found the problem, stupid regression. Will make a new build shortly.

[Groucho2004]

Found the problem, stupid regression. Will make a new build shortly.
Please try this build.
Link to temporary build removed (new release available).

[ChaosKing]

Works flawless :)

[Groucho2004]

v2.7.8

Regression from 2.7.7: Suppress duplicates in plugin enumeration

[StainlessS]

G2K4, perhaps you would like to remove link from post #86, is named just "2.7.8.7z" rather than the better named "AVSMeter278.7z"
from your main downloads suppository (I know, a rose by any other name would smell as sweet, maybe).

[Sparktank]

Thanks for the updates!

I just got a new computer (new to me, still old from 2012 era).
I'm in the middle of upgrading so have to stick with the AMD Radeon it has for now.

This will definitely help me figure out what to do with my current set up. :)
All my old logs are gone with the old PC, so I'll have to work off memory.

[Yanak]

Hello Groucho2k4,

I am wondering if it is possible to launch a script in avsmeter and skip the first step, the scan and test running at the very start for the avisynth installation and plugins.

Asking this while trying to optimize some compiled Dll's with PGO, the thing is that each time you run a script it also creates PGO data for the scan test performed at the start, so i'm wondering is there is a switch or a possibility to simply skip this step and only perform the avs benchmarking, if not I'll continue to delete the resulting files and keep only the ones containing the data from the script itself, found nothing in the documentation but I prefer to ask in case it is somehow possible to bypass this step.

Thanks a lot.

[Groucho2004]

@Yanak
Try this (https://www.dropbox.com/s/rkmqm5852m5od57/AVSTimer.7z?dl=1).

[Yanak]

Did not knew this tool thank you,

Gave it a try but i get an error message at the very start:

H:\>avstimer pgo1.avs
AVSTimer v1.00 by Groucho2004
AviSynth+ 0.1 (r2664, MT, i386)
Cannot load a 64 bit DLL in 32 bit Avisynth: 'H:/ffms2/ffms2.dll'.
(pgo1.avs, line 1)

I work on x64 version of avisynth but also have the x86 installed that i use with Mp_Pipeline from times to times when there is no other option, seems like here it goes for the x86 directly ?

Thanks.

[Groucho2004]

It's only 32 bit.

[Groucho2004]

You could try AVSMeter v2.5.1 (x86 and x64) from here (https://www.videohelp.com/software/AVSMeter/old-versions#downloadold). It has a switch "-simple" which omits the initial test. However, there will still be 2 copies of the PGO files.

[Yanak]

Arg, that's what i was fearing,

Well, nevermind then, i'll continue to manually select the data files created and eliminate the ones not needed.

Thank you very much for the try ^^

Edit : will give a try to the 2.5.1 and see how it goes if i load dll's from outside avisynth folder,

Thanks again.

[Yanak]

Just tried the -simple switch, it does the trick for me, either with vs2107 native PGO or intel compiler integrated inside VS2017, only one .pgc or .dyn file created at the very end and no more "Analysing Script" ^^

Thanks a lot, this will make things a lot easier :)

[goorawin]

I Have just built a new Windows 10 System and find that AVSMeter (current version) does not work, see captured screen shot.
It works fine on another Windos10 system that was upgraded from Windows 8.1.
What are the requirements of AVSMeter ?
Thanks in advance

[Groucho2004]

Attached screen shots may take a long time to be approved. Post it on postimage.org or similar.

[goorawin]

Thanks for the tip
I have uploaded it to:
https://s15.postimg.cc/m0uckbs2z/AVSMeter_Error.jpg