Search options (Page 4 of 12)

Playing variable frame rates videos is not always worked without issues

but frame rate is also very inconsistent in full screen mode
By any chance you're using MadVR? If so, then you need to reduce the upscale setting. Check whether the frames start to drop after full-screen mode.

I've compared playing AVC video and its HEVC encode without SVP, from my observation playing AVC with 32bit player was about the same CPU usage with playing HEVC with 64bit player.

Turn off "outer lighting".

Since it's ancient, it means it's available to low-end specs, isn't a nice thing?

SVPFlow and MVtools are available if you're not happy with their GUI manager.

Since others people didn't even need to do some lengthy setting, it's the very sign you've been solving the wrong problem.

Are laptops nowadays have display monitor with 1080p resolution?
Having "Decrease to frame size" to screen size is surely helping when the monitor is less than 1080p.

Not to mention processing burden for 1080p is different with 720p by large. And the different not simply 2x, but with some setting it could 4x or 8x.

That's why there are profiles specifically for 720p and 1080p.

In my point of view, 70% of processor usage for playing 1080p video is quite accomplishment, my CPU is much weaker compared to yours.
If you're worried about the temperature, since yours is thin "ultrabook" not that SVP can help ,
It's simply whether you need to decrease the setting or watching video on HTPC instead

Can you elaborate more where to find that value? I couldn't find any.

Actually you can check using ffdshow OSD->Avisynth Info on how many the actual buffer back/ahead is used. (Look picture in attachment)
But just to be save I used 20/20.

tl;dr (look from bottom for the summary )

Advantage:
- Custom target frame rates: For some people, having cleaner look (or minimum artifacts you could say) is preferred than smooth motion, you can choose 2x, 3x or define your own target frame rate.

- Outer lighting: This feature will give you some nice lighting effects to fill the black bar when you display AR is not same with video AR. (correct me if I'm wrong)

- Manual adjustment of video profiles: No "silver bullet" setting that will answer the issues of smoothness vs artifacts. Every person has different preference, some like smoother while other like cleaner. This feature comes to help as pro version will give the friendly user interface to tweak the setting for FRC engine.

- User defined condition: This feature is closely related to above, for example, you want the different setting for 1080p and 720p video. This feature will automatically choose based on your definition and then select the setting appropriate based on setting adjustment.

- Support for 64 bit player: Although the feature is still planned development, having 64bit player to play the video greatly help when the CPU is really at limit. For example, there is video with this particular scene, when playing with 32bit player, I always get the max of 100% CPU usage, but when playing with 64bit player, the max is only 85% CPU usage, for me this helps greatly since I use audio processing too in the background and it could eat 5% of my total CPU usage

- Support additional module: see SVPLight and NaturalGrounding by Mistery.

- Support BD-3D video: this should be obvious

- Processing of Hi10p videos: This feature to preserve decoding video that has 10 bit color depth. The 10bit encoding helps, even though the display monitor is not 10 bit, to reduce banding while keeping the file size is smaller than 8 bit counterpart. By supporting processing Hi10p videos natively, there should be minimum/no loss when processed with SVP.

In nutshell:
The most advantageous among all is "manual adjustment of video profiles". This feature by itself is worth to subscribe to pro version.
Unless you want to fiddle and experimenting with various setting in SVPFlow by yourself, it's far more easier having GUI interface that will tell you the effect on the spot . You save your time by having it pro

To answer your question: "Would it help more with processing the video much more smoothly?" Yes, it does*

*: With the correct and your preferred setting. Not to mention you can even reduce some artifacts while you still enjoying the smoothness (this is subjective observation though )

This is not recommended but if you insist, you can change the generate.js for manual value
change the expression at line 350 into:
from

avs.WriteLine("SetMemoryMax("+value("AVSmem", 1700)+")");

to

avs.WriteLine("SetMemoryMax(4096)");

and add "threads = 20" above

avs.WriteLine('global threads='+threads);

I don't know why value("AVSmem", 1700) returning 1024 when it should return the default or if no default then it returns the "1700", maybe some expressions before line 350 have changed it but I'm too lazy to read it all.
So this method is not recommended because it's hardcoded.

Kudos to you, Sir. Simplest and proven method

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 )

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

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.

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 )