For those interesting Model 4.26_heavy its out , for me at least don't work as well as 4.25, maybe for those with 4090 will.
You are not logged in. Please login or register.
SmoothVideo Project → Posts by Drakko01
For those interesting Model 4.26_heavy its out , for me at least don't work as well as 4.25, maybe for those with 4090 will.
all files
dunno which Python version it wants, probably you have to replace portable Python too
Thanks, I think better leave like it is, wait until you decided update on the future.
> I dunno if there a real benefit
nope
> How can I test R70 vapoursynth
put portable release into SVP 4/mpv64
Thanks for respond, which file do a put into mpv64 folder, if copy the entire folder i get unable to initialize vapoursynth api 4.0 error
How can I test R70 vapoursynth instead of R64 provided for svp, and you have plan to updated ? I dunno if there a real benefit but a think so many things fix/changed on it , that a like to try it. So if someone get me pointers , it will be very appreciated.
I don't know why, but after trying a crap ton of different options and combinations I can’t get SVP RIFE to do smooth 60fps playback.
There are always some microstutters/hitching and Dropped/Skipped/Delayed frames when I use SVP with RIFE, even with low CPU and GPU % usages (I'm using scaling to QHD 1440p and black bars on a RTX4080 and Ryzen 5950x).
If I disable SVP there are no Dropped/Skipped/Delayed frames or stutters/hitching.I tried MPV, PotPlayer, MPC-BE, VLC with all available video renderers and video decoders in each one, and the same happens in all of them.
All that I tried in detail here: https://www.svp-team.com/forum/viewtopic.php?pid=85781
TL;DR Can any of you play this file ( 30 seconds long dolly from Unbelievable 2160p DV HDR ) at 60fps perfectly fine with no Dropped/Skipped/Delayed frames and no visible hitches/stutters?
Give a read to this if you haven't already https://www.svp-team.com/forum/viewtopi … 057#p82057
Drakko01 wrote:Blackfyre wrote: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.
Exactly right, it kinda like the new 4.25_heavy, but reintroduce some artifacts the most models has for especific scene that 4.25 was fixed already, I hope see a combination of the two in the next model
Are you seeing any difference between the old v4.25_heavy and the new smaller one? Have you guys tried the new 4.25_heavy with SC disabled?
I only have the smaller 4.25?heavy 82.6MB, glad to look into the differences of the old 4.25h if you provide a link for download the file.
I like very much the smoothness of heavy version, most of the time , but with miss the interpolation in some scene at the point that can't used instead of 4.25. If this " errors" where fix maintaining the overall smoothness or fine a way to eliminate/minimize I will be glad to use 4.25h as main.
I give you three examples that what i'm saying for you to test. Comments are appreciated.
Avengers at 1:53:23 after Hulk jumps of the 3° building
Avengers Endgame at 2:19:12 after Drax stab Cull Obsidian , and Pepper(Rescue Armor) fly across the screen
Spiderman No way home at 38:00 when spiderman drop hanging of the bridge after the car fell. And 38:20 after Doc OP take the nanotech and camera pans 360 around him.
Am not saying that 4.25 make this scenes perfect, but managed in a way much less disrupted.
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.
Exactly right, it kinda like the new 4.25_heavy, but reintroduce some artifacts the most models has for especific scene that 4.25 was fixed already, I hope see a combination of the two in the next model
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
Same here, for me it use the 4.25 profile that was already build and not run another pass
Quick fix change the name of the model like 4.30 build engine run and create a new, testing...
For me 4.25 heavy FIX smoothness
Yeah I agree! this model is more smooth at least i gives me that impression.
BTW All this around the 4.25 model make felt good to myself about to 4.26/4.25 debate. I don't want to say I told you so, but I told you so.:D
Nope no dice. It looks like its dropping frames doesn't report that it is. I've just tried an AI Enhanced version of Wolverine Deadpool and I can notice the smooth motion immediately. At the same settings reported at 60FPS (Rife) it doesn't look smooth. If I turn on the OG frame interpolation, again I notice it (and the artifacts straight away).
I'm coming close to doing a clean windows install at this point.
You try with other player, to see if not mpv ?
Hello,
I recently had SVP before reinstalling windows 11 on my PC, and it ran absolutely fine.However, after reinstalling Windows 11, my SVP has a little problem. I try to watch a file (.MKV) it switches my colour scheme to basic! I wonder if there is an option SVP automatically enables which switches MPC to go into basic mode when loaded?
I have a powerful PC and this doesn't seem right..
If you have something like this, Mpc Render will change your display to basic
The problem is with mpv and SVP both, because this issue happens too often realtime playback, doesn't necessary for example videos...
Do you try it with this scene?
In my case for the example scene, happen exactly same position same way every time except on v4.25
@jdg4dfv7
Ok, a lot to read. Let's start by making the following clarification, when I mentioned not being interested in 0.25 speed test, I meant not doing it. But in no way was my intention to minimize your efforts in testing it in a less flawed way. I doubt that this matters to you, since you are not here for the opinions of others. I really appreciate and see the value of this type of tests, but I am convinced that the real benefit of your tests is directly with the Rife developers and I don't believe they see it as child's play, your findings may lead them to see something they can improve and extend the benefits to all of us.I encourage you, if you don't already do it, to send it to them in some way.
After reading everything else the only thing I can say is, thank you for taking the time to test and respond but from here on out I am not going to quote directly or respond to any of your post. Because I can see that it's just going to lead to endless, pointless arguments that benefit no one. And in a few days the thread will probably have 200 worthless pages.
For everyone else, I really interest on the "flawed"visual testing on normal speed playback of scene like a mentioned (Doc Op vs Spiderman under the bridge) or any other scene with obvious artifacts like this one,the kind that don't need to have superhuman vision to be able to spotted.
4) The 4.26 has significant artifacts for me even at normal playback speed, which not happens with older models, sometimes even parts of big objects interpolating separately than full object, which still not happens for older models testing, no matter what playback speed was set, I dont say 4.26 will work the same for others, atleast thats how 4.26 works for me, period!
Looking at you, and comments like this(whichever your preferred model) plus some scene example.
If you dont have the file in cuestion, can use this on youtube in the resolution you prefer or downscaling via svp.
https://www.youtube.com/watch?v=CC5c8LyPyuk&t=13s
@Drakko01
v15.5? You meant to say 4.14 or 4.15?
What do you mean by with performance?
As said, 4.26 aftter my third elaborate testing, overall the best. There is no point for me using anything else, especially since both 4.25/4.26 consume so little electricity (my rtx 4090 GPU is undervolted 0.875V).
If you don't know who you want to believe, than do your own testing.
Sorry if I was not clear, since I made reference to your post indicating v15.5 compared to v15.4, I thought you would understand that I was referring to the tensor libraries.
Notice what I wrote: I do elaborate testing; I recommend doing the same. Also test on a big screen (I test on a 55 inch Oled TV from 1 meter distance).
Testing with LCD-displays or LCD-dimming zone displays/TVs/monitors (aka misleadingly marketed "miniLED"), is not as accurate, as LCD-display technology lacks pixel-perfect dimming.
Lot of scenes across at least 10 real scene movies or animation/cartoon.
I've been using svp since its indiegogo days, and have countless hours of tests with high quality files over the years, with the advent of Rife more and more.
I agree that LCD-dimming zone displays/TVs are not as accurate as OLED ones. I work with what I have at the moment: a 65-inch Qn85B, a 65-inch NU8000 and an old 75-inch LG.
I test specifically at 0.25 speed, only this way I can perceive artifacts etc. which are not perceived even under 0.5 speed, less under normal speed (1.0)
I always do A-B repeat every scene couple of times.
I'm not interested in the 0.25 speed test, I don't think anyone here is. What interests me! is to minimize or eliminate artifacts at normal speed and have the best and smoothest viewing experience.I think that is the goal of this forum.
Additional: With v4.18 not only I noticed way less artifacts, warping etc. but especially way better image smoothness and pacing.
If there are multiple elements in the foreground, middle-ground, background, v41.8 and even better 4.26, are displaying the elements more smoothly and with better pacing.
With older models, or even with v4.18, there was more stuttering occuring; like the background element (for example a forest) was blending in more wrongly with elements of the foregound (lets say a car); both stuttered a lot, especially if the element was complex in structure (let's say a fence, a pattern).
With some scenes and the v4.18 model, I noticed the forest scene in the background was stuttering, while with the v4.25 model, even more the v4.26 model, the forest was smoothly displayed.
That means the neural network wasn't able to distinguish elements that well with older models.
I think the same but if we only talk about the v4.25 model, with 4.26 I still find errors/artifacts that are not present in 4.25, that is what I was referring to when I mentioned agreeing with dawkinscm.Beyond that I also agree that v4.26 and v4.18 are also excellent models.
A clear example of this is in Spider-Man No Way Home 2021 2160p UHD BluRay at 31:50 when the nanotech runs through Doc Op's tentacles, if you have it please test it.
And last: I'm not guessing or have to rememver what I found 1 month ago either, because I write down everything I notice.
I have a full, long text file were I wrote down all of my findings, back to v4.17.
I don't have to guess or remember, I simply know what my test scenes look like with each model and I come from Rife 4.4/4.6 going through all the models up to the current ones.
If you don't want to believe any of us, than maybe you want to believe the developers themselves?
"Currently, it is recommended to choose 4.26 by default for most scenes."
The goal of the Rife developers was not always aligned with what we are looking for here.
Many times the posts from members like dawkinscm,Blackfyre,dlr5668,flowreen91, to name a few, helped me recheck settings or combinations that brought me to the satisfactory point I am at now.
Yesterday, thanks to your post, I updated the tensor libraries, which improved the viewing experience with the v4.25 model.
Thank you for the time you take to both test and share it with the forum.
And the best part about the 4.25 & 4.26 models is how little electricity they need to achieve that. Tested with latest v15.5: latest TensorRT library, and a couple of movies at 3840x1600 resolution and 48 fps.
What do you think about the performance of the v15.5 compare with the previous version (15.4),Pros and cons?.
In my test with the Rife 4.18 /4.25/4.26 I agree more with what dawkinscm said, beyond the fact that I don't use that same x factor or resolution. I personally don't see the point of chasing maximum resolution, as a 4k downside of by svp, , increasing the frequency and upscalling to 4K is more than enough..
I
I don't know why, but there are always some dropped frames when I use SVP with RIFE, even when the CPU usage is always below 20% and GPU never reaches 100% (I'm using scaling to QHD 1440p and black bars).
If I disable SVP there are no dropped frames.
Any ideas or suggestions?
When you say scaling QHD 1440p, you referred to svp option decrease to QHD of a 4k file?. What crop option do you use?
What monitor/TV are used, its has gsync/freesync options.
Im have an RTX 4070ti super its not an a 4080 but close, for me some drivers no matter what have that behavior.
For now on driver 556.12, Rife V 4.25 @72hz, HDR, MPC-HC, MPC render, decrease to FHD@spline64,crop black bars, upscaling to 4k display via MPC render, there's minimal o not very perceptive frame drops.
You can also try the new MPC-HC https://github.com/clsid2/mpc-hc/releases, it has a new MPV render version with fixes and more HDR windows compatibility than previous version.
Whats the default align/valign values for SVP4 Pro? I forgot that I used 2x2 all the time, maybe thats why all models starting 4.16 looks fragmentary smooth!
Fragmentary smooth - when a small parts of one large object can be interpolated differently, even being a same large object! For example: faces, 4.4 to 4.16 faces looks buttery smooth, from 4.17 to 4.26 small parts like lips, cheeks, ears and other objects can be separated from the frame! There were cases when the lips moved apart alone, never happens for 4.4 to 4.16 before, also happens when the main object in the frame is interpolated correctly, but all the background moving both axis, looks like one step forward-two steps back frame!
The 4.26 new model is worse than 4.15 lite in Matrix rooftop 3 agents opening the doors, pattern errors on door textures, no door errors in 4.15v2 (both mod32 and mod64 input)!
Too noticeable door errors 4.4 (worst)
Less noticeable door errors 4.9 (okay)
No door errors 4.11 to 4.16 (perfect)
For testing what you stated, can you provide or indicate the exact scene.thanks
For me 4.26 works properly without change any files, I use V1 models but I test V2 only to make shure,and work properly too.
oriento wrote:new release
4.25beta - 21M - 2024.09.19 | [Google Drive](https://drive.google.com/file/d/10RhXyy … share_link) | I am trying using more flow blocks, so the scale_list will change accordingly.
how to install it? Previously I just dragged the .onnx file into the models/rife folder
Same as any otb other model, Drop in his respective folder, reopen if you have open Spv and selected in list
Totally agree, I test the new model v4.25 and very pleased with the results, i'll use as my main. Like dawkinscm hope that the next model continuing improving.
pensioner600 wrote:The movie Twisters (2024) is unpleasant to watch. 4K---1440p. When the characters broadcast, there are constant glitches on the screen. TRT9.2/4.15 lite. Can this be fixed? If I understand correctly, any other movie can have the same thing when the frame rate changes.
Answering myself and everyone. It's all because of black bars detection. Why is it enabled by default??? When the size of the displayed area changes in a movie (for example, a character is filming with a video camera), new black bars are detected, the resolution changes and recalculation is performed for this resolution. I disabled black bars detection and now everything is fine.
Yeah this happen in movies that have Imax format, but only if you don't have the resolution pass already save, also you maybe try black bar detection set to only one time.
oriento wrote:4.22 lite is out !
Smoother than any other lite models, except 4.15 (for me atleast)
TRT 10.3 / opt_level 2 / engine built average time - 26 seconds (720p)
Different behavior with different aspect ratios and containers!
And a quick test I wanna say I LIKE IT! Definitely use this at my main model. I much like to this models has a changelog.
Others are saying it is not as good as v4.15. v4.15 is close but not quite as good as v4.18 so it will interesting to hear what happens after further testing.
Yeah exactly, sometimes more demanding translate to worse performance so more negative comment on the hardware/setup more prone to it , sometimes there it's not the case at all , like 4.21 that i think everyone hates. I tweak here and there make so much difference, for example i don't know what change in my setting, for i'm sure that almost all my main options are the same, and somehow my movies improve , the reason maybe stability after the 0x129 microcode, Who Knows.
It came out very early this morning. But v4.22 is not a good model so the lite model will be at best the same but probably worse.
I think this it's not the same for every setup, for me it's very similar than 4.18 and I'll say that I'm some movies my experience was better. Later I will test the new model and see how it performes
you can't play 4k60 because of _renderer_ performance with 4070?
iI thought you were referring to Rife. I often comment on that topic. And you were talking about regular svp.
> Is 4K 24fps to 4k60fps with tone mapping and SVP not something that is achievable right now without a 4090?
with MPC VR it's achievable right now on almost anything
madVR is unjustifiably slow
What do you mean by almost anything,on which models this happens, I'm on a 4070 ti super and this it's not the case.
SmoothVideo Project → Posts by Drakko01
Powered by PunBB, supported by Informer Technologies, Inc.