Selur's Little Message Board

Theres an issue on newer versions of Fedora that appear to prevent the script from working and I've had zero luck fixing it on my own. I also understand this just might not be the place to report this issue, but I can't even report issues with the script because the issues page is disabled for the script on github. The error is below, though I understand I might not be supposed to receive support for this here. To reproduce just use Hybrid on a fully updated version of Fedora, with all vapoursynth plugins installed with the vapoursynth installer linked on the download page for fedora. Then go to the vapoursynth page once you've imported a video, and press the preview button. Then the vapoursynth editor will open, with this error at the bottom. 

No clue about Fedora, never used it.
Seems like a problem with your libvslsmashsource.so.
As a workaround try using BestSource.

Cu Selur

its been a while since I've used hybrid and I don't see an option for that. How would I? (I'm so sorry)

Edit: I'm so sorry, right after posting this reply I found best source. Trying now!

---

no luck with best source either, im getting the vibe that the fedora install script is faulty rather then hybrid. 
I found the so that the fedora script compiled was named bestsource.so instead of libbestsource.so, so I corrected it (maybe this wasn't a fault?) and got the below error afterwards.

Yeah, seems like the dependencies of the plugins are missing,..

I'm going to switch to running hybrid through an ubuntu container in distrobox in the hopes of having a distro agnostic way of running hybrid lol.

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. 

Quote:In file included from src/core/settings.cpp:8:
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....

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.) 

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:I'm sure many users would love a flatpak version due to how accessible it would make vapoursynth support on linux.

I would like that too, but I do not know how to create one and I'm even struggling to compile ffmpeg&co on Linux.
I just updated the https://github.com/Selur/hybrid-vapoursynth-addon a few days ago, then it worked without a problem on Ubuntu 24.04.

=> If someone can combine https://github.com/Selur/HybridDeploy and https://github.com/Selur/hybrid-vapoursynth-addon to create in a way to create a Flatpak I would be happy to release Flatpak (AppImage or whatever) packages.
Atm. it's a pain trying to compile stuff on Linux and I do not have the time or motivation to work on it. (Just spend the last 4 days every day after work trying to get ffmpeg to compile with all the dependencies and it still doesn't work.)
Also, I would like to get a proper Mac version running again to, but I do neither have the knowledge nor the time and motivation for it. (there compiling stuff is even more a pain than on Linux )
Neither MacOS nor Linux has a package manager or something similar for all the stuff.
In case I can't get the Linux build suite working again, I will probably have to drop Linux support anyway.

Cu Selur

While flatpaks and vapoursynth isn't really something I know how to even begin get working at the moment. I can likely make a version of hybrid deploy that at least works on fedora, if thats of any help I have a port of its build script that is about 25% of the way there (?). its probably actually further along but because im still smack dab in the middle of doing this I can't really make any guarentees about progress but this script itself isn't very distro specific and what issues I've ran into have been very solvable within the scope of this single script.

any help is welcome.

im actually way farther along then I expected to be at this point, though what I'm doing is probably not immeditely production ready, it is at least working fine on fedora and should (I don't have a reliable way of testing) work still on ubuntu.