сб, 10 янв. 2026 г., 22:50 Terje J. Hanssen <[email protected]>:

Den 02.12.2025 16:39, skrev Andrew Randrianasulu:

...

On Tue, Dec 2, 2025 at 6:20 PM Terje J. Hanssen via Cin <[email protected]> wrote:

...

Late 2024 onevpl support was added for the buildsystem with various presets using cin_hw_dev=vaapi.

Maybe I simplify too much, but is it possible that current CinGG-20251121-x86_64.AppImage with ffmpeg-8 is ready to test vulkan the same way, just by replacing "vaapi" with "vulkan" in the presets? I have no hardware to test, but I think if/when latest patches by me lands and it will be confirmed new appimage copies vulkan loader and it works on different systems ...

Then you can play with new Vulkan encoding presets :)

Moment, about to send second patch

I have the latest CinGG-20251231-x86_64.AppImage and cinelerra-5.1-20260106.susetw.x86_64.rpm installed on openSUSE Tw-Slowroll.

Shift-Render and Video-Wrench Compression list the previous vaapi and qsv hwaccel methods.

Shouldn't we also see a base Vulkan tag here to start experimenting with presets?

Well, I do not have vulkan(h264/5/av1) encoding capable hardware, so it will be shot in the dark .... I can cobble together something for ffv1_vulkan (it works, just slow) but I think it will be faster to just create new preset on your side? At very least we will improve our documentation about how to do so ...

...

...

hevc_vaapi_8b420.mp4

mp4 hevc_vaapi cin_hw_dev=vaapi cin_pix_fmt=nv12 profile=main # global_quality=22

hevc_vaapi_10b420.mp4

mp4 hevc_vaapi cin_hw_dev=vaapi cin_pix_fmt=p010le profile=main10 # global_quality=22

hevc_vaapi_10b422.mp4

mp4 hevc_vaapi cin_hw_dev=vaapi cin_pix_fmt=y210le profile=rext # global_quality=22

Terje J. Hanssen

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

Den 10.01.2026 21:57, skrev Phyllis Smith via Cin:

No vulkan render formats have been added.  I do not have the hardware to test either (I really need a new kick-axx computer!) But because you have Andrey's package installed, maybe you test yourself (only not sure about the first line):

1. cd <wherever the package is installed>/bin/ffmpeg/video 2. cp hevc_vaapi_10b420.mp4 hevc_vulkan_10b420.mp4 3. edit hevc_vulkan_10b420.mp4 and change the first line from "mp4 hevc_vaapi" to "mp4 hevc_vulkan". 4. restart CinGGG

cd /usr/share/cin/ffmpeg/video Copied and edited the preset cat h264_vulkan_8b420.mp4     mp4 h264_vulkan     # Requires specific GPU hardware encoding capability     #  as well as required software implementation.     cin_hw_dev=vulkan     cin_pix_fmt=nv12     profile=high     # global_quality=22 but using this cause a Cinelerra error and no rendering: int FFMPEG::open_encoder(const char*, const char*): Cant find codec h264_vulkan:/Videoklipp/VULKAN/hdv1080i50_cin_h264_vulkan_8b420.mp4 -------- Is Vulkan enabled via Cingg's built-in ffmpeg, or is there other reasons it won't work? ----- In comparison my system ffmpeg-8 works on my machines with Intel iGPU UHD 620 and also HD 530 (but unhappily not yet on the most powerful Arch A750 (DG2) for unknown reasons). ffmpeg -hide_banner -init_hw_device "vulkan=vk:0" -hwaccel vulkan -hwaccel_output_format vulkan -i hdv1080i50.m2t -vf "format=nv12,hwupload" -c:v h264_vulkan -y hdv1080i50_h264_vulkan_nv12_vk0.mp4 ..... frame=  123 fps=0.0 q=-0.0 Lsize=   16876KiB time=00:00:05.30 bitrate=26065.5kbits/s speed=12.6x elapsed=0:00:00.41 [aac @ 0x56359d824b40] Qavg: 217.60 --------- Adding "-global_quality 25" (rather than -profile) reduce the file size to 1/5 du -sh hdv1080* 20M    hdv1080i50_h264_main_vulkan_nv12_vk0.mp4 10M    hdv1080i50_h264_vaapi_nv12.mp4 3.4M    hdv1080i50_h264_vulkan_gq25_nv12_vk0.mp4 17M    hdv1080i50_h264_vulkan_nv12.mp4 17M    hdv1080i50_h264_vulkan_nv12_vk0.mp4 16M    hdv1080i50.m2t

