Vapoursynth

[stax76]

Originally Posted by Myrsloik

I've split it into separate 32 and 64 bit installers simply because it's so much easier. Now I just have to test everything again which is super boring.

Maybe writing a test script in a language you want to learn could be fun?

I didn't expect that you like the idea.

Will be testing it once it's done.

[Myrsloik]

R46 RC3/4:

64bit
32bit

The installer was reworked quite a bit to split it into two parts. The registry entries for the 32 bit version are now under a key called Vapoursynth-32 instead so they don't overlap in HKCU.

So test all the different combinations of options and report if it works/doesn't work. Especially for the 32 bit version.

[ChaosKing]

Typo?


EDIT
I can't install VS 32bit on 64bit windows?

[Myrsloik]

Originally Posted by ChaosKing

Typo?


EDIT
I can't install VS 32bit on 64bit windows?

Fixed, use the same download link.

Not a typo, just a stylistic choice.

[ChaosKing]

32 bit (per user install) works great. 64 Bit installer also installed without problems and VS seems to work as usual.

Suggestion: change "Python 3.7" to "Python 3.7 (32-Bit)" in 32 bit installer, as a hint for newbies.

[Myrsloik]

Originally Posted by ChaosKing

32 bit (per user install) works great. 64 Bit installer also installed without problems and VS seems to work as usual.

Suggestion: change "Python 3.7" to "Python 3.7 (32-Bit)" in 32 bit installer, as a hint for newbies.

Makes sense. I've updated the installers with this small change now.

[stax76]

For me it works (x64 all users), thanks for improving it.

[tuanden0]

Originally Posted by Myrsloik

R46 RC3:

64bit
32bit

The installer was reworked quite a bit to split it into two parts. The registry entries for the 32 bit version are now under a key called Vapoursynth-32 instead so they don't overlap in HKCU.

So test all the different combinations of options and report if it works/doesn't work. Especially for the 32 bit version.

I installed R46 RC 64bit
I got same error with previous version when installed with per user

Script evaluation failed:
Python exception: No attribute with the name lsmas exists. Did you mistype a plugin namespace?

Traceback (most recent call last):
File "src\cython\vapoursynth.pyx", line 1942, in vapoursynth.vpy_evaluateScript
File "src\cython\vapoursynth.pyx", line 1943, in vapoursynth.vpy_evaluateScript
File "e:\Download\Source\test.vpy", line 6, in <module>
clip = core.lsmas.LWLibavSource(r"E:\Download\Source\test.mkv")
File "src\cython\vapoursynth.pyx", line 1675, in vapoursynth._CoreProxy.__getattr__
File "src\cython\vapoursynth.pyx", line 1537, in vapoursynth.Core.__getattr__
AttributeError: No attribute with the name lsmas exists. Did you mistype a plugin namespace?

[Myrsloik]

Originally Posted by tuanden0

I installed R46 RC 64bit
I got same error with previous version when installed with per user

Did you install VS R45 using my installer and did that work?

If you installed it through pip you have a portable version and it autoloads from another directory.

[tuanden0]

Originally Posted by Myrsloik

Did you install VS R45 using my installer and did that work?

If you installed it through pip you have a portable version and it autoloads from another directory.

I installed VS R45 and it work.

I tried to install R46 and can only preview on VSEdit.
So I have to install vapoursynth via pip to get it work again
And the autoload after install via pip is correct at "C:\Program Files (x86)\VapourSynth\plugins64"

[VS_Fan]

Originally Posted by Myrsloik

R46 RC3:

64bit
32bit

I have tested 64bit without problems. But 32bit installer won't work: After doing some progress installing, it will pop a new window:

Error creating registry key:
HKEY_LOCAL_MACHINE\'SOFTWARE\Vapoursynth'
RegCreateKeyEx failed; code 87.
The parameter is incorrect.

It will repeatedly pop the same error window if you click on "retry" or "ignore". Leaving "cancel" as the only option, which will rollback any changes made.

[Myrsloik]

Originally Posted by Myrsloik

R46 RC3/4:

64bit
32bit

The installer was reworked quite a bit to split it into two parts. The registry entries for the 32 bit version are now under a key called Vapoursynth-32 instead so they don't overlap in HKCU.

So test all the different combinations of options and report if it works/doesn't work. Especially for the 32 bit version.

Link updated with an RC4 installer for 32 bit. Fixes the invalid registry entries when doing all user installs... and shows just how little attention I paid to 32 bit stuff.

[VS_Fan]

Originally Posted by Myrsloik

Link updated with an RC4 installer for 32 bit. Fixes the invalid registry entries when doing all user installs... and shows just how little attention I paid to 32 bit stuff.

Thanks, they are both working. 64bit and 32bit are autoloading plugins respectively from:

• %ProgramFiles%\VapourSynth\plugins
• %ProgramFiles(x86)%\VapourSynth-32\plugins

[ChaosKing]

How about a function to report autoloading paths in their respective order? Similar to vsrepo paths.

[Myrsloik]

Originally Posted by ChaosKing

How about a function to report autoloading paths in their respective order? Similar to vsrepo paths.

I don't understand the request. Basically you should only ever use the user autoload dir unless you have some environment set up in advance for lots of people.

[ChaosKing]

For easier debugging. For example the user tuanden0, with his R45/R46 plugin loading problem, could quickly check which folder is used. I also had 1-2 cases where I just didn't know which of my vapoursynth versions (or which plugin folder, portable+installed) are currently "active".

EDIT:

Basically you should only ever use the user autoload dir unless you have some environment set up in advance for lots of people.

user autoload dir = the folder in appdata?

I for example use the plugins64 folder (and custom VS installation). It is a bit annoying to always open the appdata folder. And for newbies even more since appdata is hidden by default.
vsrepo "fixes" it for us, but not for all plugins.

[Myrsloik]

Yes, the one in appdata where vsrepo also puts things by default. I've added a convenient shortcut in the start menu in R46.

[lansing]

If I'm converting a dvd source to rgb, should I be using matrix_in_s="170m" instead of "709"?

clip = core.resize.Bicubic(clip, matrix_in_s="170m", format=vs.RGBS)

[Keiyakusha]

Originally Posted by lansing

If I'm converting a dvd source to rgb, should I be using matrix_in_s="170m" instead of "709"?

Short answer: yes (if this is NTSC (US, JP) DVD though)
Longer answer: you shouldn't be using matrix_in_s at all, unless your input clip does not have this property for some reason (which would result in an error) or you are sure your clip is wrong and you want to correct that.

[lansing]

Originally Posted by Keiyakusha

Short answer: yes (if this is NTSC (US, JP) DVD though)
Longer answer: you shouldn't be using matrix_in_s at all, unless your input clip does not have this property for some reason (which would result in an error) or you are sure your clip is wrong and you want to correct that.

I want to apply a lut on the clip inside vs, so I need to make sure I convert it correctly, as I always got confuse with matrix_s and matrix_in_s.