Which TV? I can help if it's an LG C series one.
You are not logged in. Please login or register.
SmoothVideo Project → Posts by Blackfyre
Which TV? I can help if it's an LG C series one.
Quick fix change the name of the model like 4.30 build engine run and create a new, testing...
This worked with the two new released Heavy & Lite versions that just came out. Renaming them to 4.30.
Having said that, artefact masking is not as good as the original 4.25 that was released as a beta.
I am glad that was released as a beta, because that older one still remains the best quality version IMO and better than 4.18 too.
rife_v4.25_heavy - 153 MB
^^ Has been released around 5 hours ago. Tried to test it, but this is the first time I come across this problem; even when selected in SVP it does not work, it goes back to the previous version I had selected when running a video, so cache for "heavy" does not even build.
Not sure if something needs to be updated for it to work properly.
I only tested v2 btw, did not test v1
I am watching mostly 4K Movies in MPC-HC.
I have an RTX4090, so performance shouldn't be an Issue.
Performance will be an issue. RIFE is extremely demanding, so it depends on your refresh rate and what you are trying to push at default.
Are you dropping frames or having any delayed frames when looking at the stats in MPC?
Try using RIFE at 2x instead of "to screen refresh rate", to test if running at 48 FPS it works without issues.
I also recommend you download rife_v4.25.7z from Sep 19th from the link below. Not the LITE version from a few days ago.
https://github.com/AmusementClub/vs-mlr … nal-models
Copy the rife_v2 folder from that file above and place it below next to the rife folder:
C:\Program Files (x86)\SVP 4\rife\models
Now restart SVP (exit and open it) and you should see 4.25 v2 as an option to select, right now it's the best version available for quality.
Remember, the first time you run any NEW resolution, RIFE will have to build CACHE for that resolution for that RIFE version.
That takes time, just let it build in the background.
When you are free and happy with a RIFE version, run a bunch of movies and tv shows one by one to build the cache for each different resolution.
Rife v4.25 lite is now available for anyone who is interested.
Lots of artefacts in some test scenes. Similar to, or worse than 4.26
Back to my preferred ones below:
4.25 v2 < 1699
4.16 Lite v2 > 1700
updated vsmlrt.py to fix "Blackfyre's V2 shaking"
@jdg4dfv7
Thanks for all the info, I'll read all of it in detail later, but I skimmed through it and wanted to note that the 4.26 model definitely showed heavy artifacts in certain scenes I tested that were not present in 4.18 and 4.25. I gave the No Time to Die example before, but I noticed it elsewhere too. Maybe I will test again and see how it goes.
Another thing I wanted to note is 3840x1600 is what I call 4K letterbox, but there are a lot of IMAX releases too for the past few years, which are actual full scale 4K (or switch to it in many scenes), this also applies to some TV shows that are full scale 4K and not limited to 1600 vertical pixels.
This is why I use 4.25 v2 for 3840x1600 or lower at x2, and I use 4.16 v2 for full 4K at x2
3090 is only capable of pushing x2 and v2 models perform better than v1
The 5080 news sucks, but I am hoping the 5090 is not ridiculously priced in Australia (but it looks like it will, and I might just stick with the 3090 until it dies out now if the performance difference to the 4090 is not substantial).
Can someone explain which settings are the best for a 4090 on 7950X3D to run 4K videos? 4.16_lite or 4.18? How many GPU threads, etc?
Remember the first time you run any new video resolution with any changed RIFE version the popup comes up and cache needs to be built. Every time after that, with the same RIFE version and same resolution you previously ran, it should start immediately.
Just wanted to provide that note, as people aren't aware sometimes they just have to wait for that popup to finish its thing and not close it.
Okay, I have an RTX 3090, so I will speak from my experience with that and scale up for the 4090.
Instead of interpolation To Screen at the top, I run Movie x2, and using a program called Custom Resolution Utility (CRU) I create a custom resolution to create a 48Hz refresh rate 4K to switch to in the nVidia control panel when I want to watch a TV show or movie.
With an RTX 4090, if you can change your refresh rate to 4K 60Hz, 10bpc, RGB, full and perhaps test using To Screen, which will interpolate to 60 FPS at 60Hz, you might be able to push that, hopefully. I can't with the 3090, but perhaps that 4090 is able to do 60 FPS @ 4K, if it can't test Movie x2, and if that works properly, then crease a custom resolution with the method above using CRU.
Matching the FPS and display Refresh Rate gives a smoother experience. I had issues with VRR working properly before (flickering on OLED), so that's why I switch everything manually myself.
For the best RIFE version to use, the developer says 4.18 is the best one, but IMO the best version I have used, with the least visual anomalies, is version 4.25, which was a beta version of 4.26 (which for me is the worst).
Let me know how it goes, as I am interested in knowing the 4090 performance, if the 5090 is too expensive, I might switch to a 4090.
Is anyone having success using rife 2x framerate 48fps or more with an rtx 4080 super?
I have 12700k 32gb ram, 16gb ram on gpu.
I cant find much anecdotal comments on people having success with RIFE with UHD content without a 4090.
I am having stable smooth interpolation only at 1080p 48 fps, anything more than that jitters or plays in slower motion including slower audio.
RTX 3090 and I didn't upgrade to the 4080 Super because I saw reports before that people who upgraded struggled.
But surely it depends on which model you are using.
First of all, I recommend testing with RIFE 4.9
Second test with v2 Models, as they perform better. But you need to scroll up and find the files on the last page or page before that to replace, so it fixes screen shake issue that happens with v2
Third, overclocking MEMORY clock speed helps RIFE performance.
This below is basically the reason why the RTX 3090 outperforms the 4080 and 4080 Super with RIFE, someone can correct me if I am wrong:
The RTX 3090 boasts an additional 8GB of VRAM and features a broader 384-bit data bus, surpassing the 256-bit memory of the RTX 4080. Furthermore, its impressive 936.2 GB/s memory bandwidth is a 30.6% advantage over the RTX 4080’s 716.8 GB/s.
4.18 is the best nose.
4.15lite is a little worse.
4.26 is the worst nose, it doubles.
4.26 was the worst for me as well in my testing, it was very stable in some scenarios, but horrible in others.
If you never tried 4.25 by the way, give it a try. I use it instead of 4.18 now for 4K ≤ 1699 frame height. If you have the 4090 you can use it for everything.
Works with Vulkan but when I put on TensorRT a command window pops up and freezes the video. Any suggestions? If not, where can I find a previous version to download?
It is rebuilding the cache for every resolution. So every time you open a new resolution it will build the cache for the first time.
Just wait for it to finish, takes time.
If you play the same video twice, the 2nd time and every time after that it shouldn't pop up. Only the first time.
Just remember to open a bunch of resolutions, like 1080p narrow, 1080p IMAX, 4K Imax, 4K letterbox, etc
This happens also every time you change RIFE version and test a different one. It has to build the cache for the new RIFE version you choose. So if you test different RIFE versions, it will happen too.
Firstly flowreen91, great work on the changed files.
I downloaded and changed the default ones in rife and script folders.
.
RIFE 4.6 (very old model, fastest) - 112 fps
RIFE 4.15 lite (decent progress, exploring lite models) - 100 fps
RIFE 4.26 (finished trained 4.25) - 86 fps
RIFE 4.25 (very good breakthrough after 4.18) - 84 fps
RIFE 4.18 - 75 fpsI did speed test (with old SVP build)
Thanks for this, great work.
Wow, 4.26 has almost no interference artifacts.
4.25 v2 remains the best one for artifacts with my testing.
4.26 v2 failed the No Time to Die test at around minute 3 with the sliding glass door (most difficult scene I test). In fact it was the worst I have seen during that specific scene, but in other scenes it performed better than others.
I have reverted back to 4.25 v2 personally. Interesting that after it finished training (became 4.25), artifacts became worse.
Link not there above, where is everyone getting the Google Drive links for beta and alpha versions? I can't see on github a link to them.
Nice! Please check so we'll conclude if we can fully remove/ignore the v2 models.
So from the simple tests I done above, there is a clear difference between v1 and v2 as shown when testing with model 4.18 v1 and v2 and that is at 4K (3840 x 1600 resolution).
If someone can do the more advanced testing that you mentioned which lowers the resolution more and pushes for very high frame rates, the difference should be very clear between them when comparing frame rates as opposed to GPU usage like me.
Testing should be done with 4.18 v1 and v2
v2 shows a performance difference when using 4.18 vs 4.18 v2 while watching 4K not full screen (Rings of Power season 2).
So there is certainly better performance for v2 model here @flowreen91 achieving the same results while using around 7% to 10% less GPU power, which is a big difference.
That's more advanced testing than what I do ^ I'm just doing simple testing with samples I am familiar with.
The way I am testing is using MSI Afterburner to monitor GPU usage while using v1 and v2
Initial quick test, I can confirm 4.16 Lite and 4.16 Lite v2 are both performing similar (GPU usage between 82% and 90% when using full 4K), so SVP Devs are maybe right, and my ORIGINAL post before which I edited was most likely correct too. (Edit: check comment below, more powerful Rife 4.18 showed performance difference better)
Because I was testing with v1 and v2 after the update and was seeing similar results, but then I discovered the screen shake problem, which made me change vsmlrt.py and that caused performance changes because it wasn't working properly? (not sure, need more testing).
So the only problem that needs to be fixed is the screen shake issue? (Edit again, nope, v2 performs better still, so might be time SVP add it as an option).
The fixed files posted on the last page work fine.
For reference, there was a time when the performance below would have been 100% gpu usage on v1 and 82% to 90% on v2, that seems to be no longer the case, it's not as big a gap now? (Edit, again there is a performance difference, as seen below).
Blackfyre wrote:To test properly, remove all the models inside v1, so SVP doesn't fall back to them. That's what I am doing.
Yup doing that and works for me with files attached above:
https://gyazo.com/a8b01ddcff578c3033de7b50522481a1
Try to delete the old cache folder from here "C:\Users\Blackfyre\AppData\Roaming\SVP4\cache" and restart SVP maybe?
Files attached above are working correctly now after restarting the PC.
Closing SVP and opening it before was not working.
I'll delete all the cache files too
I will put back v1 models and test performance difference now between v1 and v2 properly.
This explains why I was seeing equal performance before.
To confirm the discussion above, I went to the rife folder and deleted all the models inside rife, and only kept the ones inside rife_v2
RIFE is not working without the v1 models, so basically it means it was just using v1 models even when v2 was selected?
Attaching sending video_player False to RIFE as dawkinscm suggests in helpers.py
Tested with these above and also rife v2 is not working.
To test properly, remove all the models inside v1, so SVP doesn't fall back to them. That's what I am doing.
Now I need to find a way to make v2 work.
I guess for now, discard everything I said above until I test on a new setup.
Formatted, clean Windows install. Clean SVP install.
Can confirm 100% the shake issue is there for v2 until I update vsmlrt.py which solves the problem as outlined above.
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. ^_^
Maybe because I had updated stuff manually before, SVP failed to update some sections (such as the latest vsmlrt.py) when it done the other updates.
I will be formatting my computer soon, so I can test on a full fresh install as well.
I guess for now, discard everything I said above until I test on a new setup. Or someone else can confirm the issue with the example I listed above.
I believe that all "fixes" the latest vsmlrt.py contains are included in SVP's one
Perhaps someone else can test and see to confirm v2 screen shake issue. Solved by updating to the latest vsmlrt.py
Testing was done with 4.16 Lite (v2).
First episode of Ahsoka below is very easy to notice, around minute 2 and 17 seconds, the highlighted area in the image below (vertical and horizontal neon lights) shake. The ones on the left side of the image do not shake.
Ahsoka.S01E01.HDR.2160p.WEB.H265
Updated comment above multiple times for accuracy. Also thanks to flowreen91 for posting the original fix for screen shaking in some scenarios while using v2's
SVP packages updated: TensortRT 10.4.0, vsmlrt 15.4
Edit: Making corrections as my previous statement was false in regards to performance.
There is still a performance difference between v1 and v2, and v2 still performs better, but the gap is smaller than what it was before. Good update overall, but it reintroduced an old v2 problem I had previously solved.
For those who are using v2. If you notice screen shaking in some scenes, or on certain elements on screen only. The fix is simple and I will post it below.
If you do not notice this screen shaking with certain elements or background items in films or shows, then do not worry about this, and this ONLY applies to v2 and advanced users who mess around with RIFE.
NOT for default users (you will not experience these issues).
Now for the fix.
Go to the link below, scroll down, download scripts.v15.4.7z (current latest), extract and copy vsmlrt.py and place it in the C:\Program Files (x86)\SVP 4\rife folder and overwrite the one that comes with SVP.
The updated script should fix the screen shake problem:
https://github.com/AmusementClub/vs-mlrt/releases
Thanks to flowreen91 for identifying the problem 20 or 30 pages back and posting the solution.
I'm on an RTX 3090 so cant speak on the performance of the 4090 and if it's capable of doing full 4K at 60FPS with RIFE 4.18 for example, but personally I am waiting for the 5090 release.
You can also ask in the RIFE thread regarding RIFE performance questions, as most people only check that and not other threads.
madvr is long dead. Use mpv with 4k x2 custom resolution on tv 48 Hz or 50 Hz with +few % speed up
4090 should be enough for that rife
Best advice here.
Forget MPC and Madvr, switch to MPV.
RTX 4090 should be more than powerful enough to push 4K at 48Hz.
You can create a custom resolution (keep it 4K) with a custom refresh rate (48Hz) using a program called CRU. Hopefully that works with your projector.
Then you use RIFE version 4.18 (best one for movies) with MPV and at 2x should convert all 24fps films to 48fps, and I can give you my MPV configuration to help as well.
If you need help, let me know. If I don't see your replies here, private message me so I come back to check here.
SmoothVideo Project → Posts by Blackfyre
Powered by PunBB, supported by Informer Technologies, Inc.