You are not logged in. Please login or register.
SmoothVideo Project → Posts by Chainik
So you have something like RPi with Boblight daemon running?
===
Boblight protocol is simple, there's no problem to add it to SVPlight... but I need to figure how to run and test it w/o having the actual device 
Nope because we still can't find a way to make Chromecast and/or Apple TV show text subtitles as a HSL stream.
The only way is to "burn" them into the video. We'll probably add this feature into the next release.
> Is there support for having multiple videos interpolated at the the same time?
Yep. See App. settings -> Add. options -> Running multiple videos.
Works with mpv as well, but you have to run different mpv instances with different "input-ipc-server" values, and list them in SVP's "All settings" main.setup.mpv_pipe
I have no idea about low GPU utilization as long as indicated performance is 10 times lower than it should be.
Just turn off GPU accel. and forget about it.
> Performance: GPU-based frame rendering [gpuID=11] = 22
> Common KVM processor
Virtualization?
Intel's IGP gives
> Performance: GPU-based frame rendering [gpuID=11] = 457
I really doubt that NV 430 is 20 times slower than Intel 530.
I can believe in 2-3 times but not 20.
Nothing changed recently in svpflow plugins except for fixed 10-bit mode in Vapoursynth plugins (in March).
Check your video driver, video renderer settings, etc.
Try to read https://www.svp-team.com/wiki/SVP:Linux, all the answers you need are there.
this usually means you are missing some dependencies
'ldd SVPManager' will show what you're missing
> Transcoding still only works with Software Encoding, anything else causes instant Fail.
I don't see how we could fix this. It completely depends on mpv and ffmpeg.
You can take a mpv command line and remove the "--vf" argument completely.
Will it still give the same error?
"code 262111" means "clCreateContext returns CL_INVALID_DEVICE"
I dunno if any of these supports "playstation vr and windows mixed reality device".
===
DeoVR claims support for "Windows Mixed Reality"
1. "Is SVP code the same quality as the real time system?" - yes
2. "Will SVP provide better results than the method I linked?" - SVP provides a lot of options affecting smoothness in various ways.
3. Neither hardware encoder will work on your AMD A10-7300. Your only option is software encoding.
So... I bet if you _uninstall_ (not re-install) Intel drivers in this mode - it will work.
But I understand this's not a good solution...
Basically the issue is in video drivers, and we can't fix it. All we can do is to make SVP Manager not crash and disable GPU acceleration.
What if disable Intel IGP from the Device Manager while in G-Sync mode?
Intel's drivers are usually the problem, not NV's.
In all above posts I see you reinstalled NV's drivers three times (or even more), and I don't see you reinstalled Intel's.
You're messing things.
First problem: SVP GPU acceleration doesn't work. This will give "SVSmoothFps: unable to init GPU-based renderer" error, and caused by video driver not supporting OpenCL or not properly installed. It has _nothing_ in common with NVENC.
Second problem: NVENC doesn't work. Ant it has _nothing_ in common with any "SVSmoothFps" / OpenCL errors.
Does SVP (not encoding, just real-time mpv) work for you with GPU acceleration enabled?
Does encoding work for you with x264 codec?
clinfo tool crashes due to some kind of misconfiguration in video drivers, exactly as in the thread I've posted above
however you don't have an option to uninstall Intel drivers completely, so I'm not sure how to fix it
try to clean ALL the video drivers with the Display Driver Uninstaller first
See %APPDATA%\SVP4\logs\active.log
Выяснить, как это пишется для ffmpeg. Написать так же.
this's about OpenCL initialization failure
which is another part of the video driver
if you turn off GPU acceleration in SVP it will work
it should be like this
mpv input -o output --no-audio --no-sub --no-sub-auto --input-ipc-server=mpvencodepipe --vf=vapoursynth:/some-path/ffff.py:4:16 --ofps 60.000 --of=matroska --ovc=h264_nvenc --ovcopts=b=11055051,rc=vbr_hq,preset=slow,profile=high,threads=16ovc=h264_nvenc
You may try to run the exact mpv command line from the log in console directly, it will probably give a more verbose output.
8 or 10 bits color depth? x264 or x265? try various combinations...
logs, sample file?
You'd better post a report via SVP itself right after the issue occurs.
для SD, HD и UHD видео по стандартам разные цветовые пр-ва должны использоваться
плеер вполне может применять соотв. преобразование основываясь только на размере кадра
если при кодировании накосячено ( = "выбрано не то пр-во"), то будет так
я так вижу 
SmoothVideo Project → Posts by Chainik
Powered by PunBB, supported by Informer Technologies, Inc.