March 2026 - Cin - Cinelerra-GG Mailing Lists

Adding CIN_HW_DEV=qsv for GPU HW decoding?
by Terje J. Hanssen 09 Mar '26

09 Mar '26

I have tested transcoding mpeg2video to h264_qsv, hevc_qsv, vp9_qsv and av1_qsv HW GPU accelerated decoding+encoding with ffmpeg. Just by adding "-hwaccel qsv" before the input file, the correct qsv codec for decoding in GPU apparently is auto-detected. ffmpeg -hide_banner -hwaccel qsv -i hdv09_04.m2t -c:v hevc_qsv -y hdv09_04_ffmpeg_hevc_qsv.mp4 With a medium powerful (balanced) Intel Alder Lake (i7-12700KF) /DG2 (A750) the qsv.mp4 video output and playback are clean and faster with GPU decoding. For the legacy, limited SkyLake (h264_qsv) and Coffee Lake (hevc_qsv) igpu's, it is best to keep decoding in CPU, due to igpu buffer errors and some distortions on the playback. So I wonder if it manageable to test-implement an additional environment variable "CIN_HW_DEV=qsv" for GPU HW decoding that adds "-hwaccel qsv" on the input side? If it works, it may be added as a "Use HW Device: qsv" next. Terje J. H

2 2

Yo, I did awful slideshow edit!
by Andrew Randrianasulu 09 Mar '26

09 Mar '26

In cinelerra-gg of course ... It looks more "my first EVAR take on compositing" and does not really follow music .. But I had a blast listening to it :) https://youtu.be/52ott-IeIV4

3 6

bug 674 (nested edl crash)
by Andrew Randrianasulu 09 Mar '26

09 Mar '26

Look for file named 0001-EXPERIMENTAL-better-fix-for-nested-edl-load-undo.patch* It fixed crash I was seeing but added massive memory leak or something so we reverted that. Thanks for all bisect work you did!

3 3

OCIO filter in ffmpeg.git
by Andrew Randrianasulu 08 Mar '26

08 Mar '26

https://source.ffmpeg.org/gitweb/ffmpeg.git/commit/677cf95ea4be805fa326adb0… looks like it uses standard one input-one output, so it may even work in cinelerra-gg, if nothing else broke.. Not sure how to properly define configuration for such filter - may be Blender have some GUI for this? Random link I stumbled upon while looking at OCIO search results - some notes on digital photography, it seems? https://juraj-notes.tomori.sk/

2 1

Forum Out of Sync
by Igor BEGHETTO 08 Mar '26

08 Mar '26

Hi, I don't know if it only occurs to me but the pages of the Forum are out of sync. I wrote a post in reply to "Extend a video clip on the timeline" by Chapolin user; if I look at the post without login, today I can see "2 Answers" and my post is hidden. But if I change the option from "Most Voted" to "Oldest", or "Newer", my post is showed and the "Answers" are 3. Same thing for the column of "Recent Posts" on the right of the screen. Links to: https://cinelerra-gg.org/forum/help-video/extend-a-video-clip-on-the-timeli… https://cinelerra-gg.org/forum/help-video/extend-a-video-clip-on-the-timeli… IgorBeg

2 5

Settings|Preferences|Performance|Use HW Device: QSV missing
by Terje J. Hanssen 04 Mar '26

04 Mar '26

I wonder if "Settings|Preferences|Performance|Use HW Device" is meant to set both gpu accelerated decoding and encoding (rendering)? and how does this possibly interact/work with selecting video preset, compression hwaccel methods or not? Use HW Device has available 5 options: none, vaapi, vdpau, cuda, vulkan, while qsv is missing, reason? I ran two av1_qsv rendering tests on Intel AlderLake/DG2 Using HW Device: None and vaapi respectively to exemplify this using the latest Cinelerra Infinity - built: Mar 1 2026 06:30:41 1) Settings|Preferences|Performance|Use HW Device: None file: hdv09_04.m2t compression av1_qsv_8b420.mp4 # Requires specific GPU hardware encoding capability # as well as required software implementation. cin_pix_fmt=nv12 profile=main # global_quality=25 libva info: VA-API version 1.23.0 libva info: Trying to open /usr/lib64/dri/iHD_drv_video.so libva info: Found init function __vaDriverInit_1_22 libva info: va_openDriver() returns 0 libva info: VA-API version 1.23.0 libva info: Trying to open /usr/lib64/dri/iHD_drv_video.so libva info: Found init function __vaDriverInit_1_22 libva info: va_openDriver() returns 0 Render::render_single: Session finished. ** rendered 5972 frames in 18.274 secs, 326.803 fps audio0 pad 64 0 (64) Fast and adequate quality/colors, although global quality may increase it somewhat. 2) Settings|Preferences|Performance|Use HW Device: vaapi (just to test) file: hdv09_04.m2t compression av1_qsv_8b420.mp4 # Requires specific GPU hardware encoding capability # as well as required software implementation. cin_pix_fmt=nv12 profile=main # global_quality=25 libva info: VA-API version 1.23.0 libva info: Trying to open /usr/lib64/dri/iHD_drv_video.so libva info: Found init function __vaDriverInit_1_22 libva info: va_openDriver() returns 0 libva info: VA-API version 1.23.0 libva info: Trying to open /usr/lib64/dri/iHD_drv_video.so libva info: Found init function __vaDriverInit_1_22 libva info: va_openDriver() returns 0 int FFVideoConvert::convert_picture_vframe(VFrame*, AVFrame*, AVFrame*): Error retrieving data from GPU to CPU file: /Videoklipp/AV1/hdv09_04.m2t int FFVideoConvert::convert_picture_vframe(VFrame*, AVFrame*, AVFrame*): Error retrieving data from GPU to CPU file: /Videoklipp/AV1/hdv09_04.m2t int FFVideoConvert::convert_picture_vframe(VFrame*, AVFrame*, AVFrame*): Error retrieving data from GPU to CPU file: /Videoklipp/AV1/hdv09_04.m2t Render::render_single: Session finished. ** rendered 5972 frames in 33.049 secs, 180.701 fps audio0 pad 64 0 (64) Decoder libdav1d does not support device type vaapi. HW device init failed, using SW decode. file:/Videoklipp/QSV/hdv09-04_cin_av1_qsv_8b420.mp4 err: Operation not permitted Decoder libdav1d does not support device type vaapi. HW device init failed, using SW decode. file:/Videoklipp/QSV/hdv09-04_cin_av1_qsv_8b420.mp4 err: Operation not permitted Total excess of backups: -50 Session time: 0:22:43 Cpu time: user: 0:01:24.375 sys: 0:00:14.084 unjoined tids / owner 3 00007f88517ff6c0 / 00007f88d16b96c0 12RenderEngine 00007f886b7fe6c0 / 00007f88d16b96c0 12RenderEngine 00007f88797fa6c0 / 00007f88d16b96c0 12RenderEngine

2 5

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 3

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