Selur's Little Message Board

A while back I switched from Windows to Arch, and for a while I simply dealt with the inability to use vapoursynth, but recently I looked around the forums to see if it was possible to make it work, and sure enough it was. Following your advice in  https://forum.selur.net/thread-753.html  I did everything needed to get it working, and it actually does work.

The problem is that Hybrid seems to require loading its plugins separately from how Vapoursynth loads all of the system plugins. If I don't specify a vsPluginsPath in the misc.ini, it refuses to enable vapoursynth. I can understand why you'd want to do that on windows in order to make it portable, as you can just have your own separate VS that ships with Hybrid, but I'm wondering if there isn't a way that I can have Hybrid use my system's plugins, or something?

Right now I can force it to work with the rather crude solution of installing the vs plugin packages, copying the plugins to a separate path I point hybrid to, and then uninstalling the packages, but that obviously leaves me unable to use those plugins with vs independently of hybrid.

Next release of Hybrid will have a 'vsNoLibraries' option for the misc.ini and setting it tovsNoLibraries=true will tell Hybrid not to load libraries.
(see: [INFO] *hidden* Hybrid options,... for where the misc.ini can be located)
(scripts will still be loaded).
I'll compile and upload a linux binary of my current dev version and send you a link via pm. (in ~30min)

Cu Selur

Ps.: send you a link

Thank you very much!

So I swapped the binaries and tried it out with vsNoLibraries=true and without defining vsPluginsPath, and vapoursynth no longer shows up as an option in the support drop down menu. It's not greyed out but it just doesn't show up.

If I do give it a path, whether real or a dummy one, it tries to start the program and fails, I'm not sure why and how exactly I would find out.

If I give a path and remove the vsNoLibraries=true option it also fails to start.

If I swap back to the old binary, everything works the same as it used to.

Really sorry for not getting back to you earlier, I got distracted and probably just assumed it would all work.

Edit: The debug log is extremely short when it fails to open, I can't figure out from looking at it what makes it close

---

And here is the debug log when it opens but fails to show vs as an option in the drop down:

You should specify:
If Hybrid does not startUp with this set, what do you see if you call it from a command line?
Does it change anything if you delete your hybrid settings?

Cu Selur

Ps.: Will try to look at it after work if I can motivate myself, but I'm mainly travelling today and tomorrow, so I might be to groggy to look at it when I get home.

When attempting to run it from the command line I get a 53418 segmentation fault when attempting to initialize the vapoursynth tab after 0.046 seconds.

If I reset all defaults (I assume that's enough?) the problem persists.

Yeah resetting the defaults should be enough.

Send you a new link.
(crash was due to a typo I made which caused to skip some Linux specific code, which causes Hybrid trying to delete an object that didn't exist )

Cu Selur

Ps.: I'll remove vsNoLibraries on the next release and instead add vsLoadLibrariesOnNonWindows and make not loading libraries the default behaviour for non-Windows systems.

Fantastic! It works perfectly now. Thanks again!