Search options (Page 10 of 17)
scb wrote:flowreen91 wrote: We should either use "video-sync=audio" like Blackfyre's configs or nothing at all.
Referring to https://mpv.io/manual/master/
I believe video-sync=audio is the mpv default behaviour.
Yes it is.
flowreen91 wrote:dawkinscm wrote:but it still has issues with horizontal slow pans.
If i'm using the mpv setting "video-sync=display-resample" this scene has massive stutters:
https://youtu.be/jZvFEtR8RH0?si=59TEOOJ … m&t=18
We should either use "video-sync=audio" like Blackfyre's configs or nothing at all.
Most configs for mpv on the Internet are out of date at best. But people will copy them verbatim without understanding. Blackfyre's config is his own and in previous comments I noted some unnecessary settings. This is another one, but I only started using "video-sync" myself in the last few days so I'm still learning.
As for the "display-resample" option, I don't need it to be on, but for me it seems to work well in smoothing out some of the remaining micro-stutters even without interpolation=on. But I watch stuff on a large VR screen so I will see micro-stutters that many wont. Because of that, my SVP setup including scripts will be different to most. Everyone's situation is different.
The remaining issue I have with RIFE is the double images for fast motion. What I found is that the higher the frame-rate the less the issue occurs. At x3 frame-rate from the issue is reduced but then I get stutters. But turning on interpolation in mpv removes those stutters and I get the smooth motion back and better fast motion handling, but it still has issues with horizontal slow pans. I like it, but the issue with slow pans annoys me. Maybe if you have a 4090 this might be useful.
MAG79 wrote:I've checked with my RTX 3060 Ti.
It has 152 Tensor cores instead of 136 in RTX 4060 Ti.
and it has 38 streaming multi-processors instead of 34 in RTX 4060 Ti.
and it has 4864 cuda cores intead of 4352 in RTX 4060 Ti.
So, my RTX 3060 Ti must be faster than RTX 4060 Ti
Not exactly. If you have a 3060ti you probably shouldn't upgrade to the 4060ti for SVP because they have similar performance. The 3060ti has a wider memory bus, but the 4060ti is using the latest generation Tensor cores, SMPs and Cuda cores which makes a difference. For example, an RTX 4080 is equivalent to the previous gen 3090ti so is much faster than a 3080. But the 4080 has less actual Tensor cores than a 3080.
If you don't follow the format then they will usually tell you but sometimes the question will just get ignored. It's structured in a way to stop random questions filling up the list.
Interesting. I guess we were all wrong lol But I did ask for a clarification and all I got was answers from everyone except @Chainik hence my assumption. But at least now we know what's actually happening. It is still all good 
Blackfyre wrote:You can see in the SVP logs as @Chainik already showed the SVP is active and working with d3d11va. I mean you can test it yourself, switch to d3d11va and test it with RIFE + SVP + MPV
I see now that SVP is doing the copy. But to clarify, I had previously tested copy vs no copy a few times. When using copy I saw was a decrease in performance and the copy buffers not being used which made sense when taken with the default mpv.conf using copy. The default mpv.conf is a little out of date, but I still couldn't see why they would supply a config with a poor performing option like copy. Especially when the manual says the same thing.
Blackfyre wrote:The whole point of the pictures was to show the difference...
I simply missed it. I didn't see any difference when I looked at it. I do now.
Blackfyre wrote:the only reason I mentioned colour once at the start then edited it out was because the crushed blacks results in a visible difference in the entire image,
I only focussed on what you wrote. What was edited out afterwards I don't know.
But it's all good
Two things.
First is @Chainik saying that I no longer need to use copy? The manual still says use "copy-back".
Second, I thought @Blackfyre said that there was no difference between d3d11va and copy and I didn't see those differences in pictures. To me that made sense because it the mechanism should have nothing to do with color. But I see there is a massive difference in the two pictures which I must have somehow missed. But a possible explanation for the difference would be that it is being affected by SVP which brings me back to my first point.
So still confused.
Chainik wrote:no magic here, mpv is doing copying automatically in this case:
[ 0.245][v][vo/gpu-next] Loading hwdec driver 'd3d11va'
...
[ 1.787][][autoconvert] HW-downloading from d3d11
[ 1.787][][autoconvert] Converting p010 -> yuv420p10
Now I'm just confused.
Blackfyre wrote:dawkinscm wrote:There's working, then there's working properly.
Okay, but what is there to working properly? The interpolation is happening, and it appears as smooth as copy.
So I'm not sure what more can “properly” do in this case. RIFE is doing its job and the frame rate is doubling as I am requesting it to do.
What happens to your performance when you use copy? I assume it goes down?
dawkinscm wrote:But unless the devs come on here and tells us that the manual is wrong then I'm sticking with "copy".
Blackfyre wrote:Wouldn't mind some clarification on this too tbh
Hopefully @Chainik can clarify perhaps.
My guess is that the manual just has old information which was perhaps resolved, maybe with gpu-next
Not gpu-next. That has nothing to do with this.
scb wrote:So should I be using auto-copy rather than auto? SVP appears to work either setting.
Blackfyre wrote:
There's working, then there's working properly. From the SVP manual:
Only "copy-back" hardware video decoders are compatible with Vapoursynth filters, use hwdec=auto-copy
If the SVP manual is wrong then great we get more performance!!! But unless the devs come on here and tells us that the manual is wrong then I'm sticking with "copy".
Blackfyre wrote:dawkinscm wrote:If you are using d3d11va then SVP doesn't work properly because it doesn't have full access to all frames.
Never had such an issue with RIFE + SVP + MPV
Unless a dev comes on and tells me that the way SVP has always works has now changed, then whether you recognise it or not, using d3d11va and not d3d11va-copy means that SVP is not working properly.
Blackfyre wrote:dawkinscm wrote:Also hwdec has very little to do with colours which is why you see no differences. But it might have some impact on banding depending on what card you are using.
Pictures look exaggerated, captured with ExpertRAW on my phone. But you can understand what I mean by banding, and the blacks are not perfect blacks, they become very very dark grey, but not perfect black levels.
You're kind of mixing up colour with banding but I get what you mean. I did say that hwdec can affect banding depending on the card and parameters used. What happens if you set hwdec=no? If you still have the same banding then the issue is definitely not the card or hwdec but is probably your display and its setup. If the banding disappears then you need to check your card settings.
Blackfyre wrote:Testing only with:
hwdec=d3d11va *Prevents VRR but black levels are good, and no banding.
Changed to d3d11va-copy *VRR works but same problem as above crushed blacks & banding
nvdec, cuda, etc all same thing, do not work properly.
hwdec=d3d11va provides the best black levels and no banding, but breaks VRR.
It's weird that people are using d3d11va when the base mpv.conf uses d3d11va-copy. If you are using d3d11va then SVP doesn't work properly because it doesn't have full access to all frames. Also hwdec has very little to do with colours which is why you see no differences. But it might have some impact on banding depending on what card you are using.
Chainik wrote:> But also mpc-hc is very old
wat? 
One of the reasons mpc-be came out was because HC was a dead project. But I forgot that it has been restarted. I've updated my original post.
SHTH34D wrote:I have an I7-8086K and a RTX 4090. I watch movies on MPC-HC with Vapoursynth, MPC internal renderer, and Internal LAV filter. My performance is very odd, with huge spikes then dropping to zero. It is making movies unwatchable. It is not an issue when SVP is not running. Any help would be greatly appreciated!
You may have to use mpv instead. If you still have issues, even with mpv then there's something wrong and as @flowreen91 says you can try re-installing SVP.
RickyAstle98 wrote:Im already use mpv player since SVP4 Pro buy, I custom mpv for my preferences, so I cant get extra performance at all? I test d3d11va and RTX 4070 dies at 720@24>144 realtime playback, but d3d11va-copy didnt
The reason you get better performance with d3d11va over d3d11va-copy is because with d3d11va SVP can't properly process the frames. d3d11va-copy copies frams to system ram where SVP has full access to them. So unless SVP has changed and somehow has direct access to GPU memory, you need to use copy. But you probably already know this and you were just joking.
Gippy wrote:I deleted mpv after one day. Horrible GUI and doesn't work with the MadVR renderer.
What made you think that it should work with MadVR? Running mpv is equivalent to running mpc-be+MadVR and with that flexibility there is a learning curve. Yes it is text based but you can also download gui's for it. There are also gui based players that use mpv as a display engine.
But SVP comes with baseline mpv.conf file so unlike mpc-be, it will just work with zero extra configuration.
Gippy wrote:VLC is the "for dummies" media player and doesn't have much customization. mpv goes too far extreme in the other direction and is for those who think FFmpeg command line is the greatest encoder. MPC-HC/BE is in the middle and that's good enough for me.
mpc-be is a great media player and a nice middle ground, but mpv just works more efficiently with SVP. mpv is open source and uses code from other oepn source projects including ffmpeg and even VLC "for dummies".
Xenocyde wrote:Is MPC-HC better for GPUs like RTX 4080? I'm on MPV but screen is 1080p so don't think it really matters right now. I'm thinking of getting a 4K screen soon, though, so maybe MPC-HC is better for 4K?
No. One of the reasons I switched from mpc to mpv is that it works better with SVP at any resolution.
RickyAstle98 wrote:MAG79 wrote:Gippy thanks for information.
In the past D3D11 Native value in LAV decoder was incompatible to SVP.
Need to check if it works correctly and SVP does its work fine (24 to 60 fps conversion).
---
I've checked. D3D11 works good with SVP.
In LAV decoder filter properties it indicates as Active Decoder: d3d11 cb direct
Does d3d11va-copy same thing D3D11 in mpv player? How to force D3D11 thru svp and mpv player, a bit confused, I want more performance!
For SVP, whichever decoder you use in mpv it needs to be a copy-back decoder where the frames are copied back to RAM, wtherwise SVP can't process them. d3d11va-copy is one of the better Windows copy-back decoders. If you want to start using mpv then use the SVP installer to install it then use the default mpv.conf that comes with SVP. It's not perfect but it will 100% work.
KanitkarRana wrote:While employing MPV with Rife 2, I've noticed seamless performance, yet I'm unaware of regularly dropping "output" frames. Despite my GPU hovering around 80%, the root cause eludes me. Moreover, I stumbled upon the "ffdshow" parameter under Advanced Settings, which is currently set to "true". Is this configuration accurate?
I've asked the ffdshow question myself a long time ago. I don't remember getting an answer so I just set it to false. With mpv there could be a number of reasons for frame drops including a bug in the stats page, the hwdec you are using or something else. Also make sure that the SVP index is not lower than 1.0 because if it is then you may have to use a less compute heavy version of Rife. You are just going to have to troubleshoot it. If it's not affecting what you are seeing on screen then maybe don't worry about it too much until you see a problem
scb wrote:This is good to know, but what are the differences between the models? When should one pick a particular one? What are the different models best at? What are the quality differences?
I suppose you can choose different models for different content if you wish. But no one can answer this question for you. You will have to test each model with different content. Later models have less artefacts and better motion handling. So maybe choose the one that works best for you and stick with it?
BTW my latest tests suggest that as good as Rife 4.14 is for fast movement, Rife 4.13 is actually a little better in reducing the double images.
scb wrote:Guys,
I still haven't seen a full explanation about the different between the 'normal' and 'lite' models of the same versions? What situations should I pick the 'lite' version over the 'normal' version of a model?
The purpose of the "lite" versions were never fully clear to me except for Rife 4.14 "lite" which is different to every model that came before it. But there is no answer to your question, you just have to try them and see which one works best for you. As of right now, if you don't have a high end card then don't bother with anything above Rife 4.9. Rife 4.13 is computationally heavy even for a 4080. Rife 4.14 "lite" is not "lite" at all unless you have a card with high memory bandwidth like a 'maybe' a 3070ti and above.
StanTheMan wrote:RTX 3060 Ti, i5 12400f, 32 GB of RAM.
"Lite" versions works better everytime. From newest versions with "lite" (4.12 and so on) usual versions dropped frames and it's like don't have enough power or overloading, because it's not working on 60 FPS everytime (48 FPS works OK), but i didn't do any test, just saw the FPS and my internal feelings. So, now i'm on 4.12 "lite" version and it's great.
Newest 4.13 and 4.14 and lite too don't work properly in any scenarios with my GPU because of overloading or something. So, now i'm on 4.12 "lite" with hope for better versions in the future.
Rife 4.14 "lite" is different to the other "lite" models. It uses a technology that requires more GPU bus bandwidth but not as much compute power. Rife 4.13 "lite" is similar to regular Rife 4.9 so if you struggle with 4.9 you will struggle with 4.13. I think maybe Rife 4.14 needs more compute power and memory bandwidth than the 3060ti can provide.
jimdogma7 wrote:roshin1401 wrote:Im noob to this software. While using TensorRT, a cmd popups doing compilation. Does this occur for every video file opened? or only once? And also please suggest best rife model for my gpu. Its a 3070 laptop.
I'm having the same problem and unfotunately this post wasn't responded to. I've put the .OONX files in the "models" and/or 'Rife" folders as instructed and yes, they do show up in the AI models pulldown in the SVP manager, but when I select it and try to run a video, a CMD box pops up and after a few seconds goes away. The video then plays but is not converted. Nor does the little green text in the lower left corner come up telling you what setting you're using, etc. Tres bizarre. Plus, if I try to transcode the video it doesn't work either. Says conversion failed.
It seems pretty straitforward, I don't what I'm doing wrong here. Please help!
I keep saying this but it's worth repeating. If you are new to this then don't do anything you see here because we are experimenting. SVP works out of the box. Just uninstall everything, go to the SVP Rife AI page https://www.svp-team.com/wiki/RIFE_AI_interpolation and follow the instructions. All the information you need about the Rife, the DOS box and everything else is on that page. Once you have done that then have a look at the SVP Transcoding page https://www.svp-team.com/wiki/Manual:SVPcode. I don't transcode, but once you have followed those instructions there are others on here who can help you with any specific questions you have.
RAGEdemon wrote:537.58 eliminated the pan stutters for me.
It made no difference for me when I tried it but I do like the options that come with the installer. So I installed the latest version because of Cuda 12.3 but with the options. It works at least as well as before with or without 537.58 but with a couple of non SVP related improvements.
RAGEdemon wrote:Other modes such as sync 24fps video to screen refresh, or fps x 2.5, or whole multiples, is really taxing on the GPU. An overclocked 4090 can't do it, even on the highest performing RIFE (4.4/4.6).
I tried 2.5 and it was pretty bad but then if an overclocked 4090 can't do it then I've got not chance
Blackfyre wrote:Thanks for the input, so looks like I'll just stick with the 3090 until 5090 is released.
3840x2160 was watchable on the 4080, but with slow pan stutters. I updated the Nvidia Driver to latest version released yesterday and used the v14Test3 TensorRT library (Cuda 12.3) and the latest vslmrt.py with Rife 4.14v2 lite. It's still dropping frames but the slow pans are now mostly smooth. The 4090 should have no problem so you don't need to wait for a 5090.
I currently don't have any intention of using SVP with 4K but this should help to clarify your options.
Posts found: 226 to 250 of 404