View Single Post
Old 15th September 2018, 21:59   #16  |  Link
zorr
Registered User
 
Join Date: Mar 2018
Posts: 447
Quote:
Originally Posted by Groucho2004 View Post
There are much easier ways to run a script.
For example: "avsmeter script.avs -o".
D'oh! To my defense, I did try a few other options for running avs scripts (like AVS2AVI) but found that they weren't as reliable as VirtualDub. Back then I wanted to save the video too so I didn't investigate AVSMeter.

Luckily (or rather, by design ) it's very easy to use AVSMeter instead of VirtualDub, you only need to change the runavs.bat to something like this:

Code:
title %2
"D:\optimizer\bin\tools\AvsMeter\AvsMeter" %1 -o
exit
However, I ran into some problems when I tried it. Running the denoise.avs gave this error:

Code:
D:\optimizer\bin\tools\AvsMeter>avsmeter ../../../test/flower/denoise.avs -o

AVSMeter 2.8.5 (x86) - Copyright (c) 2012-2018, Groucho2004
AviSynth 2.60, build:Mar 31 2015 [16:38:54] (2.6.0.6)

Number of frames:                    5
Length (hh:mm:ss.ms):     00:00:00.200
Frame width:                       352
Frame height:                      288
Framerate:                      25.000 (25/1)
Colorspace:                       i420


Exception 0xC0000094 [STATUS_INTEGER_DIVIDE_BY_ZERO]
Module:   D:\optimizer\bin\tools\AvsMeter\AVSMeter.exe
Address:  0x00324CD3
Without the -o there was no exception but this report
Code:
Script runtime is too short for meaningful measurements
and the perFrameResults.txt was not generated.

I was able to make it work by adding more test frames to the script, it worked with TEST_FRAMES = 50.

Another issue is that AVSMeter takes quite a long time (several seconds) displaying "Query Avisynth info..." which then gets replaced with the AviSynth version information. Would it be possible to skip this part and start running the script right away? I didn't find a switch to suppress that.
zorr is offline   Reply With Quote