You are not logged in. Please login or register.
SmoothVideo Project → Posts by Chainik
> 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.
jdg4dfv7
you don't need anything to use 4.16+ models, just put it into the models folder
if you don't know exactly _why_ you need updated TensorRT and/or vsmlrt.py files then you don't need them
Kaiji
please upload the source clip
> but on testing the results seem worse than using image comparison
you'd better provide a sample video if you want this fixed
for the samples I tested MVs-based scene change is significantly better
> Would it be possible to add an option to configure the sensitivity of the motion detection
https://www.svp-team.com/forum/viewtopi … 680#p84680
"Scene change-related params from override.js should also work, such as smooth.scene.limits.zero, .blocks, .scene (see a short description there - https://www.svp-team.com/wiki/Manual:SVPflow")
SVP 4.6.0.272
1. added motion vectors-based scene change detection for RIFE
2. configurable "decrease to..." function (on the "Frame size" page) - selectable target resolution and downscaling filter
check "certification path" page, which one is not ok
you did something with system's root certificates?
"GlobalSign Code Signing Root R45" must be installed
SmoothVideo Project → Posts by Chainik
Powered by PunBB, supported by Informer Technologies, Inc.