![]() |
[GUIDE] Ubuntu repository - maintained by djcj - Printable Version +- Selur's Little Message Board (https://forum.selur.net) +-- Forum: Hybrid - Support (https://forum.selur.net/forum-1.html) +--- Forum: Problems & Questions (https://forum.selur.net/forum-3.html) +--- Thread: [GUIDE] Ubuntu repository - maintained by djcj (/thread-18.html) |
RE: Ubuntu repository - maintained by djcj - Selur - 14.07.2019 Quote:Why not use "$HOME/.hybrid/vapoursynth" for the VS installation?having executables in hidden directories seems wrong ![]() 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 RE: Ubuntu repository - maintained by djcj - djcj - 14.07.2019 I've uploaded the scripts into my Github repository where I sometimes dump scripts: https://github.com/darealshinji/scripts/tree/master/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? RE: Ubuntu repository - maintained by djcj - Selur - 14.07.2019 Quote:Can you give me a list of the source repositories?I'll get on it. RE: Ubuntu repository - maintained by djcj - Selur - 14.07.2019 Here you go: A list of all the Vapoursynth filters currently used/supported by Hybrid: (which should work on Linux)
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 RE: Ubuntu repository - maintained by djcj - djcj - 14.07.2019 Thanks. Will write a build script later. Quote:Filters Hybrid supports but are not available for Linux afaik: 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. RE: Ubuntu repository - maintained by djcj - Selur - 14.07.2019 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.4I 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,... RE: Ubuntu repository - maintained by djcj - djcj - 14.07.2019 (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. RE: Ubuntu repository - maintained by djcj - Selur - 14.07.2019 Nice! And thanks again for all your effort! Cu Selur RE: Ubuntu repository - maintained by djcj - djcj - 17.07.2019 Build files for Vapoursynth and the plugins: https://github.com/darealshinji/scripts/tree/master/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). RE: Ubuntu repository - maintained by djcj - Selur - 17.07.2019 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. ![]() Quote:Build files for Vapoursynth and the plugins: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.showed a few times,.. adding pip3 install --upgrade pip export PYTHONUSERBASE="$vsprefix" Quote:You are using pip version 8.1.1, however version 19.1.1 is available.but most of the builds still fail. -> DOH, think I got it I have to call the other scripts (especially vapoursynth.sh) beforehand. ![]() -> yup, first calling vapoursynth.sh seems to help ![]() |