Search options (Page 14 of 18)
cemaydnlar wrote:Tried everything seems like v2 does not work on 3070 plus i am having frame drops on 4.13.
A 3090 would struggle with 4.12+ that is why 4.9 is the default.
cemaydnlar wrote:They should somehow start to find a solution to make it use less gpu.
They can't at the moment. The models are getting better which is why 4.9 is the default, not 4.6. But as they get better they become more compute intensive. I assume that it would take a paradigm shift in model building before that changes. I'm just hoping that it gets just better enough to remove any obvious remaining artefacts without requiring a 4090.
cemaydnlar wrote:I can't use v2 on any version of rife. Do you guys know why plus %100 sct makes soap opera effect dissapear so i switched to %20.
You can either completely uninstall SVP then reinstall. That should fix everything. Or you can delete the files from the v2 folder and download the models again since there was a mixup with some of the model files. If you don't know where the files are, then reinstall and follow the instructions in the RIFE AI FAQ. That way you can be sure everything is setup correctly.
After a bit more experimentation I've found that Rife v4.12 with SC=7.15 works best for my VR setup so far. It is the best balance I've found between fast movement and slow panning. Reducing SC like this make the fast action a little less smooth with occasional repeated frames, but still clearer overall because the artefacts are gone. With the most recent builds of mpv I am able to match my VR fps using Fixed 60fps so maybe that helps. It seems to reduce GPU usage as well which I assume is because it's not interpolating as many frames.
Rife v4.13 is out. No obvious difference with v4.12 for me, maybe others will find something. They've also re-released Rife v4.7-4.12. No major differences found with v4.9.
Interesting. I found 9.1 to use a bit more of everything with no obvious improvements and the Dev notes seem to confirm my findings.. I think 9.2 just a fix for the crashing issues but let us know what you find.
Gippy wrote:Has RIFE become any faster? Do you still need a 4090 to go from 4k24 to 4k120 in realtime, without the use of TensorRT pre-caching? Or is a less powerful card good enough now? I'm considering a 4070Ti but am concerned that just won't be fast enough for RIFE 4k24 to 4k120.
No it's not becoming faster. After v4.6, Rife is effectively becoming slower because the models are getting bigger and more compute intensive. Rife v4.6 is about 20% faster than v4.9 which is about 20% faster than v4.12.
redraiderj wrote: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.
For live video the Rife 4.12 handles some fast motion better but for the most part you won't notice a difference compared to Rife 4.9. So depending on what you are doing, most users shouldn't bother with Rife 4.12. I know with my workload even a 3090ti would struggle.
Xenocyde wrote:flowreen91 wrote:P.S. OMG setting "Scene change threshold" to 100% makes the video look amazing just like the old "Uniform (max fluidity)" setting from https://www.svp-team.com/wiki/Manual:FRC
Why did nobody mention this before? Will only use this from now on. Many thanks!
Woah, I switched SCT to 100% and ya, can't really see any artifacts and sudden camera moves seem almost perfectly smooth on default 4.9.
I checked with my test files and anything over 15 gives a similar or the same effect for me which is basically what I have seen before. The major fast motion artefacts are still there, but this time I did see an improvement to a minor artefact. So for now I've set mine to 20 and will see how it goes. It would be interesting to see what the Devs think about setting to a 100.
Blackfyre wrote:@Chainik regarding "Scene Change Threshold", it's interesting how it works like artifact masking in the past. 15% provides the smoothest panning shots and the most artifacts. 6% shows the least artifacts, but less smoothness. 1% (set manually from all settings) has ZERO artifacts, but LEAST smoothness.
I use the same 3-8 movies scenes to check for panning smoothness and artefacts. I've tried SCT set to anywhere between 1 and 20% and 12% is the best balance I've found between artefacts and smoothness, especially with Rife 4.9 and above. I think I will play around between 13 and 15% for future testing.
reconhell wrote:How do I update to the latest version of RIFE for live conversion?
...
Why does my SVP screen does not show "engine" or "performance boost"?
Also I tried this and i have the files on location like in screenshots. but the dropdown box in SVP doesnt show any new option...
- Uninstall SVP completely.
- Reboot your machine
- Follow the instructions on this page https://www.svp-team.com/wiki/RIFE_AI_interpolation.
- Choose Rife 4.9 or if your GPU has problems then choose Rife 4.6.
Harze2k wrote:Just one more question you might know, when using svp with plext htpc. i cant see the ffmpeg.exe in any folder on my device, is that somehow included somewhere else?
a lot of the logs in mpv that points to issues, fails or error has ffmpeg in them but i cant find that executable anywhere.
MPV uses ffmpeg libraries for codecs, shaders etc. So even the Plex "fixes" are fixes to ffmpeg not mpv. The rate of development for ffmpeg is ridiculous considering the size of the project: https://github.com/FFmpeg/FFmpeg/tree/master
Harze2k wrote:yeah i got a 14900KF so the cpu part is covered,
You can say that again lol.
Harze2k wrote:ill check the pre built libmpv from the link you sent, cheers!
What site did you say had the plex fixes?
https://github.com/mitzsch/mpv-winbuild-cmake is the site. It also provides info on creating a Linux mpv build environment. Or you can use https://github.com/m-ab-s/media-autobuild_suite to create a Windows build environment but it's not MPV centric and I found builds failed more often. It's also extremely slow, a full MPV build with Plex extras takes about 30+ minutes.
There is a version with some minor fixes for Plex you can build and I can show you the web page on how to start. You basically need to set up a full Windows or Linux gcc or Clang build environment. It helps if you have a PC with a modern CPU. But if you just want the latest mpv then download the latest version of libmpv from https://sourceforge.net/projects/mpv-pl … dows/files
Yeah I saw it earlier but I didn't bother to update because after testing it doesn't seem to be any different from 4.12lite or v9. I will wait for a full v4.13 or maybe 4.14 before commenting on here.
Blackfyre wrote:Will this driver scheduled for later today promising 5x the performance increase for TensorRT-LLM for 3000 and 4000 series GPU's have an impact on us using RIFE? I assume no.
Or will this improve performance for us? Or maybe something that needs a RIFE update to utilise version 0.6.0 benefits? Not sure. Just asking.
NVIDIA states a 5x performance boost with TensorRT-LLM v0.6.0 which will be available later this month
https://wccftech.com/nvidia-brings-up-t … x-30-gpus/
Chainik wrote:how exactly "a library that leverages NVIDIA RTX architecture for accelerating large language models (LLMs)" is connected with us?
odedg wrote:After trying 4.9 VS 4.12 Lite at least on performance aspect I can't see any difference at 4K on RTX4090 & i9 11900K. Same usage & power draw on both.
Yep. There may or may not be differences between the two for Anime. But for live action I couldn't find a clear difference although 4.12 might be slightly better for fast motion.
odedg wrote:What is the difference between 4.9 and 4.12 lite versions ?
If I would guess lower picture quality better performance ?
And if so is it easier on CPU or GPU or Both ?
Very little difference. So try both and let us know what you think.
RAGEdemon wrote:I think your post will be reverenced many times going into the future... 
Everything needed is already on this SVP manuals page https://www.svp-team.com/wiki/RIFE_AI_interpolation The extra stuff you've seen some of us doing here is interesting but not necessary for Rife. Especially since the SVP devs recently created a script that does most of the extra stuff for you.
The instructions you need are as follows:
1. Download and install SVP.
2. Follow the Rife AI manuals page.
3. Restart SVP.
4. Don't worry about the experimental stuff myself and others are doing because for most it's more likely to break your install than help it.
Chainik wrote:don't you know that SVP works via vapoursynth filter? 
I'm pretty good at getting things working without know too much about them then I eventually learn more as I go along. I am still learning about all of this stuff. I know nothing about vapoursynth except that it is similar to avisynth and that has it's own library of ffmpeg based filters?. So since mpv uses filters based on ffmpeg I assume that vapoursynth is using the same filters?
I checked out base.avs but saw nothing there.
Sorry to bother you but as I asked for above, where would I look in future within SVP code for something like this? Where were/are the mpv filters used?
Thanks. I would never have guess that SVP would be the cause of this. For future reference, where in SVP does it use/remove mpv filters?
The changelog says:
= adjusted for recent mpv (pre-0.37) changes
Does that include making sure that deprecated options have been accounted for?
aloola wrote:dawkinscm wrote:aloola wrote:can anyone run model 4.7+ V2 with "performance boost" Disabled?
I can run model v2 4.7>4.11 with "performance boost" enabled but not when disabled
also, 4.12 lite is out.
my benchmark on blank clip 1080p, all model v1
Output 8000 frames in 34.47 seconds (232.12 fps) 4.0
Output 8000 frames in 34.14 seconds (234.35 fps) 4.4
Output 8000 frames in 33.90 seconds (235.99 fps) 4.6
Output 8000 frames in 45.65 seconds (175.26 fps) 4.7
Output 8000 frames in 46.70 seconds (171.29 fps) 4.9
Output 8000 frames in 63.21 seconds (126.56 fps) 4.11
Output 8000 frames in 63.36 seconds (126.26 fps) 4.12
Output 8000 frames in 50.69 seconds (157.83 fps) 4.12 lite
4.0: 98.36%
4.4: 99.30%
4.6: 100.00%
4.7: 74.31%
4.9: 72.58%
4.11: 53.64%
4.12: 53.48%
4.12 lite: 66.88%
The aim of the 4.12 Lite version is to make it less GPU intensive of 4.9. So it should arguably be called 4.9 Lite. But I'm just glad they are releasing updates and trying things.
have you tested with SVP? The SVP script needs to be updated to work with 4.12 lite.
you can easily check this by going to the cache folder to see if there is any model cache name 4.12_lite
Yes I tested it and as discussed it is almost identical to 4.9. I saw that SVP couldn't handle the name so I just renamed it and it works fine.
@Chainik Have you had a chance to look at my mpv question?
aloola wrote:can anyone run model 4.7+ V2 with "performance boost" Disabled?
I can run model v2 4.7>4.11 with "performance boost" enabled but not when disabled
also, 4.12 lite is out.
my benchmark on blank clip 1080p, all model v1
Output 8000 frames in 34.47 seconds (232.12 fps) 4.0
Output 8000 frames in 34.14 seconds (234.35 fps) 4.4
Output 8000 frames in 33.90 seconds (235.99 fps) 4.6
Output 8000 frames in 45.65 seconds (175.26 fps) 4.7
Output 8000 frames in 46.70 seconds (171.29 fps) 4.9
Output 8000 frames in 63.21 seconds (126.56 fps) 4.11
Output 8000 frames in 63.36 seconds (126.26 fps) 4.12
Output 8000 frames in 50.69 seconds (157.83 fps) 4.12 lite
4.0: 98.36%
4.4: 99.30%
4.6: 100.00%
4.7: 74.31%
4.9: 72.58%
4.11: 53.64%
4.12: 53.48%
4.12 lite: 66.88%
The aim of the 4.12 Lite version is to make it less GPU intensive of 4.9. So it should arguably be called 4.9 Lite. But I'm just glad they are releasing updates and trying things.
I'm getting an error message when SVP stops working properly with the latest versions of mpv and Plex. This doesn't happen on the first video played. It happens after the first video is stopped or finished. The once the pipe/socket is disconnected it doesn't seem to get reconnected to any other video until I exit Plex and start again. The error message says "Option vf-del : 0 Doesn't exist" because they the "-del" option has been deprecated in the latest version.
donnieyeen wrote:@Chainik @aloola did any of you try the new TensorRT 9.1.0?
v14.test2 pre-release uses trt 9.1.0 + cuda 12.2.2 + cudnn 8.9.5, which can only run on driver >= 525 and 10 series and later gpus, with improved support for self-attentions found in transformer models.
It does much faster compilation of cache. It used to work with previous version of SVP4, but now I can't get it to work anymore. I am going to buy the SVP4 licence today, really like this program and smooth playback.
When I get home I'll test the V2 models, also @aloola shoot me your discord, can add you and we can talk some video players
I got it working last week but it doesn't very well consumer GPUs.
Chainik wrote:> only the folder issue is still present
no idea, it's still
> os.path.expandvars("%APPDATA%\\SVP4\\cache\\")
in vsmlrt.py
Yeah that stop working for me some time ago as well. Another issue is that I can't even find the original cache temp folder the unmodified code requests from the OS. I was able to some time ago but not now.
Posts found: 326 to 350 of 442