By enabling libplacebo and using the 0012-Experimental-vulkan-encode.patch patch, I was able to render with a Vulkan preset for the first time. However, decoding with Vulkan still does not work for me.. The fact that ffv1_vulkan (with nv12) works but my other presets for hevc, av1, and h264 do not, does that mean I need to find the right pix_fmt for them? Furthermore, nv12 is not suitable for ffv1, which is generally an archiving codec and requires little or no color compression. ( https://trac.ffmpeg.org/ticket/11515). I tried changing the pixel format (from the render configuration window) of your preset from nv12 to: nv16; nv24, p010,p210,y210 and y416. But the result is the same as nv12. ffprobe indicates yuv420p for the various renders. Note: In ./configure, the “--enable-libplacebo” option does not work for me, but the “--with-libplacebo” option does. Note2: I tried the latest appimage made for Terje, even though I don't have Intel hardware, and rendering with Vulkan doesn't work for me.
чт, 12 февр. 2026 г., 17:26 Andrea paz via Cin <[email protected]>:
By enabling libplacebo and using the 0012-Experimental-vulkan-encode.patch patch, I was able to render with a Vulkan preset for the first time. However, decoding with Vulkan still does not work for me.. The fact that ffv1_vulkan (with nv12) works but my other presets for hevc, av1, and h264 do not, does that mean I need to find the right pix_fmt for them? Furthermore, nv12 is not suitable for ffv1, which is generally an archiving codec and requires little or no color compression. ( https://trac.ffmpeg.org/ticket/11515). I tried changing the pixel format (from the render configuration window)
No, sorry, you need to change it by editing preset itself .. :( Do other presets you created just fail to render, or crash everything? of your preset from nv12 to: nv16; nv24, p010,p210,y210 and y416. But the
result is the same as nv12. ffprobe indicates yuv420p for the various renders.
Note: In ./configure, the “--enable-libplacebo” option does not work for me, but the “--with-libplacebo” option does. Note2: I tried the latest appimage made for Terje, even though I don't have Intel hardware, and rendering with Vulkan doesn't work for me.
Crash or fail to render? Check with vulkaninfo that you have video encode extensions exposed .... _______________________________________________
Cin mailing list -- [email protected] To unsubscribe send an email to [email protected]
Do other presets you created just fail to render, or crash everything?
No crash, it's the same old error: A hardware frames reference is required to associate the encoding device. FFMPEG::open_encoder err: Invalid argument int FFMPEG::open_encoder(const char*, const char*): open failed hevc_vulkan:/home/paz/test_vulkan.mov The only difference between my presets and yours is the absence of cin_pix_fmt=nv12. I am inclined to think that the “hardware frame reference” is actually the pixel format, or at least that it is provided by it. With your preset in the “Pixels” field, you have the option of nv12 or vulkan; vulkan does not work and produces the usual error. In my presets, there is only the vulkan option, and in fact they do not work (usual error). Tomorrow I will try to create various presets with nv16,24 and also with p010,210,216 and y210,216,416. Then I will compile CinGG with these and see if they work. Simply changing the cin_pix_fmt=... entry in your preset does not work and it is still rendered with nv12 (default), as if you had not made any changes. I don't understand why; I thought our settings would override the default ones. Note2: I tried the latest appimage made for Terje, even though I don't have
Intel hardware, and rendering with Vulkan doesn't work for me.
Crash or fail to render?
No crash; same error.
I made some presets for Vulkan and got the following results: 1- av1_vulkan.mkv Device does not support encoding av1! (I think it's normal, my graphics card doesn't support AV1 encoding.) 2- h264_vulkan.mkv Works with cin_pix_fmt=nv12 (16,24) I tried it from the terminal with CinGG's ffmpeg and h264_vulkan, and it works. The fps from the terminal is twice as high as from CinGG. /path/to/cinelerra/..././ffmpeg -init_hw_device "vulkan=vk:0" -hwaccel vulkan -hwaccel_output_format vulkan -i big_buck_bunny_720p_16sec.mp4 -c:v h264_vulkan output_h264.mp4 3- hevc_vulkan It doesn't work! When set to nv12, it says that hevc_vulkan does not support nv12. When set to vulkan, I get the usual error: "A hardware frames reference is required to associate the encoding device." Using CinGG's ffmpeg from the terminal, rendering works. So the problem with the hevc_vulkan preset is figuring out which cin_pix_fmt it wants. PS: I made separate presets for ffv1_vulkan.mov with nv12,16, and 24. I was wondering if it was possible to have a single preset (yours) but allow the pixel format to be changed from the “pixels” window. PS2: Today I wanted to continue testing on vulkan, but CinGG no longer starts due to an Arch update with libplacebo going from version 7.351.0 to version 7.360.0. The error is as follows: /home/paz/cinelerra/cinelerra-5.1/bin/cin: error while loading shared libraries: libplacebo.so.351: cannot open shared object file: No such file or directory With a new build, CinGG is back up and running with the new version of libplacebo.
сб, 14 февр. 2026 г., 13:43 Andrea paz <[email protected]>:
I made some presets for Vulkan and got the following results:
1- av1_vulkan.mkv
Device does not support encoding av1! (I think it's normal, my graphics card doesn't support AV1 encoding.)
2- h264_vulkan.mkv
Works with cin_pix_fmt=nv12 (16,24)
I tried it from the terminal with CinGG's ffmpeg and h264_vulkan, and it works. The fps from the terminal is twice as high as from CinGG.
/path/to/cinelerra/..././ffmpeg -init_hw_device "vulkan=vk:0" -hwaccel vulkan -hwaccel_output_format vulkan -i big_buck_bunny_720p_16sec.mp4 -c:v h264_vulkan output_h264.mp4
3- hevc_vulkan
It doesn't work! When set to nv12, it says that hevc_vulkan does not support nv12. When set to vulkan, I get the usual error:
"A hardware frames reference is required to associate the encoding device."
Using CinGG's ffmpeg from the terminal, rendering works. So the problem with the hevc_vulkan preset is figuring out which cin_pix_fmt it wants.
from libavcodec/vulkan_encode.c
av_log(avctx, AV_LOG_VERBOSE, "Supported input formats:\n"); for (i = 0; i < nb_out_fmts; i++) av_log(avctx, AV_LOG_VERBOSE, " %i: %i\n", i, ret_info[i].format); so try to set loglevel=verbose in bin/ffmpeg/encode.opts and see what it outputs?
PS: I made separate presets for ffv1_vulkan.mov with nv12,16, and 24. I was wondering if it was possible to have a single preset (yours) but allow the pixel format to be changed from the “pixels” window.
Just setting pix_fmt in gui window *in additional* to pre-set by profile cin_pix_fmt does not work?
PS2: Today I wanted to continue testing on vulkan, but CinGG no longer starts due to an Arch update with libplacebo going from version 7.351.0 to version 7.360.0. The error is as follows:
/home/paz/cinelerra/cinelerra-5.1/bin/cin: error while loading shared libraries: libplacebo.so.351: cannot open shared object file: No such file or directory
With a new build, CinGG is back up and running with the new version of libplacebo.
On 2/14/26 11:43 AM, Andrea paz via Cin wrote:
I made some presets for Vulkan and got the following results:
1- av1_vulkan.mkv
Device does not support encoding av1! (I think it's normal, my graphics card doesn't support AV1 encoding.)
2- h264_vulkan.mkv
Works with cin_pix_fmt=nv12 (16,24)
I tried it from the terminal with CinGG's ffmpeg and h264_vulkan, and it works. The fps from the terminal is twice as high as from CinGG.
/path/to/cinelerra/..././ffmpeg -init_hw_device "vulkan=vk:0" -hwaccel vulkan -hwaccel_output_format vulkan -i big_buck_bunny_720p_16sec.mp4 -c:v h264_vulkan output_h264.mp4
What about the default file size and colors of the vulkan output file compared with the input?. In my case rendered with h264_vulkan.mp4 output, the red color was gone (grey-greenish) and the file size increased 47% compared with hdv.m2t input. By uncommenting and setting the global_quality=28 in the preset window, the file size was reduced to about 25% of the default output. Tried also Cingg Settings > Prefs > Appearance > Color: YUV color space BT709 (HD)/range MPEG which didn't repair the loss of red colors.
3- hevc_vulkan
It doesn't work! When set to nv12, it says that hevc_vulkan does not support nv12. When set to vulkan, I get the usual error:
"A hardware frames reference is required to associate the encoding device."
Using CinGG's ffmpeg from the terminal, rendering works. So the problem with the hevc_vulkan preset is figuring out which cin_pix_fmt it wants.
PS: I made separate presets for ffv1_vulkan.mov with nv12,16, and 24. I was wondering if it was possible to have a single preset (yours) but allow the pixel format to be changed from the “pixels” window.
PS2: Today I wanted to continue testing on vulkan, but CinGG no longer starts due to an Arch update with libplacebo going from version 7.351.0 to version 7.360.0. The error is as follows:
/home/paz/cinelerra/cinelerra-5.1/bin/cin: error while loading shared libraries: libplacebo.so.351: cannot open shared object file: No such file or directory
With a new build, CinGG is back up and running with the new version of libplacebo.
_______________________________________________ Cin mailing list -- [email protected] To unsubscribe send an email to [email protected]
On 2/16/26 4:03 PM, Andrea paz wrote:
What about the default file size and colors of the vulkan output file compared with the input?.
I append my test and my preset. I have not color problem.
Yeah, thanks. Your ffmpeg and ffprobe outputs confirms that the video+audio * input bitrate: 768 kb/s * output bitrate: 2175 kb/s (2176.9) * No rate control settings specified, using fixed QP = 18 As mentioned I tested with global_quality=28 and got much lower output bitrate (file size) And as Andrew mentioned, the color issue seems to be a bug in the ANV driver.
participants (3)
-
Andrea paz -
Andrew Randrianasulu -
Terje J. Hanssen