The following warnings occurred:
Warning [2] Trying to access array offset on null - Line: 198 - File: inc/plugins/google_seo.php PHP 8.3.12-nmm1 (Linux)
File Line Function
/inc/class_error.php 153 errorHandler->error
/inc/plugins/google_seo.php 198 errorHandler->error_callback
/inc/plugins/google_seo/redirect.php 135 google_seo_tid
/inc/class_plugins.php 142 google_seo_redirect_hook
/global.php 100 pluginSystem->run_hooks
/showthread.php 28 require_once
Warning [2] Trying to access array offset on null - Line: 14 - File: inc/plugins/cookielaw.php(272) : eval()'d code PHP 8.3.12-nmm1 (Linux)
File Line Function
/inc/class_error.php 153 errorHandler->error
/inc/plugins/cookielaw.php(272) : eval()'d code 14 errorHandler->error_callback
/inc/plugins/cookielaw.php 272 eval
/inc/class_plugins.php 142 cookielaw_global_intermediate
/global.php 100 pluginSystem->run_hooks
/showthread.php 28 require_once
Warning [2] Trying to access array offset on null - Line: 14 - File: inc/plugins/cookielaw.php(272) : eval()'d code PHP 8.3.12-nmm1 (Linux)
File Line Function
/inc/class_error.php 153 errorHandler->error
/inc/plugins/cookielaw.php(272) : eval()'d code 14 errorHandler->error_callback
/inc/plugins/cookielaw.php 272 eval
/inc/class_plugins.php 142 cookielaw_global_intermediate
/global.php 100 pluginSystem->run_hooks
/showthread.php 28 require_once



This forum uses cookies
This forum makes use of cookies to store your login information if you are registered, and your last visit if you are not. Cookies are small text documents stored on your computer; the cookies set by this forum can only be used on this website and pose no security risk. Cookies on this forum also track the specific topics you have read and when you last read them. Please confirm whether you accept or reject these cookies being set.

A cookie will be stored in your browser regardless of choice to prevent you being asked this question again. You will be able to change your cookie settings at any time using the link in the footer.

[GUIDE] Ubuntu repository - maintained by djcj
running build-plugins.sh, building
  • fms2000 failed
  • mvtoolssf failed, and can be removed since it's Windows only
so it would be cool if you could look into fms2000
----
Dev versions are in the 'experimental'-folder of my GoogleDrive, which is linked on the download page.
Reply
Good news: I managed to get vspipe working (the vspipe location changed from vapoursynth/bin/vspipe to vapoursynth/vspipe which caused a few problems).

Still working on vsViewer to get it working.

Cu Selur
----
Dev versions are in the 'experimental'-folder of my GoogleDrive, which is linked on the download page.
Reply
this is driving me nuts,..
1st I noticed that vsViewer/vsEdit by default tries to load 'vapoursynth-script', but there only is 'libvapoursynth-script' in the vapoursynth/lib-folder.
2nd after changing the code to look for libvapoursynth-script inside ~/opt/vapoursynth/lib and the file (/home/selur/opt/vapoursynth/lib/libvapoursynth-script.so) exists, but loading the library still fails,.. :/
will look more into it after some sleep Smile