On Sat, Jan 10, 2026 at 12:50 PM Terje J. Hanssen via Cin <[email protected]> wrote:

Den 02.12.2025 16:39, skrev Andrew Randrianasulu: > On Tue, Dec 2, 2025 at 6:20 PM Terje J. Hanssen via Cin > <[email protected]> wrote: >> Late 2024 onevpl support was added  for the buildsystem with various >> presets using cin_hw_dev=vaapi. >> >> Maybe I simplify too much, but is it possible that current >> CinGG-20251121-x86_64.AppImage with ffmpeg-8 is ready to test vulkan the >> same way, just by replacing "vaapi" with "vulkan" in the presets? > I have no hardware to test, but I think if/when latest patches by me > lands and it will be confirmed new appimage copies vulkan loader and > it works on different systems ... > > Then you can play with new Vulkan encoding presets :) > > Moment, about to send second patch

I have the latest CinGG-20251231-x86_64.AppImage and cinelerra-5.1-20260106.susetw.x86_64.rpm installed on openSUSE Tw-Slowroll.

Shift-Render and Video-Wrench Compression list the previous vaapi and qsv hwaccel methods.

Shouldn't we also see a base Vulkan tag here to start experimenting with presets?

> >> hevc_vaapi_8b420.mp4 >> >>       mp4 hevc_vaapi >>       cin_hw_dev=vaapi >>       cin_pix_fmt=nv12 >>       profile=main >>       # global_quality=22 >> >> >> hevc_vaapi_10b420.mp4 >> >>       mp4 hevc_vaapi >>       cin_hw_dev=vaapi >>       cin_pix_fmt=p010le >>       profile=main10 >>       # global_quality=22 >> >> >> hevc_vaapi_10b422.mp4 >> >>       mp4 hevc_vaapi >>       cin_hw_dev=vaapi >>       cin_pix_fmt=y210le >>       profile=rext >>       # global_quality=22 >> >> >> Terje J. Hanssen >> >> >> _______________________________________________ >> Cin mailing list -- [email protected] >> To unsubscribe send an email to [email protected]

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

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

Den 11.01.2026 18:33, skrev Andrew Randrianasulu:

вс, 11 янв. 2026 г., 20:21 Terje J. Hanssen via Cin <[email protected]>:

Den 10.01.2026 21:57, skrev Phyllis Smith via Cin:

...

No vulkan render formats have been added.  I do not have the hardware to test either (I really need a new kick-axx computer!) But because you have Andrey's package installed, maybe you test yourself (only not sure about the first line):

1. cd <wherever the package is installed>/bin/ffmpeg/video 2. cp hevc_vaapi_10b420.mp4 hevc_vulkan_10b420.mp4 3. edit hevc_vulkan_10b420.mp4 and change the first line from "mp4 hevc_vaapi" to "mp4 hevc_vulkan". 4. restart CinGGG

cd /usr/share/cin/ffmpeg/video

Copied and edited the preset

cat h264_vulkan_8b420.mp4

    mp4 h264_vulkan     # Requires specific GPU hardware encoding capability     #  as well as required software implementation.     cin_hw_dev=vulkan     cin_pix_fmt=nv12     profile=high     # global_quality=22

but using this cause a Cinelerra error and no rendering:

int FFMPEG::open_encoder(const char*, const char*): Cant find codec h264_vulkan:/Videoklipp/VULKAN/hdv1080i50_cin_h264_vulkan_8b420.mp4

