• Thanks: 1
  • Thanks for the post: 1

Topic: SVP with Vapoursynth: unable to init GPU-based renderer

When using Vapoursynth 64bit:

# Imports
import os
import sys
import vapoursynth as vs
core = vs.get_core()
# Import scripts folder
scriptPath = 'G:/Hybrid/vsscripts'
sys.path.append(os.path.abspath(scriptPath))
# Loading Plugins
core.std.LoadPlugin(path="G:/Hybrid/vsfilters/FrameFilter/Interframe/svpflow2_vs64.dll")
core.std.LoadPlugin(path="G:/Hybrid/vsfilters/FrameFilter/Interframe/svpflow1_vs64.dll")
core.std.LoadPlugin(path="G:/Hybrid/vsfilters/SourceFilter/LSmashSource/vslsmashsource.dll")
# Import scripts
import havsfunc as havsfunc
# Loading F:\TestClips&Co\test.avi using LWLibavSource
clip = core.lsmas.LWLibavSource(source="F:/TESTCL~1/test.avi", format="YUV420P8", cache=0)
# making sure input color matrix is set as 470bg
clip = core.resize.Point(clip, matrix_in_s="470bg")
# making sure input color range is set to TV (16-235) scale.
clip = core.std.SetFrameProp(clip=clip, prop="_ColorRange", intval=1)
# adjusting frame count with Interframe/SVP
clip = havsfunc.InterFrame(clip, Preset="fastest", NewNum=60, NewDen=1, GPU=True)
# Output
clip.set_output()

I get: "SVSmoothFps: unable to init GPU-based renderer - code 255" any clue what I'm missing? (Got an NVIDIA Geforce 980 Ti with driver version 381.65)
(Interframe works fine when using through 32bit Avisynth 2.6 MT)

Cu Selur

Re: SVP with Vapoursynth: unable to init GPU-based renderer

the most common reason is a major Windows updates, after that you'll have to re-install graphics drivers manually

  • Thanks: 1

Re: SVP with Vapoursynth: unable to init GPU-based renderer

Thanks! Reinstalling the drivers fixed the issue in Vapoursynth.

Cu Selur

  • Thanks: 97

Re: SVP with Vapoursynth: unable to init GPU-based renderer

Selur, Slightly offtopic but have you ever thought about automatic mechanism of integration SVP playback scripts into Hybrid?

All latest video playback's scripts where SVP has been used are saved at ~AppData\Roaming\SVP4\scripts location and unlike Interframe these scripts already contain all detailed settings which were used in SVP GUI. If there was any easier option to integrate those than manually open scripts folder, open one in notepad, find manual AVS script field in Hybrid and then doublecheck that nothing is broken considering manual part is added at the very end if I recall correct...
What I mean if you could just click "Open SVP script" and choose one in explorer window then it would be almost seamless fluid convertion option.