Search options (Page 2 of 9)

A user said to switch the video player to MPV instead:
https://www.svp-team.com/forum/viewtopi … 205#p85205
Check if this crashes?
https://mpv.io/

Delete mpv cache maybe? "C:\Users\User\AppData\Local\mpv"
Restart SVP and make sure it runs in background
mpv version from SVP is a bit older, while SMPlayer's is ancient.
try to update them by replacing mpv.exe from "C:\Program Files (x86)\SVP 4\mpv64\mpv.exe" and "C:\Program Files\SMPlayer\mpv\mpv.exe" with the one from latest archive:
https://github.com/shinchiro/mpv-winbui … 7a59a12.7z

Also i see SMplayer overrides this setting general->video->Output driver which might cause issues related to color detection
https://gyazo.com/5b706354d3c45e0b2fac0ddc18aa8090
Try to set it on gpu-next?

I think it's normally colored when it finds a normal video.
https://gyazo.com/9fbe058e807d6e26d962b4e3a9e54ebb
It's greyed out when it finds a video with HDR metadata
https://gyazo.com/6d637addeee3043f59356d259c62609e
It's brightly colored when it finds a video with Dolby Vision metadata
https://gyazo.com/1f21254bb5176125bc2f370f323c18e1
If you want to disable it, just uncheck "Show OSD messages" here:
https://gyazo.com/b90cf5e13cb34faeb01b51f8b7975cf2

I managed to fix the black stripe issue:
https://gyazo.com/d7f90a5f5d0bdf7fd3bd467f00d2347b
please open "C:\Program Files (x86)\SVP 4\script\generate.js" and edit this:
var pw = Math.floor((media.dst_w-1)/32+1)*32 - media.dst_w;
var ph = Math.floor((media.dst_h-1)/32+1)*32 - media.dst_h;
to this:
var pw = Math.floor((media.dst_w-1)/64+1)*32 - media.dst_w;
var ph = Math.floor((media.dst_h-1)/64+1)*32 - media.dst_h;
save and restart SVP and see if issue persists.

"did not feel the difference between all these versions"
default SVP cannot find the heavy rife model so it loads rife_v4.25 non-heavy instead
did you correctly replace the "helpers.py" and "vsmlrt.py" files from the bottom of the guide?
Please confirm by checking the folder where the RIFE models were generated and see if they contain "rife_v4.25_heavy.onnx" in their name:
"C:\Users\username\AppData\Roaming\SVP4\cache\Program Files (x86)\SVP 4\rife\models\rife_v2"
https://gyazo.com/7464860a70795a29754a7eeff6ba3d32
If all good, then that means there are no visual improvements and those artifacts are still present. All we can do is wait for RIFE devs to train new models. xD

I see there's an ancient madVR guide here, but not much else:
https://kokomins.wordpress.com/2021/03/ … e/#madvr-1

Are you looking for a guide like this one?
https://www.svp-team.com/forum/viewtopi … 352#p83352
The "rattling" of the picture originates from for example 2x speed, SVP showing you the original frame and then showing you the RIFE interpolated frame that is slightly off.
But to obtain the RIFE frame, the current frame and the next frame are being passed to Vapoursynth.
For Vapoursynth to process them, they are first converted into something Vapoursynth can read and then converted back into a media player frame, but this frame is now not aligning anymore with the original frame and looks like it's "rattling".
Only fix for now is to increase from 2x to 4x+ so you will see more RIFE frames and less the original non-aligned frame.
To increase the frames while your hardware cannot run it (until the end of this month when RTX 5090 releases), please try to play around with the resize setting so you limit to only send 1080p pixels or less of your 4K video.
https://gyazo.com/078014a0fd8fdab1a6d9d98a1b596566

On 9 september 2021 the Vapoursynth devs moved the misc filters from initial location to a separate repository:
https://github.com/vapoursynth/vs-miscf … ilters.cpp
SVP devs will have to fix that when they decide they want to update Vapoursynth

In that case just increase RIFE to 240 fps:
https://gyazo.com/5928e9b1f871b7a62d9f69997247d4d1
and disable scene change detection that might throttle the interpolation on high motion scenes.
This will have the effect of generating motion of 9 extra frames between each two original images. The smoothness will be capped by what your TV can display at that point.
If that doesn't work then u can go back to "Topaz Video AI software" cause probably they are processing the video differently by giving it more time to smooth things out.
It's a 300 bucks product with recurring subscription, of course it has better support:
https://gyazo.com/3a211b80408f420e9e92160a4ccc79d1
With a PRO version of 1100 bucks!
https://gyazo.com/d604a84eff4bcf699fd31aa656724c47

@Chainik when do we get a SVP PRO version too with recurring subscription? Cause it seems that products that contain generative AI are highly valued right now.
-Chainik limiting the max fps to 48 for non-PRO users when their subscription expires- xD

These files should allow SVP to find files ending with "_large.onnx".

Try 4.25_lite_v2 from last week?
https://github.com/AmusementClub/vs-mlr … nal-models
Should require less processing power.

Actually no, that scene has non-fluent movement, blame it on being a 1984 film. xD

Nice one!
Nope, stutters and hitches a lot for me too. Probably video player reaches a bottleneck somewhere even when GPU/CPU/Memory is not 100%.
Only solution would be to upgrade your system until it massively outperforms the video player requirements... or resize to 480p instead xD

[10/17/2024-16:48:41] [E] Error[9]: IBuilder::buildSerializedNetwork: Error Code 9: API Usage Error (Target GPU SM 61 is not supported by this TensorRT release.)
Time to upgrade GPU xD