On 23/02/2026 23:33, Andrew Randrianasulu wrote:

вт, 24 февр. 2026 г., 01:04 Terje J. Hanssen via Cin <[email protected]>:

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.

May be it was disabled upstream due to lack of red channel you reported?

Yeah, I also suspected that could be the case. But when vulkan still worked on SkyLake online updated, I thought maybe not. I also have replaced kernel default 6.18.9 with kernel longterm 6.12.73 on XPS as previously, but no difference with regards to vulkan.

After all, if image is missing one color channel it hardly worth keeping it enabled, people will get completely ruined encodes ...

I aggree, vulkan is not useable for video. SkyLake is yet ok as a test platform in case vulkan/mesa manage solve the issues.

There is whole "Intel fired some devs, Intel trying to hire some devs" thing going on, so I guess internally it can be quite inconsistent view about what can be done about that case, realistically.

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

_______________________________________________ Cin mailing list -- [email protected] To unsubscribe send an email to [email protected]

вт, 24 февр. 2026 г., 22:35 Phyllis Smith via Cin < [email protected]>:

Should we at least put a line or 2 in the manual stating vulkan is only experimental?

Yes, at least encoding part of it seems to be not really that great right now..... Also should we change the option in Settings->Preferences, Performance tab

from "Vulkan" to "Vulkan-exper."?

This one is for *decoding*. Also experimental, but something I can test on my end. Maybe someone will try it and be able to suggest some fixes.

Yeah, may be even on nvidia-proprietary.

It worked previously when I tested cin-12-02-2026-x86_64.AppImage and

...

ffmpeg transcoding with h264_vulkan before that.

_______________________________________________ Cin mailing list -- [email protected] To unsubscribe send an email to [email protected]

Should we at least put a line or 2 in the manual stating vulkan is only

...

...

experimental?

Yes, at least encoding part of it seems to be not really that great right now.....

Andrea, could you add that to the hardware performance section in Latex for the Manual if you have time?

...

Also should we change the option in Settings->Preferences, Performance

...

tab from "Vulkan" to "Vulkan-exper."?

This one is for *decoding*. Also experimental, but something I can test on my end.

Maybe someone will try it and be able to suggest some fixes.

...

Yeah, may be even on nvidia-proprietary.

Also, do you plan to flip vulkan/libplacebo "on" for new Appimage builds?

My plan is to try to get an up to date AppImage on another laptop and there will flip these on. I will try anylinux-appimage but do not know if I will succeed.

I think we should note that for now vulkan switch is off by default (but if you build with system's libav* libs it will depend on how those were build ...)

...

...

It worked previously when I tested cin-12-02-2026-x86_64.AppImage and

...

ffmpeg transcoding with h264_vulkan before that.

_______________________________________________ Cin mailing list -- [email protected] To unsubscribe send an email to [email protected]

On 25/02/2026 14:09, Andrea paz wrote:

Andrea, could you add that to the hardware performance section in Latex for the Manual if you have time?

To add Vulkan to the manual, I would need some clarification.

Decoding: 1- Is the “vulkan” setting in Preferences --> performance only valid for amdgpu? 2- Is there a need for libplacebo and certain environmental variables? Which ones? 3- Is there anything else about vulkan that should be included in the manual?

Encoding: 4- Are presets with Vulkan hardware agnostic? (Apart from Intel with problems in ANV). 5- Is there a need for libplacebo and certain environmental variables? Which ones? 6- Is there anything else about vulkan that should be included in the manual?

This is  more some topic comments, and I hope someone else can clarify your specific questions above. Via FFMpeg we have ffmpeg -hide_banner -hwaccels Hardware acceleration methods: vdpau cuda vaapi qsv drm vulkan Generic I think the open source methods vaapi, qsv and vulkan should get equal treatement in the manual. As known Vulkan is seemingly still in progress, immature and more or less experimental.  Especial the Mesa ANV driver for Intel has reported video encoding issues during more than a year. Hopefully it will be fixed not far into the future https://www.phoronix.com/news/Mesa-26.1-devel-ANV-H265-Encode Else, selecting or switching between dual GPU or Hybrid GPU could get a section in the manual.. ----------- I was not aware of the “vulkan” setting in Preferences --> performance or which capability they are meant to offer. Therefore I just tried to set "Use HW Device: vulkan" (Intel SkyLake) and tested vulkan rendering with h264_vulkan_8b420.mp4 Set the usual environment variable export ANV_DEBUG="video-decode,video-encode" and launched Andrew's appimage Cinelerra Infinity - built: Feb 12 2026 02:45:04 The extra output I noticed was Decoder mpeg2video does not support device type vulkan. HW device init failed, using SW decode. file:/home/terje/Videoklipp/hdv09_04.m2t   err: Operation not permitted And the Red color still lacks on the rendered video.

On 25/02/2026 20:07, Andrew Randrianasulu wrote:

ср, 25 февр. 2026 г., 19:29 Terje J. Hanssen via Cin <[email protected]>:

On 25/02/2026 14:09, Andrea paz wrote:

...

Andrea, could you add that to the hardware performance section in Latex for the Manual if you have time?

To add Vulkan to the manual, I would need some clarification.

Decoding: 1- Is the “vulkan” setting in Preferences --> performance only valid for amdgpu? 2- Is there a need for libplacebo and certain environmental variables? Which ones? 3- Is there anything else about vulkan that should be included in the manual?

Encoding: 4- Are presets with Vulkan hardware agnostic? (Apart from Intel with problems in ANV). 5- Is there a need for libplacebo and certain environmental variables? Which ones? 6- Is there anything else about vulkan that should be included in the manual?

This is  more some topic comments, and I hope someone else can clarify your specific questions above.

Via FFMpeg we have

ffmpeg -hide_banner -hwaccels Hardware acceleration methods: vdpau cuda vaapi qsv drm vulkan

Generic I think the open source methods vaapi, qsv and vulkan should get equal treatement in the manual.

As known Vulkan is seemingly still in progress, immature and more or less experimental.  Especial the Mesa ANV driver for Intel has reported video encoding issues during more than a year. Hopefully it will be fixed not far into the future https://www.phoronix.com/news/Mesa-26.1-devel-ANV-H265-Encode

Else, selecting or switching between dual GPU or Hybrid GPU could get a section in the manual..

Whole section? ;)

