VSRepo - the official easy plugin manager

[ChaosKing]

BTW I added support for auto updating scripts (without releases) in (a)vsrepo. It works, but not fully tested yet.
https://github.com/theChaosCoder/avsrepo/commit/191e2ae2984d53b53aec93a05fc817e8a1893b93

It adds only the newest commit of a script. Should I make a PR when I'm finished or is this too evil :devil:
The last commit on vsrepo was generated with this function.

[Myrsloik]

BTW I added support for auto updating scripts (without releases) in (a)vsrepo. It works, but not fully tested yet.
https://github.com/theChaosCoder/avsrepo/commit/191e2ae2984d53b53aec93a05fc817e8a1893b93

It adds only the newest commit of a script. Should I make a PR when I'm finished or is this too evil :devil:
The last commit on vsrepo was generated with this function.

It's too evil. Better to force script writers to make releases.

[shader]

I'm using VS portable for a long time now.

I wanted to run R49//Python 3.8 (python-3.8.2-embed-amd64.zip) on my Win10 64bit machine with installed Python 3.7 64bit.

When I run "python vsrepo.py -p available" in the R49 folder I get the error:
Traceback (most recent call last):
File "vsrepo.py", line 100, in <module>
os.makedirs(py_script_path, exist_ok=True)
File "os.py", line 223, in makedirs
FileNotFoundError: [WinError 3] Das System kann den angegebenen Pfad nicht finden: ''


The same call in my old R48 folder works fine.

Seems that the portable version needs some packages from outside?!? At least on Win64 machine.

Can anybody help me?

[ChaosKing]

Can confirm. The py_script_path var is empty.
It works if you use the full path for python like C:\Python38\python.exe vsrepo.py -p available

[Myrsloik]

I'm using VS portable for a long time now.

I wanted to run R49//Python 3.8 (python-3.8.2-embed-amd64.zip) on my Win10 64bit machine with installed Python 3.7 64bit.

When I run "python vsrepo.py -p available" in the R49 folder I get the error:
Traceback (most recent call last):
File "vsrepo.py", line 100, in <module>
os.makedirs(py_script_path, exist_ok=True)
File "os.py", line 223, in makedirs
FileNotFoundError: [WinError 3] Das System kann den angegebenen Pfad nicht finden: ''


The same call in my old R48 folder works fine.

Seems that the portable version needs some packages from outside?!? At least on Win64 machine.

Can anybody help me?

What about R50-RC1?

[ChaosKing]

I tested it with R50. But vsrepo did not change in R50 so it's the same err.

[Myrsloik]

I tested it with R50. But vsrepo did not change in R50 so it's the same err.

Will give it a try then.

[Myrsloik]

Download the latest https://github.com/vapoursynth/vsrepo/blob/master/vsrepo.py and give it a try. There were some minor path handling issues in portable mode.

[shader]

Works, thank you!

[shader]

Not serious, but anyway...


if (args.operation in ['install', 'upgrade', 'uninstall']) == ((args.package is None) or len(args.package) == 0):
print('Package argument only required for install, upgrade and uninstall operations')
exit(1)


leads to


Traceback (most recent call last):
File "vsrepo.py", line 74, in <module>
exit(1)
NameError: name 'exit' is not defined

[Myrsloik]

Not serious, but anyway...



leads to

Doh, fixed.

[ChaosKing]

Small issue in vsrepo ... I pushed some updates for descale_script https://github.com/vapoursynth/vsrepo/blob/master/local/descale_script.json
Because the script itself does not have changed (only the descale plugin) in r4, r5, r6, the hash is the same as r3.


vsrepo recognices it as r3 and not r6 and an update does not fix it (hash stays the same)

.\vsrepo.py installed
*Descale descale r3 r6

Adding r4-6 to the ignore list would be one option. But I think vsrepo should just read the releases from bottom to top to avoid this.
What do you think?

EDIT
No wait its a totally different issue

EDIT2
script
"name": "Descale Script",
"identifier": "descale",
"modulename": "descale",

plugin
"name": "Descale",
"identifier": "tegaf.asi.xe",
"namespace": "descale",

.\vsrepo.py upgrade descale
Package Descale Script not upgraded, latest version installed
Nothing done

Both names or identifier are "descale", that seems to be the problem.

[Myrsloik]

I'm a bit sleepy but the identifier should probably be changed to descale_script. I think that's what causes the problem. I'll investigate it further tomorrow and will probably add a better check for it too.

