VSRepo - the official easy plugin manager

[ChaosKing]

Is this a good time to bring up the namespace issue? :D

I want to add https://github.com/sekrit-twc/EdgeFixer to vsrepo but we already have https://github.com/MonoS/VS-ContinuityFixer with the same namespace edgefixer.json

[Myrsloik]

Is this a good time to bring up the namespace issue? :D

I want to add https://github.com/sekrit-twc/EdgeFixer to vsrepo but we already have https://github.com/MonoS/VS-ContinuityFixer with the same namespace edgefixer.json

We need to have a fight to the death!

Actually the MonoS version should go since it's an obsolete fork. So make a replacement package and it's all good.

[ChaosKing]

ContinuityFixer is dead, long live EdgeFixer!

[kypec]

Is this tool supposed to work only on Windows platform? Because trying to run it on Linux like this python3 vsrepo.py install hnwvsfunc ffms2 gives me only :confused: Traceback (most recent call last):
File "vsrepo.py", line 35, in <module>
import winreg
ModuleNotFoundError: No module named 'winreg'

[Myrsloik]

Is this tool supposed to work only on Windows platform? Because trying to run it on Linux like this python3 vsrepo.py install hnwvsfunc ffms2 gives me only :confused: Traceback (most recent call last):
File "vsrepo.py", line 35, in <module>
import winreg
ModuleNotFoundError: No module named 'winreg'


Yes, it's windows only.

[kypec]

Yes, it's windows only.

OK, and how is one supposed to install VS plugins on Linux then? ffms2 for instance, I couldn't find installation instructions neither on your VapourSynth page nor on FFMS github...

[StainlessS]

AutoLoading:- http://www.vapoursynth.com/doc/autoloading.html

More stuff:- Google "vapoursynth install plugins linux" (EDIT: Excluding the double quotes)
https://www.google.com/search?source=hp&ei=GpwOXJ2xOtCXsAf5ua7YCA&q=vapoursynth+install+plugins+linux&btnK=Google+Search&oq=vapoursynth+install+plugins+linux&gs_l=psy-ab.3...46.6438..6743...0.0..0.774.6279.1j12j5j1j2j2j1....2..0....1..gws-wiz.......0j0i131j0i10j0i30j0i22i30j0i22i10i30j33i22i29i30.GZB1zOcGccA

EDIT: And from D9 forum only:- Google "vapoursynth install plugins linux site:forum.doom9.org"
https://www.google.com/search?ei=c54OXN35CdGX1fAPn_Og4Ao&q=vapoursynth+install+plugins+linux+site%3Aforum.doom9.org&oq=vapoursynth+install+plugins+linux+site%3Aforum.doom9.org&gs_l=psy-ab.3..0i71l2.0.0..39740...0.0..0.0.0.......0......gws-wiz.qWv89ZQjA_c

EDIT: And from Vapoursynth.com only:- Google "vapoursynth install plugins linux site:vapoursynth.com"
https://www.google.com/search?ei=t50OXNiMNbuc1fAPqtaX6As&q=vapoursynth+install+plugins+linux+site%3Avapoursynth.com&oq=vapoursynth+install+plugins+linux+site%3Avapoursynth.com&gs_l=psy-ab.3...40613.40613..41226...0.0..0.98.98.1......0....1j2..gws-wiz.......0i71.whXPltYrUqY

EDIT: Enclose linux in above Google search in double quotes if eg post MUST HAVE linux in results posts.

[Are_]

Most probably somebody have them packaged for your distro, I know Arch, Ubuntu (and anybody that can use their packages) and Gentoo have them. If not you will have to compile and install them yourself.

[kypec]

Most probably somebody have them packaged for your distro, I know Arch, Ubuntu (and anybody that can use their packages) and Gentoo have them. If not you will have to compile and install them yourself.

