You are not logged in. Please login or register.
SmoothVideo Project → Posts by Chainik
DolbyVision blinking must be fixed at last 
plus DV colors (i.e. brightness) were incorrect because of wrong colorspace conversion before/after RIFE processing
24 * 5 , and then take every other frame
did you updated to mpv 0.38?
> SVP motion has at least a couple of clear and repeatable stutters for certain scenes that IC does not.
meaning
1. it's a false positive SC, right? in which case you'd better share a sample with the problem... there're a lot of variables to adjust there.
2. you really prefer "RIFE-generated "garbage" frames" over frame repeating at a false-positive SC
> 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
Drakko01
>I still think that image comparison work the best
to be "the best" it must give less false positive scene changes, and less missed scene changes
which is not true
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
"the same problem" is only regarding AMD cards and AMD drivers
it has nothing common with NV cards and mpv versions
> if I need to update my ICD loader
not for SVP
cool
but "2x conversion" looks much more user-friendly
> Can you share the command line
it's right in the transcoding log
> 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!!!
> Maybe it won't have the seek crash.
_very_ unlikely
> 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.
.dll attached
> to see if gerappa can use 2 threads if that line was turned into a warning
still the device will be reporting queueCount = 1
https://registry.khronos.org/vulkan/spe … rties.html
I really doubt there're any performance benefits settings "thread" count higher than device caps
but here you are...
> for us to correctly use the latest rife_vs.dll file
why exactly you want this?
no idea what "solution" you're looking for...
VLC crashes with renderer different from d3d9. Period.
SVP v.246 runs VLC with d3d9, while later versions runs VLC with OpenGL by default (configurable via adv. settings)
не понял вопроса
что именно ищем, какую конкретно "кнопку"?
Это настройки в профиле RIFE.
> With the new update downscaling to 720p is now gone
long-press the button 
> please write down here, for laymen to understand, what's the best opion to use
the default one! (which is "SVP motion vectors")
> So this - "vsmlrt.py - Added support for RIFE v4.17 models." - can be completely ignored
yes, it can be completely ignored
This is what a Vulkan driver reporting about the hardware caps, we can do nothing about it.
SmoothVideo Project → Posts by Chainik
Powered by PunBB, supported by Informer Technologies, Inc.