Vapoursynth

[MonoS]

Originally Posted by Myrsloik

Yes, that should work and give you the best information.

Ok, i'll try to take a look, but it will probably take me about a week as i'm currently doing an encode.

[Myrsloik]

Originally Posted by Myrsloik

R48-RC6

Fixes premultiplied maskedmerge and a few expr problems that most likely were never encountered by anyone.

4 days without any bugs found! Final release when bug free for a whole week. Keep testing!

[Patman]

Hi,

R48 final based on python 3.7.x module? Which version of Vapoursynth will be based on python 3.8?

Gesendet von meinem HMA-L09 mit Tapatalk

[Myrsloik]

Originally Posted by Patman

Hi,

R48 final based on python 3.7.x module? Which version of Vapoursynth will be based on python 3.8?

Gesendet von meinem HMA-L09 mit Tapatalk

Yes, it will use python 3.7.x. I'll switch to 3.8.x when cython adds official support for it.

[Patman]

Originally Posted by Myrsloik

Yes, it will use python 3.7.x. I'll switch to 3.8.x when cython adds official support for it.

Thanks for the info.

Gesendet von meinem HMA-L09 mit Tapatalk

[Myrsloik]

R48 is released!

[stax76]

Is there a particular reason why vsrepo downloaded files don't have original timestamps?

staxrip has packages with lost timestamps and I would like to recover them.

[Myrsloik]

Originally Posted by stax76

Is there a particular reason why vsrepo downloaded files don't have original timestamps?

staxrip has packages with lost timestamps and I would like to recover them.

Because the way I'm handling things it's kinda annoying to set them. And it's not like you can ever trust them anyway...

[hydra3333]

Originally Posted by Myrsloik

Yes, it will use python 3.7.x. I'll switch to 3.8.x when cython adds official support for it.

just checking,

does that mean the v48 portable version
will run under portable python 3.7.5 ?
but not 3.8.0 ?

[l00t]

Originally Posted by hydra3333

just checking,

does that mean the v48 portable version
will run under portable python 3.7.5 ?
but not 3.8.0 ?

exactly

[Jukus]

What needs to be done to make a video have different FPS?
For example, I want to do something like that

from vapoursynth import core
import havsfunc as haf

clip = core.d2v.Source('index.d2v')
clip1 = core.std.Trim(clip, 0, 5579)
clip1 = haf.QTGMC(clip1, Preset='Very Slow', Sharpness=0.5, FPSDivisor=1, SourceMatch=3, Lossless=2, MatchEnhance=0.75, TFF=True)
clip2 = core.std.Trim(clip, 5580, 24186)
clip2 = haf.QTGMC(clip2, Preset='Very Slow', Sharpness=0.5, SourceMatch=3, MatchEnhance=0.75, InputType=1)
clip = clip1+clip2

clip.set_output()

but this code will not work correctly.

[poisondeathray]

Originally Posted by Jukus

What needs to be done to make a video have different FPS?
For example, I want to do something like that

from vapoursynth import core
import havsfunc as haf

clip = core.d2v.Source('index.d2v')
clip1 = core.std.Trim(clip, 0, 5579)
clip1 = haf.QTGMC(clip1, Preset='Very Slow', Sharpness=0.5, FPSDivisor=1, SourceMatch=3, Lossless=2, MatchEnhance=0.75, TFF=True)
clip2 = core.std.Trim(clip, 5580, 24186)
clip2 = haf.QTGMC(clip2, Preset='Very Slow', Sharpness=0.5, SourceMatch=3, MatchEnhance=0.75, InputType=1)
clip = clip1+clip2

clip.set_output()

but this code will not work correctly.

Internally in vapoursynth, it has to be CFR (constant frame rate)

1) You can duplicate frames and framerate in the second section (but same content speed). eg. by using core.std.Interleave

Or ,

2) you can temporarily assign a 2xFPS to the 2nd section using core.std.AssumeFPS to append sections (so it plays double speed), then use external timecodes (timestamps) method to make it VFR

[DJATOM]

Internally in vapoursynth, it has to be CFR (constant frame rate)

No. You can splice mixed fps clips, or even mixed resolution clips, vapoursynth can handle that. But encoding app might fail to understand such clip, that depends on what you're using.
I made x264 input filter and successfully provided vapoursynth timecodes (but code is a bit dirty), you can pick it here and compile: https://pastebin.com/QhjQ26qG

[_Al_]

http://www.vapoursynth.com/doc/insta...n-via-pip-pypi says that pip install should be done only after Vapoursynth is installed. So what is it for, or what is the purpose of that PIP installation?

[MonoS]

Originally Posted by Myrsloik

Yes, that should work and give you the best information.

I've reinstalled my whole system so i am now on a clean OS.
Installed Python 3.7.5 for all user (so it is in "C:\Program Files\Python37" ), installed Vapoursynth R48 and it gives me the same error.

I've then started debuging and the line that is failing is the PyImport_ImportModule in vapoursynth_api.h, the module returned is NULL.
Folder "Lib\site-packages", where i would put my script, is empty, would expect to find file "vapoursynth.pth" and the folder "vapoursynth" (checked in another system with R45), probably is that that is making VSPipe fails?

[stax76]

Originally Posted by Myrsloik

Because the way I'm handling things it's kinda annoying to set them. And it's not like you can ever trust them anyway...

If both timestamps and module version info is missing (it's missing very often in my experience), what else do we have? The file size will be the only thing left and that isn't very much.

[ChaosKing]

We have the hash...
https://github.com/vapoursynth/vsrep...t3dfilter.json

[MonoS]

Originally Posted by MonoS

I've reinstalled my whole system so i am now on a clean OS.
Installed Python 3.7.5 for all user (so it is in "C:\Program Files\Python37" ), installed Vapoursynth R48 and it gives me the same error.

I've then started debuging and the line that is failing is the PyImport_ImportModule in vapoursynth_api.h, the module returned is NULL.
Folder "Lib\site-packages", where i would put my script, is empty, would expect to find file "vapoursynth.pth" and the folder "vapoursynth" (checked in another system with R45), probably is that that is making VSPipe fails?

I think i fixed the issue downloading the portable version of Vapoursynth and putting the file vapoursynth.cp37-win_amd64.pyd inside the site-packages folder under Python37. Hope this could help you fix the problem.

[Lypheo]

core.resize.Bicubic(core.std.BlankClip(format=vs.YUV444PS), format=vs.RGB24, matrix_in=1, primaries_in=1, primaries=1) #errors out (Resize error 3074: invalid colorspace definition (1/2/1 => 0/2/1). May need to specify additional colorspace parameters.)
core.resize.Bicubic(core.std.BlankClip(format=vs.YUV444PS), format=vs.RGB24, matrix_in=1, primaries_in=1, primaries=1, transfer_in=1, transfer=1) #works
core.resize.Bicubic(core.std.BlankClip(format=vs.YUV444PS), format=vs.RGB24, matrix_in=1) #works

Seems like a bug to me. vsresize/zimg seems to think it needs to do a primary conversion when in and out primaries are specified (even when equal), and thus demands that the transfer function be specified. This causes the error mentioned above when previewing clips with vsedit (which calls vsresize internally, I presume) that ffms2 attached _Primaries != 2 and _Transfer = 2 to (this is the case for files which have a primaries flag but no transfer flag).

[Richard1485]

Originally Posted by _Al_

http://www.vapoursynth.com/doc/insta...n-via-pip-pypi says that pip install should be done only after Vapoursynth is installed. So what is it for, or what is the purpose of that PIP installation?

I was wondering the same thing.