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.

[HELP] How to change directory location of installed "hybrid-vapoursynth-addon"
#1
The installation instructions call for installing to "opt" directory within the user's home directory.
I instead wanted to install to ".opt", so I replaced all instances of "opt" with ".opt" during the installation process.
However The Hybrid application was not able to detect this location for the vapoursynth plugin.
So post-install I went and changed the directory name from ".opt" to "opt", as well as the paths entries in .bashrc and .profile
After doing this, the Hybrid application was then able to detect the vapoursynth plugin and create a vapoursynth dropdown menu under filters tab.

I still want to have the install location be somewhere else other than "opt".
My question is: where else do I need to change the directory name to ".opt" within all the various lines of code?
Here are the only places I currently know to change it.
- The directory name itself
- Paths lines in .bashrc and .profile
- The "SystemPluginDir=" line in vapoursynth.conf located in /home/username/.config/vapoursynth

So far I've tried a step involving the creation of a misc.ini file with suggested lines added to it, but that did not work.

I am wondering, is hidden folder syntax not possible? --> .opt instead of opt
Or... is the installation script generating lines pointing to "opt" directory regardless if the user installed to that path or not?
Reply
#2
I'll adjust Hybrid to also look for '.opt' (in the next public release), but that will only make Hybrid detect the Vapoursynth installation.
with:
[General]
vapoursynth=true
vsPluginsPath="absolute path to plugins folder"
vsScriptPath="absolute path to scripts folder"
in the misc.ini (see: https://forum.selur.net/thread-10.html) you can tell Hybrid to a. enable Vapoursynth b. where to find the plugins c. where to find the scripts.
If the plugins are not in the autoload folder of Vapoursynth, you can also add 'vsLoadLibrariesOnNonWindows=true' to let Hybrid explicitly know that it explicitly needs to load each library.

For Vapoursynth itself, look at: https://www.vapoursynth.com/doc/installation.html#linux

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: 1 Guest(s)