--------

Is Vulkan enabled via Cingg's built-in ffmpeg, or is there other reasons it won't work?

I think if you use cingg with internal ffmpeg libs you should pass newly-added --enable-vulkan configure switch? If vulkan sdk is new enough this should tell ffmpeg to enable various encoders and decoders based on Vulkan video. I think I tied libshaderc (shader compiler) to libplacebo enable, while it theory it can have its own switch. but only Vulkan-shaders based decoders and encoders depend on that (compared to driving dedicated hw blocks via Vulkan) so right now at ffmpeg-8.0 I think this is not really limiting. You can try to install libplacebo/libzimage devel libs, enable all three switches and see if it compiles/runs fine?

Rather than recompiling the internal ffmpeg, I wonder if also the internal ffmpeg may need some export variables for vulkan executed somewhere first to work? As discussed in earlier posts, the system ffmpeg with vulkan decoding/encoding require the following: default no output from vulkaninfo | grep VK_KHR_video after export ANV_DEBUG="video-decode,video-encode" vulkaninfo | grep VK_KHR_video     VK_KHR_video_decode_av1                       : extension revision 1     VK_KHR_video_decode_h264                      : extension revision 9     VK_KHR_video_decode_h265                      : extension revision 8     VK_KHR_video_decode_queue                     : extension revision 8     VK_KHR_video_decode_vp9                       : extension revision 1     VK_KHR_video_encode_h264                      : extension revision 14     VK_KHR_video_encode_h265                      : extension revision 14     VK_KHR_video_encode_queue                     : extension revision 12     VK_KHR_video_maintenance1                     : extension revision 1     VK_KHR_video_maintenance2                     : extension revision 1     VK_KHR_video_queue

-----

In comparison my system ffmpeg-8 works on my machines with Intel iGPU UHD 620 and also HD 530 (but unhappily not yet on the most powerful Arch A750 (DG2) for unknown reasons).

ffmpeg -hide_banner -init_hw_device "vulkan=vk:0" -hwaccel vulkan -hwaccel_output_format vulkan -i hdv1080i50.m2t -vf "format=nv12,hwupload" -c:v h264_vulkan -y hdv1080i50_h264_vulkan_nv12_vk0.mp4 ..... frame=  123 fps=0.0 q=-0.0 Lsize=   16876KiB time=00:00:05.30 bitrate=26065.5kbits/s speed=12.6x elapsed=0:00:00.41 [aac @ 0x56359d824b40] Qavg: 217.60

---------

Adding "-global_quality 25" (rather than -profile) reduce the file size to 1/5

du -sh hdv1080* 20M    hdv1080i50_h264_main_vulkan_nv12_vk0.mp4 10M    hdv1080i50_h264_vaapi_nv12.mp4 3.4M    hdv1080i50_h264_vulkan_gq25_nv12_vk0.mp4 17M    hdv1080i50_h264_vulkan_nv12.mp4 17M    hdv1080i50_h264_vulkan_nv12_vk0.mp4 16M    hdv1080i50.m2t

...

On Sat, Jan 10, 2026 at 12:50 PM Terje J. Hanssen via Cin <[email protected]> wrote:

Den 02.12.2025 16:39, skrev Andrew Randrianasulu: > On Tue, Dec 2, 2025 at 6:20 PM Terje J. Hanssen via Cin > <[email protected]> wrote: >> Late 2024 onevpl support was added  for the buildsystem with various >> presets using cin_hw_dev=vaapi. >> >> Maybe I simplify too much, but is it possible that current >> CinGG-20251121-x86_64.AppImage with ffmpeg-8 is ready to test vulkan the >> same way, just by replacing "vaapi" with "vulkan" in the presets? > I have no hardware to test, but I think if/when latest patches by me > lands and it will be confirmed new appimage copies vulkan loader and > it works on different systems ... > > Then you can play with new Vulkan encoding presets :) > > Moment, about to send second patch