[Myrsloik]

Things are now adjusted. The identifier is changed to descale_script which makes more sense for duplicate names.

And for "duplicate" releases simply ignore the older duplicates. That's the easiest way. They're fortunately quite rare and mostly harmless anyway.

[ChaosKing]

Does someone get an error with vsrepo.py update or is it just me?
The url works in my browser... :/


vsrepo.py update
Traceback (most recent call last):
File "D:\Apps\VapourSynth\vsrepo\vsrepo.py", line 821, in <module>
update_package_definition('http://www.vapoursynth.com/vsrepo/vspackages.zip')
File "D:\Apps\VapourSynth\vsrepo\vsrepo.py", line 627, in update_package_definition
with urllib.request.urlopen(req_obj) as urlreq:
File "C:\Python38\lib\urllib\request.py", line 222, in urlopen
return opener.open(url, data, timeout)
File "C:\Python38\lib\urllib\request.py", line 531, in open
response = meth(req, response)
File "C:\Python38\lib\urllib\request.py", line 640, in http_response
response = self.parent.error(
File "C:\Python38\lib\urllib\request.py", line 569, in error
return self._call_chain(*args)
File "C:\Python38\lib\urllib\request.py", line 502, in _call_chain
result = func(*args)
File "C:\Python38\lib\urllib\request.py", line 649, in http_error_default
raise HTTPError(req.full_url, code, msg, hdrs, fp)
urllib.error.HTTPError: HTTP Error 404: Not Found

EDIT
Seems my browser used the cached version. In Edge I get a 404 wordpress page

EDIT2
Should be working again

[Cary Knoop]

Not sure if I should report this here but VSRepo refers to an old version ffm2.dll
(from 2016).

[ChaosKing]

We have basically 2 options here:
- The ffms2 authors make a new release
- Someone make a github repo with ffms2 releases so vsrepo can use these releases. (+ auto update)

It would be too much work to track down individuall web links + keep them up to date. Of course if someone wants to do it, make a pull request on github ;-)

[Emulgator]

To not doublepost, I will link to the appropriate thread.
https://forum.doom9.org/showthread.php?p=1933141#post1933141

[MysteryX]

Does vsrepo work under Linux? Where do I find it, and any issues or limitations to be aware of?

[ChaosKing]

It's a python download script / manager for DLLs. There is no Linux support. This could change if someone would offer compiled .so files. Not see it to happen anytime soon.

See first page for link...

[MysteryX]

So although VapourSynth works in Linux, all packages need to be custom-compiled, I'd have no vsrepo support, so everything would have to be done manually?

What work would need to be done to get proper Linux support?

[ChaosKing]

So although VapourSynth works in Linux, all packages need to be custom-compiled, I'd have no vsrepo support, so everything would have to be done manually?

What work would need to be done to get proper Linux support?

Yes, vsrepo was made only for windows since only windows binaries of plugins are provided.
Welcome to the world of linux package management.

Depending on which Distro you use, many plugins may already be compiled and packaged. See http://www.vapoursynth.com/doc/installation.html#linux-installation

I saw several repos on Github with ready to use compile/install scripts for most of the plugins.


Maybe if someone does the work and provides Linux binaries (and keeps them up tp date), then I'm sure linux support could be add to vsrepo.

Relevant github issue https://github.com/vapoursynth/vsrepo/issues/33

[Are_]

So although VapourSynth works in Linux, all packages need to be custom-compiled, I'd have no vsrepo support, so everything would have to be done manually?

What work would need to be done to get proper Linux support?

vsrepo is useless in Linux, most distros have the libs and plugins already packaged ready to consume with their package managers.

Also, are you going to provide a different build that will properly dynamically link with the system libraries of every distro? Or are you going to compile them statically?

If you are new to Linux my recommendation is to get an Arch-based distro and use the already packaged plugins.

[ChaosKing]

But the problem remains that not every distro has all plugins packaged. For the average joe compiling a plugin is very challenging task. I mean people already complain that clip.std.Crop() is too compilicated instead of just crop() :devil:

What would be so bad about statically linked plugins? It's not like these are some system libs and are always in use by the system.

[Are_]

No real problem for me, but packaging that is huge. And keep in mind that not all the plugins support static linking out of the box, so you are going to have to dirty your hands with it.

I was only suggesting that using rpm / deb distros is a bad idea if you want to use vapoursynth painlessly.

[MysteryX]

