Are you able to ssh into the box and compile and install software as user (not root) _somehow_?

Piwigo uses either PHP IMagick, external ImageMagick or PHP GD, depending on what's available. These don't handle movie, for that ffmpeg is needed (or rather, the VideoJS plugin uses it).

There are ffmpeg static builds provided, https://johnvansickle.com/ffmpeg/ (as linked from https://ffmpeg.org/download.html), that you could install in a user directory and tell VideoJS where it lives. Similar for mediainfo. It's all described in the VideoJS wiki, https://github.com/Piwigo/piwigo-videoj … m-not-root .

ember1205 wrote:

First, it appears that Piwigo 13.6.0 plus videojs 2.9.b is broken in its entirety.

Might be, it hasn't seen much love by the author in the last years.. and there are quite some issues open https://github.com/Piwigo/piwigo-videojs/issues

I tried it after a long time again and it has at least problems with the path configuration.
The code in git advanced a bit compared to the release, I tried that as well but it doesn't show the dependencies section.

Opening the plugin shows errors for the last config item (resolution settings, apparently) and trying to run even a simulated sync results in server errors.

I don't get errors there though, with PHP 8.0

Second, the author's installation steps make no sense. He talks about extracting mediainfo from an OS's package as opposed to directly creating a statically-linked version of the tool. He has included the specific library files that are needed to run the dynamically-linked version of the executable, but the LD_LIBRARY_PATH update he suggests doesn't actually refer to the linked libraries he has included in the zip file (what's the point, then?).

Oversight? After all, it's a wiki and could be edited. Probably meant was

LD_LIBRARY_PATH="/home/youruser/usr/lib64:$LD_LIBRARY_PATH"

Third, the install directions for the videojs plugin tell one to edit local files, but don't explicitly state WHICH file needs to get which piece of code added. And, certain pieces of the updates don't show any examples so it's impossible to know if it's to be done a certain way or not (do I need to update ONLY the path to find the mediainfo executable, or can I specify the full path to it including the mediainfo executable itself?). I can make reasonable guesses, but given that the plugin never executes and just throws errors, I have no way to know if it is even READING the code I've added.

Yes it's quite a mess. The file to edit is linked in the wiki though.. BUT, the wiki is outdated and doesn't reflect the "new" code. It should not be necessary anymore to edit the code file linked there. Instead, it's intended that the paths could be added to the local Piwigo config, like

$conf['vjs_mediainfo_dir'] = '';
$conf['vjs_exiftool_dir'] = '';
$conf['vjs_ffprobe_dir'] = '';
$conf['ffmpeg_dir'] = '';

and fill the directory names as needed. However, if you have to set LD_LIBRARY_PATH then you'll need an invoker script like

LD_LIBRARY_PATH="/home/youruser/usr/lib64:$LD_LIBRARY_PATH" /home/youruser/usr/bin/mediainfo

and place that as for example /home/youruser/bin/mediainfo and in the local config have

$conf['vjs_mediainfo_dir'] = '/home/youruser/bin/';

Note the final slash. BUT, again, the sync page doesn't pick that up and one has to enter /home/youruser/bin/mediainfo each time. See also [Github] piwigo-videojs issue #132 that I submitted over four years ago.

ember1205 wrote:

erAck wrote:

I don't get errors there though, with PHP 8.0

I am running PHP8.1, but I suspect that would not be the issue in itself.

Oh it well may be.. 8.1 errs more for code it only warned about earlier. Unmaintained for years code may get trapped.

and place that as for example /home/youruser/bin/mediainfo and in the local config have

Code:

$conf['vjs_mediainfo_dir'] = '/home/youruser/bin/';

But there again arises the same issue. If I edit the ~/subdir/local/config/config.inc/php

Erm.. what? Which file?

and I specify

Code:

$conf['vjs_mediainfo_dir'] = './';

That wouldn't be quite right. ./ is the current directory, which when running the site is another directory than your home directory. You need to specify the full absolute path as in my example, in your case /home/youruser/

The plugin still show an error when you load the Settings page. So, did I specify the correct directory? I do have a script file there called mediainfo which contains:

Code:

#!/usr/bin/bash

LD_LIBRARY_PATH=.:usr/lib64 usr/bin/mediainfo

Do not use a single dot for current directory in LD_LIBRARY_PATH. And read what is written. That should be

LD_LIBRARY_PATH="/home/youruser/usr/lib64:$LD_LIBRARY_PATH" /home/youruser/usr/bin/mediainfo

again with full absolute paths.

That script is executable, and if I run "./mediainfo" in my home directory, it works as expected.

Yes, but not anywhere else.

If I try to run a simulated sync, I get a page full of errors that starts with one stating:

Code:

Warning: Undefined array key "vjs_sync..."

That is a warning, not an error, but they corrupt the UI. You can suppress or redirect them, see [Forum, post 183126 by erAck in topic 31852] Menubar tags issue after 12.2.0 upgrade.

The whole process is completely dead at that point.

Upon some further investigation, I also see that the PHP environment on my server shows that imagick is not installed yet my server does have the convert tool from ImageMagick on it. If there's no module in PHP for it, then how is it being properly called for image resizing?

Yes, unless directed otherwise the auto order tried is imagick, ImageMagick, GD.

What additionally might play part (maybe not error related) is a lacking `Has Settings: true` in the plugin's main.inc.php like in
[Github] piwigo-videojs commit bcef4a0d
that never was released though. As some other fixes weren't. (something with the vjs_sync above as well, but as said, that HEAD version for me ran even worse).

ember1205 wrote:

Where you said "don't use a dot in the LD_LIBRARY_PATH"... but, that's actually what the howto doc says to do.

Yes, for quick testing whether it works, which it even doesn't if the zip is unzipped preserving the directories. And it's ill-advised anyway, you do not want to pull arbitrary libraries in that happen to reside in your current working directory. And isn't clarified that it's not the final value that needs to be used.

I just corrected that in the wiki to
LD_LIBRARY_PATH="$HOME/usr/lib64:$LD_LIBRARY_PATH"  $HOME/usr/bin/mediainfo