*Subject: AppImage with Hardware Acceleration* After experimenting with different AppImages created on different computers, different Operating Systems with different graphics cards and different vaapi/vdpau libraries installed, or none of these libraries installed, I think I can safely conclude the following:
1) Hardware acceleration, vaapi or vdpau, works the same running either the created binary or the created AppImage from that binary on that same computer. 2) Hardware acceleration using an AppImage created on another computer running a different Operating System or even just a different level of Operating System, most likely will not work unless the user's computer just happens to have the same characteristics with respect to vaapi/vdpau as the computer where the AppImage was created. Does MatN or anyone else's experience differ from this? I did open BT #604 in case there is some way to make hardware acceleration more accessible. Glitterball3 uses a workaround (see forum) to create links to different libraries to get this to work, but varies so much. *************************************** Some experimental results ****************************** For example using Test1 (hockey.ts television recording) and Test2 (Life Untouched 4K HDR10 Demo.mp4 downloadable file): CinGG-20220131-x86_64.AppImage -on *AMD laptop *with Radeon RX-580 graphics card where AppImage was created (Fedora 32): Test1 hardware acceleration vaapi and vdpau both work as expected. Test2 hardware acceleration vaapi works, but vdpau does not - this is as expected. CinGG-20220131-x86_64-older_distros.AppImage - on AMD laptop with Radeon RX-580 using AppImage created on AMD Opteron Ubuntu 16.04: Test1 and Test2 hardware acceleration do not work due to missing Radeon so file. CinGG-20220131-x86-64-older_distros-multibit.AppImage - on AMD laptop with Radeon RX-580 using AppImage created on Intel 4-core with Broadwell graphics: Test1 hardware acceleration only vdpau works and that could be due to a "wrapper". Test2 hardware acceleration does not work. CinGG-20220131-x86_64.AppImage (same results as if built on this computer/this O/S) - on *Intel 4-core laptop* with Broadwell using AppImage created on AMD laptop with different O/S of Fedora 32: Test1 hardware acceleration only vaapi works, but vdpau does not. Test2 hardware acceleration does not work.. CinGG-20220131-x86_64-older_distros.AppImage - on Intel 4-core laptop with Broadwell using AppImage created on AMD Opteron Ubuntu 16.04: Test1 and Test2 hardware acceleration do not work. CinGG-20220131-x86-64-older_distros-multibit.AppImage - on Intel 4-core laptop with Broadwell using AppImage created on same computer but older O/S of Fedora 29: Test1 and Test2 hardware acceleration do not work.
-- Cin mailing list Cin@lists.cinelerra-gg.org https://lists.cinelerra-gg.org/mailman/listinfo/cin