Problem seems to be
/home/selur/opt/vapoursynth/lib/libvapoursynth-script.so is a symlink to libvapoursynth-script.so.0, but libvapoursynth-script.so.0 doesn't exist!
-> seems to be a problem with the compilation/deployment of Vapoursynth
----
Dev versions are in the 'experimental'-folder of my GoogleDrive, which is linked on the download page.
Reply
modifying the .deploy-vapoursynth.sh
by changing
mv -f bin/*.so lib/vapoursynth/
into
mv -f bin/*.so* lib/vapoursynth/
does fix the symlink from
/home/selur/opt/vapoursynth/lib/libvapoursynth-script.so to libvapoursynth-script.so.0
but loading
/home/selur/opt/vapoursynth/lib/libvapoursynth-script.so
still fails.
As aside note: needed to adjust the 'install-vs.sh' to use "g++ -std=c++11" instead of gcc and g++ in the compile vspipe on Ubuntu 16.04.
here's what I changed in the deploy-vapoursynth.sh
selur@ubuntu1604:~/workspace/scripts/Hybrid$ git diff deploy-vapoursynth.sh
diff --git a/Hybrid/deploy-vapoursynth.sh b/Hybrid/deploy-vapoursynth.sh
index d3d1618..b785e40 100755
--- a/Hybrid/deploy-vapoursynth.sh
+++ b/Hybrid/deploy-vapoursynth.sh
@@ -8,7 +8,7 @@ test -e "$vsprefix"
mkdir -p AppDir/usr/
cp -r "$vsprefix/include" "$vsprefix/lib" "$vsprefix/src" install-vs.sh AppDir/usr/

-for l in AppDir/usr/lib/vapoursynth/*.so ; do
+for l in AppDir/usr/lib/vapoursynth/*.so* ; do
   cmdLine="$cmdLine -e$l"
done

@@ -24,7 +24,7 @@ rm linuxdeploy-x86_64.AppImage
mv AppDir/usr/ vapoursynth
rmdir AppDir
cd vapoursynth
-mv -f bin/*.so lib/vapoursynth/
+mv -f bin/*.so* lib/vapoursynth/
rm -rf bin lib/python*/ lib/vapoursynth/*.la lib/*.la
mv lib/vapoursynth/ vsplugins
cd ..
and here what I changed in the install-vs.sh:
selur@ubuntu1604:~/workspace/scripts/Hybrid$ git diff install-vs.sh
diff --git a/Hybrid/install-vs.sh b/Hybrid/install-vs.sh
index bc1eec5..3dcdcd1 100755
--- a/Hybrid/install-vs.sh
+++ b/Hybrid/install-vs.sh
@@ -33,20 +33,20 @@ cp -r include lib vsplugins "$vsprefix" &
counter $! "Copy files"

# cython
-gcc -shared -fPIC -O3 -Isrc  $(pkg-config --cflags python3) \
+g++ -std=c++11 -shared -fPIC -O3 -Isrc  $(pkg-config --cflags python3) \
   src/src/cython/vapoursynth.c  -o "$sitepackages/vapoursynth.so" \
   -Llib -lvapoursynth  -s -Wl,-rpath,"$vsprefix/lib" &
counter $! "Build Python module"

# vsscript
-g++ -shared -fPIC -O3 -Isrc/include  $(pkg-config --cflags python3) \
+g++ -std=c++11 -shared -fPIC -O3 -Isrc/include  $(pkg-config --cflags python3) \
   src/src/vsscript/vsscript.cpp  -o "$vsprefix/lib/libvapoursynth-script.so.0" \
   $(pkg-config --libs python3)  -s -Wl,-rpath,"$vsprefix/lib"  -Wl,-soname,libvapoursynth-script.so.0 &
counter $! "Build VSScript library"
ln -sf libvapoursynth-script.so.0 "$vsprefix/lib/libvapoursynth-script.so"

# vspipe
-g++ -O3 -Isrc/include  src/src/vspipe/vspipe.cpp  -o "$vsprefix/vspipe" \
+g++ -std=c++11 -O3 -Isrc/include  src/src/vspipe/vspipe.cpp  -o "$vsprefix/vspipe" \
   -L"$vsprefix/lib" -lvapoursynth-script  -s -Wl,-rpath,"$vsprefix/lib" &
counter $! "Build VSPipe"
I also modified the build-tools.sh
selur@ubuntu1604:~/workspace/scripts/Hybrid$ git diff build-tools.sh
diff --git a/Hybrid/build-tools.sh b/Hybrid/build-tools.sh
index 728dd69..72785bf 100755
--- a/Hybrid/build-tools.sh
+++ b/Hybrid/build-tools.sh
@@ -243,7 +243,8 @@ fi
### vsViewer
if echo "$args" | grep -q -i -w -E 'all|vsviewer'
then
-  git clone https://github.com/Selur/vsViewer build
+  git clone --single-branch --branch debug2 https://github.com/Selur/vsViewer build
+#  git clone https://github.com/Selur/vsViewer build
   cd build
   git clone https://github.com/vapoursynth/vapoursynth vapoursynth-git
   cd vapoursynth-git
@@ -262,21 +263,14 @@ scriptDir="\$(dirname "\$(readlink -f "\$0")")"

env="\$HOME/opt/vapoursynth/env.sh"
if [ -f "\$env" ]; then
-  echo "sourcing \$env"
   . "\$env"
else
-  echo "'\$env' does not exist!"
-fi
-
-env="/opt/vapoursynth/env.sh"
-if [ -f "\$env" ]; then
-  echo "sourcing \$env"
-  . "\$env"
-else
-  echo "'\$env' does not exist!"
+  env="/opt/vapoursynth/env.sh"
+  if [ -f "\$env" ]; then
+    . "\$env"
+  fi
fi
-
-"\$scriptDir/vsViewer" \$*
+$*
EOF
   chmod a+x vsfilters_env.sh
fi
to modify the vsfilters_env.sh and use debug2-branch of vsViewer to get some debug info,...
sadly all this didn't really help with the loading.
update: small correction the initialization of the libraries did work, bug now it fails at 'vssInit' which is the function pointer to Vapoursynths 'vsscript_init'.


Cu Selur
----
Dev versions are in the 'experimental'-folder of my GoogleDrive, which is linked on the download page.
Reply
Quote:vsscript_init

int vsscript_init()

Initialises the available scripting interfaces.

Returns the number of times vsscript_init() has been called so far, including this call, or 0 in case of failure. This function will only fail if the VapourSynth installation is broken in some way.
see: http://www.vapoursynth.com/doc/api/vsscr...cript-init
-> :/
----
Dev versions are in the 'experimental'-folder of my GoogleDrive, which is linked on the download page.
Reply
Okay, until I figure this out R47 breaks vsViewer (and vsedit).
-> will look at restricting Vapoursynth to R46 tomorrow

Cu Selur
----
Dev versions are in the 'experimental'-folder of my GoogleDrive, which is linked on the download page.
Reply
Think I figured out how to adjust vsViewer to be Vapoursynth R46 compatible.
-> hopefully this fixes the Vapoursynth problem I had (will report back)

Cu Selur
----
Dev versions are in the 'experimental'-folder of my GoogleDrive, which is linked on the download page.
Reply
Nope there's still a problem with vapoursynth (neither vspipe nor vsviewer work; still having problems initializing vsscript). Sad
(aside from ffms2k not building)

Cu Selur
----
Dev versions are in the 'experimental'-folder of my GoogleDrive, which is linked on the download page.
Reply
Moin, djcj
How to add libaom (AV1) to ffmpeg ?
Reply
The PPA for Ubuntu 18.04 isn't maintained anymore? I can't install updates and also can't add the PPA on my Notebook.
Reply


Forum Jump:


Users browsing this thread: 2 Guest(s)