"not working" how? does clinfo work? restart SVP after switching graphics configuration.
You are not logged in. Please login or register.
SmoothVideo Project → Posts by Chainik
"not working" how? does clinfo work? restart SVP after switching graphics configuration.
> What should i do?
do not install "VapourSynth-x64-R68.exe from https://github.com/vapoursynth/vapoursynth/releases), and Python 3.12.3"
SVP has everything it needs.
ну тут только Хуангу письма писать, больше посоветовать нечего
кроме HAGS вкл/выкл
работает - не трогай (с) народная мудрость
кто-то вон пишет про влияние HAGS на производительность RIFE
https://obsproject.com/wiki/How-to-disa … -Scheduler
> Why would this only be an issue with TensorRT while everything else works as normal?
not exactly... "normal" SVP works with 1st/2nd SVP shader on this file regarding of the profile settings
> Is it possible to remove that?
attached SVP 4\rife\helpers.py
will blink with pure DolbyVision video
I'd say this's because of embedded DolbyVision data.
Not sure how _normal_ for DolbyVision is changing meta-data in _every_ frame, but this's what happens in this sample.
> I don't know why MacPorts install doesn't include it.
sudo port install mpv +vapoursynth +libmpv
check the log for errors
It isn't SVP's job, there're plenty of options in various video players for "AI upscaling".
option "libplacebo" removed in mpv 0.37
> I would appreciate an explanation
use a scene change detection from "generic SVP" with RFIE
> I figured it could do that to anime since the characters still move at like 8 to 14fps.
RIFE interpolates between two adjacent frames only. If there's no motion between two frames it will do nothing.
In a simple case when characters animated at, for example, 12 fps while the video is 24 fps, you could "remove every other frame" making 12 fps video, and then interpolate it.
the file attached there was updated 4 times already
the last time - yesterday
pensioner600
> That is, the first frame (or the first few frames), but most likely only the first frame of the next scene seems to be lost and shifted a little to the side and with the next frame it returns to its correct position.
try updated svpflow2_vs.dll from that post: https://www.svp-team.com/forum/viewtopi … 672#p84672, any changes?
вон там - https://www.svp-team.com/forum/viewtopi … 672#p84672 - .dll которая, возможно, это исправляет
пока только для Vapoursynth
check with clinfo tool that OpenCL drivers are ok
https://www.svp-team.com/forum/viewtopi … 672#p84672
updated svpflow2_vs.dll, default value for scene.limits.blocks set to 40 for RIFE
> instead finding rife_sc all the time?
just don't close the window
> Then how to make proper frame blending when RIFE_SC threshold over 15?
this is why you need a MV-based scene change detection instead of dumb image comparison
%APPDATA%\SVP4\override.js
smooth.scene.limits.blocks = 40;
default value is 20
with 40 at least the Hugo intro - the fly over the city and through the train station - is better (almost no scene changes)
btw
smooth.debug.qmode = true;
will draw a color square in the frame corner, when it's red it's a scene change
flowreen91
> I think it's easier to test if u go to line 222 from generate.js and delete the following
how is this easier than choosing "6%" in the gui?
> NVOF algo fixes vertical motion artefacts but causes problems elsewhere.
It just can't "cause problems". It can only:
a. (_very_ unlikely!) miss the scene change that is actually a scene change --> which shows RIFE's artifacts at this frame
b. mark a scene change where there's no scene change --> makes it choppy where it could be not choppy
that Hugo?
"6%" or "8%" mean nothing here
IF "6%" THEN USE "scene change based on SVP's motion vectors"
IF "8%" THEN USE "scene change based on NVOF's motion vectors"
ELSE USE "dumb frame comparison"
Testing RIFE update with SVP's scene change detection added.
Replace script\generate.js, script\base.py and plugins64\svpflow2_vs.dll, restart SVP.
Now THREE different modes are possible, controlled by the "Scene change threshold" profile option:
1. default - old behavior with "dumb" scene change
2. scene change based on SVP's motion vectors - when "scene change threshold" is "6%"
3. scene change based on NVOF's motion vectors - when "scene change threshold" is "8%"
Scene change-related params from override.js should also work, such as smooth.scene.limits.zero, .blocks, .scene (see a short description there - https://www.svp-team.com/wiki/Manual:SVPflow)
UPDATE: svpflow2_vs.dll updated, also supporting blending on scene changes instead of frame repeating.
There's no "processing of scene changes" option in the RIFE profile so you have to set it via 'All settings' - find the profile and set 'fi_scene_changes' to 0 (blend) or 1 (repeat)
UPDATE 2: svpflow2_vs.dll updated, default value for scene.limits.blocks set to 40 for RIFE
UPDATE 3: svpflow2_vs.dll updated, using correct frame for repeating on a scene change
because they are ... different
> I would switch to MPV but I can't stand that it's completely barebones with zero UI
SMPlayer
> I can't actually find any ncnn vs dml benchmarks for rife.
TRT is 2 times faster than ncnn
DML is _10_ times slower than TRT
SmoothVideo Project → Posts by Chainik
Powered by PunBB, supported by Informer Technologies, Inc.