All plugins should be placed inside/lib/lives This is where "make
install" will place them.
If the plugins are installed to a non-standard location then you still need
to edit the config file by hand,
the config file is now in ~/.config/lives/settings
If this is an issue then please feel free to c
Perhaps version 3.2.0 which was released in November 2020 solves this.
See also https://bugs.launchpad.net/ubuntu/+source/lives/+bug/1903465
If you use a library path other than /usr/lib, (or to be more precise,
$PREFIX/lib) for the plugins you need to do two things:
1) ./configure --libdir=
e.g. ./configure --libdir=/usr/lib/libx86_64-linux-gnu/
Assuming the libweed libs are also in the same directory:
2) Adjust the library paths
On Thu, Sep 25, 2014 at 11:20 AM, Wookey wrote:
> Changing the in the ~/.lives file from
> /usr/lib/
> to
> /usr/lib/x86_64-linux-gnu/ (on this machine)
> solves the issue:
So, essentially you're saying that the very first time you launch
lives, it creates the config file and then stores file a
+++ Wookey [2014-09-25 03:19 +0100]:
> Package: lives
> Version: 2.2.6~ds0-1
> Severity: important
>
> So this looks like lives-plugins package has been multiarched, but lives
> itself is not looking in the multiarch path.
>
> I assume all that is needed is a rebuild with the correct default
> se
Package: lives
Version: 2.2.6~ds0-1
Severity: important
I have just installed and tried to use lives for the first time
On startup lives reports:
LiVES was unable to find any encoder plugins.
PLease check that you have them installed correctly in
/usr/lib//lives/plugins/encoders/
You will not be
6 matches
Mail list logo