Could you please post a link to Ubuntu PPA with such packages? :thanks:
I' mostly interested in recent build of ffms2 VapourSynth plugin. I am desperately trying to compile it myself from sources but can't get past configure step, even though I have built fairly recent ffmpeg following this thorough guide (https://trac.ffmpeg.org/wiki/CompilationGuide/Ubuntu). The farthest I have been able to get was after specifying my local paths like this: kypec@acer:~/ffms2$ ./configure FFMPEG_CFLAGS="/home/kypec/ffmpeg_build/include" FFMPEG_LIBS="/home/kypec/ffmpeg_build/lib"
It seems that it fails with libswscale recognition, though the files reported as missing (https://pastebin.com/ZXsucmuV) are there as expected. I'll be extremely grateful for any help with building this plugin!

[VS_Fan]

Could you please post a link to Ubuntu PPA with such packages?

From the VS documentation (http://www.vapoursynth.com/doc/installation.html#linux-installation-from-packages): Ubuntu – PPA (https://launchpad.net/~djcj/+archive/ubuntu/vapoursynth)

vapoursynth-extra-plugins - 20180501-1~bionic package includes ffms2 2.23.1

darealshinji (a.k.a. djcj) has a repo (https://github.com/darealshinji/vapoursynth-plugins)that contains all the sources used for the package

[ChaosKing]

I think it would be nice if vsrepo or vsupdate would have a "search for dependencies for filter/script XY in repo" function. Because I actually forgot to look for dependencies in vs-scripts while replacing edgefixer. Luckily there weren't any, so nothing broke. With this one can quickly check if replacing a filter would break stuff.

[Myrsloik]

Can someone help with VMAF r3 models? That one just has so many files to list and I don't have that much time to do it mysef.

[ChaosKing]

I still should have my crappy models hash script somewhere that I used vor v1. Wait for my PR :)
I was thinking if a "hash this folder" or "hash everything inside this zip" (and create a release entry ofc) could be implemented in vsrupdate.
Something like vsrupdate -lazypack path/url -version 1.2.3 -remove-path "plugins64" -target vmaf_model

[Myrsloik]

I still should have my crappy models hash script somewhere that I used vor v1. Wait for my PR :)
I was thinking if a "hash this folder" or "hash everything inside this zip" (and create a release entry ofc) could be implemented in vsrupdate.
Something like vsrupdate -lazypack path/url -version 1.2.3 -remove-path "plugins64" -target vmaf_model

Yes, I also thought about implementing it. Then I saw the pile of actually paid work with deadlines I've got to do.

[ChaosKing]

Idea for some automation: compile it, zip it and upload to ftp via travis-ci.

[Pat357]

Upon upgrade-all using vsrepo, it places the 64bit TCanny in the 32 bit plugin directory.
Because there is no 32bit version for TCanny r12, I'd expect vsrepo not to touch the plugins32 directory.


{
"name": "TCanny",
"type": "VSPlugin",
"description": "Canny edge detection",
"website": "https://github.com/HomeOfVapourSynthEvolution/VapourSynth-TCanny",
"doom9": "https://forum.doom9.org/showthread.php?t=172158",
"category": "Other",
"identifier": "com.holywu.tcanny",
"namespace": "tcanny",
"github": "https://github.com/HomeOfVapourSynthEvolution/VapourSynth-TCanny",
"releases": [
{
"version": "r12",
"published": "2019-02-05T10:01:28Z",
"win32": {
"url": "https://github.com/HomeOfVapourSynthEvolution/VapourSynth-TCanny/releases/download/r12/TCanny-r12.7z",
"files": {
"TCanny.dll": [
"plugins64/TCanny.dll",
"ce9bb45071b326c6c8e626da2b94ea2b86fe2ee39a1be5bd14a065ac42547121"
]
}
},
"win64": {
"url": "https://github.com/HomeOfVapourSynthEvolution/VapourSynth-TCanny/releases/download/r12/TCanny-r12.7z",
"files": {
"TCanny.dll": [
"plugins64/TCanny.dll",
"ce9bb45071b326c6c8e626da2b94ea2b86fe2ee39a1be5bd14a065ac42547121"
]
}
}
},

[Myrsloik]

TCanny fixed. The script gets a bit confused when one type of binaries disappears sometimes.

[lansing]

vcmove is missing from the repo:

https://forum.doom9.org/showthread.php?t=171414

[ChaosKing]

It's there https://github.com/vapoursynth/vsrepo/blob/master/local/vcmove.json

[lansing]

It's there https://github.com/vapoursynth/vsrepo/blob/master/local/vcmove.json

Oh I saw it now, I must be looking at the "w" section instead of "v" on the listing

[Myrsloik]

I'd really appreciate it if someone could take the time to manually update the https://github.com/HomeOfVapourSynthEvolution/VapourSynth-Waifu2x-w2xc packages since it's a complicated one.

The best strategy is probably to keep both w2xc.json and w2xc_models.json and simply make them both point to the same file.

[ChaosKing]

done, see PR.

[Myrsloik]

done, see PR.

Nice. I guess the other small tasks I've got lying around would be to go through this rejected pull request and do things correctly. After that we're up to date again.

https://github.com/vapoursynth/vsrepo/pull/98

[MeteorRain]

https://github.com/HomeOfVapourSynthEvolution/VapourSynth-DeLogo
is deprecated in favor of
https://github.com/HomeOfAviSynthPlusEvolution/DelogoHD

DelogoHD supports both AviSynth+ and VapourSynth interfaces, and has SIMD optimizations and native HBD support from YUV420P8 up to YUV444P16.

[ChaosKing]

PR is ready. Should vsrepo show a warning if a package is deprecated? I mean should we add a new field like "deprecated": "deleogohd" to vsrepo. Would then show "Delogo is deprecated, better install/use DelogoHD". But it won't happen very often...

[Myrsloik]

I'll add some kind of deprecation warning then now that we actually have something to deprecate...

[Boulder]

Muvsfunc fetched by VSRepo is a very old version. Is there any way to make VSRepo use the one from github?

[Myrsloik]

Muvsfunc fetched by VSRepo is a very old version. Is there any way to make VSRepo use the one from github?

Just tell the maintainer to make an actual github release and it'll be picked up automatically.

[lansing]

There is a more up to date descale plugin from one of its fork

https://github.com/BluBb-mADe/vapoursynth-descale/releases

[Myrsloik]

There is a more up to date descale plugin from one of its fork

https://github.com/BluBb-mADe/vapoursynth-descale/releases

The original author is still around so it has to be renamed or I won't include it.

[Myrsloik]

We're missing l-smash source I think. No surprise considering how elusive the binaries and releases are but lots of people use it so it'd be nice to have.

[ChaosKing]

The only github repo with "vsrepo auto update compatibility" is this one https://github.com/HomeOfAviSynthPlusEvolution/L-SMASH-Works
I could make a PR, a package exists already https://github.com/theChaosCoder/avsrepo/blob/master/local/lsmash.json

p.s. yes, the binary supports both avs and vs

[Myrsloik]

The only github repo with "vsrepo auto update compatibility" is this one https://github.com/HomeOfAviSynthPlusEvolution/L-SMASH-Works
I could make a PR, a package exists already https://github.com/theChaosCoder/avsrepo/blob/master/local/lsmash.json

p.s. yes, the binary supports both avs and vs

That'd be nice. It's not ancient either so better than nothing.

[ChaosKing]

That'd be nice. It's not ancient either so better than nothing.

Arghh it was a different one. This one only supports avisynth :o

[ChaosKing]

I made a handy script to quickly check for new dependencies in VS-scripts. Maybe it can also be added to vsrupdate.
It downloads the latest script und searches for all known namespaces.

EDIT: maybe it would be also a good idea to track removed plugins (namespaces)?

print('Checking dependencies')

with open('vspackages.json', 'r', encoding='utf-8') as vsp:
packages = json.load(vsp)['packages']

for plugin in packages:
if (plugin['type'] == 'PyScript'):
os.system("vsrepo.py -p -d install " + plugin.get('modulename'))
print("\nDependencies for: ", plugin.get('modulename'))
print("------------------")

filename = list(plugin['releases'][0]['script']['files'].keys())[0]
with open(filename, 'r', encoding='utf-8') as module:
current_script = module.read()
deps = []
deps_new = []
for p in packages:
if (p['type'] == 'VSPlugin'):
search = "." + p['namespace'] + "." # search for core .dfttest. DFTest() and clip .dfttest. DFTest(). Seems to be reliable enough...
if search in current_script:
deps.append(p['identifier'])
if not p['identifier'] in plugin['dependencies']:
deps_new.append(p['identifier'])
print(p['identifier'])
print("NEW: ", deps_new)

[Myrsloik]

What do you even mean by "track removed plugins"? Either they're there or not...

[ChaosKing]

What do you even mean by "track removed plugins"? Either they're there or not...

If a script gets updated and does not use plugin xy anymore. There is no need to keep it as a dependency then? (it won't happen very often)

[Myrsloik]

If a script gets updated and does not use plugin xy anymore. There is no need to keep it as a dependency then? (it won't happen very often)

That's so rare doing it manually is fine. Just like adding additional dependencies manually generally is fine too since they're rarely added.

Since VSRepo uses unique strategies (keeps no state and tries to figure out the mess you've got) there's only so much you can with regards to tracking these no longer required plugins for removal.

[Myrsloik]

Package requests:
https://github.com/Irrational-Encoding-Wizardry/Vapoursynth-RemapFrames
and f3kdb

[ChaosKing]

Pushed remapframes.
There is no f3kdb repo with releases. But we have neo_f3kdb which is basically f3kdb + two more modes

[Myrsloik]

Pushed remapframes.
There is no f3kdb repo with releases. But we have neo_f3kdb which is basically f3kdb + two more modes

Right, I completely forgot that. Then it's pointless.

[ChaosKing]

What is the correct/preferred way again for package file names?

1# MyMoDulE.json <=> MyMoDulE.py
2# mymodule.json <=> MyMoDulE.py

Most script packages follows 1# but some also 2#.
I would like to correct the script packages to 1#

[ChaosKing]

What is the correct/preferred way again for package file names?

1# MyMoDulE.json <=> MyMoDulE.py
2# mymodule.json <=> MyMoDulE.py

Most script packages follows 1# but some also 2#.
I would like to correct the script packages to 1#

I noticed it because VSRepoGUI shows a link to every git package and some are not working bcs it is assumed that Module Name = File Name. Otherwise I don't know how to direct link as the url is case sensitive.

[Myrsloik]

What is the correct/preferred way again for package file names?

1# MyMoDulE.json <=> MyMoDulE.py
2# mymodule.json <=> MyMoDulE.py

Most script packages follows 1# but some also 2#.
I would like to correct the script packages to 1#

I noticed it because VSRepoGUI shows a link to every git package and some are not working bcs it is assumed that Module Name = File Name. Otherwise I don't know how to direct link as the url is case sensitive.

Simple rules:
For plugins it's always the namespace which is lowercase.
For scripts it's generally the lowercased main script filename. In case of collisions with a plugin name you append _script.

Maybe I accidentally merged something that doesn't follow this pattern in which case you're welcome to fix it.

[shader]

I successfully installed neo_f3kdb in VS 64bit portable on Win10. neo-f3kdb.dll is now in pluginsfolder.
But when I run "vsrepo.py installed" all installed plugins are listed except that one.

[ChaosKing]

Did you run your command with -p for portable?

vsrepo installed looks in %appdata%\VapourSynth\plugins64
vsrepo -p installed looks in plugins64

[shader]

@ChaosKing You got it!!!

In %appdata%\VapourSynth\plugins64 there was an old vspackages.json without neo f3kdb inside.
I just used -p for install and update, but forgot it when running installed.

[ChaosKing]

@Myrsloik You missed some packages in your last packages update (descale + neo_f3kdb). Has the updater not detected it?

[Myrsloik]

@Myrsloik You missed some packages in your last packages update (descale + neo_f3kdb). Has the updater not detected it?

They weren't properly detected and I didn't have time to manually poke around. I think there's some updater bug causing the descale failure too.

[ChaosKing]

Strange, because on my machine it was detected (and updated) properly, descale plugin and script.