I have the latest CinGG-20251231-x86_64.AppImage and cinelerra-5.1-20260106.susetw.x86_64.rpm installed on openSUSE Tw-Slowroll.

Shift-Render and Video-Wrench Compression list the previous vaapi and qsv hwaccel methods.

Shouldn't we also see a base Vulkan tag here to start experimenting with presets?

> >> hevc_vaapi_8b420.mp4 >> >>       mp4 hevc_vaapi >>       cin_hw_dev=vaapi >>       cin_pix_fmt=nv12 >>       profile=main >>       # global_quality=22 >> >> >> hevc_vaapi_10b420.mp4 >> >>       mp4 hevc_vaapi >>       cin_hw_dev=vaapi >>       cin_pix_fmt=p010le >>       profile=main10 >>       # global_quality=22 >> >> >> hevc_vaapi_10b422.mp4 >> >>       mp4 hevc_vaapi >>       cin_hw_dev=vaapi >>       cin_pix_fmt=y210le >>       profile=rext >>       # global_quality=22 >> >> >> Terje J. Hanssen >> >> >> _______________________________________________ >> Cin mailing list -- [email protected] >> To unsubscribe send an email to [email protected]

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

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

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

Den 11.01.2026 23:56, skrev Andrew Randrianasulu:

On Sun, Jan 11, 2026 at 11:42 PM Terje J. Hanssen <[email protected]> wrote:

...

Den 11.01.2026 18:33, skrev Andrew Randrianasulu:

вс, 11 янв. 2026 г., 20:21 Terje J. Hanssen via Cin <[email protected]>:

...

Den 10.01.2026 21:57, skrev Phyllis Smith via Cin:

No vulkan render formats have been added. I do not have the hardware to test either (I really need a new kick-axx computer!) But because you have Andrey's package installed, maybe you test yourself (only not sure about the first line):

1. cd <wherever the package is installed>/bin/ffmpeg/video 2. cp hevc_vaapi_10b420.mp4 hevc_vulkan_10b420.mp4 3. edit hevc_vulkan_10b420.mp4 and change the first line from "mp4 hevc_vaapi" to "mp4 hevc_vulkan". 4. restart CinGGG

cd /usr/share/cin/ffmpeg/video

Copied and edited the preset

cat h264_vulkan_8b420.mp4

mp4 h264_vulkan # Requires specific GPU hardware encoding capability # as well as required software implementation. cin_hw_dev=vulkan cin_pix_fmt=nv12 profile=high # global_quality=22

but using this cause a Cinelerra error and no rendering:

int FFMPEG::open_encoder(const char*, const char*): Cant find codec h264_vulkan:/Videoklipp/VULKAN/hdv1080i50_cin_h264_vulkan_8b420.mp4

--------

Is Vulkan enabled via Cingg's built-in ffmpeg, or is there other reasons it won't work?

I think if you use cingg with internal ffmpeg libs you should pass newly-added --enable-vulkan configure switch? If vulkan sdk is new enough this should tell ffmpeg to enable various encoders and decoders based on Vulkan video. I think I tied libshaderc (shader compiler) to libplacebo enable, while it theory it can have its own switch. but only Vulkan-shaders based decoders and encoders depend on that (compared to driving dedicated hw blocks via Vulkan) so right now at ffmpeg-8.0 I think this is not really limiting. You can try to install libplacebo/libzimage devel libs, enable all three switches and see if it compiles/runs fine?

Rather than recompiling the internal ffmpeg, I wonder if also the internal ffmpeg may need some export variables for vulkan executed somewhere first to work? As discussed in earlier posts, the system ffmpeg with vulkan decoding/encoding require the following:

Well, this might be true, and easy to test

Set them before starting cin, and try again!

WE do not set anything like this internally ...

Tested again with the export varibles exported first. Unhappily, what works with my system ffmpeg vulkan decoding&encoding, seemingly doesn't work at this time for Cinelerra/internal ffmpeg. Anyone else getting Cin vulkan video decoding/encoding to work on Intel or other platforms?