I have an Arch-based distro. So how do I install those plugins?

By the way, with all the excitement around Windows 11, I expect Linux to grow a lot in the coming 1 to 3 years.

Also with Wine/Proton allowing to play most Windows games on Linux, and with the Steam Deck. That's another huge push for Linux adoption. Vapoursynth is one of those few areas that remain lacky on Linux.

[quietvoid]

I have an Arch-based distro. So how do I install those plugins?

There are a lot of plugins/scripts on the AUR. Most of them are prefixed by vapoursynth-plugin.

[MysteryX]

Cool! That's actually pretty good Linux support; for Arch with AUR at least.

Linux and MacOS should be better documented on the main website IMO.

[MysteryX]

I've installed all the packages I needed from the AUR. Only BM3D_CUDA fails to compile, and... Akarin plugin (https://github.com/AkarinVS/vapoursynth-plugin) is the only one missing from the AUR.

BM3D_CUDA gives this


==> Starting build()...
-- The CXX compiler identification is GNU 11.1.0
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Check for working CXX compiler: /usr/bin/c++ - skipped
-- Detecting CXX compile features
-- Detecting CXX compile features - done
CMake Error at /usr/share/cmake/Modules/CMakeDetermineCUDACompiler.cmake:179 (message):
Failed to find nvcc.

Compiler requires the CUDA toolkit. Please set the CUDAToolkit_ROOT
variable.
Call Stack (most recent call first):
source/CMakeLists.txt:3 (project)

[MysteryX]

vsakarin got added, that was quick! Less than 12h
https://aur.archlinux.org/packages/vapoursynth-plugin-vsakarin-git/

[sl1pkn07]

I've installed all the packages I needed from the AUR. Only BM3D_CUDA fails to compile, and... Akarin plugin (https://github.com/AkarinVS/vapoursynth-plugin) is the only one missing from the AUR.

BM3D_CUDA gives this


==> Starting build()...
-- The CXX compiler identification is GNU 11.1.0
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Check for working CXX compiler: /usr/bin/c++ - skipped
-- Detecting CXX compile features
-- Detecting CXX compile features - done
CMake Error at /usr/share/cmake/Modules/CMakeDetermineCUDACompiler.cmake:179 (message):
Failed to find nvcc.

Compiler requires the CUDA toolkit. Please set the CUDAToolkit_ROOT
variable.
Call Stack (most recent call first):
source/CMakeLists.txt:3 (project)



try now

[MysteryX]

For BM3D_CUDA, it worked after rebooting. It needs a reboot for cuda package to be detected.

One annoying thing, however, is that it requires a 3GB dependency to compile, and that dependency remains there afterwards.

[sl1pkn07]

you not need reboot. just relogin your user (or run by hand `source /etc/ld.so.conf.d/cuda.conf`). the plugin needs cuda to run. so need keep for runing (for that is setted in depends=() ). arch not separe the package in modules like ubuntu/debian. package all cuda as only one package

and please use the package comments in [AUR] if you have a problem with the packages

greetings

[Tohno_Neil]

I usually manually install VapourSynth plugins and scripts,

and last time get bugs that I can't fix (haf.QTGMC),

until I use the vsrepo, :helpful: :thanks:


vsrepo.py install havsfunc ffms2 d2v -t win64 -b "C:\VapourSynth\plugins" -s "C:\Users\Administrator\AppData\Local\Programs\Python\Python39\Lib\site-packages"

vsrepo.py install Bifrost Bilateral "CAS - Contrast Adaptive Sharpening" Cnr2 Curve Damb DCTFilter Deblock DeLogo DFMDerainbow DFTTest degrainmedian DotKill fillborders FieldHint Histogram IT LSMASHSource MCDenoise "Miscfilters (obsolete)" ReadMpls MSmoosh muvsfunc MVTools "MVTools (float)" mvsfunc NRDB Oyster DeblockPP7 Retinex RemoveGrain Scxvid SmoothUV SSIQ TCanny TComb TDeintMod TIVTC TempLinearApproximate TNLMeans vctrans VagueDenoiser VFRToCFR VSFilter VSFilterMod vsTAAmbk AWarpSharp2 xvs Yadifmod ZNEDI3 -t win64 -b "C:\VapourSynth\plugins" -s "C:\Users\Administrator\AppData\Local\Programs\Python\Python39\Lib\site-packages"

[Selur]

Please add a comment to vsrepo on github that it's only for Windows. Thanks