You are not logged in. Please login or register.
SmoothVideo Project → Posts by Chainik
then do the opposite - 120 hz mode from PC and play a 24 fps (or 48 fps via SVP) video
TV won't get a chance to smooth anything if you feed it with a 120 hz signal
> And obviously svp doesnt get recognized.
This part is simple - Plex now wants mpv.conf in C:\Users\<name>\AppData\Local\Plex\mpv.conf instead of C:\Users\<name>\AppData\Roaming\mpv\Plex.exe\mpv.conf
> the player wont even give me the option to change quality and more
what "more"?
> его можно смотреть в с SVP?
dolby vision похоже и без SVP особо смотреть не в чем
не углублялся пока в этот вопрос
а где такое видео брать то? с ойфона что ли?
ну, я вижу только взять mpv, наколдовать параметров ffmpeg для кодирования в rtmp, ну и добавить фильтр svp
за точку отсчета взять команду запуска из лога SVPcast
I'd suggest updating to the latest version first...
avisynth filter + madVR
it works since "4.3.0.191 – 2020-04-11" because SVP enumerates all mpv processes and tries /tmp/mpvSockets/<pid>
just take this - https://github.com/wis/mpvSockets - and that's it
ну вон DAR правильно выставляется в 1.3333
что, если потом в плеере открыть, то неправильно показывает?
вот для примера:
14:48:28.348 []: Media: video 720x464 [PAR 1.422] at 25.000 fps
14:48:28.348 []: Media: codec type is AVC, YUV/4:2:0/8 bits
14:48:28.355 []: Transcoder: Frame server (64-bit) C:\Program Files (x86)\SVP 4\mpv64\vapoursynth.dll
14:48:28.355 []: Transcoder: resulting video frame 720x464
....
а в логе кодировщика:
14:48:33.669: Command line: C:\Program Files (x86)\SVP 4\mpv64\mpv.exe D:/share/test video/Дни Затмения [1988]_sample.mkv --o=D:/tmp/Дни Затмения [1988]_sample.SVP.temporary.mkv --no-audio --no-sub --no-sub-auto --input-ipc-server=mpvencodepipe --input-media-keys=no --no-msg-color --vf=vapoursynth:[C:\Users\chain\AppData\Roaming\SVP4\scripts\ffff.py]:4:16,format=dar=2.20474 --of=matroska --ovc=h264_nvenc --ovcopts=b=3223155,preset=slow,profile=high,rc=vbr,maxrate=4190102,bufsize=6446310,time_base=1000/71875,threads=16
720 * 1.422 / 464 = 2.205
логи надо. перекодировщик должен сохранять aspect ratio при не-квадратном пикселе, это специально исправлялось и проверялось.
из 25 совершенно точно получится не 59.94, а 60
сделать можно что угодно, но делать именно 59.94 из 25 - плохая идея
по умолчанию если ничего не трогать то будет 23.976 * 2.5 = 59.94
и только если поставить галочку на "точное значение", то будет 60
dunno 
the "Avisynth Filter" installer script sets all the registry values on installation/update
and I just checked - it really does
do you have /usr/local/lib/libvapoursynth-script.dylib ?
---
in fact it must be here: /usr/local/opt/vapoursynth/lib/libvapoursynth-script.0.dylib
and it will be here if you install Homebrew in a default location
> Maybe the moves to Nvof 2.0
"nvof 2.0" was added in 445.87
---
I have 460.79 on my laptop with gtx 2060, never seen this error too
---
dunno, I can't reproduce this with 460.89 neither on a 2060/laptop nor 2070/desktop
поправить "все параметры" -> cast.encode.opts.h264_nvenc = "b=$B,rc=cbr,preset=slow,profile=high"
"cbr_hq" поменять на просто "cbr"
most likely you don't have python 3.8 installed
libsvptube.so depends on python 3.8
os? any errors in the log?
halo is the most common artifact for any motion interpolation, you can't get rid of it with "increase bitrate and change encoders"
you can only play with the manual SVP interpolation options to get a result that looks good enough for you
there're numerous topics on this problem within this forum - use search
not sure it's related to the "Avisynth filter quality"...
btw, this error code means nothing - i.e. "indicates that an unknown internal error has occurred" while creating GPU memory buffer
to be clear: it comes not from our (SVP's) code but from the video driver
> are those sliders only valid during realtime playing?
yep, it always selects the highest quality in transcoding mode
> Do these improve the quality of Optical Flow over Turing GPU's?
no idea... if yes then it's already "improved" with the drivers update
try Avisynth Filter instead of ffdshow, it works much better when seeking
https://www.svp-team.com/wiki/Avisynth_Filter_(AVSF)
SVP doesn't support 1x1 motion vectors right now
and I really don't think it should
from what I read that 1x1 vectors field is just the same hardware-interpolated 4x4 field
SmoothVideo Project → Posts by Chainik
Powered by PunBB, supported by Informer Technologies, Inc.