Selur's Little Message Board

Here's the whole terminal log,

Seems like the plugin path couldn't be detected, since I accidentally removed the search for it. :/
Assuming that '/home/elaajjan/opt/vapoursynth/plugins' exists, adjust your misc.ini file to
Add:

Cu Selur

(11.01.2021, 18:13)Selur Wrote: [ -> ]Seems like the plugin path couldn't be detected, since I accidentally removed the search for it. :/
Assuming that '/home/elaajjan/opt/vapoursynth/plugins' exists, adjust your misc.ini file to
Add:

Code:

[General]
vsPluginsPath=/home/elaajjan/opt/vapoursynth/plugins

Cu Selur

It worked, thanks!

I cannot build the Vapoursynth plugins. I do follow the instructions in this thread and in the hybrid-vapoursynth-addon GitHub page. Building the Vapoursynth by the build-vapoursynth.sh script seems to finish well. I do not change anything in the config.txt file, so Vapoursynth gets builded into the ~/opt/vapoursynth directory. Nothing is being made in /usr/local. Vspipe in the ~/opt/vapoursynth directory works, the version parameter returns the version R53.

The paths in the ~/.profile and ~/.bashrc files are modified in the following way:

The build-plugins.sh script runs and finished well, without any problems. It reports the building of all the plugins to be done. But it is not in fact. There is no plugins subdirectory in ~/opt/vapoursynth, only the vsplugins subdirectory. And this one is empty after the build-plugins.sh script finishes.

There are no build logs in the hybrid-vapoursynth-addon-master build directory when bulding the plugins is done. Even no build subdirectory. But this subdirectory exists when the building process is in progress. So I catched one log during building just as an example. But it doesn't contain any errors nor warnings:

So making it short, building the Vapoursynth runs and makes the output (working vspipe at least). Building Vapoursynth plugins runs, reports to be done well, but doesn't make any output (no built plugins).

The system is Ubuntu 20.04. Python3.8 is installed. What may be wrong?

libraries should end up under:

output of build-plugins should be something like:
(ideally without the 'failed',..)

content of '~/opt/vapoursynth/lib/vapoursynth' should be something like:
Aside from the 'failed' builds, the script seems to work fine here.
-> I'll give it a spin in a new vm

Cu Selur

Allright Selur,

my plugin result and the '~/opt/vapoursynth/lib/vapoursynth' looks the same as yours. So maybe just some misuderstanding here.

So, you are telling me that the built plugins are now in '~/opt/vapoursynth/lib/vapoursynth', not in '~/opt/vapoursynth/plugins' as was written earlier in this thread, nor in '~/opt/vapoursynth/vsplugins' where they were made the last time a I did the plugins build many months ago? If so, then everything should be OK.

Yes, plugins should be in '~/opt/vapoursynth/lib/vapoursynth'.

Cu Selur

I tried the whole thing in a clean VM:

What I did:

• install git
  
  Code:

  sudo apt-get install git
• checkout the addon
  
  Code:

  git clone https://github.com/Selur/hybrid-vapoursynth-addon.git
• build Vapoursynth
  
  Code:

  cd hybrid-vapoursynth-addon
./build-vapoursynth.sh
• adjusted the environment
  
  Code:

  nano ~/.profile
  Code:

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

  nano ~/.bashrc
  Code:

  export LD_LIBRARY_PATH=/usr/local/lib
export PYTHONPATH=~/opt/vapoursynth/lib/python3.8/site-packages
export PATH="~/opt/vapoursynth/bin:$PATH"
• rebooted
  
• switched to the repo again
  
  Code:

  cd hybrid-vapoursynth-addon
• called build-plugins.sh
  
  Code:

  ./build-plugins.sh
  
  A lot of plugins failed:
  
  Code:

  Build plugins:
addgrain (1/62) ... failed
awarpsharp2 (2/62) ... failed
bifrost (3/62) ... done
bilateral (4/62) ... done
bm3d (5/62) ... failed
cas (6/62) ... failed
ctmf (7/62) ... failed
d2vsource (8/62) ... done
dctfilter (9/62) ... failed
....
  which can probably be explained through the warnings:
  
  Code:

  ERROR: launchpadlib 1.10.13 requires testresources, which is not installed.
  WARNING: The script wheel is installed in '/home/selur/.local/bin' which is not on PATH.
  Consider adding this directory to PATH or, if you prefer to suppress this warning, use --no-warn-script-location.
  NOTE: The current PATH contains path(s) starting with `~`, which may not be expanded by all applications.
  WARNING: The script meson is installed in '/home/selur/.local/bin' which is not on PATH.
  Consider adding this directory to PATH or, if you prefer to suppress this warning, use --no-warn-script-location.
  NOTE: The current PATH contains path(s) starting with `~`, which may not be expanded by all applications.
  WARNING: The script ninja is installed in '/home/selur/.local/bin' which is not on PATH.
  Consider adding this directory to PATH or, if you prefer to suppress this warning, use --no-warn-script-location.
  NOTE: The current PATH contains path(s) starting with `~`, which may not be expanded by all applications.
  -> I then changed the environment files:
  
  Code:

  nano ~/.profile-
  Code:

  export PATH="/home/selur/opt/vapoursynth/bin:$PATH"
