2,076

(6 replies, posted in Using SVP)

Is SVP 4 any better than SVP 3? wink

it's x265 limitation
there're a few more x265-specific options - "pools" and "numa-pools", you can specify them on your own in Advanced mode
https://x265.readthedocs.io/en/default/ … tion-pools

2,078

(6 replies, posted in Using SVP)

> Are the old versions free to use?

yes, SVP 3 always was free

2,079

(11 replies, posted in Using SVP)

If Python itself doesn't run properly on your system it's either Python's fault or your system's fault. Not SVPtube's.

Try previous versions:
3.8.1 - https://www.python.org/ftp/python/3.8.1 … -win32.zip
3.8.0 - https://www.python.org/ftp/python/3.8.0 … -win32.zip

BTW, what is your OS?

2,080

(11 replies, posted in Using SVP)

ok, this is probably the good news... cause it's definitely not our fault big_smile

is it possible you have some files broken? hmm

take the official distro - https://www.python.org/ftp/python/3.8.2 … -win32.zip
and unpack into into mpv32 folder

2,081

(11 replies, posted in Using SVP)

run mpv32\python.exe, type 'import ctypes' - does it work?

it appears it doesn't work if the "threads" parameter is >16
right now what you can do is move the "cpu usage" slider to the left to the point where it work

SVPcode only re-encodes video to high frame rate, leaving any other tracks (audio/subs) untouched. This is by design.

default values: tolerance = 0.02, vfr_diff = 0.2

2,085

(11 replies, posted in Using SVP)

[removed]

2,086

(5 replies, posted in Using SVP)

easy...
replace the file in SVP 4\extensions\tube\youtube-dl\extractor and restart SVP

2,087

(11 replies, posted in Using SVP)

any other python 3.8 somewhere in the PATH?
search for python38.dll

2,088

(5 replies, posted in Using SVP)

it (youtube-dl) actually failed on parsing available subtitles

dunno what we could do other than do NOT download subtitles

2,089

(1 replies, posted in Using SVP)

CUVID is definitely better in some cases (like playing 4K on a 120+ Hz screen)

> because of SMPlayer or newer MPV

SMPlayer uses a command line switch "input-file" deprecated in mpv 0.30 and completely removed 8 days ago

Here's the previous build.

===
https://forum.smplayer.info/viewtopic.p … mp;t=12378

still no newer version here, we just have to wait: https://sourceforge.net/projects/smplay … nt-builds/

yeah, will be fixed asap

2,092

(2 replies, posted in Using SVP)

> How do I make it stop?

only by manually removing the "ext.tube.ydl" section from the components.xml file (use the plain text editor)

2,093

(11 replies, posted in Using SVP)

any errors on the log?

the main difference is Python 3.8 vs 3.7

2,094

(12 replies, posted in Using SVP)

yep

> 25 долларов, но это слишком дорого

а за 499 рублей - не годится?

2,096

(12 replies, posted in Using SVP)

gpuid=11
"nvof==0 ? ...", not "nvof=true ?"

why don't just run SVP and look at the script? hmm

2,097

(98 replies, posted in Эксплуатация SVP)

не знаю, не знаю... пока что только не доложил 8-битного кодирования в x265, ну и я еще забыл что там нужен патчик для правильной работы Plex Media Player
поэтому пришлось опять самому собрать. но больше никаких отличий от его скриптов - нет.

2,098

(12 replies, posted in Using SVP)

you just copied the SVP-generated script, obviously it is correct

===
gpuid:0

NVOF needs gpu acceleration ON

2,099

(64 replies, posted in Using SVP)

you probably want to post a bug report at NV's forum wink
don't even mention SVP, low fps in FH4 is enough

2,100

(12 replies, posted in Using SVP)

There're actually no parameters at all. Considering the usual script is:

super = SVSuper(input, super_params)
vectors = SVAnalyse(super, analyse_params, src=input)
SVSmoothFps(input, super, vectors, smoothfps_params, mt=threads)

the NVOF one would be like this:

nvof_blk = 16
nvof_src = input.BicubicResize(input.width/nvof_blk*4,input.height/nvof_blk*4,src_width=-(input.width % nvof_blk),src_height=-(input.height % nvof_blk))
SVSmoothFps_NVOF(input, smoothfps_params, nvof_src=nvof_src, mt=threads)

"smoothfps_params" string is exactly the same
you can play with different "nvof_blk" values (4,8,16,32), but the NVOF engine itself always uses 4*4 blocks - that is why we need to prepare resized clip first to emulate other block sizes