Search options (Page 1 of 2)
flowreen91 wrote:redraiderj wrote:If I use 4.4v2 for vertical, there is no frame skipped.
That's the answer then: on your card 4.6 is too heavy for a 4K vertical frame at x2, and 4.4 v2 fits.
I need to correct my Task Manager tip. With the same model and frame rates here (4.4 v2, 24 to 48 fps, no drops), nvidia-smi shows only 63-74% GPU utilization. So utilization doesn't reach 100% even at the limit, and skipped frames are the real test, which you already did.
One difference: my monitor is 1440p, not 4K. RIFE still processes the full 4K frame (SVP doesn't scale it to the window), only the final scaling in the renderer differs.
About that, you may want to check Frame Size -> Alter video frame size. Anyway I guess I'll need a more powerful card for any 4K 30fps video, probably when RTX60 release I'll get one lol
flowreen91 wrote:redraiderj wrote:firstly I played vertical video on horizontal monitor, got 748 skipped frames; secondly I played horizontal video on vertical monitor, no skipped frames.
Thanks, that settles it: the drops follow the vertical video, not the rotated monitor. So it's the RIFE side on your card, not the display.
I repeated your setup here with MPC Video Renderer (adjust present time), a 24 fps 4K clip, RIFE 4.4 v2 on TensorRT x2 to 48 fps, on my monitor rotated to portrait and set to 60 Hz, 3 runs per video. No difference between them here: landscape skipped 0 / 129 / 135, portrait 0 / 133 / 139. All of those skips happened in the first seconds after opening the file, none during playback. That matches the "warm-up" you noticed, and why your second run dropped from 748 to 57.
In VSPipe, the portrait frame is about 2% slower for RIFE here (4.4 v2: 81.5 vs 79.7 fps). If your 5070 Ti is right at its limit with 4K x2, the difference may be bigger on your card and enough to tip it over. To check, open Task Manager > Performance > GPU while each video plays: if the vertical one sits at 100% and the horizontal one below, that's it.
Both 3D and GPU overall utilization stays around 70%, but I'm not sure if it's already the ceiling RIFE can get. Because if I use 4.6 for vertical, it keeps skipping frames but the utilization is still around 70%. If I use 4.4v2 for vertical, there is no frame skipped. Both works perfectly for horizonal with 0 skipped frame.
flowreen91 wrote:redraiderj wrote:For horizontal video there are no skipped frames, and the frame curve in Ctrl-J is very flat; while for vertical video there are 357 skipped frames
Your two screenshots come from different monitors. The horizontal video played on the XV272K (primary, 120 Hz) and the vertical one on the P272U PRO (the rotated one, running at 60 Hz). So the video and the monitor changed together, and the stats can't tell which one causes the drops. The vertical one also looks like it's falling behind before the renderer: 47.606 fps measured vs 47.952 target, while the horizontal one is at 47.984.
Could you swap them? Play the vertical video on the XV272K and the horizontal one on the P272U, with the same settings, and check Ctrl+J again. If the drops stay with the vertical video, it's the video/RIFE side. If they move to the P272U, it's the rotated monitor or its 60 Hz. Here the rotated monitor made no difference, but mine is 1440p and I tested with EVR-CP. You use MPC Video Renderer on a 4K screen, so your setup may behave differently.
Just tested, firstly I played vertical video on horizontal monitor, got 748 skipped frames; secondly I played horizontal video on vertical monitor, no skipped frames. Then I wonder if there is any "warm-up" mechanism, so I played vertical video on horizontal monitor again and got 57 skipped frames, which is much better than the first time, but still have some performance drop.
flowreen91 wrote:redraiderj wrote:I wonder if you have any ideas why vertical videos consume more than horizontal videos?
I tested it here (RTX 5090 Laptop, stock TensorRT, x2 to 60 fps). The difference is small:
RIFE itself runs at the same speed on both. 4K in VSPipe, 3 runs each: 4.4 did 74.6 fps landscape vs 75.0 portrait, 4.4_v2 81.5 vs 79.7.
The difference comes from SVP's script for MPC-HC: it cuts 16 rows off the bottom and pads the frame for RIFE, so a 4K landscape video ends up as 3840x2144 and a portrait one as 2176x3840, about 1.5% more pixels. In MPC-HC (RIFE 4.6 v2) that showed as about 3% more GPU power, 133 W vs 136 W on average, and both held 60 fps.
The rotated monitor made no difference either. I rotated my second monitor to portrait and played both files fullscreen on it in MPC-HC: both held 60 fps, with the same jitter as on a landscape monitor.
My guess: you already get 296 skipped frames on landscape 4K30 with TensorRT, so your GPU is right at its limit, and a few percent more work for portrait is enough to turn a few drops into many.
One thing that did cause stutter here: if MPC-HC starts on one monitor and you drag it to a monitor connected to a different GPU, it keeps rendering on the first one (Ctrl+J shows it under "Render device"). If both of your monitors are on the same card, this doesn't apply.
I'm connecting both monitors to my 5070Ti, and my CPU doesn't have an integrated GPU. For me the performance is significantly different, I just tested another 3 minutes 54 seconds 4K 24FPS video which my graphic card can handle, I converted it into vertical and played it. For horizontal video there are no skipped frames, and the frame curve in Ctrl-J is very flat; while for vertical video there are 357 skipped frames and the frame curve has a lot of spikes. To avoid the frame skipping when opening the videos, I always play it for 10 seconds and rewind to the beginning and play them from the start. Here are the screenshots.
flowreen91 wrote:redraiderj wrote:when I open a video file, it will say failed to load C:\Program Files\SVP 4\rife\akarin.dll. If I copy akarin.dll to your rife folder and reopen the video, it will say Importing the numpy C-extensions failed.
Your screenshot shows the cause: your VapourSynth runs on Python 3.13, but the rife\pylib folder in my zip is built for Python 3.12, which is what SVP's own VapourSynth uses, so numpy can't load.
To fix it, either download the archive again and copy it over the same way:
https://drive.google.com/drive/folders/ … XX-S2JMOXD
or run this command, it installs the Python 3.13 versions of the packages TensorRT-RTX needs into your own Python (numpy, onnx and onnxconverter-common to convert the model to fp16, onnxruntime to prepare the v2 models):
d:\develop\python\python313\python.exe -m pip install numpy onnx onnxconverter-common onnxruntime
Your own packages are used before pylib, so nothing else needs changing. I reproduced both of your errors here with Python 3.13 + R79, and after this command RIFE worked with both the normal and v2 models.
About akarin.dll: the zip's rife folder is meant to be copied on top of SVP's rife folder (merge and overwrite), not to replace it. SVP's own rife folder already has akarin.dll, the models and the rest. If yours was replaced, restore it (SVP's maintenance tool or a reinstall), then copy the zip's rife folder over it again.
Just a side question, I noticed an issue regarding vertical videos https://www.svp-team.com/forum/viewtopic.php?id=8025, I wonder if you have any ideas why vertical videos consume more than horizontal videos?
flowreen91 wrote:redraiderj wrote:when I open a video file, it will say failed to load C:\Program Files\SVP 4\rife\akarin.dll. If I copy akarin.dll to your rife folder and reopen the video, it will say Importing the numpy C-extensions failed.
Your screenshot shows the cause: your VapourSynth runs on Python 3.13, but the rife\pylib folder in my zip is built for Python 3.12, which is what SVP's own VapourSynth uses, so numpy can't load.
To fix it, either download the archive again and copy it over the same way:
https://drive.google.com/drive/folders/ … XX-S2JMOXD
or run this command, it installs the Python 3.13 versions of the packages TensorRT-RTX needs into your own Python (numpy, onnx and onnxconverter-common to convert the model to fp16, onnxruntime to prepare the v2 models):
d:\develop\python\python313\python.exe -m pip install numpy onnx onnxconverter-common onnxruntime
Your own packages are used before pylib, so nothing else needs changing. I reproduced both of your errors here with Python 3.13 + R79, and after this command RIFE worked with both the normal and v2 models.
About akarin.dll: the zip's rife folder is meant to be copied on top of SVP's rife folder (merge and overwrite), not to replace it. SVP's own rife folder already has akarin.dll, the models and the rest. If yours was replaced, restore it (SVP's maintenance tool or a reinstall), then copy the zip's rife folder over it again.
Thanks, it works! I tested with one 3.5 minutes 4K 30fps video on my 5070Ti, with SVP stock settings + RIFE 4.4v2 model I got 296 skipped frames, while with rtx I got 104. Looks like I still can't perfectly run a 4K 30fps video, but it improves. Also, the engine building process takes significantly less time. Thanks a lot, and hopefully SVP can take this solution into their development roadmap.
Just to ring a bell, this issue still exists.
flowreen91 wrote:Drakko01 wrote:could you share how exactly you got R79 to work with SVP?
I'm trying to test it myself, but MPC-HC crashes instantly as soon as I try to use R79.
I had only tested their performance with vspipe: SVP's RIFE (TRT and TRT-RTX) and svpflow scripts at 1080p and 4K on R73 and R79 (RIFE also on R80 via a ported plugin), all the same speed within noise.
If you actually want to run R79, try this (works in both MPC-HC and SVP's mpv, RIFE and seeking fine). Don't replace anything in SVP's folder, both players can be pointed at a separate R79 folder instead:
1. Download VS-R79.zip from here and extract it to C:\ so you get C:\VS-R79\python.exe
https://drive.google.com/drive/folders/ … XX-S2JMOXD
2. Add a user environment variable (Win+R, type SystemPropertiesAdvanced, Environment Variables..., New under "User variables"):
Name: VSSCRIPT_PATH
Value: C:\VS-R79\Lib\site-packages\vapoursynth\vsscript.dll
3. Close SVP and the player completely, start them again and play a video.
The player then loads R79 from that folder instead of SVP's R73. To undo, delete the variable.
The zip is just SVP's own Python 3.12 files plus the official R79 package from GitHub.
I'm using standalone MPC-HC and standalone vapoursynth, I followed your instructions to copy the rife folder and generate.js into SVP 4 folder, and added the rife_rtx profile, but when I open a video file, it will say failed to load C:\Program Files\SVP 4\rife\akarin.dll. If I copy akarin.dll to your rife folder and reopen the video, it will say Importing the numpy C-extensions failed. Please check the screenshot attached.
nemoW wrote:Version 4.7.0.320 seems to have already been replaced by 4.7.0.321
Restart the SVP4 client to refresh the list of available updates
You're right, now I'm able to see the update in maintainance tool and install it.
In SVP it says there's an update "[VPS_64] Core for Vapoursynth 64-bit - 4.7.0.320 (2026/9/6)", but I can't find it in the maintenance tool. How can I update it?
MAG79 wrote:You can get mediainfo from your videofiles both horizontal and vertical one. And we will see the difference.
Please find attached, also I used ffmpeg -i input.mp4 -vf "transpose=1" -c:a copy output.mp4 to make the horizontal video vertical and played it, there were also a lot of stutters and skipped frames.
dawkinscm wrote:redraiderj wrote:Please find attached
Different codec and bitrate, but both are within normal parameters. It might be the weird aspect ratio that SVP is struggling with?
I don't know how SVP processes frames but theoretically it shouldn't be significantly different in terms of performance. I think maybe dev team can check if they need to process vertical frames in a separate way?
I'm using 5070Ti with SVP, and I have two 4k monitors. I mainly use the horizontal one but occasionally use the other to view vertical videos. I have a RIFE profile which uses 4.4v2 model for 4K videos under 30FPS, and it works almost fine for horizontal 4K 30FPS videos, like 4 skipped frames out of a 3 minutes video, but when I try to play a vertical 4K 30FPS video it keeps dropping frames with noticeable lag. Is there any difference when SVP processes horizontal and vertical videos? The pixel amount should be the same I guess.
dawkinscm wrote:redraiderj wrote:4.24 is out, anyone tried it?
Yep and and my advice is don't bother. v4.18 is still the best for live action and even the dev has updated the README to agree.
Thanks, but where can I see the readme?
4.24 is out, anyone tried it?
You can use standalone MPC-HC with standalone VapourSynth, I tried use embedded MPC-HC and VapourSynth but it just didn't work for me
Never mind, thought there would be some benefits
Will SVP update the components accordingly? And if not, how can I manually update them in my computer?
I'm using 3070 and I can get 720p@120Hz with 4.14 model, 1080p@60Hz with 4.13_lite and 1440p@2xFPS with 4.13_lite. 4.9 should cost less than either 4.14 or 4.13_lite, so your 3060Ti should at least easily process 720p@60Hz or even 120Hz without any issue.
cemaydnlar wrote:I tried both disabled and enabled performance boost for v2 but still not working. I know that normally even a 3090 would struggle but i am watching animes on a 1080p monitor and use downscaling method from svp than i upscale it back to 1080p with anime4k. I use x3.
You have to put v2 models under rife_v2 folder, not the rife one, the full path would be like C:\Program Files (x86)\SVP 4\rife\models\rife_v2
reconhell wrote:When you download new rife you get 2 folders. normal and V2, which to use?
Also which is better lite or normal rife?
I'm using 3070, v2 doesn't work at all for me, while normal one gives me a lot of stutter, I have to switch back to 4.9. I think you can just try both and see how they work.
Chainik wrote:both profiles match any interlaced video regardless of its resolution
source frame area = A
framerate = R
interlaced = I
now you have: (A and R) or I
while you probably wanted: A and (R or I), which is equal to: (A and R) or (A and I)
Thank you!
I have created profiles for HD, FHD and UHD based on the framerate and source frame area, and they are working fine. But today when I play an interlaced video, I notice it doesn't fall into the correct profile. If I play a 1080i video, whose frame size is 1440x1080, it should fall into the FHD profile but it goes to HD profile. Can someone please let me know how to change my conditions?
I updated my SVP to the latest version and noticed that I can use RIFE 4.9 model, but after switching when generating the model files I noticed some warnings. Do they matter? How to fix them? Here is an example:
"[W] [TRT] Skipping tactic 0x0000000000000000 due to exception [] Mismatched type for tensor (UnnamedLayer_ 106) [Shuffle]_output', f16 vs. expected type:f32."
Please check the screenshots for more details.
Posts found: 1 to 25 of 31