This forum uses cookies
This forum makes use of cookies to store your login information if you are registered, and your last visit if you are not. Cookies are small text documents stored on your computer; the cookies set by this forum can only be used on this website and pose no security risk. Cookies on this forum also track the specific topics you have read and when you last read them. Please confirm whether you accept or reject these cookies being set.

A cookie will be stored in your browser regardless of choice to prevent you being asked this question again. You will be able to change your cookie settings at any time using the link in the footer.

[GUIDE] Ubuntu repository - maintained by djcj
Quote:Why not use "$HOME/.hybrid/vapoursynth" for the VS installation?
having executables in hidden directories seems wrong Smile
I think it would be better to keep the config/settings separated from the tools.

Quote:I have "$HOME/bin" added to PATH and I try to avoid installing directories in there.
When installing as root I would add Vapoursynth under /opt/vapoursynth, as a user $HOME/opt/vapoursynth would probably be the best alternative.

regarding vsViewer:
Adding a vsViewer_withenv.sh and calling that in Hybrid works fine and it's easy, I think hardcoding a PYTHONPATH would be a mistake.

---
Maybe installing Vapoursynth system wide (under /opt/vapoursynth) is the cleanest way to go about the whole thing.

Cu Selur
Reply
I've uploaded the scripts into my Github repository where I sometimes dump scripts: https://github.com/darealshinji/scripts/...ter/Hybrid

build-tools.sh now creates vsViewer_withenv.sh and deploy.sh adds it to the deploy directory.

If build-vapoursynth.sh is run as root or with sudo it will install files into /opt/vapoursynth, otherwise $HOME/opt/vapoursynth is used.
Now I only need to write a build script for the needed VS plugins. Can you give me a list of the source repositories?
Reply
Quote:Can you give me a list of the source repositories?
I'll get on it.
Reply
Here you go:
A list of all the Vapoursynth filters currently used/supported by Hybrid: (which should work on Linux) As a side note[/u]: http://vsdb.top/ has a nice list of filters.

Filters Hybrid supports but are not available for Linux afaik:
Interframe, DGHDRToSDR, DGDecNV, ImageMagick, FFMS2000, vsavsreader

Additional tools:
D2VWitch:              https://github.com/dubhater/D2VWitch/releases
ffmsindex:              is part of ffms2

Cu Selur
Reply
Thanks. Will write a build script later.


Quote:Filters Hybrid supports but are not available for Linux afaik:

Interframe, DGHDRToSDR, DGDecNV, ImageMagick, FFMS2000, vsavsreader


Looking up the vsdb shows me:
 - InterFrame is part of the havsfunc script, so it should work on Linux?
 - ImageMagick is the imwri plugin, which is build together with Vapoursynth and available on Linux.
 - FFMS2000 leads to the ffms2 Github page. ffms2 can be build on Linux.

vsavsreader is Windows-only because of avisynth and the DG* stuff is proprietary.
Reply
Quote:InterFrame is part of the havsfunc script, so it should work on Linux?
havsfunc is only a wrapper, but seems like the libraries are available:
Quote:SmoothVideo Project (SVP) v.4
=============================

svpflow1 - motion vectors search based on MVTools2 and x264 under GPL
svpflow2 - frame rendering

Binary files naming convention:
- *.dll - Avisynth 32-bit (Windows only)
- *_64.dll - Avisynth 64-bit (Windows only)
- *_vs.* - Vapoursynth 32-bit
- *_vs64.* - Vapoursynth 64-bit
- *.dll - Windows
- *.so - Linux
- *.dylib - Mac

As of now, Linux and Mac builds depend on libQt5Core and libQt5Network ver.5.4 or later.
This may change in the future.

svpflow1 sources: http://www.svp-team.com/files/gpl/svpflow1-src.zip

svpflow_cpu.dll - CPU rendering from svpflow2.dll, removed since 1.1.12
svpflow_gpu.dll - GPU rendering from svpflow2.dll, removed since 1.1.12
I also found:
http://www.svp-team.com/files/gpl/svpflow-4.2.0.142.zip and
http://www.svp-team.com/files/svp4-latest.php?linux
over at https://www.svp-team.com/wiki/Download

Quote:ImageMagick is the imwri plugin, which is build together with Vapoursynth and available on Linux.
Nice.

Quote:FFMS2000 leads to the ffms2 Github page. ffms2 can be build on Linux.
FMS2 and FMS2k are two different filters afaik,...
Reply
(14.07.2019, 19:08)Selur Wrote: FMS2 and FMS2k are two different filters afaik,...

Now I see, it's on a different branch: https://github.com/FFMS/ffms2/tree/ffms2000

However it seems to build and work on Linux: https://aur.archlinux.org/packages/ffms2000-git/

I've noted all the links and see what I can do.
Reply
Nice! And thanks again for all your effort!

Cu Selur
Reply
Build files for Vapoursynth and the plugins:
https://github.com/darealshinji/scripts/...ter/Hybrid

Instead of 1 build file for all plugins I made 1 for each, but they're all called from the "plugin.sh" build script.
That way you can continue building even if 1 or more plugins fail to build. And I figured in this case it was better than writing Makefiles.
BTW I think 1 or 2 of the links you provided were dead (repo deleted from Github I guess).
Reply
Quote:I think 1 or 2 of the links you provided were dead (repo deleted from Github I guess).
Thought I checked them all but, may be I overlooked one. Smile (might have been Depan which is now part of mvtools iirc.)

Quote:Build files for Vapoursynth and the plugins:
https://github.com/darealshinji/scripts/...ter/Hybrid
Nice I'll give it a try tomorrow and report back.

Cu Selur

Ps.: did a quick test:
https://pastebin.com/31Vi3BMJ
most of the builds failed, but:
Quote:You are using pip version 8.1.1, however version 19.1.1 is available.
You should consider upgrading via the 'pip install --upgrade pip' command.
showed a few times,..
adding
pip3 install --upgrade pip
under
export PYTHONUSERBASE="$vsprefix"
didn't remove the
Quote:You are using pip version 8.1.1, however version 19.1.1 is available.
You should consider upgrading via the 'pip install --upgrade pip' command.
but most of the builds still fail.
-> DOH, think I got it I have to call the other scripts (especially vapoursynth.sh) beforehand. Wink (will test more tomorrow)
-> yup, first calling vapoursynth.sh seems to help Smile
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)