[Cin] vaapi vs appimage, kdenlive way

[Phyllis Smith]

Andrew,
Unfortunately, the setenv for LIBVA_DRIVERS_PATH in main.C used in an
AppImage does not solve the problem of being able to use the Hardware
Vaapi/Vdpau capability of the computer CinGG is executed on.  I am assuming
that this was the goal?  Here is what I tested:

1. Compiled CinGG with the setenv in main.c on AMD computer that had no
graphics hardware/software installed.
2. Verified that on this computer when I changed
Settings/Preferences/Performance hw device to either vaapi or vdpau and
executed the binary, I would get "operation not permitted ... using
software".
3. Created AppImage on same computer.
4. Ran that AppImage on laptop where the hardware/software supports both
vaapi and vdpau.  This failed to allow using either vaapi or vdpau.

So I fail to see any advantage to adding the setenv.  Am I wrong?  What
does it solve, if anything?

On Mon, May 6, 2024 at 6:06 PM Andrew Randrianasulu <randrianasulu at gmail.com>
wrote:

>
> https://invent.kde.org/packaging/craft-blueprints-kde/-/commit/ce5096a51ce1f9009ba98c339894aaceb79fc5ef
>
> see, they set
>
>
> "LIBVA_DRIVERS_PATH=/usr/lib/dri:/usr/lib64/dri:/usr/lib/x86_64-linux-gnu/dri:/usr/lib/aarch64-linux-gnu/dri"
>
> I wonder if we should do the same ....
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.cinelerra-gg.org/pipermail/cin/attachments/20240508/0af24749/attachment.htm>