Search options (Page 7 of 55)

You MUST also run your monitor at 96Hz+ for this to actually be beneficial.  Considering that OP is running 60fps, it is extremely likely that they also use a 60Hz display.

If we're going to get into monitor overclocking, then it's worth mentioning that achieving an overclock of 72Hz (movie x3) is much more common than an overclock of 96Hz.

I discreetly linked to it once, but it seems to have been largely ignored so I must be blatant this time - PLEASE review the following thread of mine that goes over the general concept of what frame rates and refresh rates are ideal for optimal smoothness and minimized artifacts in SVP:

http://www.svp-team.com/forum/viewtopic.php?pid=61595

Though for the most part, maxing-out everything except "artifact masking" and "motion vectors grid" should work just fine if you have the performance (and at low resolutions like 480p, even maxing out "motion vectors grid" can work).

You're more likely to see a stand-alone third party video editor that can hook into SVP just like the media players can.

I had made a thread about Avidemux since it now supports VapourSynth, but the thread was DOA...

That works because games are not rendered at 100% constant framerates (that's partially why Adaptive Sync and G-sync are a thing).  On non-variable refresh displays, if you set your maximum framerate to slightly above your display's maximum refresh rate, then most of any frame-rendering inconsistency will still be above your display's maximum refresh rate.

Videos, unlike games, are rendered at constant framerates (well, they are 99.99% of the time), so there's no need to leave this headroom between your monitor's refresh rate and the video frame rate.

That's because 24 --to-> 75fps @ 76Hz is one of the worst scenarios possible to the point that even 24 --to-> 90fps @ 76Hz will look better (more info).

You should have much better results if you simply set your monitor to 72Hz and then do 24 --x3-to-> 72fps.

This.  I myself use some pretty non-standard refresh rates for various things (74Hz, 83Hz, 110Hz), but setting SVP to interpolate to a refresh that is considerably higher (i.e. not just by 1 or so fps) than whatever your display is running at is a waste of CPU utilization and can give a less smooth result.

When your video file is an MKV or WebM, MPC-HC will do this automatically when an audio file has the same file name as the MKV video.

For reference, this will occur even if you're using MPC-HC by itself without any additional software (such as SVP and ffdshow).

I would very much love this as I use non-standard aspect ratios in order to achieve a higher refresh rate than my would normally support - I can use true 16:9 for 90Hz, but for 96Hz I have to use a 1.83 aspect ratio and for 100Hz I have to use a 1.91 ratio.

Mac computers are pretty much exclusively 16:10, tablets are commonly 16:10 or 3:2, and Microsoft seems to prefer 3:2 for its newer "Surface" branded products.

Completely close SVP (right-click the SVP taskbar icon, select "close") - does the issue still occur with DXVA2?

The link you gave me says that your GPU is capable of decoding 120fps video encoded at HEVC, but it does not say if that is 8bit or 10bit.  It's very possible that this 120fps maximum is only for 8bit and that its capabilities are much less (say, 30fps) for 10bit HEVC.

SVP's interpolation engine is completely independent of your GPU's HEVC decoding - it does not matter if you are trying to interpolate to 144fps or 240fps if your GPU can't decode 60fps 10bit HEVC.

I wouldn't call it "garbage", but it is tru that 60fps--to->120Hz is better than 60fps--to->144Hz - more info here.

But could you still test it?

Also you can use the Page Up and Page Down keyboard keys to go to the next/previous item in the current playlist.

OK yeah, on my CPU it's actually a difference of 10% CPU utilization - for reference that's basically the difference between decoding Xvid vs decoding VP9 (both in software).

With SVP's downscaling I was only able to do half pixel + 16px with Xvid (VP9 required too much CPU).  Using "fast billinear" downscaling, I was able to do half pixel + 16px with VP9 at similar CPU utilization.