...

default no output from vulkaninfo | grep VK_KHR_video

after export ANV_DEBUG="video-decode,video-encode"

vulkaninfo | grep VK_KHR_video VK_KHR_video_decode_av1 : extension revision 1 VK_KHR_video_decode_h264 : extension revision 9 VK_KHR_video_decode_h265 : extension revision 8 VK_KHR_video_decode_queue : extension revision 8 VK_KHR_video_decode_vp9 : extension revision 1 VK_KHR_video_encode_h264 : extension revision 14 VK_KHR_video_encode_h265 : extension revision 14 VK_KHR_video_encode_queue : extension revision 12 VK_KHR_video_maintenance1 : extension revision 1 VK_KHR_video_maintenance2 : extension revision 1 VK_KHR_video_queue

...

-----

In comparison my system ffmpeg-8 works on my machines with Intel iGPU UHD 620 and also HD 530 (but unhappily not yet on the most powerful Arch A750 (DG2) for unknown reasons).

ffmpeg -hide_banner -init_hw_device "vulkan=vk:0" -hwaccel vulkan -hwaccel_output_format vulkan -i hdv1080i50.m2t -vf "format=nv12,hwupload" -c:v h264_vulkan -y hdv1080i50_h264_vulkan_nv12_vk0.mp4 ..... frame= 123 fps=0.0 q=-0.0 Lsize= 16876KiB time=00:00:05.30 bitrate=26065.5kbits/s speed=12.6x elapsed=0:00:00.41 [aac @ 0x56359d824b40] Qavg: 217.60

---------

Adding "-global_quality 25" (rather than -profile) reduce the file size to 1/5

du -sh hdv1080* 20M hdv1080i50_h264_main_vulkan_nv12_vk0.mp4 10M hdv1080i50_h264_vaapi_nv12.mp4 3.4M hdv1080i50_h264_vulkan_gq25_nv12_vk0.mp4 17M hdv1080i50_h264_vulkan_nv12.mp4 17M hdv1080i50_h264_vulkan_nv12_vk0.mp4 16M hdv1080i50.m2t

On Sat, Jan 10, 2026 at 12:50 PM Terje J. Hanssen via Cin <[email protected]> wrote:

...

Den 02.12.2025 16:39, skrev Andrew Randrianasulu:

...

On Tue, Dec 2, 2025 at 6:20 PM Terje J. Hanssen via Cin <[email protected]> wrote:

...

Late 2024 onevpl support was added for the buildsystem with various presets using cin_hw_dev=vaapi.

Maybe I simplify too much, but is it possible that current CinGG-20251121-x86_64.AppImage with ffmpeg-8 is ready to test vulkan the same way, just by replacing "vaapi" with "vulkan" in the presets? I have no hardware to test, but I think if/when latest patches by me lands and it will be confirmed new appimage copies vulkan loader and it works on different systems ...

Then you can play with new Vulkan encoding presets :)

Moment, about to send second patch I have the latest CinGG-20251231-x86_64.AppImage and cinelerra-5.1-20260106.susetw.x86_64.rpm installed on openSUSE Tw-Slowroll.

Shift-Render and Video-Wrench Compression list the previous vaapi and qsv hwaccel methods.

Shouldn't we also see a base Vulkan tag here to start experimenting with presets?

...

...

hevc_vaapi_8b420.mp4

mp4 hevc_vaapi cin_hw_dev=vaapi cin_pix_fmt=nv12 profile=main # global_quality=22

hevc_vaapi_10b420.mp4

mp4 hevc_vaapi cin_hw_dev=vaapi cin_pix_fmt=p010le profile=main10 # global_quality=22

hevc_vaapi_10b422.mp4

mp4 hevc_vaapi cin_hw_dev=vaapi cin_pix_fmt=y210le profile=rext # global_quality=22

Terje J. Hanssen

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

---

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

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

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