hwdec=d3d11va-copy
What happens if you use hwdec=no ?
You are not logged in. Please login or register.
SmoothVideo Project → Posts by zxcvbnm821
Pages 1
hwdec=d3d11va-copy
What happens if you use hwdec=no ?
V2 models for some reason have jiggling, the more to the right and down, the worse the effect. Almost unnoticeable for 1080p, but very annoying for 1440p and 4K (both native and downscaled to 1440p, here's the example - https://cdn.discordapp.com/attachments/ … WGll8w.mp4). For this one, I'm running Game of Thrones S1 E1 at 4K on 3440x1440 (so SVP downscales to 2560x1440) at x2 framerate on 2080 Ti with 4.4v2, 4.6v2, 4.9v2 and 4.13_litev2. There's no such effect on V1 models (tried all same versions)
I have the same problem here too
tried using v14.4, but the problem was not fixed
The same problem occurs in Dolby Vision movies
before
after
before
after
Is this a BUG?
RTX4090 1080P x5
Very smooth when using V2
But when I use V1, sometimes there will be a stuttering
Now I use V2 when watching 1080P, and need to switch back to V1 when watching 4K
This is inconvenient, hopefully V3 will fix these issues
I recently started using MPV because of RIFE
Need to wait 4-5 seconds when skipping forward/backwards, this makes me impatient
I used to use mpc with avisynth without these problems, it only needs 0.1 seconds of buffering time
I heard that the reason may be from vaporsynth
RIFE has to work with vaporsynth, so is it impossible for me to fix this?
Hello everyone, would it be better for RIFE to enable NVIDIA Optical Flow?
To anyone confused, these are the full instructions to get the best setup going right now as far as I am aware. Please correct me if I'm wrong. With all due respect to Chainik, I think they're too smart and could benefit from giving a little more detail in the instructions for us non-developers.
1. Install SVP - select whatever player you want, I'm using MPV because back in the previous pages people claimed it was faster than MPC-HC/BE.
2. Go to Utilities -> Additional Programs and Features
3. Install the RIFE AI thing and the Tensor RT thing at the bottom. I also chose MPV Shared Libraries, not sure if it matters.
4. Restart the program.
5. Download the V2 model folder from here. https://github.com/AmusementClub/vs-mlr … e_v2_v1.7z SEE FOOTNOTE - MAYBE STOP HERE FOR NOW
6. Extract the "rife_V2" folder into your models folder (SVP 4\rife\models) so it sits beside the "rife" folder.
7. You should have a path like "C:\Program Files (x86)\SVP 4\rife\models\rife_v2\rife_v4.6.onnx" when this is done.
8. Download the updated vsmlsrt.py from here: https://www.svp-team.com/forum/misc.php … download=1
9. Replace "SVP 4\rife\vsmlrt.py"
10. Restart SVP 4.
11. Now you can select your settings as before. This seems optimal for me:
12. The thing here that confused me is that you don't have to select the V2 model specifically. It seems like SVP chooses the V2 model automatically if the folder structure exists like that. So you'll be using the non-ensemble V2 rife 4.6 model by default if you have your thing set up like mine.
13. I'm doing x3 for 21:9 1080P and below, and x2 for 4K and 16:9 1080P. Seems to work okay with a 3090 though I've only tested a couple videos, I'll report back.
14. The threads doesn't seem to make much of a difference.Thank you to Chainik and the SVP team (IS there a team?) for making a great program, and thanks to UHD and everyone else who has contributed to this thread. The RIFE interpolation looks so good. I look forward to seeing it progress, and eagerly await the theoretical RTX 5090. Told myself I'd sit out this current generation now that GPUs cost more than my first car.
---
NOTE: If you read further down, we've determined V2 may be substantially reducing visual quality (at least at 4K). Recommend sticking with the out of the box RIFE model configuration for now. (V1 4.6 + TensorRT + performance boost).
---
Do I need replace the updated vsmlsrt.py if I don't use V2?
I get this error when I use RIFE, please help
Pages 1
SmoothVideo Project → Posts by zxcvbnm821
Powered by PunBB, supported by Informer Technologies, Inc.