Vapoursynth

[feisty2]

Originally Posted by Myrsloik

Broken how?

the right half of the image looks like "interlaced" kinda stuff, I'm testing on Gray16 clips

[feisty2]

and mode15/16 are broken as well, same issue like 13/14

[Myrsloik]

Originally Posted by feisty2

and mode15/16 are broken as well, same issue like 13/14

You're right, and it only seems to happen with gray16 input. That's very odd...

[Myrsloik]

Here's just a R28 work in progress version for you to try.

Changes:

fixed an image corruption bug with 9-16 bit input to rgvs when the c++ code is used
fixed division by zero issues in muldivrational in vshelper.h
blankclip can now create 0 (unknown/variable) fps clips
added float support to planedifference and planeaverage
added half support to addborders
relevant compile time options are now in the version string

[feisty2]

rgvs works okay now
good news

[jeremy33]

Is somebody have an idea ?

Originally Posted by jeremy33

Hello,

I use this PPA to install vapoursynth and some python scripts, like finesharp, on Ubuntu.
I'm in touch with djcj, the ppa maintainer, to allow the use of the python scripts without the need to make some /home config files like :

$ mkdir -p "${HOME}/.config/vapoursynth"
$ tee "${HOME}/.config/vapoursynth/vapoursynth.conf" << 'EOF'
UserPluginDir=/Path/To/filters/
EOF
- add to ~/.profile
 export PYTHONPATH=$PYTHONPATH:/Path/To/filters/

The scripts are installed here "/usr/lib/python3/dist-packages/vapoursynth-scripts/".

Is it possible to do that and how ?

