02.10.2025, 17:16
no luck there either for reasons I am even more baffled about, is there a place I can just download it all precompiled like the windows version? this linux port feels like a mess vapoursynth wise (understandibly since linux is a mess), but it would be of great use to have something that works out of the box with vaporsynth support like a flatpak or appimage. if you want to test your ubuntu script on distrobox what I did was created a box with its own home directory, using an ubuntu image with the same ubuntu version listed in the readme. Then I installed cython before running the build-vapoursynth script. You should get the error below regardless of your host distro, but if you get something else then I am even more baffled.
I do also acknowledge I'm not very knowledgable in ubuntu, debian distros just aren't my thing. But I give it the best try I can to make it compile and it doesn't because of an issue I can't even begin to understand (I'm not into this level of programming either, its just sadly beyond me). When if it were a flatpak I'd be able to open discover, search Hybrid, and install it. Sure it would absolutely be reasonable for this version not to be fully up to date at all times since flatpaks are basically their own format for applications to be packaged in (and in some ways their own small linux file systems), and thus become their own major part of the distribution process for applications. But its so distro agnostic that even on completely immutable distros like SteamOS something like ancient flash players can be packaged as a flatpak and still work. Probably not the best example I could give though. I don't say this to discount the work being done on Hybrid either, or the work done to make it and vapoursynth support work on linux (developers like you are my hero I swear!). Just that surely the work to establish making flatpak versions would surely in the long run be worth it due to how distro agnostic *and* future proof it would make Hybrid with Vapoursynth filters.
This also isn't me waving my white flag with getting vapoursynth support working on fedora myself, I still have the drive from my last arch install that I abanonded due to the laptop it was on failing. So I'm going to try an arch distrobox and the scripts I wrote for making it work on arch there. As above, I'm sure many users would love a flatpak version due to how accessible it would make vapoursynth support on linux.
Quote:In file included from src/core/settings.cpp:8:Regardless though with this being my third time setting up this program on Linux, I'm left very curfluffled Even on arch where I was capable of getting it working it was still very hacky, and somehow on whats supposed to be a less hacky distro its even hackier. Without a distro agnostic way of installing this I'm not sure how an average user is supposed to unless they are running on ubuntu (and does that even work consistently? hypothetically within the distrobox setup I poorly described above, it should be installing just the same as a fresh ubuntu install.)
src/core/vscore.h: In member function ‘const VSFilterDependency* VSNode::getDependency(int) const’:
src/core/vscore.h:885:32: warning: comparison of integer expressions of different signedness: ‘int’ and ‘std::vector<VSFilterDependency>:ize_type’ {aka ‘long unsigned int’} [-Wsig
n-compare]
885 | if (index < 0 || index >= dependencies.size())
| ~~~~~~^~~~~~~~~~~~~~~~~~~~~~
CXX src/core/libvapoursynth_la-simplefilters.lo
CXX src/core/libvapoursynth_la-textfilter.lo
CXX src/core/libvapoursynth_la-vsapi.lo
In file included from src/core/vsapi.cpp:21:
src/core/vscore.h: In member function ‘const VSFilterDependency* VSNode::getDependency(int) const’:
src/core/vscore.h:885:32: warning: comparison of integer expressions of different signedness: ‘int’ and ‘std::vector<VSFilterDependency>:ize_type’ {aka ‘long unsigned int’} [-Wsig
n-compare]
885 | if (index < 0 || index >= dependencies.size())
| ~~~~~~^~~~~~~~~~~~~~~~~~~~~~
CXX src/core/libvapoursynth_la-vscore.lo
In file included from src/core/vscore.cpp:21:
src/core/vscore.h: In member function ‘const VSFilterDependency* VSNode::getDependency(int) const’:
src/core/vscore.h:885:32: warning: comparison of integer expressions of different signedness: ‘int’ and ‘std::vector<VSFilterDependency>:ize_type’ {aka ‘long unsigned int’} [-Wsig
n-compare]
885 | if (index < 0 || index >= dependencies.size())
| ~~~~~~^~~~~~~~~~~~~~~~~~~~~~
CXX src/core/libvapoursynth_la-vslog.lo
CXX src/core/libvapoursynth_la-vsresize.lo
CXX src/core/libvapoursynth_la-vsthreadpool.lo
In file included from src/core/vsthreadpool.cpp:21:
src/core/vscore.h: In member function ‘const VSFilterDependency* VSNode::getDependency(int) const’:
src/core/vscore.h:885:32: warning: comparison of integer expressions of different signedness: ‘int’ and ‘std::vector<VSFilterDependency>:ize_type’ {aka ‘long unsigned int’} [-Wsig
n-compare]
885 | if (index < 0 || index >= dependencies.size())
| ~~~~~~^~~~~~~~~~~~~~~~~~~~~~
CXX src/core/expr/libvapoursynth_la-jitcompiler_x86.lo
CYTHON src/cython/vapoursynth.c
CXX src/vspipe/vspipe-vspipe.o
CXX src/vspipe/vspipe-printgraph.o
Error compiling Cython file:
------------------------------------------------------------
...
env.core.funcs.removeLogHandler(env.log, env.core.core)
env.log = NULL
cdef void __stdcall _logCb(int msgType, const char *msg, void *userData) noexcept nogil:
^
------------------------------------------------------------
src/cython/vapoursynth.pyx:353:73: Syntax error in C variable declaration
make: *** [Makefile:2057: src/cython/vapoursynth.c] Error 1
make: *** Waiting for unfinished jobs....
I do also acknowledge I'm not very knowledgable in ubuntu, debian distros just aren't my thing. But I give it the best try I can to make it compile and it doesn't because of an issue I can't even begin to understand (I'm not into this level of programming either, its just sadly beyond me). When if it were a flatpak I'd be able to open discover, search Hybrid, and install it. Sure it would absolutely be reasonable for this version not to be fully up to date at all times since flatpaks are basically their own format for applications to be packaged in (and in some ways their own small linux file systems), and thus become their own major part of the distribution process for applications. But its so distro agnostic that even on completely immutable distros like SteamOS something like ancient flash players can be packaged as a flatpak and still work. Probably not the best example I could give though. I don't say this to discount the work being done on Hybrid either, or the work done to make it and vapoursynth support work on linux (developers like you are my hero I swear!). Just that surely the work to establish making flatpak versions would surely in the long run be worth it due to how distro agnostic *and* future proof it would make Hybrid with Vapoursynth filters.
This also isn't me waving my white flag with getting vapoursynth support working on fedora myself, I still have the drive from my last arch install that I abanonded due to the laptop it was on failing. So I'm going to try an arch distrobox and the scripts I wrote for making it work on arch there. As above, I'm sure many users would love a flatpak version due to how accessible it would make vapoursynth support on linux.


ize_type