23.08.2020, 08:45
vsViewer is something I wrote based on old vseditor code: https://github.com/Selur/vsViewer/
About testing:
simply do the following:
1. open a file with Hybrid check the Vaporusynth Script Preview, it should look similar to:
best use a source which uses 'LWLibavSource'
2. copy that content into a new text file you name "test.vpy"
3. insert an these additional lines before the '# adjusting output color from:' line:
for KNLMeansCL:
for NNEDI3CL:
4. save the file
5. call:
if it worked it should output the general characteristics of the script otherwise it should give you an error message.
About testing:
simply do the following:
1. open a file with Hybrid check the Vaporusynth Script Preview, it should look similar to:
# Imports
import vapoursynth as vs
core = vs.get_core()
# loading source: /Users/selur/Desktop/5000frames.mp4
# color sampling YUV420P10@10, matrix:470bg, scantyp: progressive
# luminance scale TV
# resolution: 640x480
# frame rate: 25 fps
# input color space: YUV420P10, bit depth: 10, resolution: 640x480, fps: 25
# Loading /Users/selur/Desktop/5000frames.mp4 using LWLibavSource
clip = core.lsmas.LWLibavSource(source="/Users/selur/Desktop/5000frames.mp4", format="YUV420P10", cache=0, prefer_hw=0)
# making sure input color matrix is set as 470bg
clip = core.resize.Point(clip, matrix_in_s="470bg",range_s="limited")
# making sure frame rate is set to 25
clip = core.std.AssumeFPS(clip, fpsnum=25, fpsden=1)
# Setting color range to TV (limited) range.
clip = core.std.SetFrameProp(clip=clip, prop="_ColorRange", intval=1)
# adjusting output color from: YUV420P10 to YUV420P8 for x264Model (i420)
clip = core.resize.Bicubic(clip=clip, format=vs.YUV420P8, range_s="limited")
# Output
clip.set_output()
2. copy that content into a new text file you name "test.vpy"
3. insert an these additional lines before the '# adjusting output color from:' line:
for KNLMeansCL:
# testing KNLMeansCL
clip = core.knlm.KNLMeansCL(clip=clip)
# testing NNEDI3CL
clip = core.nnedi3cl.NNEDI3CL(clip = clip, field = 0)
5. call:
<PATH TO vspipe> --info <PATH to test.vpy> -
if it worked it should output the general characteristics of the script otherwise it should give you an error message.