Search options (Page 6 of 16)

Sorry I was sloppy with my language but at 6% it's 'b' and at '8%' it seems to be a combination of the two.

Yes that Hugo at the intro when the night sky starts to appear. The choppyness sometimes starts earlier but always happens from when the night sky appears onwards.

I was hoping someone would make a change for below 10% because this is what I was using to fix the vertical fast motion issues I saw but the choppiness it introduced elsewhere wasn't worth it.. 8% works well on fixing those issues, but maybe not quite as smooth on one or two other scene changes above 10%. Still testing. 6% is too choppy no matter what.  Blending/repeat doesn't seem to make much difference.

Update: Did my ultimate test (introduction to Hugo) and below 10% is way too choppy even at 8%. If a similar SC algorithm fix could be applied to 10 or even 12% that would work. But maybe that's not possible because of how it works?

I started with SMPlayer for similar reasons but you have to set it up to use mpv. The GUI makes things easier, but I remember having weird issues once I started to get a little advanced. I also remember that the manual felt incomplete and to get the best out of it I still needed to Google a lot. Just like MPV So I ended up learning enough to start using mpv by itself without SMPlayer.

Here is a page with links to a few GUI based players based on mpv: https://github.com/stax76/awesome-mpv?t … dia-player

But unless you are using SVP to play HDR content then the best case might be to just use the default mpv.conf from SVP which has the bare minimum config you need to work and the picture quality will be decent enough to start with. If you do want to play HDR content then it gets complicated

You are conflating 4K resolution with the  important technologies of HDR and WCG. Marketers knew that these technologies wouldn't "sell" to the average joe without significant explanation.  But everyone "thinks" they understand resolution so that's the easy sell.

When I watch 4K HDR content on my PC, I don't see any detail loss at all, even on a very large screen. So whatever loss there is, isn't significant or obvious without pixel peeping. I can also download 1080p HDR rips that look as good as many 4K discs. That's why I decided to re-encode most of my non Dolby Vision 4K discs down from 60GB+ to half or less, saving disc space while keeping 99% of picture quality.

As for my blu-ray collection, I literally can't see any quality loss at all, and for blu-ray, as long as you are using a decent player then you shouldn't either. 4K HDR playback on a PC is a little trickier, not because of the resolution, but because of HDR. Especially Dolby Vision and HDR10+

The way mpv is built and in particular its reliance on other large libraries means that "stable" is relative. So even without the DoVI issue I agree that they shouldn't upgrade. If anything they should be one version behind the latest version to ensure stability.

If you wish to use 0.38 then SVP will still find mpv as long as you put the files in the mp64 folder. Just make sure you stop SVP from installing mpv. This is what I do because I use my own mpv builds.

I would be surprised if I ever said that Rife v2 has better picture quality, but if I did say that then was incorrect. But there definitely was a time when v2 was better/quicker at FF/REW a video, but that is no longer the case. 

I said the difference was "minor" but "perceptible" and I'm watching on a very large VR Cinema screen so I'm going to see things that others don't. That's why I wouldn't use anything below Rife v4.9.  Over the development time of Rife from v4.6 to v4.15 I've seen artefacts improve to the point where they either disappear or have been reduced.  Vertical fast movement artefacts are still an issue but v4.15/v2 handles those the best.

Thanks for the extra testing and I remember now that you also said this in January when I asked why I should upgrade to TRT9. But after downscaling is it still necessary to use v2?

Noted thanks. I'm currently using v4.15 but if I go back to a v2 model then I will update TRT. Cheers

Yes.

No. As @Chainik stated above, this is nothing to do with TRT version.

lazy is harsh lol. But if the issue is vslmrt and you want to upgrade then I would recommend upgrading to the November 2023 script and not later because later vslmrt scripts made changes that require mods to the helper script too.

Done some more testing and I've learned or at least confirmed a few things. Not sure I see any real benefits with Tensor 9 and Tensor 10 seems to be moving further away from us. So I'm sticking with the last non LLM Tensor 8.6.1 along with the latest vslmrt to have the most up to date build defaults. Using BO=5 but I see no obvious difference to the default. 72fps seems to be the sweet spot for me which might be because the thrown away frames reduces the effect of certain fast movement artefacts. There's more but that about summarises it.

*deleted*