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

It also acts as a web gui for VSRepo (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]

Originally Posted by fAy01

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]

Originally Posted by Myrsloik

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

[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]

Originally Posted by 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.

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 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/funct...ml#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]

Originally Posted by ChaosKing

//Edit
@Myrsloik I think the docs are not up to date or am I reading this wrong?
http://www.vapoursynth.com/doc/funct...ml#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]

Originally Posted by 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.

YUV420 <-- this.

[ChaosKing]

So basically we take this list then http://www.vapoursynth.com/doc/pytho...rmat-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]

Originally Posted by ChaosKing

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]

Originally Posted by fAy01

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.