dawkinscm wrote:It's a change to the code in base.py. I got this from a previous post by @blackmickey1007 for completely disabling SC.
SVP4\script\base.py
input_m = input_m.misc.SCDetect(threshold= 0.1 or 0.2).
The old line is:
input_m = input_m.misc.SCDetect(threshold=rife_sc)
and changing it manually to 0.1 and 0.2 values translates to:
- selecting "Scene change threshold" from SVP and selecting "10%" or "20%"
- or by going to application settings and search "rife_sc" and set it to 10 or 20 like in following image:
https://gyazo.com/714dd3a8a3159f1ac7f496126d92ee70dawkinscm i suggest you revert that line change since SVP devs were nice enough to allow us to control it from both mentioned places.
For "completely disabling SC" just set "rife_sc" application setting at 100 to see max smoothness with zero animation stuttering.
Thanks for clarifying. I just used that the 0.1/0.2 examples from the original post. I've tried 100 and other high values before and Rife is smooth with anything from 15% or 100% on my machine.
But the double image issue I'm talking about you may never see this issue depending on the the type of stuff you watch. I want to fix this while keeping the smooth motion which is pretty much impossible. With a low enough value, the stutters disappear but also causes slow pan stutters. My actual setting is a decimal fraction below 10% and rife_sc only accepts integers. Increasing fps actually fixes the issue but causes slow pan stutters and resource issues. The only real solution is for the model to get better and I've noticed a couple of small improvements so hopefully that trend will continue.
BTW I didn't want to say it before without more testing but Rife 4.14 uses a little less GPU resources than 4.12/4.13. YMMV.