Maybe at the compile time we have to use something like that (http://www.vapoursynth.com/doc/autoloading.html#linux):

SystemPluginDir, whose default value is set at compile time to $libdir/vapoursynth, or to the location passed to the --with-plugindir argument to configure.

[Are_]

Sincerely, I fail to understand what is your problem.

[jeremy33]

We simply try to install vapoursynth and some python scripts, like finesharp, on Ubuntu with this PPA and we want to make these scripts (eg. finesharp) works "out of the box".
At the moment Vapoursynth doesn't find the scripts and we need to make some config files after the install to make them work.

This is what I need to use after the install :

$ mkdir -p "${HOME}/.config/vapoursynth"
$ tee "${HOME}/.config/vapoursynth/vapoursynth.conf" << 'EOF'
UserPluginDir=/Path/To/filters/
EOF
- add to ~/.profile
export PYTHONPATH=$PYTHONPATH:/Path/To/filters/

So the question is how can we tell to Vapoursynth where the scripts are without the need of some config files after the install ?

[sl1pkn07]

install in the python3 sites-package

python -c "from distutils.sysconfig import get_python_lib; print(get_python_lib())" for get the path

example for Arch https://aur4.archlinux.org/cgit/aur....-finesharp-git

[jeremy33]

Thank you I will try

[kaefert]

I have a long vapoursynth script working on many videos resulting in a clip "sum" with RGB48 colorspace.

I want to output yuv 10bit to ffmpeg to encode as x265 mp4.

previously, I converted my RGB48 clip to YUV16 like that:

c=core.fmtc.matrix (clip=sum, mat="601", col_fam=vs.YUV, bits=16)
c=core.fmtc.resample (clip=c, css="420")
c.set_output()

but now the core.fmtc package is gone and the only replacement I could find is
core.resize.Bicubic(clip=sum, format=vs.YUV420P10) # vs.YUV420P16

but this does not seem to work: both P10 and P16 give this error:

$ "/cygdrive/c/Program Files (x86)/VapourSynth/core64/vspipe.exe" -y "join_prepared.vpy" -
YUV4MPEG2 C420 W3840 H2160 F0:0 Ip A0:0
[swscaler @ 00000015D3790020] gbrp16le is not supported as output pixel format
[swscaler @ 00000015D3790020] gbrp16le is not supported as output pixel format
[swscaler @ 00000015D379A020] gbrp16le is not supported as output pixel format
[swscaler @ 00000015D379A020] gbrp16le is not supported as output pixel format
[swscaler @ 00000015D379A020] gbrp16le is not supported as output pixel format
[swscaler @ 00000015D379A020] gbrp16le is not supported as output pixel format
[swscaler @ 00000015D379A020] gbrp16le is not supported as output pixel format
[swscaler @ 00000015CDE28020] gbrp16le is not supported as output pixel format
Error: Failed to retrieve frame 1 with error: Resize: context creation failed
Output 0 frames in 492.19 seconds (0.00 fps)

whats the correct way to do it, or do I need to step back to an older vapoursynth version still containing the core.fmtc package?

[sneaker_ger]

You can download fmtc here:
http://forum.doom9.org/showthread.php?t=166504

[kaefert]

thanks sneaker_ger!

now my next problem is: I have a ton of 16bit color-depth tif files, which all work fine to import into vapoursynth using the imwri.Read plugin, and turning up as clips in RGB48 format, just as I want them to.

But I have this one tif file, which looks just the same as all the others with all the tools I could think of like picture viewers, MediaInfo.exe and GIMP. But imported into Vapoursynth it results in a clip with the Format: Gray16

What could cause that? Or do I need to ask this question over there? http://forum.doom9.org/showthread.php?t=170981

UPDATE: strike that. I did not read MediaInfo.exe output exactly enough. color space of my problematic tif is "Y" instead of "RGB" as all the others. though I have no idea why it is a different color space, all have been created the same way by loading a JPG into imagemagick manipulating it a bit and exporting to a 16 bit tif file.

UPDATE2: okey, so it seems ImageMagick has decided based on the image content that RGB is not needed, and gray is enough. The image looked to me to have not only gray but also a little yellowish and redish taint, but maybe thats just my screen
So I found I need to force ImageMagick to output an RGB color space TIF by using the option "-type truecolor"

[Myrsloik]

Originally Posted by kaefert

thanks sneaker_ger!

now my next problem is: I have a ton of 16bit color-depth tif files, which all work fine to import into vapoursynth using the imwri.Read plugin, and turning up as clips in RGB48 format, just as I want them to.

But I have this one tif file, which looks just the same as all the others with all the tools I could think of like picture viewers, MediaInfo.exe and GIMP. But imported into Vapoursynth it results in a clip with the Format: Gray16

What could cause that? Or do I need to ask this question over there? http://forum.doom9.org/showthread.php?t=170981

No idea. Does it work if you use the imagemagick commandline stuff to convert it?

[kaefert]

Originally Posted by Myrsloik

No idea. Does it work if you use the imagemagick commandline stuff to convert it?

sorry Myrsloik for causing this confusion. I've updated my previous post to reflect what I've found: I needed to force ImageMagick to write my tif with RGB color space using -type truecolor since apperantly this one picture only had gray pixels (althought to my eyes through my screen it looked like having a yellow and/or redish taint)

[jeremy33]

Originally Posted by sl1pkn07

install in the python3 sites-package

python -c "from distutils.sysconfig import get_python_lib; print(get_python_lib())" for get the path

example for Arch https://aur4.archlinux.org/cgit/aur....-finesharp-git

I didn't try yet but is there a "cleaner" way to do that because I think it's better to put all the scripts in a folder inside python3 dist-package (dist-package is for ubuntu) like "/usr/lib/python3/dist-packages/vapoursynth-scripts/" whereas to put them directly in "dist-packages".

[sl1pkn07]

https://github.com/vapoursynth/vapoursynth/issues/156

[foxyshadis]

Originally Posted by foxyshadis

Turns out my old request was a lot easier to accomplish than I thought; merely adding another line, <VS_FOLDER>\scripts, to vapoursynth.pth let me put all of the common scripts in that folder instead of polluting my relatively difficult to access Python folder.

I prefer autoloading from a subfolder of VS, Avisynth style, but you can arrange yours as you wish. I found that VS will overwrite vapoursynth.pth each install, so creating a new vs-scripts.pth was more reliable. These files all go in the site-packages folder. As soon as you do that, you can import the script without loading it.

Note that .pth files actually add their contained folders to the runtime path, not just the import path, if that affects anything you do.

[feisty2]

@Myrsloik
will you add float point support to core functions and rgvs in the next release?
if so, that means I get to process my vids again pretty soon, and I will decide to make peace with 16bits mvtools
if not, that means I still got a lot of time to mess with filters, then I will stick to mvtools modification

[Myrsloik]

I won't have time to change that much before the next release. So no.