export LD_LIBRARY_PATH=/usr/local/lib
export PYTHONPATH=/home/selur/opt/vapoursynth/lib/python3.8/site-packages
export PATH="/home/selur/.local/bin:$PATH"
  Code:

  nano ~/.bashrc
  Code:

  export LD_LIBRARY_PATH=/usr/local/lib
export PYTHONPATH=/home/selur/opt/vapoursynth/lib/python3.8/site-packages
export PATH="/home/selur/opt/vapoursynth/bin:$PATH"
export PATH="/home/selur/.local/bin:$PATH"
  closed and reopened a terminal and now the builds worked fine.
  
  Code:

  Build plugins:
addgrain (1/62) ... done
awarpsharp2 (2/62) ... done
bifrost (3/62) ... done
bilateral (4/62) ... done
bm3d (5/62) ... done
cas (6/62) ... done
ctmf (7/62) ... done
d2vsource (8/62) ... done
dctfilter (9/62) ... done
deblockpp7 (10/62) ... done
deblock (11/62) ... done
decross (12/62) ... done
dedot (13/62) ... done
degrainmedian (14/62) ... done
depan (15/62) ... done
descale (16/62) ... done
dfttest (17/62) ... done
dotkill (18/62) ... done
eedi2 (19/62) ... done
eedi3m (20/62) ... done
f3kdb (21/62) ... done
ffms2 (22/62) ... done
fft3dfilter (23/62) ... done
fixtelecinedfades (24/62) ... done
fluxsmooth (25/62) ... done
fmtconv (26/62) ... done
hqdn3d (27/62) ... done
it (28/62) ... done
knlmeanscl (29/62) ... done
lghost (30/62) ... done
minideen (31/62) ... done
msmoosh (32/62) ... done
mvtoolssf (33/62) ... done
mvtools (34/62) ... done
neofft3d (35/62) ... done
nnedi3cl (36/62) ... done
nnedi3 (37/62) ... done
readmpls (38/62) ... done
retinex (39/62) ... done
sangnommod (40/62) ... done
sangnom (41/62) ... failed
scenechange (42/62) ... done
ssiq (43/62) ... done
svpflow (44/62) ... done
tcanny (45/62) ... done
tdeintmod (46/62) ... done
templinearapproximate (47/62) ... done
temporalmedian (48/62) ... done
temporalsoften2 (49/62) ... done
temporalsoften (50/62) ... done
timecube (51/62) ... done
tonemap (52/62) ... done
ttempsmooth (53/62) ... done
vaguedenoiser (54/62) ... done
vcmod (55/62) ... failed
vfrtocfr (56/62) ... done
vsimagereader (57/62) ... done
vslsmashsource (58/62) ... failed
vsrawsource (59/62) ... done
vsznedi3 (60/62) ... done
waifu2x-w2xc (61/62) ... done
yadifmod (62/62) ... done

Finished after 6 min 47 sec

Funny thing is, those changes were not needed before,.. seems like Ubuntu again changes something.
(/home/selur/opt/vapoursynth/lib/vapoursynth/ also did include the libraries.)

Cu Selur

Thank you Selur a lot for your investigation of the Vapoursynth plugins building process. So the only problem was that I did not find the built plugins in neither place where I expected them. Maybe I could find where they are now, but when I was missing the build logs too, I was convinced that something was wrong.

Unfortunately still not good. Even plugins are built, misc.ini edited to point Hybrid to their new place, added ~/opt/vapoursynth/bin and ~/.local/bin/ paths into $PATH, Hybrid still cannot detect Vapoursynth:

vspipe --version returns:

Could you please help again?

seems wrong.
Additionally, Hybrid automatically checks for some stuff in case no entry in the misc.ini is used:

• the scripts under:
  • <path to Hybrid>/64bit/vsscripts
    
  • <user home>/.hybrid/vsscripts
    
  • <path to Hybrid>/.vsscripts
    
  • /usr/share/vsscripts
    
  • <user home>/opt/vapoursynth/vsscripts
    
• Vapoursynth plugins under:
  • <path to Hybrid>/64bit/vsfilters
    
  • <path to Hybrid>/vsfilters
    
  • <path to Hybrid>/vapoursynth/plugins
    

(will add <path to Hybrid>/vapoursynth/lib/vapoursynth for the next release)
so you probably only need to specify the plugins path,..

Cu Selur