а, нет. на квадратики, конечно же, черные полосы не влияют.
а влияют параметры кодера
вот бы знать какие...
You are not logged in. Please login or register.
SmoothVideo Project → Posts by Chainik
а, нет. на квадратики, конечно же, черные полосы не влияют.
а влияют параметры кодера
вот бы знать какие...
> Уверен доход упал когда цена стала $25
а что если нет?
> Необходимо подробное пособие как на МПВ
открыть подробное пособие на SVP не пробовали?
> h264_nvenc: No NVENC capable devices found
what video card do you have?
reinstall graphics drivers
Ну поиск не работает, а просто обрезка работает
"поиск" при перекодировании не работает
still not sure where the bottleneck is, but mpv plays 5400*2700*60 -> 80 significantly better than MPC-HC
and in MPC-HC CUDA decoder works way better than DXVA2
You can... I just thought the main point is play it in a VR
in fact this topic is a little bit theoretical cause almost all 5-6-8K videos are encoded in HEVC and ffdshow video decoder doesn't support it so there's no way to watch them in a VR headset with SVP now
as I'm now working on a laptop and can only access desktop PC (Ryzen, 2070 and Rift) remotely, it's a bit tricky to test it myself
well, 5400x2700x60 is indeed equal to 4x4Kx30, which is a lot of pixels
but it shouldn't be a problem for NVOF, there's a bottleneck somewhere, I'll try to take a look
"35% charge, but 2 threads seems to be overcharged at 100%" - with NVOF, right?
still making 80 fps out of 60 is not the best idea, I doubt it can be fluent anyway
just watch 60 fps in 60 fps, it's already good enough
30 -> 80 or 60 -> 120 make sense, but not 60->80
even IF can be fluent, EVERY output frame will be interpolated, i.e. with a visual artifacts
and don't forget that in Whirligig/SimpleVR/etc we are limited with an outdated and software-only ffdshow video decoder
> i thought 60fps to 80fps will be easier than 30 to 60
nope, it's at least twice as hard (w/o NVOF)
Update: SVPtube rev.191 clears cache automatically on each SVP start. Turn off with 'tube.ydl.clear_cache = false'.
Remove/clear the cache folder manually:
* Windows: %HOMEPATH%\.cache\youtube-dl
* macOS, Linux: ~/.cache/youtube-dl
because prices and conditions were different in 2015, obviously
AFAIK mpv doesn't use d3d/openGL renderers in encoding mode.
I saw a thread on this topic on Github, can't find it now
Можно покадрово посмотреть, правда "моргает", или "как будто"
as 10-bit AVS chain is completely useless for the SVP itself, it's definitely not the high priority task...
> iGPU, which now gives me green pixelated distortions when chosen
increase RAM amount for the iGPU to at least 512 MB
I don't have any of these "lua-settings" stuff too, but the script works...
this is probably not good:
[ 0.009][w][mpvSockets] stack traceback:
[ 0.009][w][mpvSockets] [C]: at 0x00afaa80
[ 0.009][f][mpvSockets] Lua error: ...rs\*\AppData\Roaming/mpv/scripts/mpvSockets.lua:7: unexpected symbol near '<'
check mpv log then...
> некоторые на 50
интерлейс?
mpv runs
mpv loads mpvSocket.lua script
it sets the 'input-ipc-server' to the 'mpvSocket/<some_number>', where <some_number> is the mpv.exe process PID
SVP finds all the mpv.exe processes and their PIDs ant tries to connect to all of the corresponding sockets
20748 was the process PID in that example
it doesn't matter what you have in mpv.conf file as a 'input-ipc-server' cause lua script will overwrite this value, but it's probably better to remove this line completely
it doesn't matter what you have in SVP's config 'mpv_pipe' variable either
hope it's clear
# first window opened
16:11:26.134 []: VideoPlayer: mpv [mpv.exe] connected, waiting for the video info...
# second window opened
16:11:31.204 []: VideoPlayer: mpv [mpv.exe] connected, waiting for the video info...
# drop file in the 1st window
16:12:01.740 []: VideoPlayer: mpv 0.32.0-322-g5824ac7d36 /via 'mpvSockets/3448'
16:12:02.207 []: Media: video 1280x720 [PAR 1.000] at 25.000 fps [constant]
16:12:02.207 []: Media: codec type is AVC, YUV/4:2:0/8 bits/BT.709 BT.709
16:12:02.223 []: Playback: starting up...
...
# drop file in the 2nd window
16:12:09.486 []: VideoPlayer: mpv 0.32.0-322-g5824ac7d36 /via 'mpvSockets/11316'
16:12:09.846 []: Media: video 1920x1080 [PAR 1.000] at 29.970 fps [constant]
16:12:09.847 []: Media: codec type is AVC, YUV/4:2:0/8 bits/BT.709 BT.709
16:12:09.902 []: Playback: starting up...
...
> And in the SVP options it still says mpvpipe
it doesn't matter
it _dynamically_ adds new sockets to the list - in this case, 'mpvSockets/3448' and 'mpvSockets/11316'
Are we still talking about SMPlayer?
SVP rev.191
note the socket path in use!
1. old SMPlayer (before ver.19.10.0.9290 from 2020-04-06) + old mpv (before 2020-03-26)
SVP log:
13:36:16.860 []: VideoPlayer: mpv 0.32.0 /via 'mpvpipe'
only one instance will work
2. new SMPlayer + old mpv -> doesn't work at all
3. new SMPlayer + new mpv
13:38:46.648 []: VideoPlayer: mpv 0.32.0-322-g5824ac7d36 /via 'C:/Users/chain/AppData/Local/Temp/smplayer-mpv-1adc'
socket name is specific to the SMPlayer instance
4. mpv with fixed "input-ipc-server"
13:36:16.860 []: VideoPlayer: mpv 0.32.0-322-g5824ac7d36 /via 'mpvpipe'
only one instance will work
5. mpv with mpvSockets script
13:44:35.210 []: VideoPlayer: mpv 0.32.0-322-g5824ac7d36 /via 'mpvSockets/20748'
socket name is specific to the mpv instance
SmoothVideo Project → Posts by Chainik
Powered by PunBB, supported by Informer Technologies, Inc.