Introducing Zopti (ex AvisynthOptimizer)

[Seedmanc]

I don't think I understand how to use the new method. I tried incorporating it into my script and thing went wrong I think, the pareto graphs look weird and the "best" results now are terribly slow and very different from anything I've gotten before.
Where should I get a x64 version of GaussianBlur? How do you determine the radius that should be used there?

Here's the script https://pastebin.com/c65dhju2, I launch it like F:\avsoptim\optimizer.bat F:\avsoptim\genBC.avs -iters 7h -runs 2 -pop 24

[StainlessS]

Where should I get a x64 version of GaussianBlur?

I think its in the VariableBlur whatsit:- http://avisynth.nl/index.php/AviSynth%2B_x64_plugins

[Reel.Deel]

Originally Posted by StainlessS

I think its in the VariableBlur whatsit:- http://avisynth.nl/index.php/AviSynth%2B_x64_plugins

Actually at the moment is not on there, the download link points to the 32-bit version. I did add it on there but someone edited a few things and changed the link

Also I don't recall a 64-bit version of the latest VariableBlur (v0.7), only v.05 is available:

• Binary: http://www.mediafire.com/download/0z...eBlur05_x64.7z
  
• Source: http://www.mediafire.com/download/hz...ur05_x64src.7z

[StainlessS]

Hi RD, glad that you are still lurking about

Just checked, I got v0.5 only on x64.

OK, had a bit more of a look, here is v0.7 (x86 only) with source, but its got lots of asm.
http://www.mediafire.com/file/1ugcb8...r_0.7.zip/file

[zorr]

Originally Posted by Seedmanc

I don't think I understand how to use the new method. I tried incorporating it into my script and thing went wrong I think, the pareto graphs look weird and the "best" results now are terribly slow and very different from anything I've gotten before.

Sorry, I should have made a better example. You don't actually need to blur anything, it was there just to demonstrate how B-SSIM score gets lower if you increase the blurring.

Replace the lines 135-146 with this and it should work.

scharr_orig = scharr(orig_yv12)
scharr_inter = scharr(inter_yv12)
FrameEvaluate(last, """
	#global ssim = SSIM_FRAME(scaled_orig, scaled_inter)
	global ssim = SSIM_FRAME(orig_yv12, inter_yv12)
	global bssim = BSSIM_MOD(scharr_orig, scharr_inter, ssim)	
	global ssim_total = ssim_total + (bssim == 1.0 ? 0.0 : bssim)		
""")

[zorr]

New release, new name! AvisynthOptimizer is called "Zopti" from now on. Why? 'Cause it supports VapourSynth as well, that's why. Download the version 1.0-beta here.

There's some other improvements as well, here's a complete list:

• added support for VapourSynth scripts
• Linux support (with VapourSynth)
• added zoptilib python module to ease script writing
• added support for VMAF output logs
• improved heat map visualization:
  -updates optimization progress to title bar when using autorefresh
  -shows correct visuals also when smallest value is best
  -added latest results visualization
  -heat maps can be saved to image sequence with the -animation argument
  -initial window size scaled to full screen
• improved scatter chart visualization:
  -improved zooming (-top)
  -better legend position when smallest value is best
• uses resolve for initial population when using randomized arguments fails 100 times
• more error handling options when script execution fails: new argument -errors with options:
  -stop (default, stops execution)
  -ignore (continues optimization)
  -log (continues optimization and logs errors into a separate error log)
• checks that input arguments are all valid for the chosen -mode
• improved error handling and error reporting in reverse polish notation parser
• new option -priority for setting the optimizer process priority (on Windows only), options are:
  -"": same as /NORMAL, default
  -lowest: same as /LOW
  -lower: same as /BELOWNORMAL
  -higher: same as /ABOVENORMAL
  -highest: same as /HIGH
• removed bias from the random number generation

A few notes about upgrading: I renamed the optimizer.ini to zopti.ini and the optimizer.bat to zopti.bat. If you already have the .ini you can just rename it to zopti.ini and it will work.

I have used the -priority option to set the thread priority lower because when VapourSynth/MVTools is running a heavy task the other programs can become sluggish with the default priority. Priority option is Windows only for now, Linux probably doesn't even need it.

The error handling options are useful when running the VapourSynth MVTools which is currently not as robust as Pinterf's version. With -errors ignore or -errors log you can keep running the optimization even when the plugin crashes. I still recommend running with the default error handling option (which stops the execution) unless you are expecting errors.

I will make another thread to the VapourSynth section to tell more about the VapourSynth-specific stuff.

[Seedmanc]

Is this version abandoned and will any development only happen for the VS fork? I don't feel like learning a whole new language just to continue processing video as I did before just fine with AVS.

For some reason I was unable to find this thread in the thread list for Avisynth Development section, it said "Displaying 12 of 12 threads". Now that I bumped it, it's displayed there and says "13 of 13". How do I see all threads at once?

[wonkey_monkey]

In your forum user Control Panel, go to Edit Options, then find and change "Default Thread Age Cut Off."

[zorr]

Originally Posted by Seedmanc

Is this version abandoned and will any development only happen for the VS fork? I don't feel like learning a whole new language just to continue processing video as I did before just fine with AVS.

No, the same version works for both AviSynth and VapourSynth. So most of the improvements will affect both versions (new algorithms etc). The only VapourSynth-specific thing is the Zoptilib helper library which is not really needed. I wish I was able to write a similar helper for AviSynth but it would take a guru like StainlessS to accomplish that.

I haven't made much progress lately, so it's quiet on both fronts.

[StainlessS]

Oh do stop it.