SVP 4 64-bit Windows

Has there been any updates on whether this will be introduced?

We can't release it to the public cause there's no stable Avisynth 64-bit available.

Ah that makes sense then. It looks like there are a lot of discontinuted 64-bit branches on Github.

These seem to be the most popular currently:
http://forum.doom9.org/showthread.php?t=152800
http://forum.doom9.org/showthread.php?t=168856

Neither has been updated in over a year but they're suppose to be compatible with 32-bit extensions as well.

But I've been using Avisynth+ x64 MT already http://avisynth.nl/index.php/AviSynth%2 … ent_branch
It's the r1779 though, the r1825 somehow didn't work well with svpflow (Likely I screwed it up when change the DLLs but oh well )

r1825 dosnt work with svp. author optimized it too much
For 32bit svp I still prefer avs set mt.

I dont care about RAM only faster seeks. 1600mb still better than 10 Gb ram in x64

Hmm, I've been using AVS+ x64 together with SVPFlow x64 and find the memory leak doesn't that severe. (on the contrary, I subjectively found it's quite stable )

Above graph is about 4 episode, each ~23 minute, the dip in middle happened when I press "Page down" to load next episode.
It ate quite big for each video load and then tried to dispose/reclaim the unused memory allocation.

The ffdshow version:
ffdshow tryouts rev4534 Aug 12 2015 21:30:00 (MSVC 2010, x64, unicode, r)

From my logs, it's about ~1000-1500 mb every time I watch video 720p.

Sure, find that in attachment, though I just modify the "last used script", nevertheless I made several files for different profile (my pc can't handle 1080p as handling 720p, my monitor is 1600x900)
Use the SVPFlow 1.1.17, it should work better https://www.svp-team.com/wiki/Download#libs

The script has several redirection, mainly just for selecting the profile though
1. First script is in ffdshow video decoder avisynth option,

global myavs="D:\avisynth_scripts\"
Try {
SetFilterMTMode("DEFAULT_MT_MODE", 2)
SetFilterMTMode("ffdshow_source", 3)
ffdshow_source()
 import(myavs+"svp64.avs")
}
Catch(err_msg) {
 ffdShow_source().Subtitle(err_msg)
}

Don't forget the check the "Buffer back/ahead"

2. File 2 is svp64.avs (find it in attachment) which selects the profile between 1080p and 720p, and then importing...
3. File 3 is the setting for each profile (find in attachment too), svp64_1080p.avs only because 720p is about same, only different options and without calculating the width and height.

You can adapt the options by referencing this SVPFlow manual, https://www.svp-team.com/wiki/Plugins:_SVPflow

Ironclad

showinfo = true
showinfo ? \
    last.Subtitle("Speedup:" + string(speedup) +\
        " => (" + string(num) + ":" + string(den) + ")") :\
    last

Put this at the bottom of the script (or after importing the "actual" script that do the interpolation), you can toggle it off by making showinfo false, "showinfo = false"
If it's Javascript, I can add "setTimeout(function() { last.Subtitle(); }, 5000)" to automatically disable it after 5 seconds but it's Avisynth script not Javascript

The script that I use is calculating the numerator and denominator without limit so for video with 23.946 FPS, it will print "Speedup:2.502502 => (25000:999)"

You can set the limit in ContinuedNumerator and ContinuedDenominator so the change will be

speedup = targetFramerate / last.FrameRate
num = ContinuedNumerator(speedup, limit=100)
num = ContinuedDenominator(speedup, limit=100)

It will print "Speedup:2.502502 => (5:2)"

You have to change manually the value though and reload the video in order to apply the change
(It's possible to use JScript to do that automatically, but I never touch JScript/VBScript before)

Yes, it's same whether in bottom of ffdshow Avisynth tab, or in my case in svp64.avs.
But that's actually only printing the numerator and denominator that would be fed to "smoothfps_params".
When you've got it correct, the "catch block" won't catch any exception that would be thrown, it's actually works when there's no OSD like shown at the video (Of course before adding our additional last.Subtitle to know the value of num and den)

You don't have to. Because "last.Subtitle" has different meaning with video subtitle (it's same but the purpose is different
Subtitles tab is for rendering the subtitles that video has, while "last.Subtitle" is for rendering "our subtitle"

Yes, AFAIK, it's limited to the predefined categories. Maybe we can add it for other category but I don't find any info for that.

Yes, that's the exception caught when something is wrong, look at

Try {.... } catch (error_message) { last.Subtitle(error_message) }

It will tell you where/which line that actually gives you the error, whether it's syntax error, plugin error, etc. You can then check it again in that line. The most common errors are usually syntax error though (I did it many times, like forgot adding the comma, forgot adding backslash before newline, etc )