March 2026 - Cin - Cinelerra-GG Mailing Lists

thirdparty ffmpeg-8.0 vs system ffmpeg-8.0.1
by Terje J. Hanssen 03 Mar '26

03 Mar '26

I build a standard single-user, static bundled Cingg and looked at the thirdparty ffmpeg-8.0 cd /cinelerra/cinelerra-5.1/thirdparty/ffmpeg-8.0 Trying to verify its available hwaccels methods: ./ffmpeg -hwaccels Hardware acceleration methods: vdpau cuda vaapi Verifying the same with my system ffmpeg-8.0.1 on Tumbleweed-Slowroll I get ffmpeg -hide_banner -hwaccels Hardware acceleration methods: vdpau cuda vaapi qsv drm vulkan I wonder why not also the thirdparty ffmpeg-8.0 does list "qsv" and "vulkan"? Seemingly among encoders "--enable-libvpl" and "--enable-vulkan" are listed.

2 1

My device not longer support vulkan capabillty
by Terje J. Hanssen 02 Mar '26

02 Mar '26

I had to re-install openSUSE Tw-Slowroll on my Dell XPS-13/9370 with i7/ UHD620 iGPU ( Intel Coffe Lake, gen8, 2017). It worked previously when I tested cin-12-02-2026-x86_64.AppImage and ffmpeg transcoding with h264_vulkan before that. The equivalent tests errors out with h264_vulkan, but works with h264_vaapi and h264_qsv Cingg ------ [h264_vulkan @ 0x7f2f462a0900] Device does not support the VK_KHR_video_maintenance1 extension! FFMPEG::open_encoder err: Function not implemented int FFMPEG::open_encoder(const char*, const char*): open failed h264_vulkan:/home/terje/Videos/hdv09_04_cin_h264_vulkan_8b420.mp4 Render::render_single: Session finished. ffmpeg-8 (system) ----------------- [h264_vulkan @ 0x55c10724c340] Device does not support the VK_KHR_video_maintenance1 extension! [vost#0:0/h264_vulkan @ 0x55c1071c8cc0] [enc:h264_vulkan @ 0x55c1071ea0c0] Error while opening encoder - maybe incorrect parameters such as bit_rate, rate, width or height. [vf#0:0 @ 0x55c10724c700] Error sending frames to consumers: Function not implemented [vf#0:0 @ 0x55c10724c700] Task finished with error code: -38 (Function not implemented) [vf#0:0 @ 0x55c10724c700] Terminating thread with return code -38 (Function not implemented) [vost#0:0/h264_vulkan @ 0x55c1071c8cc0] [enc:h264_vulkan @ 0x55c1071ea0c0] Could not open encoder before EOF [vost#0:0/h264_vulkan @ 0x55c1071c8cc0] Task finished with error code: -22 (Invalid argument) [vost#0:0/h264_vulkan @ 0x55c1071c8cc0] Terminating thread with return code -22 (Invalid argument) [out#0/mp4 @ 0x55c1071b95c0] Nothing was written into output file, because at least one of its streams received no packets. I have verified that the same tests work on my 2 year more legacy Sky Lake with i7/ HD530 iGPU (gen6, 2015) and Slowroll. -------- So far I have not discovered possible missing package, driver or lib that cause this issue, so troubleshooting hints are welcome. Without equivalent hardware and system, it is difficult to compare installed package lists, but these expected the most relevant: zypper se -i driver i | brltty-driver-at-spi2 | AT-SPI 2 driver for BRLTTY | package i | brltty-driver-brlapi | BrlAPI driver for BRLTTY | package i | brltty-driver-speech-dispatcher | Speech Dispatcher driver for BRLTTY | package i | brltty-driver-xwindow | XWindow driver for BRLTTY | package i+ | intel-media-driver | Intel Media Driver for VAAPI | package i+ | intel-vaapi-driver | Intel Driver for Video Acceleration (VA) API for Linux | package i | xorg-x11-driver-video | Compatibility metapackage for X.Org video drivers | package zypper se -i intel i+ | intel-media-driver | Intel Media Driver for VAAPI | package i+ | intel-vaapi-driver | Intel Driver for Video Acceleration (VA) API for Linux | package i | kernel-firmware-intel | Kernel firmware files for Intel-platform device drivers | package i | libdrm_intel1 | Userspace interface for Kernel DRM services for Intel chips | package i+ | libvulkan_intel | Mesa vulkan driver for Intel GPU | package zypper se -i vulkan i | libgstvulkan-1_0-0 | GStreamer Streaming-Media Framework Plug-Ins | package i | libvulkan1 | The Vulkan 3D graphics and compute API | package i+ | libvulkan_intel | Mesa vulkan driver for Intel GPU | package i | libvulkan_lvp | Mesa vulkan driver for LVP | package i | Mesa-vulkan-device-select | Vulkan layer to select Vulkan devices provided by Mesa | package i+ | vulkan-tools | Diagnostic utilities for Vulkan | package zypper se -i libmfx libvpl libva i+ | libmfx-gen1_2 | Intel oneVPL GPU Runtime | package i+ | libmfx1 | The Intel Media SDK | package i | libva-drm2 | DRM backend for the Video Acceleration API | package i | libva-glx2 | GLX backend for the Video Acceleration API | package i+ | libva-utils | A collection of utilities and examples to exercise VA-API | package i | libva-wayland2 | Wayland backend for the Video Acceleration API | package i | libva-x11-2 | X11 backend for the Video Acceleration API | package i | libva2 | Video Acceleration API | package i | libvpl2 | oneAPI Video Processing Library (oneVPL) dispatcher | package i | Mesa-libva | Mesa VA-API implementation | package

4 19

Another test appimage, hopefully this time with onevpl/vulkan/libplacebo/zimg
by Andrew Randrianasulu 02 Mar '26

02 Mar '26

https://disk.yandex.ru/d/Eqvrpylgwvc7Rw I fighted libplacebo and not sure who won - there is no Vulkan device in qemu VM! Try when you can and tell me what works? I did not include 16bpc crash fixes there, but without specifical env. variable those old new formats should not show up

2 9