Vapoursynth

[bjoker]

Usually the safety shutdown temp is much higher than where some CPU-intensive application causes hangs. It's what any overclocker sees when they start finding the limits of the chip.

Thank you! You are right, it IS CPU heating issue as I solved it by disabling Overclocking my CPU (its base clock is 3.4GHz and i did OC'ed to 4GHz earlier).
Now after disabling OC, there're no more hangs. Everything works perfectly! Perhaps I could do OC to 3.7GHz again and retry.

I recommen using occt (https://www.ocbase.com/) to really test stability. I think it changed a bit in the most recent version but avx2 linpack is what I like to use to test stability. Note that the CPU usage percentage isn't a perfect indicator of actual load. It's actually really shit.

when I run occt on my AMD threadripper, it tries to open/run but closes on its own without any error. It does NOT run. Is this tool for Intel CPUs only? It ran fine on my Intel CPU laptop.

[lansing]

Thank you! You are right, it IS CPU heating issue as I solved it by disabling Overclocking my CPU (its base clock is 3.4GHz and i did OC'ed to 4GHz earlier).
Now after disabling OC, there're no more hangs. Everything works perfectly! Perhaps I could do OC to 3.7GHz again and retry.


I'm suspecting a thermal paste issue. You'll need to apply new thermal paste every couple of years to keep it fresh.

[bjoker]

I'm suspecting a thermal paste issue. You'll need to apply new thermal paste every couple of years to keep it fresh.

Bought it less than a year ago, also not much used until last April.

[Myrsloik]

I'm suspecting a thermal paste issue. You'll need to apply new thermal paste every couple of years to keep it fresh.

Those familiar with the 1950x will instead say that hitting 4ghz on air is rare. As someone who has one I can say that "overclocking" on air is a mostly pointless exercise since it at the same time disables the turbo when only a few cores are active.

This is about unrealistic expectations and not thermal paste.

[Myrsloik]

R46 RC1 is here (https://www.dropbox.com/s/wisb4gasos4ngdi/VapourSynth-R46-RC1.exe?dl=1)!

Go test the installer that no longer needs admin privileges. Everything except AVFS should work as expected with it (pismo runtime requires admin rights to install).

r46:
updated windows projects to use vs2019, inno setup 6 and zimg 2.9
the windows installer now supports installs without administrator privileges
the windows installer no longer puts a copy of vsscript.dll in the system directory and no longer writes the legacy registry entries, deprecated since r31
the windows installer will no longer offer to install the visual studio 2013 runtime since it hasn't been required by vapoursynth for a very long time
the portable install now includes all the sdk files
added a fallback to how the appdata path is retrieved which works even if %USERPROFILE% isn't set
the default number of threads used is now based on the process affinity on windows, linux and bsd
added an option to vspipe to make it not modify the current working directory
added a better equality check for the Format class in python
fixed doubleweave sometimes using the opposite field order (dubhater)
fixed broken output when stride wasn't equal to width in the python output function (stuxcrystal)
relaxed mask clip requirements in maskedmerge (dubhater)
fixed overflow with int16 in maskedmerge (dubhater)
fixed swapped fields in doubleweave (dubhater)
fixed selectevery breaking and leaking when there are no frames to return

[ChaosKing]

vapoursynth.get_core().version() still shows R45

[Myrsloik]

vapoursynth.get_core().version() still shows R45

You must have an old dll lying around somewhere. It prints the right version for me.

[ChaosKing]

Figured it out. I had vapoursynth also installed via pip and VS R45 dlls were in python site-packages. pip uninstall vapoursynth fixed it.

[lansing]

Those familiar with the 1950x will instead say that hitting 4ghz on air is rare. As someone who has one I can say that "overclocking" on air is a mostly pointless exercise since it at the same time disables the turbo when only a few cores are active.

This is about unrealistic expectations and not thermal paste.

Oh I misread, I thought he was talking about intel chip.

[masterkivat]

I'm trying to install R46-RC1, but...
https://puu.sh/DDb9B/1a147f13a1.png
...am I doing something wrong? :confused: :(

EDIT: I had no other way but to install using the "install to this user only" option, Myrsloik told me on IRC that I certainly installed Python for not all users... derp :rolleyes:

[Myrsloik]

R46-RC2 (https://www.dropbox.com/s/fzj9ou2qjafynj9/VapourSynth-R46-RC2.exe?dl=1) (probably final RC)

The installer now has more informative error messages so dudes like the one in the post before won't have to ask me.

[tuanden0]

R46-RC2 (https://www.dropbox.com/s/fzj9ou2qjafynj9/VapourSynth-R46-RC2.exe?dl=1) (probably final RC)

The installer now has more informative error messages so dudes like the one in the post before won't have to ask me.

After install this version, I got this error and x265 can't read vpy file because the plugins's path but I can preview vpy file on VSEdit :(

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\test.vpy", line 6, in <module>
clip = core.lsmas.LWLibavSource(r"E:\Download\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?

x265 [error]: unable to open input file <->
mkvmerge v34.0.0 ('Sight and Seen') 64-bit
Error: The file 'e:\Download\test.hevc' could not be opened for reading: open file error.

# Edit: I install vapoursynth via pip and it work, but the version is 45

C:\Users\Home>pip install vapoursynth
Collecting vapoursynth
Downloading https://files.pythonhosted.org/packages/b0/0c/8c18ec1db6c8cd3be0caadb2901b06161dd3117ba5bee39a6e9e369815e2/VapourSynth-45-cp37-cp37m-win_amd64.whl (817kB)
|████████████████████████████████| 819kB 819kB/s
Installing collected packages: vapoursynth
Successfully installed vapoursynth-45

[ChaosKing]

Where is you lsmas plugin located? pip doesn't install the RC version.
@Myrsloik Is there a way to see which vapoursynth dll is loaded?

Feature request for VS: print all plugin search paths AND/OR show also a full path to plugin dlls in core.get_plugins()

[Myrsloik]

Where is you lsmas plugin located? pip doesn't install the RC version.
@Myrsloik Is there a way to see which vapoursynth dll is loaded?

Feature request for VS: print all plugin search paths AND/OR show also a full path to plugin dlls in core.get_plugins()

What do you mean by which vapoursynth dll? The full path? Version? It's unclear what you want. If you simply want the path I believe GetModuleFileName() and GetModuleHandle() in the windows API is what you want.

I won't print the path to the dlls ever. The plugins are managed by VS and nothing else. Why do you even need to know this?

[Myrsloik]

After install this version, I got this error and x265 can't read vpy file because the plugins's path but I can preview vpy file on VSEdit :(



# Edit: I install vapoursynth via pip and it work, but the version is 45

Did you do a per user install? Did you check if it could load other plugins correctly?

[ChaosKing]

What do you mean by which vapoursynth dll? The full path? Version? It's unclear what you want. If you simply want the path I believe GetModuleFileName() and GetModuleHandle() in the windows API is what you want.
The location of the dll, so yes the full path. It seems a vapoursynth.__file__ in python does what I want, it shows the full path to vapoursynth.cp37-win_amd64.pyd and the vapoursynhs.dll is next to it. So this one is solved.

I won't print the path to the dlls ever. The plugins are managed by VS and nothing else. Why do you even need to know this?
Two reasons: 1. To easily find plugin duplicates. If the abc.dll is in "AppData\plugins" and the same file (or a different version) is in "vapoursynth\plugins64" only one of them is loaded (or the other ignored). But now what I re-checked the docs this is also a feature...
2. if I use get_plugins() I can't know which dll file corresponds to which plugin in the output string. I wanted to automatically track if a plugin function is changed or a new one is added (only the dll name would be enough for me).
I mean, yes, I could also build a "file to identifier connection" list I just think it is a usefull feature to have.

[tuanden0]

Did you do a per user install? Did you check if it could load other plugins correctly?

Yes, I did use a per user install.

I can load all plugin via VSEdit to preview but can't encode with x265 :devil:

[Myrsloik]

Yes, I did use a per user install.

I can load all plugin via VSEdit to preview but can't encode with x265 :devil:

NEW INFORMATION! Apparently I completely messed up the per user registry entries and will need to rework things. This probably explains some of the plugin related problems.

All user installs and portable still works so just test that for now.

[stax76]

I avoid x86 like the plague and would like to request a separate setup for x86 and x64. :)

Example:

https://github.com/stax76/mpv.net/blob/master/setup.iss

https://github.com/stax76/mpv.net/blob/master/setup.ps1

[Myrsloik]

I avoid x86 like the plague and would like to request a separate setup for x86 and x64. :)

Example:

https://github.com/stax76/mpv.net/blob/master/setup.iss

https://github.com/stax76/mpv.net/blob/master/setup.ps1

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.

[stax76]

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 (https://www.dropbox.com/s/pcpnwstvniwzric/VapourSynth64-R46-RC3.exe?dl=1)
32bit (https://www.dropbox.com/s/ai7kt0ecmgvauvk/VapourSynth32-R46-RC4.exe?dl=1)

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?
https://i.imgur.com/mEvaUXC.png

EDIT
I can't install VS 32bit on 64bit windows?
https://i.imgur.com/mkshr9z.png

[Myrsloik]

Typo?
https://i.imgur.com/mEvaUXC.png

EDIT
I can't install VS 32bit on 64bit windows?
https://i.imgur.com/mkshr9z.png

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.
https://i.imgur.com/reve9Ku.png

[Myrsloik]

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.
https://i.imgur.com/reve9Ku.png

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]

R46 RC3:

64bit (https://www.dropbox.com/s/pcpnwstvniwzric/VapourSynth64-R46-RC3.exe?dl=1)
32bit (https://www.dropbox.com/s/r0jdtijw4d8nulb/VapourSynth32-R46-RC3.exe?dl=1)

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 :eek:

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]

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

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]

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 :confused:
And the autoload after install via pip is correct at "C:\Program Files (x86)\VapourSynth\plugins64"

[VS_Fan]

R46 RC3:

64bit (https://www.dropbox.com/s/pcpnwstvniwzric/VapourSynth64-R46-RC3.exe?dl=1)
32bit (https://www.dropbox.com/s/r0jdtijw4d8nulb/VapourSynth32-R46-RC3.exe?dl=1)
I have tested 64bit without problems. But 32bit installer won't work: After doing some progress installing, it will pop a new window:
https://imgur.com/a/XL5LvAm
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]

R46 RC3/4:

64bit (https://www.dropbox.com/s/pcpnwstvniwzric/VapourSynth64-R46-RC3.exe?dl=1)
32bit (https://www.dropbox.com/s/ai7kt0ecmgvauvk/VapourSynth32-R46-RC4.exe?dl=1)

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]

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]

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]

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]

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.

[Myrsloik]

R46 is released. Here's the usual blog post (http://www.vapoursynth.com/2019/06/r46-windows-installer-fun/) with a summary of the important changes.

[fAy01]

R46 is released. Here's the usual blog post (http://www.vapoursynth.com/2019/06/r46-windows-installer-fun/) with a summary of the important changes.

https://i.imgur.com/7ampSAo.png

Could you please label the 32bit and 64bit packages.

https://i.imgur.com/MzBe4OF.png

Do I have to reinstall Python? Can I bypass it somehow?

[stax76]

It should be OK when you re-run the VS installer and select 'Install for me only'.

[fAy01]

It should be OK when you re-run the VS installer and select 'Install for me only'.

Doesn't work for 64bit installer.

[~ VEGETA ~]

I want to encode a bluray interlaced material in vapoursynth but I cannot use the .dgm file generated by dgavcindex. I even always fail to LoadPlugin it as avs plugin for no obvious reason (I tried all path shapes).

Is there anyway I can do it?

Here is my script: https://pastebin.com/VmenRNmh

BTW, I am trying to solve combing issue which is why I got to the IVTC function in there...

[DJATOM]

Just pick LWLibavSource for interlaced blu-rays if you can't use DGSource.

[jackoneill]

I want to encode a bluray interlaced material in vapoursynth but I cannot use the .dgm file generated by dgavcindex. I even always fail to LoadPlugin it as avs plugin for no obvious reason (I tried all path shapes).


You should get an error message from avs.LoadPlugin, though. What does it say?

[Pat357]

I've some problems with the update from R45 -> R46.
After installing R46 (for single user), none of the applications like VSEdit R19, VSRepoGUI can find my vapoursynth install.
My own compiled ffmpeg (--enable-vapoursynh) give my an error like "can not find VSScript.dll" upon starting.
VirtDUP can no longer open a .vpy script.

My Registry contains the correct keys as far as I know :

[HKEY_CURRENT_USER\Software\VapourSynth]
"Version"="R46"
"Path"="C:\\Users\\patri\\AppData\\Local\\Programs\\VapourSynth"
"CorePlugins"="C:\\Users\\patri\\AppData\\Local\\Programs\\VapourSynth\\core\\plugins"
"Plugins"="C:\\Users\\patri\\AppData\\Local\\Programs\\VapourSynth\\plugins"
"VapourSynthDLL"="C:\\Users\\patri\\AppData\\Local\\Programs\\VapourSynth\\core\\vapoursynth.dll"
"VSScriptDLL"="C:\\Users\\patri\\AppData\\Local\\Programs\\VapourSynth\\core\\vsscript.dll"
"PythonPath"="C:\\Users\\patri\\AppData\\Local\\Programs\\Python\\Python37\\"


Never had any problems with any previous updates, so I don't know what to do next ....
After adding "C:\Users\patri\AppData\Local\Programs\VapourSynth\core" to my PATH, I can run my own compiled FFmpeg & MPV again.
Also VSPIPE is working fine : I get correct output from my scripts.
Python 3.70 is in my path and produces a correct list from all my plugins.
Also the normal vsrepo can install plugins and list the available plugins versus the installed.

Where do things like VSRepoGUI/VSEdit look for the installation ? Apparently not at my registry key .....
Also why is the VFW module not working ? It looks like the system is unable to find it...

Any clues to continue from here ?
I've already uninstalled and reinstalled several times, but no avail..

[stax76]

I would like to request a setup option (enabled by default for user setup) to add vspipe to the PATH environment variable on Windows if it's not already available. As far as I know modifying user PATH does not require elevated privileges, nor does it require a reboot.

[Myrsloik]

I've some problems with the update from R45 -> R46.
After installing R46 (for single user), none of the applications like VSEdit R19, VSRepoGUI can find my vapoursynth install.
My own compiled ffmpeg (--enable-vapoursynh) give my an error like "can not find VSScript.dll" upon starting.
VirtDUP can no longer open a .vpy script.

My Registry contains the correct keys as far as I know :

...


Never had any problems with any previous updates, so I don't know what to do next ....
After adding "C:\Users\patri\AppData\Local\Programs\VapourSynth\core" to my PATH, I can run my own compiled FFmpeg & MPV again.
Also VSPIPE is working fine : I get correct output from my scripts.
Python 3.70 is in my path and produces a correct list from all my plugins.
Also the normal vsrepo can install plugins and list the available plugins versus the installed.

Where do things like VSRepoGUI/VSEdit look for the installation ? Apparently not at my registry key .....
Also why is the VFW module not working ? It looks like the system is unable to find it...

Any clues to continue from here ?
I've already uninstalled and reinstalled several times, but no avail..

You installed for the current user only. This puts the registry entries in HKCU instead of HKLM which most likely is why they can't be found by existing applications. You'll simply have to wait for them to be updated and point out this (optional on install) change to them.