Selur / hybrid-vapoursynth-addon

Adding Vapoursynth and plugins to Hybrid
11 stars 4 forks source link

Final step, build-plugins.sh, fails with error #16

Closed mikewesten closed 6 days ago

mikewesten commented 6 days ago

$ bash build-plugins.sh error: missing a local installation of FFmpeg libraries and Vapoursynth in /home/my-user-name/opt/vapoursynth' Have you forgotten to runbuild-vapoursynth.sh' before ?

The previous $bash build-vapoursynth.sh command executed and completed and created an opt directory with some contents within my home directory.

I'm using Ubuntu 24.04 and have the latest Hybrid (Linux) installation from official download site

It's as though the 'build-vapoursynth.sh' script failed to put everything where it's supposed to be in order for the 'build-plugins.sh' script to execute properly. I followed instructions very closely so I'm really not certain what went wrong or why this occurs.

Selur commented 6 days ago

Strange. Did you use the scripts from the Ubuntu2404 branch https://github.com/Selur/hybrid-vapoursynth-addon/tree/Ubuntu2404 ? or from the main branch? Will try to look at it tomorrow. (not at home today)

mikewesten commented 6 days ago

No, I used the master branch ubuntu1804 but I will try now with the ubuntu2404 branch.

Okay, I extracted hybrid-vapoursynth-addon-Ubuntu2404.zip and moved into it With this I get an error mid-compile on step one

$bash build-vapoursynth.sh configure: error: expected an absolute directory name for --prefix: "/home/my-user-name/opt/vapoursynth" Error configuring 'zimg'. I'll play around with it a little this weekend see if I can figure out what's wrong. There's no hurry at all.

protvis74 commented 6 days ago

I found the little error. The $prefix strings in the configure options were wrongly escaped. I have corrected that and created a pull request.

To fix this you have to remove the backslashes.

configure_options="--prefix=\"$VSPREFIX\" -> configure_options="--prefix="$VSPREFIX"

mikewesten commented 6 days ago

Yes that fixed it. Successfully installed all but one plugin (Akarin) Hybrid is still showing a greyed out synth chooser under the filters tab though. It doesn't appear to be aware of the existence of the plugins I've just installed. I'm sure there's a simple final step to accomplish this but I'm unaware of what that final step is.

protvis74 commented 5 days ago

@mikewesten: I can't reproduce your issue. I am using Ubuntu 24.04 LTS fully patched. Akarin builds without error. (All plugins were build successfully.)

I added this to ~/.profile and ~/.bashrc:

export LD_LIBRARY_PATH=\~/opt/vapoursynth/lib export PYTHONPATH=\~/opt/vapoursynth/lib/python3.12/site-packages export PATH="\~/opt/vapoursynth/bin:$PATH" export PATH="\~/.local/bin:$PATH"

I am using Hybrid 2024.09.29.1.

hybrid

Addition: I had to add the path to vspipe (Tools tab) manually because hybrid has not detected it automatically.

hybrid-tools

mikewesten commented 5 days ago

@protvis74 I was able to correct the mistake. I had performed my install using .opt (hidden folder syntax) rather than opt. So post-install I went through and changed the directory name from .opt to opt as well as changing the paths entries in .bashrc and .profle in accordance, which Hybrid is now able to find for some reason. I would prefer that "system" folders in my home directory be hidden but this is okay for now.

However I'm not able to perform an encode yet due to (byteSize: 0byte) error. Are you familiar with this error? I'll have to troubleshoot this soon. I played around with temp directory locations as well as making the temp directory the same as output folder. No luck so far.

-> 2024-11-01@17_45_23_5210_04_video crashed: ERROR: /home/my-user-name/Hybrid Output/2024-11-01@17_45_23_5210_05.264 is too small! (byteSize: 0byte) Aborting '2024-11-01@17_45_23_5210_04_video' due to: ERROR: /home/my-user-name/Hybrid Output/2024-11-01@17_45_23_5210_05.264 is too small! (byteSize: 0byte)

Selur commented 5 days ago
mikewesten commented 2 days ago

No worries. I included the line

SystemPluginDir=/home/my-user-name/opt/vapoursynth/vsplugins

in /home/my-user-name/.config/vapoursynth/vapoursynth.conf

now encoding works as expected. I will bring any further support questions to the forum. Thanks for building this great app and extending it's compatibility to Linux.