Search options (Page 2 of 7)
Yes, it seems SVP detects something really wrong if u want to double the frames:
https://gyazo.com/ece3993a94f81d6a5f9aced049eddd99
Probably LosslessCut breaks something.
If i re-encode your video with https://handbrake.fr/ it detects the source frames correctly afterwards:
https://gyazo.com/30ed5fdb98f6c772c39b4dc77de561ea
So try to play around with LosslessCut encode settings until it exports a SVP compatible video.
Or re-encode your video again with handbrake if u want for the source frames data to be detected ok.
narkohol wrote:Mmm... all those videos are 23.976 fps.
They are test scenes I cut from the original source videos using LosslessCut.
I installed SVP yesterday, how can I update it more?
Weird that it detects higher fps that 23.976 and crashes.
Please share an example of the cut test scene that gives that error.
You are using latest then, all good.
To update it in the future, right click the SVP icon and select "Additional programs and features..."
https://gyazo.com/f7f87353420412aa1250b1fbabcff7e9
TechnoStone wrote:Messed with reinstallations, BOTH of these methods just make svp use v1 models
Hahaha you are right! I never noticed that.
It means the fix is actually longer than one line, hidden somewhere in the vsmlrt.py file from scripts.v15.4.7z
Will wait for SVP developers for actual fix.
Thanks TechnoStone!
Temporarily we can use these that don't have the v2 shake and load v2 models correctly:
Attaching latest version of vsmlrt.py from here https://github.com/AmusementClub/vs-mlr … /vsmlrt.py
dawkinscm wrote:video_player: bool = False should be the default setting.
Attaching sending video_player False to RIFE as dawkinscm suggests in helpers.py
narkohol wrote:05:04:18.996 [E]: Playback [c0145ab3]: VS - ValueError: vsmlrt.RIFE: RIFE: multi must be at least 2
But setting to "Fixed 60fps" doesn't solve it.
It means the video u are opening already has 60 fps.
Try specifying a higher fps value.
And also update SVP.
Chainik wrote:I believe that all "fixes" the latest vsmlrt.py contains are included in SVP's one
The v2 shake issue seems to get fixed if u add this on line 1027:
video_player: bool = False,
https://gyazo.com/d7798e1ee97ecfa658d8587466561630
(nevermind it seems it just makes it load the v1 model instead)
Blackfyre wrote:Also thanks to flowreen91 for posting the original fix for screen shaking in some scenarios while using v2's
The old tree wiggle issue was present only on TensorRT v14.test2 and older, and was fixed just by upgrading to TensorRT 14.test3 or newer.
https://www.svp-team.com/forum/viewtopi … 617#p84617
It was unrelated to what's inside the vsmlrt.py file.
But if u indeed manage to reproduce a new screen shaking issue and fix it on your 4K screen while using latest TensorRT please provide more data/video/recording example so Chainik can look into it. ^_^
John86 wrote:4.18 (v2) still the best atm?
On RIFE page: https://github.com/hzwer/Practical-RIFE
RIFE devs say "For anime scenes, it is recommended to choose 4.22.lite, and for real scenes, it is recommended to choose 4.18."
So i would go with 4.22_lite v2 cause it's fastest recent lower computational cost model.
Wasn't this a great time to fully switch to the v2 models?
Or are there certain scenarios where they actually perform slower than v1 models?
If madvr is too slow, maybe try MPC VR or mpv instead?
https://www.svp-team.com/forum/viewtopi … 359#p85359
Here there are some parameters that add some metadata, not sure if it has your desired effect:
https://www.svp-team.com/forum/viewtopi … 885#p84885
If you have a non-HDR video, you can enable Nvidia App's HDR filter on it by using https://www.nexusmods.com/site/mods/781
This should display any non-HDR video in full HDR.
Valtruis wrote:I wonder if there's an issue with HDR of some sort.
Weird issue.
To disable hardware accelerated gpu scheduling follow this guide:
https://www.howtogeek.com/756935/how-to … indows-11/
If issue still persists u can try to upgrade TensorRT by downloading https://github.com/AmusementClub/vs-mlr … 4.test3.7z and unzipping
vstrt.dll
and the folder
vsmlrt-cuda
into
C:\Program Files (x86)\SVP 4\rife
and check if RIFE issue persists.
If issue still persists u can also try to copy vsmlrt.py too from the same archive.
Valtruis wrote:When I transcode a video that is:
- .mkv (.mp4 works)
If u convert that .mkv video to .mp4 first (using other software like https://handbrake.fr/ )
and only after that transcoding the .mp4 with RIFE
Will that fix the issue?
Curious if SVP devs encountered this before...
According to Steam Hardware Survey average user will upgrade to a 4000 series soon so they will be able to handle it:
https://gyazo.com/c16215fe1fd071bce48e62115e13bb83
Overall stats:
RTX 4000 Series: 19.90%
RTX 3000 Series: 20.80%
RTX 2000 Series: 7.21%
GTX 1000 Series: 13.26%
Mardon85 wrote:Has anyone experienced this issue before?
Everything was working fine but as of the last month MPV has stopped working.
Try to update to latest mpv version from here:
https://mpv.io/installation/
Try to delete mpv cache folder from here:
"C:\Users\Username\AppData\Local\mpv"
Try to delete RIFE cache folder from here:
"C:\Users\Username\AppData\Roaming\SVP4\cache"
Restart pc maybe?
cemaydnlar wrote:How can i see if vsync is working on my mpv ?
To accurately measure your current frames per second (FPS), you should install NVIDIA App from here:
https://www.nvidia.com/en-us/software/nvidia-app/
And enable Statistics in the NVIDIA Overlay:
https://gyazo.com/a17a74b5b071a3d8c137c17a67ad00d4
you can also try to add this in mpv.conf file:
video-sync=display-resample
if you want to "Resample audio to match the video. This mode will also try to adjust audio speed to compensate for other drift. (This means it will play the audio at a different speed every once in a while to reduce the Audio/Video difference.)"
GGGG wrote:Hi all, I am new to this forum, can you please tell me which version of rife is the performance?
https://github.com/AmusementClub/vs-mlr … nal-models
The rife models with "lite" in their name consume way less power.
Version 4.22 lite is latest that you should use if your pc is slow.
Other tips:
https://www.svp-team.com/forum/viewtopi … 352#p83352
Logs say it detects 24 fps then 120 fps then it goes back to 24 fps.
Can you try to select anything other than "To screen" from this list:
https://gyazo.com/9f782dc677db51837af1a534b83fc44f
then restart SVP and run any movie. Then it should not revert back to 24 fps.
No clue, can't reproduce on specified video.
You can try different stuff maybe to identify what causes the issue.
Try to transcode a short video using different Rife models.
Try to transcode a short video using the default Automatic interpolation instead.
Try to transcode a short .mpv video instead of .mkv
Weird.
Please also link the source from where u got Split.2016.2160p.UHD.BluRay.x265.10bit.HDR.DTS-HD.MA.5.1-RARBG so we can download the original non-transcoded version to try transcoding it and see if it consistently breaks.
Thanks!
lurker wrote:pre-prepared frames
concurrent-frames i think is the frc.threads from here:
https://gyazo.com/a12c49b425024e65b789ff0d4a190db8
Bensam123 wrote:do you use vsmlrt-windows-x64-cuda.v15.2.7z or vsmlrt-windows-x64-tensorrt.v15.2.7z?
It seems unpacking the cuda archive and deleting all the extra files doesn't make any difference on both TensorRT and ncnn/Vulkan models.
I think it's safe to use the vsmlrt-windows-x64-tensorrt.v15.2.7z instead of the uselessly big cuda archive.
Nice! Does the 4090 haz enough power for u to watch 2x on 4K and 2K videos with latest TensorRT + latest models?
Does it smooth it out? Yes!
But does it do a great job doing it? Not so much currently.
If u check this panning scene from the start with LSFG:
https://drive.google.com/drive/folders/ … nG0qJnlw4I
You can notice how even if you see that everything goes up, LSFG does not know the direction of the movement.
So it will create artifacts on left/right side of the screen where the stars teleport left/right/up/down around their initial positions instead of going up.
This looks horrible and really confusing and makes me always pick the Automatic Interpolation which simply pans the scene up.
RIFE is on another level, it somehow identifies the objects and generates new frames based on where the objects will move next, making the movements more accurate than Automatic.
Pick what u think it's best (or just use the resize functionality to decrease video size u send to SVP until your hardware reaches your desired FPS).
aloola wrote:v15.2 gives me a tiny FPS boost
v14test3 ~150fps vs ~ v15.2 ~158fps, also fixed dynamic shape (Performance boost: off) bug
15.2 changelog:
Upgraded to TensorRT 10.3.0.
Fixed performance regression of RIFE and SAFA models starting with vs-mlrt v14.test4. This version may still be slightly slower than vs-mlrt v14.test3 under some conditions, however.
Looking forward to @aloola benchmarks for the new TensorRT like he did before:
https://www.svp-team.com/forum/viewtopi … 324#p84324
erriep2703 wrote:# Deband filter. Always turn on for anime.
deband=yes # Default values are 1:64:16:48
I see that these settings are present in an outdated guide:
https://kokomins.wordpress.com/2019/10/ … fig-guide/
<meta property="article:modified_time" content="2024-02-08T06:53:17+00:00"/>
Probably we should use more recent configs from 2024:
https://kohana.fi/article/mpv-for-anime
https://artoriuz.github.io/blog/mpv_upscaling.html
https://iamscum.wordpress.com/guides/vi … /mpv-conf/
https://thewiki.moe/tutorials/mpv/
Xenocyde wrote:Can confirm the edge artifacts are still there in 4.21.
The devs fixed the smoothness issue:
https://github.com/hzwer/Practical-RIFE … 2275333756
aloola wrote:v15.2 gives me a tiny FPS boost
v14test3 ~150fps vs ~ v15.2 ~158fps, also fixed dynamic shape (Performance boost: off) bug
15.2 changelog:
Upgraded to TensorRT 10.3.0.
Fixed performance regression of RIFE and SAFA models starting with vs-mlrt v14.test4. This version may still be slightly slower than vs-mlrt v14.test3 under some conditions, however.
Is this finally the time SVP upgrades the out of the box TensorRT version to 10.3.0 and v2 models only for faster performance? xD
Wow! that's a lot of scripts!
You can check for obvious errors if you press ` while a video plays in mpv.
Or to enable full logs output go to mpv.conf and change this line:
#log-file=mpv.log
to
log-file=mpv.log
This will generate a log file with everything mpv does when you play something. Maybe it will give you some useful information on how to fix it.
If nothing works anymore, reinstall SVP and try again.
Posts found: 26 to 50 of 161