Aren't CIN_DRM_ENC/CIN_DRM_DEC already documented?

Yes, there is a subsection in 19.1.1 GPU hardware decoding using the HW device node component In addition for a computer with dual graphics cards, you can select your specific device with an environment variable to decode and encode. For example: CIN_DRM_DEC=/dev/dri/renderD129 CIN_DRM_ENC=/dev/dri/renderD128 ./cin Maybe we don't need to care about the SW driver configuration component (VK_ICD_FILENAMES, missing or misconfigured driver)? /usr/share/vulkan/icd.d/ (JSON files) I also thought of the alongside switcherooclt as used for vkcube.

-----------

I was not aware of the “vulkan” setting in Preferences --> performance or which capability they are meant to offer.

Therefore I just tried to set "Use HW Device: vulkan" (Intel SkyLake) and tested vulkan rendering with h264_vulkan_8b420.mp4

Set the usual environment variable export ANV_DEBUG="video-decode,video-encode"

and launched Andrew's appimage Cinelerra Infinity - built: Feb 12 2026 02:45:04

The extra output I noticed was

Decoder mpeg2video does not support device type vulkan. HW device init failed, using SW decode. file:/home/terje/Videoklipp/hdv09_04.m2t   err: Operation not permitted

Yeah, no mpeg2 love here ;)

Try h264/h265 encoded input file?

And the Red color still lacks on the rendered video.

_______________________________________________ Cin mailing list -- [email protected] To unsubscribe send an email to [email protected]

Further modification to Tips.tex.

I really like the name, switcherooctl, and I can use this on my laptop to switch GPU since I have 2 and never quite know which one is being used. I just wish Vulkan was named something much more meaningful - why could they not make it obvious like the name OpenGL is? at least put GL in the name somewhere, like vulkanGL2.

Switching between multiple GPUs using switcherooctl

I have written it as a small worked example freely usable and editable._____________________

Nicely stated in my opinion. I have updated the GIT Manual accordingly. I did change one thing so as not to "scare" every one - I left out the part that eventually Vulkan would replace OpenGL. In reality Cinelerra should have Vulkan a choice in the Video Driver section of the Settings->Performance but I do not ever see that happening in my lifetime unless some expert volunteers. Thank you to Andrea. I made some additions to the manual regarding Vulkan, but only in the

general section. I'm not sure if I was always accurate, so please check what I wrote. However, I have not made any changes to the specific sections on decoding [19.1.1] and encoding [19.1.2] because I do not fully understand the subject. Is what is written in these sections still valid? What should we add? I'm sorry, I'm just confused and unable to make corrections.