VSDB - A VapourSynth Database

[ChaosKing]

*BETA- work in progress*


I'm creating a database for vapoursynth to make our lives easier. The main issue with VS is that there is no complete list of what's ported and what's not.
I know there's http://www.vapoursynth.com/doc/pluginlist.html but it's not good enough.

Did You know that there are at least 9 dehalo functions ported to VS?
Well with VSDB you can now find out easily :D

It also acts as a web gui for VSRepo (https://forum.doom9.org/showthread.php?t=175590) (ideally all plugins will be available via vsrepo someday)


The main "problems" what I have now is this:
- categorize all plugins (need help!). I used the categories from vsrepo and http://www.vapoursynth.com/doc/pluginlist.html for now, but it's a bit limited (or most would go into "others"). I added a Collection category for scripts like havsfunc or muvsfunc. A less extreme version of http://avisynth.nl/index.php/External_filters would be nice, suggestions?

Current categories:

Anti-aliasing
Collection
Color/Levels manipulation
Dehaloing
Deinterlacing
Denoising
Dot Crawl and Rainbows
Inverse Telecine
Line Darkening
Other
Resizing and Format Conversion
Scripts
Sharpening
Source/Output
Subtitles
unknown


- All functions inside a "Collection" are shown as a separate item in the table. They are just copies of a "Collection entry" with name, description and category replaced (for now). I don't know how to represent them better. Should I remove the other columns for them (Version, Links) since they are redundant now?


What features would you like? What data or relations are important? Maybe I'm missing something.

Update

New url is: http://vsdb.top (.top domain was cheap lol)
If you want to add or edit a plugin go to http://vsdb.top/dashboard
login/pw vsdbhelper@vsdb.top and vsdbhelper as the pw

Github: https://github.com/theChaosCoder/vsdb
Json export https://github.com/theChaosCoder/vsdb-json

Todo:
- Add some statistics
- auto fetch new vsrepo updates
- some styles are still old
- export to json files on github (as a backup and to keep track of what changed)

[fAy01]

That's nice. Thank you. Could you possibly add release date for each plugin/script/etc as well?

[Myrsloik]

That's nice. Thank you. Could you possibly add release date for each plugin/script/etc as well?

That's not stored in the VSRepo package files yet. I'm going to add it the in next few days.

[fAy01]

That's not stored in the VSRepo package files yet. I'm going to add it the in next few days.

:thanks:

[ChaosKing]

Alpha2
Check out the dropdown infos.

[lansing]

Are the plugin listing read from a database or files or just hardcoded?

I don't like the auto stretching table width when maximize, makes it hard to read with a big block of empty space in between.

Also in the pagination, it doesn't go back to the top when I click on next page.

[ChaosKing]

I have a mysql db, but in this case it's harcoded (generated by my script). I'm using https://datatables.net

[poisondeathray]

Maybe add another category dealing with color/levels manipulation - so things like tweak(adjust.py) , gradcurve, smoothlevels, maybe even timecube, etc... (I'm sure there are many more) could probably be organized under that category.

[Myrsloik]

Maybe add another category dealing with color/levels manipulation - so things like tweak(adjust.py) , gradcurve, smoothlevels, maybe even timecube, etc... (I'm sure there are many more) could probably be organized under that category.

I'll add that category to VSRepo too. Makes sense.

[fAy01]

Would you consider listing color formats supported by the plugins/scripts/etc in your database? Similar to avs: http://avisynth.nl/index.php/External_filters
It is very helpful for working with different color formats.

[ChaosKing]

Is this relevant in VS? Different formats usually *just* works in VS (ok, plugins often without rgb support).
I would include such information if someone will provide it or knows an easy way to get it programmatically.

I think bitsPerSample(8bit, 16, 32) is a more interessting value then colorFamily. (at least for me)

[ChaosKing]

I added a bit depth column with values like: 8 int, 8-16 int / 32 float

And I got an idea. I should be able to get all supported bit depth and color space values by just a simple try and catch block. Will try it tomorrow.

For example LSFmod (with float support) from hnwvsfunc (For example LSFmod (with float support) from hnwvsfunc throws an exception with 16 bit float bcs it is using std.Minimum and it only supports clips with 8..16 bits integer per sample or float.)throws an exception with 16 bit float bcs it is using std.Minimum and it only supports clips with 8..16 bits integer per sample or float.

//Edit
@Myrsloik I think the docs are not up to date or am I reading this wrong?
http://www.vapoursynth.com/doc/functions/minimum_maximum.html#std.Minimum
Clip to process. It must have integer sample type, and bit depth between 8 and 16. If there are any frames with float samples or bit depth greater than 16, an error will be returned.
But this works...
clip = mvf.Depth(clip, 32, sample=1)
clip = hnwvsfunc.LSFmod(clip)

[Wolfberry]

//Edit
@Myrsloik I think the docs are not up to date or am I reading this wrong?
http://www.vapoursynth.com/doc/functions/minimum_maximum.html#std.Minimum


@ChaosKing I am aware of the documentation is outdated, so I made a pull request 2 weeks ago and it's merged.

The doc on vapoursynth.com is created using Sphinx, and it should be updated once R45 is out.

And very few filter support half precision, so when talking about float support I mean single precision (32-bit float)

[ChaosKing]

ahh ok thx for the info

My automation attempt kinda works for simple plugins, others have different parameter dependencies and my automation fails. I guess it's better to do this by hand even it this take some time (helpers are very welcome!)
I also added a colorspace column now.
//Edit
How should the color space formats be represented. YV12 vs YUV420 ? or just YUV, GRAY, RGB

The next step would be a web backed so people can edit the stuff.

[fAy01]

ahh ok thx for the info

My automation attempt kinda works for simple plugins, others have different parameter dependencies and my automation fails. I guess it's better to do this by hand even it this take some time (helpers are very welcome!)
I also added a colorspace column now.
//Edit
How should the color space formats be represented. YV12 vs YUV420 ? or just YUV, GRAY, RGB

The next step would be a web backed so people can edit the stuff.

YUV420 <-- this.

[ChaosKing]

So basically we take this list then http://www.vapoursynth.com/doc/pythonreference.html#format-constants
What about YCbCr and YCgCo, is there also a YCgCo420, YCgCo422, YCgCo444 etc representation?

[ChaosKing]

So currently this is how it would look like:
nnedi3
color space: GRAY, YUV4XX, RGB
bit depth: 8-16 int
SangNom
color space: GRAY, YUV4XX, RGB
bit depth: 8-16 int / 32 float

or is this better
nnedi3
supported formats: GRAY8, GRAY10, GRAY12, GRAY16, YUV420P8, YUV422P8, YUV444P8, ... YUV444P16, RGB24, ... RGB48
SangNom
supported formats: GRAY8, GRAY10, GRAY12, GRAY16, YUV420P8, YUV422P8, ... YUV444P8, ... YUV444P16, YUV444PS32, RGB24, ... RGB48, RGBS

or
nnedi3
supported formats: GRAY8-16, YUV4XXP8-16, RGB24-48
SangNom
supported formats: GRAY8-16, GRAYS, YUV4XXP8-16, YUV4XXPS32, RGB24-48, RGBS

[fAy01]

nnedi3
supported formats: GRAY8, GRAY10, GRAY12, GRAY16, YUV420P8, YUV422P8, YUV444P8, ... YUV444P16, RGB24, ... RGB48
SangNom
supported formats: GRAY8, GRAY10, GRAY12, GRAY16, YUV420P8, YUV422P8, ... YUV444P8, ... YUV444P16, YUV444PS32, RGB24, ... RGB48, RGBS


This one.

What about YCbCr and YCgCo, is there also a YCgCo420, YCgCo422, YCgCo444 etc representation? <-- unsure.

[ChaosKing]

Really? Wasn't expecting that since the lists will be very long like this.

I wanted to list ALL formats but were too lazy hence the ... But maybe GRAY8-GRAY16 will be better?

[Myrsloik]

This one.

What about YCbCr and YCgCo, is there also a YCgCo420, YCgCo422, YCgCo444 etc representation? <-- unsure.

That's insane. Many filters have support for 4*10*5*5 = 1000 formats.

The maximum number is 4*25*5*5 = 2500. Blankclip, crop and addborders support that. Even if you ignore subsampling you still end up with 40+ regularly.

[ChaosKing]

@Myrsloik Which one do you prefer? Or is there maybe another "better" representation?
I still like the first one for its compactness and readability.

color space: GRAY, YUV4XX, RGB
bit depth: 8-16 int / 32 float

[Myrsloik]

@Myrsloik Which one do you prefer? Or is there maybe another "better" representation?
I still like the first one for its compactness and readability.

color space: GRAY, YUV4XX, RGB
bit depth: 8-16 int / 32 float

That's the most reasonable representation. Just call it YUV and nothing else. Probably mention subsampling too if there are specific requirements.

[ChaosKing]

Just call it YUV and nothing else. Probably mention subsampling too if there are specific requirements.

I saw some avs ports that only supports YV12, so I would then make it specific with YUV420 otherwise YUV = YUV4XX

[unix]

Why Xsharpen not available?
"VSRrepo is NOT available! "

[ChaosKing]

Pushed Alpha3, added color space & bit depth for 90% of the plugins and hnwvsfunc, made some formatting/fixes.
@unix Because it is not in vsrepo (yet). I will push my script collection incl. xsharpen later

[Wolfberry]

Here is Xsharpen (https://forum.doom9.org/showthread.php?p=1803044) by Myrsloik
It is not available simply because there's no definition created.
ChaosKing will probably integrate those lost functions into lostfunc someday

Edit: posted too late

[unix]

Thank you ChaosKing & Wolfberry

[Myrsloik]

Here is Xsharpen (https://forum.doom9.org/showthread.php?p=1803044) by Myrsloik
It is not available simply because there's no definition created.
ChaosKing will probably integrate those lost functions into lostfunc someday

Edit: posted too late

I'll create a proper repository it. Completely forgot I ported it...

Edit: the home is here (https://github.com/myrsloik/WarpSharpSupport)

Will create a proper release and package for it in a bit.

[ChaosKing]

Big update. VSDB has a new home http://vsdb.top and source is here (https://github.com/theChaosCoder/vsdb) . I created a backend in laravel so people can contribute more easily.
There are still some things I want to implement. See todo on the first page.

[tuanden0]

I think there is some mistake at ffms 2000
The link on your database is: https://forum.doom9.org/showthread.php?t=174469 and the new release is test8 (3rd March 2018) but the link download is here: https://github.com/FFMS/ffms2/releases that not updated to new release

[ChaosKing]

thx, I added the github link as well
The release comes from vsrepo https://github.com/vapoursynth/vsrepo/blob/master/local/ffms2.json
test8 is not considered stable, that's why it is not listed.

edit: keeping track of all beta/alpha/custom versions would be too much work. But an "unstable/bleeding edge" version could be added to vsrepo in my optinion...

[tuanden0]

@ChaosKing I love your work, keep it up :thanks:

[ChaosKing]

Oh and this works too http://vsdb.top/plugins/hnwvsfunc
Also with multiple namespaces http://vsdb.top/plugins/dfttest

[ChaosKing]

Added VSRepo GUI page. All data are from vsrepo-github. http://vsdb.top/vsrepogui

[Wolfberry]

When editing in the dashboard, it does not preserve the position and will always go to the first page.
That's not very convenient, also the Plugin column in Dashboard / Plugin Functions are all blank

[ChaosKing]

All blank? Can you make a screeshot?

Edit: fixed.

Yeah I need to improve some ui stuff.

[ChaosKing]

Now the table jumps back to the page of the edited plugin.
But I will switch to something else, either server-side processing or a different "table system". I saw some nice laravel packages.

[ChaosKing]

Now with json backup git-repo https://github.com/theChaosCoder/vsdb-json

[ChaosKing]

You want some some statistics? Here: http://vsdb.top/stats
In the next update Add and Edit stuff will be supported by vuejs.

Let me know if you want feature xy, I will try to implement it.

[lansing]

Missing Retinex:
https://github.com/HomeOfVapourSynthEvolution/VapourSynth-Retinex

[ChaosKing]

Nope, it's here: http://vsdb.top/plugins/retinex

[lansing]

Nope, it's here: http://vsdb.top/plugins/retinex

Oh I didn't realize there is a second page, I was searching on the main page and couldn't find it.

[ChaosKing]

It's also on the main page, just type retinex in the searchbox.

[sl1pkn07]

http://vsdb.top/plugins/hnwvsfunc is removed in upstream

https://github.com/Helenerineium?tab=repositories

[ChaosKing]

Yeah I know. I just noticed, instead of adding every function from G41fun (again) I can just simply rename hnwvsfunc xD

[shph]

Is it possible to add "Bit Depth" column? For some workflows it is critical to know that at least 10 bit is supported from start to end and select plug-ins accordingly.

[ChaosKing]

For bit depth info click on the namespace link e.g. http://vsdb.top/plugins/nnedi3cl

Bit Depth Color Space Category
NNEDI3CL 8-16 int / 32 float GRAY, YUV, RGB, YCOCG unknown

EDIT
In case you're wondering why is it not on the main page? Look at this http://vsdb.top/plugins/havsfunc
Plugins and scripts can have more than one function with different capabilities.

[shph]

Yep, multiple function with different capabilities and different bit depth. never thought from this point of view. Now it make sense. Too bad that a lot of bit depth is unknown from specification...

[ChaosKing]

The data needs to be updated manually, so helpers are welcome. Read the docs and update it.

[foxyshadis]

The main improvement I might ask for at this point is a linked list of all categories at the top, like "Anti-aliasing · Borders and Cropping · Collection · ...." etc, since pagination doesn't really tell you anything.

[ChaosKing]

The select box should be good enough? (see website)

[shph]

Ok, rethinking my idea and i guess it may be nice just to see somehow warning that plug-in is 8bit only
I guess i can do real life bit depth tests similar to codec bit depth tests i done before here https://forum.selur.net/showthread.php?tid=1288

For Example here are [ProRes 12 bit 444] vs [Hybrid ProRes 10 bit 422 with ColorMatrix filter] vs [Hybrid ProRes 10 bit 422 with DeRainbow Bifrost filter]
As you can see DeRainbow Bifrost filter is 8 bit only.
https://i.imgur.com/0JR20rq.gif

[shph]

Ok, here it is: 8 bit only filters list
(tested with Hybrid UI on macOS 10.14.6):
DeGrain -> MLDegrain
DeGrain -> TemporalDegrain
Artefacts -> DeCrawl -> DotKill
Artefacts -> DeCrawl -> DeDot
Artefacts -> DeRainbow -> BiFrost
Artefacts -> DeRainbow -> SSIQ
Artefacts -> DeCross
Line -> AntiAliasing -> SangNomMod (removed from Hybrid due conflict with SangNom)
Line -> Resizer -> Anime4KCPP

Overall situation is not so bad...

[ChaosKing]

Ok, rethinking my idea and i guess it may be nice just to see somehow warning that plug-in is 8bit only
I guess i can do real life bit depth tests similar to codec bit depth tests i done before here https://forum.selur.net/showthread.php?tid=1288

For Example here are [ProRes 12 bit 444] vs [Hybrid ProRes 10 bit 422 with ColorMatrix filter] vs [Hybrid ProRes 10 bit 422 with DeRainbow Bifrost filter]
As you can see DeRainbow Bifrost filter is 8 bit only.
https://i.imgur.com/0JR20rq.gif

Hmm yes I know it's only 8bit because it says so in the documentation and an error is shown if you feed it a 10bit clip.

I don't see a reason to add a warning for 8bit filters since everyone has different requirements. Some users filter only in 32 float. From their perspective 80% of the plugins should have a warning :D

[shph]

It was a mistake in Hybrid script with Flash3kDB. Problem fixed and Flash3kDB is confirmed 16 depth filter now. See details here https://forum.selur.net/showthread.php?tid=1288&pid=8861#pid8861

[Myrsloik]

Ok, here it is: 8 bit only filters list
(tested with Hybrid UI on macOS 10.14.6):
DeGrain -> MLDegrain
DeGrain -> TemporalDegrain
Artefacts -> DeCrawl -> DotKill
Artefacts -> DeCrawl -> DeDot
Artefacts -> DeRainbow -> BiFrost
Artefacts -> DeRainbow -> SSIQ
Artefacts -> DeCross
Line -> AntiAliasing -> SangNomMod (removed from Hybrid due conflict with SangNom)

Overall situation is not so bad...

Provide some sample material and maybe I'll be motivated to add support to dotkill. Bifrost will probably be completely obsolete in a month or two once I adapt the temporal filter from dotkill to be slightly more general.

[shph]

Can you specify what means "sample material" ? Here are ProRes422HQ 10 bit and ProRes 444 12 bit source gradient examples generated in DaVinci Resolve if it helps https://www.dropbox.com/sh/bak63hnr7mnpgbj/AAAf-rMK0LvHYTAFjPuQaaxFa?dl=0

You can see difference in 8 vs 10 vs 12 bit gradient banding when you compress levels

[Myrsloik]

Can you specify what means "sample material" ? Here are ProRes422HQ 10 bit and ProRes 444 12 bit source gradient examples generated in DaVinci Resolve if it helps https://www.dropbox.com/sh/bak63hnr7mnpgbj/AAAf-rMK0LvHYTAFjPuQaaxFa?dl=0

As in actual rainbows and dot crawl at a higher bitdepth (and not just upsampled).

[shph]

Not sure if i have captures with rainbows and dot crawl. Probably it somehow possible to simulate them: Take source 10 bit capture from Hi8 tape and transcode it incorrectly or use damaged s-video/rca cable, or somehow else (not sure exact how). I'm rather new to these specific restoration filters and don't exact understand how to reproduce these artifacts. But i guess formally it is possible. I have Blackmagic Intensity Pro capture card, Kramer FC-400 Time Base Corrector with Frame Synchronizer (it can generate test patterns), JVC S-VHS player and Sony Hi-8 camera. All devices can do RCA/S-Video in/out. PAL only.

[ChaosKing]

I finally moved the website to my new server. Loading times should be very fast now.
I will also start updating the site in 2 weeks. User friendly backend (current one is horrible) and a faster table with better search and server side rendering (supported by Livewire). I noticed that rendering almost 700 table entries (with sorting and pagination in js) takes to much time.

I also want to show the readme.md from github repos, so you have the "docs" directly on the same page.

If you have some suggestions or feature requests, now would be the best time to tell me :D

Some ideas I have:
- Small tut for beginners.
- A plugin upload service ( e.g for vapoursynth MacOS binaries or avisynth plugins. For those who does not want to use github :devil:) It will have an api so you can check for new stuff with apps like vsrepo/avsrepo etc.

p.s. the site uses ssl by letsencrypt now.

[lansing]

Requesting a search option to search for the dependents (don't know if this is the right word) of a plugin? Like if I'm to modify a plugin, I want to know how many plugins are affected by it.

[ChaosKing]

Like this?

A has D1, D2, D3 as depencies
B has D3

You want to mod D3 and want to see which plugins (scripts) are used by D3. In this case it would be A & B as search result
Correct?

[lansing]

Like this?

A has D1, D2, D3 as depencies
B has D3

You want to mod D3 and want to see which plugins (scripts) are used by D3. In this case it would be A & B as search result
Correct?

Yes..

[ChaosKing]

It should be relatively easy to implement. But adding it will take some time (maybe 2 weeks) as I'm busy with some work right now.

[mastrboy]

Can we get an update to the "vsutil" package? The current version has code references to "vs.YCOCG" which broke with some Vapoursynth version, it was fixed on Jul 29, 2021: https://github.com/Irrational-Encoding-Wizardry/vsutil/commits/master

[ChaosKing]

They don't provide a "wheel" file anymore. So fetching new version is currently on hold.

See https://github.com/vapoursynth/vsrepo/issues/168

[mastrboy]

They don't provide a "wheel" file anymore. So fetching new version is currently on hold.

See https://github.com/vapoursynth/vsrepo/issues/168

Thanks for the update, didn't know there already was a known issue on this.
I'll keep on eye on that github issue.

[Julek]

https://vsdb.top/dashboard/plugins/213/edit
Can't edit this one
500 | Server Error

Add GH link please: https://github.com/OpusGang/awsmfunc

[Selur]

Bifrost will probably be completely obsolete in a month or two once I adapt the temporal filter from dotkill to be slightly more general.
@Myrsloik: any news on that?

[Myrsloik]

@Myrsloik: any news on that?

Uh... it happened? Was released. The world yawned apart from a few anime encoders. Basically it now uses the temporal redundancy in 3:2 pulldown which can recover more details than any other script ideas I've seen (assuming ntsc 3:2 pulldown dvd material).

Go download it and play around. The pulldown pattern offset has to be specified manually. I'll try to post some sample clips to increase excitement in a day or two.

[Selur]

Ah okay, thanks. :) (totally mised that the post was 2 years old and thought a new dotkill was in the planning :))

[poisondeathray]

CK - when you get a chance can you add Real-CUGAN to the database ? The vapoursynth script demo works

https://github.com/bilibili/ailab/tree/main/Real-CUGAN
https://github.com/bilibili/ailab/tree/main/Real-CUGAN/VapourSynth

[ChaosKing]

I will add them very soon :)

[Julek]

I just added this one (https://github.com/HolyWu/vs-waifu2x-ncnn-vulkan), that is w2x with updated ncnn-vulkan by HolyWu, the old version (https://github.com/Nlzy/vapoursynth-waifu2x-ncnn-vulkan) doesn't seem to get updated anymore, maybe it is better to remove from vsdb?

@poisondeathray: if you have an nvidia card, this cugan will be faster: https://github.com/AmusementClub/vs-mlrt/wiki/CUGAN

[Boulder]

The main landing page and the VSRepo GUI page have different content it seems. Would it make sense to just show the current VSRepo data by default?

[ChaosKing]

The main landing page and the VSRepo GUI page have different content it seems. Would it make sense to just show the current VSRepo data by default?

That is by design. Not every plugin has binary releases hence it's not in vsrepo. The vsrepo listing was only a last minute addition.

But I'll remove the vsrepo view and add it as a filter option or something in the future. So you'll have one view for everything.

[Boulder]

That is by design. Not every plugin has binary releases hence it's not in vsrepo. The vsrepo listing was only a last minute addition.

But I'll remove the vsrepo view and add it as a filter option or something in the future. So you'll have one view for everything.

Ah, ok. It was just confusing that lsmash has a very old release on the main page and then the current one in VSRepo side.

[Selur]

btw. from time to time, checking whether the github&co links still work might be a good idea, so that stuff that doesn't exist any more gets removed or the links updated.

[Selur]

Seeing that more and more VapourSynth plugins are available through pip, it would be nice if https://www.vsdb.top/ would also indicate if a filter is available through pip.

Cu Selur

[Myrsloik]

Seeing that more and more VapourSynth plugins are available through pip, it would be nice if https://www.vsdb.top/ would also indicate if a filter is available through pip.

Cu Selur

The plan is to flip the switch in a few weeks or so when more plugins and scripts are available.

[ChaosKing]

I'm cooking something https://imgur.com/a/ONPG32C

[Selur]

nice!