You are not logged in. Please login or register.
SmoothVideo Project → Posts by Chainik
SVP installation app downloads and runs the very same setup .exe files as listed there.
That's it.
> The MPC-HC build in your kit breaks this.
this's the very same official MPC-HC installer
Just play it at last 
this is a half side-by-side stereo pair in 24 fps
At least post here Mediainfo of the converted file
I've tried to convert the .ssif files into a format that activates the LAV filter, such as H.264, but the resultant format / file plays at 12 FPS.
MVC video (i.e. ".ssif") converted to a H.264 stereo-pair is just a usual 2D video.
I have no idea how you managed to play usual 2D videos at 12 fps 
Probably it's somehow connected to the 3D viewing mode you're using in Stereoscopic Player - which is still unknown.
for the best results keep CPU load at 70% at maximum
1. SVP doesn't affect video colors.
2. MV search settings are different between SVP 3 and 4 => "Search Radius: Large" means different things.
3. For the best results keep CPU load at 70% at maximum.
4. A quote from the manual:
Setting all options to the maximum possible values will worsen the quality of motion interpolation and significantly increase the load on the system.
A torrent files downloader?
Personally I'm good with a usual MPC-HC playing any kind/format of stereo pair and watching it on LG's 4K TV.
What you need is a reference file - i.e. an over-under stereo pair made by "professional ripper".
SVP installs 64-bit Avisynth+ if you choose 64-bit players support at the install time.
well... try to reset madVR settings to defaults
x64 is probably better than x86
> when I run the video player in a small window (about 1/4th of Full HD size), the video seems smooth and fluid
start with switching to EVR-CP instead of madVR
try to read User manual - it's free 
and this's not a rocket science
> а когда появиться возможность обновить мадвр в пакете SVP?
когда новой версии хотя бы неделю не будет
again - the black SVPflow magic, when each parameter affects resulting image in a very unclear way
it's like 10-way optimization problem when you never can say that "parameters set A is always better than parameters set B"
it IS already set to "adaptive"
"small" maps to "analyse.main.search.coarse.distance = -6", "average" = "-8", "large" = "-12"
by "adaptive" I mean negative values in SVPflow parameters
the actual search radius depends on the contrast value of the image block
the only ultimate solution for "window blind artifacts" is search radius = 1
however SVP's "adaptive" search radius makes it much better for larger values as well
behold the black magic power of SVPflow (MVTools) limits and penalties
larger radius helps find longer motion vectors - i.e. detect faster motion
SmoothVideo Project → Posts by Chainik
Powered by PunBB, supported by Informer Technologies, Inc.