Selur's Little Message Board

(16.04.2021, 05:33)Selur Wrote: [ -> ]

Code:

Vapoursynth script path: /opt/hybrid/vsscripts

seems wrong.

Why do you think so? This directory contains scripts. I have no idea where else these scripts could be placed if not right there.

I finally managed Vapoursynth to be detected. Changing the path to plugins in misc.ini from
to
did the trick!

But still not a happy end for me, because QTGMC deinterlace filter (nor the other Vapoursynth filters) is not available in the GUI. And having it available is the reason why I'am struggling so hard to make Vapoursynth working. Do you have any idea why QTGMC is not available when Vapoursynth is finally detected? Perhaps because of these three plugins that failed to be built?

UPDATE!
After couple of minutes and one Hybrid crash during the start (did not start because of segfault), the Vapoursynth plugins (including the QTGMC) are finally available in GUI! I did no changes in between these two cases, first Hybrid with no Vapoursynth plugins in GUI and the second Hybrid with Vapoursynth plugins already available. Only restarted Hybrid after it crashed...

Unfortunately I did not grab the crash output from terminal, but system log shows the following:
I guess the crash I mean is the second one. I did not recognized any other crash since then.

I already deleted the ~/.hybrid directory an started Hybrid couple of times since then and the Vapoursynth plugins are always available now. I hope it stays that way...

BTW1: I realized you use this setting:

Is there any reason for that when Vapoursynth is built into ~/opt/vapoursynth? I use the following setting:

and it seems to be working fine. I deleted (renamed in fact) the whole /usr/local in order to avoid any confusion with the old Vapoursynth build that was made there long time ago.

BTW2: Might interest you. When Hybrid is started for the first time on my system (Ubuntu 20.04), i.e. no ~/.hybrid directory exists, it always miss the tools...

...but no more when started for the second and other time, i.e. with ~/.hybrid already existing.


Thank you much for your support and helping me to get Vapoursynth be available in Hybrid! Now I'am going to test it a bit...

Quote:Why do you think so? This directory contains scripts. I have no idea where else these scripts could be placed if not right there.

since '/opt/hybrid/vsscripts' isn't the same as '~/opt/hybrid/vsscripts'

Cu Selur

I see, but I do not have any '~/opt/hybrid' directory in my setup. Only '~/opt/vapoursynth'. Hybrid is installed in '/opt/hybrid/'.

Quote:Hybrid is installed in '/opt/hybrid/'.

Okay,.. normally it's installed under '~/opt/hybrid/', but if you put Hybrid and Vapoursynth both under / not ~/ than that was okay.

Cu Selur

Selur, I'am so sorry to be such troublemaker, but Vapoursynth scripts are not not working to me. I tried some basic deinterlace script and it failed because of missing libneofft3d.so plugin. I checked it and found the libneo-fft3d.so file instead in my Vapoursynth plugins directory. So I symlinked it to libneofft3d.so. This worked. But the script is missing the libvslsmashsource.so too. And this the real problem, because this one is one of those three plugins which building has failed:


Is there any alternate solution how to build the vslsmashsource plugin?

This is its build log:

I tried to use the libvslsmashsource.so from an old build, but this not worked obviously.

This looks like some old ffmpeg/libav is used.
Strange thing is that it works fine here.
Not sure whether it helps, but here's the vapoursynth folder with the plugins that I build inside the 20.04 vm:
https://drive.google.com/file/d/1NTFtTYp...sp=sharing
No clue why the build process would use another ffmpeg/libav source on your system than on mine,..

Cu Selur

just tried building the plugins again, those three failed for me too.
-> will look into it later

Cu Selur

(17.04.2021, 09:57)Selur Wrote: [ -> ]just tried building the plugins again, those three failed for me too.
-> will look into it later

Cu Selur

OK, thank you much!

BTW: The first (if I remember well) of these three failed because of the not working URL it uses for building. The other two because of some building errors.

for sangnom:
changing the content of 'build-plugins/plugin-sangnom.sh' to
fixes the issue. (source https://bitbucket.org/James1201/vapoursynth-sangnom/ doesn't exist any more, or isn't accessible at the moment at least from here)

Problem with plugin-vcmod.sh is that:
a. the source location changed
b. the source a lot of suff is broken from the looks of it
https://aur.archlinux.org/packages/vapou...gin-vcmod/ as a link to a patch and pkbbuild instructions for it,.. argh,...

Okay, I know how to fix vcm, builds here now.
Looking into vslsmashsource next, will update hybrid-vapoursynth-addon.git once I figured out the problem.

Cu Selur