Search options (Page 22 of 365)

dunno, YT now gives error 403 on some video and/or audio streams
lets hope it's something that will be fixed soon in yt_dlp

> But an example of why IC is slightly better is in Dr Strange 2 where he throws his cloak to catch the girl. At the point she is caught the scene changes to show her being carried back.

what is the timecode?

> At the point she is caught the scene changes to show her being carried back. With both NVOF and SVP this is a very sharp and jarring cut. With IC there's still an issue but it's less jarring and looks more natural.

So MVs see the scene change while IC doesn't, and still it's "better". OK then

DolbyVision blinking must be fixed at last

plus DV colors (i.e. brightness) were incorrect because of wrong colorspace conversion before/after RIFE processing

did you updated to mpv 0.38?

> but Image Comparison just performs better overall for every problem scene I have.

probably you just prefer RIFE-generated "garbage" frames over repeated or blended ones

apparently, DV blinking _was_ fixed, but it seems that now, with a processing logic changed for "motion vectors scene change", the blinking is back, but for a different reason and it's a different kind of blinking now...

still the latest "0.38" changes were necessary, but not enough

можно проверять 0.38

cool

but "2x conversion" looks much more user-friendly

> Where???

App. settings -> All settings

> Watch on my Youtube video

It's absolutely unclear what video output settings you have in each case...
When you run VLC from SVP's menu, video output will be set to the one set in SVP's main.setup.vlc.vout value, regardless of what you'll see in VLC's Preferences!!!

> Overall, it looks like it's not the driver problem anymore, the vs_rife.dll was the problem

.dll is not the problem, it just preventing user from setting dangerous values, leading to undefined behavior

overall setting threads higher than driver-reported value is not practically usable
q.e.d.