The following warnings occurred:
Warning [2] Undefined array key 1 - Line: 313 - File: inc/plugins/google_seo/redirect.php PHP 8.3.12-nmm1 (Linux)
File Line Function
/inc/class_error.php 153 errorHandler->error
/inc/plugins/google_seo/redirect.php 313 errorHandler->error_callback
/inc/class_plugins.php 142 google_seo_redirect_hook
/global.php 100 pluginSystem->run_hooks
/showthread.php 28 require_once
Warning [2] Undefined array key 1 - Line: 314 - File: inc/plugins/google_seo/redirect.php PHP 8.3.12-nmm1 (Linux)
File Line Function
/inc/class_error.php 153 errorHandler->error
/inc/plugins/google_seo/redirect.php 314 errorHandler->error_callback
/inc/class_plugins.php 142 google_seo_redirect_hook
/global.php 100 pluginSystem->run_hooks
/showthread.php 28 require_once
Warning [2] Undefined array key "" - Line: 327 - File: inc/plugins/google_seo/redirect.php PHP 8.3.12-nmm1 (Linux)
File Line Function
/inc/class_error.php 153 errorHandler->error
/inc/plugins/google_seo/redirect.php 327 errorHandler->error_callback
/inc/class_plugins.php 142 google_seo_redirect_hook
/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
GPAC fails,..
https://pastebin.com/fmfh4DC7
-> seems like it's trying do build more than necessary,..
(see: https://gpac.wp.imt.fr/2015/07/29/gpac-b...platforms/)
----
Dev versions are in the 'experimental'-folder of my GoogleDrive, which is linked on the download page.
Reply
The pip warnings are harmless but I've silenced them. I've also added a check if Vapoursynth is even installed before anything is built. And mp4box should hopefully now build.
Reply
Tested it -> MP4Box builds fine now. Smile

Cu Selur
----
Dev versions are in the 'experimental'-folder of my GoogleDrive, which is linked on the download page.
Reply
small overview:
  • vapoursynth.sh, builds vapoursynth and places it into ~/opt/vapoursynth
  • plugins.sh, builds the vapoursynth plugins and places them into the build folder
  • tools.sh, builds the plugins in a build folder and deletes the build folder at the end
  • deploy.sh takes the collects and patches the tools and their dependencies and places them in a now portable 'hybrid' folder

some small problems and bugs:
1. deploy.sh: looks for 'build-vapoursynth.sh', but the script is named vapoursynth.sh -> script should use 'vapoursynth.sh'
2. if plugins.sh is called before tools.sh, tools.sh deletes the compiled plugins -> maybe better move the plugins in a vsplugins folder
3. deploy.sh: does not copy the plugins.sh -> script should also copy the plugins.sh script into the hybrid folder

Cu Selur
----
Dev versions are in the 'experimental'-folder of my GoogleDrive, which is linked on the download page.
Reply
On Ubuntu i have some applications that are manually "installed" (saved to $HOME/bin). I update them manually using scripts every time i update my system (there is a function to run commands and script every time apt is finished). Can i do this also with hybrid? Is there an option like

hybrid --update

to only download new version? Normally updates are disabled because i don't want to download updates every time i start hybrid. The only way i see at the moment is to write a script, enable updates, start hybrid gui and disable updates after all is done.
Reply
So 'No' there is no 'hybrid --update' and it is not planed atm.

Reading this thread you could have read that:
a. the usual updating through the old PPA doesn't work anymore
b. djcj created a few scripts which allow to:
1. download and compile the tools Hybrid uses by default
2. download and compile Vapoursynth
3. download and compile the Vapoursynth Plugins Hybrid uses.
c. I will probably, release the following in the future:
1. the normal binary (dynamically compiled, so installing qt libraries and the tools Hybrid uses is necessary)
2. a packaged version which includes a folder with Hybrid, all the basic tools Hybrid uses, scripts to build Vapoursynth and the Vapoursynth plugins and a README.

So the typical usage for Ubuntu users would be:
1. download the packaged version and place it for example under ~/opt/hybrid, run the vapoursynth.sh and plugins.sh to update/build Vapoursynth and it's plugins.
2. if you want to update Hybrid delete, the ~/opt/hybrid folder download and extract the package and run vapoursynth.sh and/or plugins.sh in case those were updated.

Users of other Linux distribution would need to update the binary and all the tools they want updated fully manually.

-> If you want an automated way create one and share it with the rest of the Linux users.

Cu Selur
----
Dev versions are in the 'experimental'-folder of my GoogleDrive, which is linked on the download page.
Reply
@djcj:
two tools are missing:
d2vwitch: https://github.com/dubhater/D2VWitch
and
ffmsindex: https://github.com/FFMS/ffms2

would be cool if you could add them to the tools.sh (and deploy.sh) Smile
also another modification to the deploy.sh:
diff --git a/Hybrid/deploy.sh b/Hybrid/deploy.sh
index 54a914b..cb521cd 100755
--- a/Hybrid/deploy.sh
+++ b/Hybrid/deploy.sh
@@ -1,6 +1,6 @@
#!/bin/bash

-binaries_copy="nvhsp vsViewer_withenv.sh build-vapoursynth.sh"
+binaries_copy="nvhsp vapoursynth_env.sh vapoursynth.sh README"
binaries_qt="Hybrid bdsup2sub++ delaycut FrameCounter IdxSubCutter vsViewer"
binaries_32bit="DivX265 neroAacEnc tsMuxeR"
binaries_64bit="""
@@ -114,6 +114,7 @@ EOF

rm -rf ./usr ./bin ./share ./patchelf *.AppImage
cd ..
-
-7z a -m0=lzma2 -mx Hybrid.7z hybrid
+rsync -r build/* hybrid/vsfilters/
+now=$(date +"%Y%m%d")
+7z a -m0=lzma2 -mx "Hybrid_$now.7z" hybrid
(adding README, renaming vsViewer_withenv.sh to vapoursynth_env.sh, rsync build to hybrid/vsfilters and setting the current date in the Hybrid.7z file name)

I missed some Vapoursynth plugins: -> would be nice if you could add these to the plugins.sh

Cu Selur

Ps.: if VSFilterMod is to problematic I could rewrite Hybrid to use https://github.com/HomeOfVapourSynthEvolution/VSFilter and https://github.com/HomeOfVapourSynthEvol...y-VSFilter instead
----
Dev versions are in the 'experimental'-folder of my GoogleDrive, which is linked on the download page.
Reply
I will do all that in the next days or at least this weekend. The vsfilter plugins have only Visual Studio Solution files to build. Are you sure they can be build and used on Linux?
Reply
Not really,I'll ask about it over at doom9s. Smile
----
Dev versions are in the 'experimental'-folder of my GoogleDrive, which is linked on the download page.
Reply
okay, forget VSFilter:
Quote:VSFilter will always be windows only due to how it's coded.
source: https://forum.doom9.org/showthread.php?p...ost1880014
-> I'll adjust Hybrid (probably over the weekend) to only use VSFilterXX only on Windows. Smile

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


Forum Jump:


Users browsing this thread: 2 Guest(s)