The Kdenlive 26.04 Release Candidate is ready for testing. Many bug fixes and workflow adjustments should make your editing sessions nicer. It is also worth noting that we had quite a few new contributors helping our small team on this, so thanks to all those who helped us!
Operating System: Fedora Linux 43
KDE Plasma Version: 6.6.3
KDE Frameworks Version: 6.24.0
Qt Version: 6.10.2
Kernel Version: 6.19.10-200.fc43.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 12 × AMD Ryzen 5 PRO 4650U with Radeon Graphics
Memory: 9 GB of RAM (7.6 GB usable)
Graphics Processor: AMD Radeon Graphics
I’m not sure if I should report RC-specific bugs on the bugtracker or here, but anyways, it appears that VAAPI rendering is broken. Using the default profile for VAAPI, the rendering crashes:
Rendering of /home/user/Videos/untitled.mp4 aborted, resulting video will probably be corrupted.
Error log (displayed in Rendering widget)
Rendering of /home/user/Videos/untitled.mp4 crashed
[VAAPI @ 0x7f51a02040c0] Failed to initialise VAAPI connection: -1 (unknown libva error).
[consumer avformat] Failed to initialize VA-API: -5
[h264_vaapi @ 0x7f51a0201740] A hardware frames reference is required to associate the encoding device.
[VAAPI @ 0x7f51a4011780] Failed to initialise VAAPI connection: -1 (unknown libva error).
[VAAPI @ 0x7f51a51bbd00] Failed to initialise VAAPI connection: -1 (unknown libva error).
Oh, I just realized that AppImage hardware acceleration isn’t implemented.
No, that’s an old bug, and I’ve just closed it now. Whatever your issue is it’s something else that will need investigating - and at first blush it seems to be either a Fedora thing, or deps missing from your system - because VAAPI H.264 at least works just fine for me in both 25.12.3 and this 26.04.0-rc appimage.
We had an issue that was resolved late last year with the build farm using a libva that was too old and incompatible with most modern distro releases, but that has been fixed too and this Should Be Working, and doesn’t seem to have regressed.
Have you ever had this working? If the answer isn’t obvious to you with what I’ve just said, maybe open a separate thread for this one here while we figure out what’s Special about your system.
(and this is probably the right place to initially triage any issues, we can move them to the tracker if/when they are confirmed if the fix isn’t obvious and applied immediately).
VAAPI works fine on Flatpak (25.12.2), and .rpm as well, but I just tested 25.12.3 AppImage, and I get the same error. I’ll open a separate thread when I get time.
The problem persists when trying to modify keyframe interpolation. Works fine in kdenlive-25.08.3-x86_64.AppImage
I’m getting an error when I do that. Where is the log generated? I’ll take a look and post if necessary.
Could it be because I’m using this and the previous version at the same time (installed in separate directories)?
You should have access right to ~\AppData\Roaming\kdenlive\transitions\previews. Check if this folder exists: windows+r enter AppData then navigate to the folder.
I’ll check where the log file is stored.
@GaryB If you are willing to help, on Windows you have to install dbgview. Then run dbgview when you do in Kdenlive the Generate Preview. Then you see in dbgview what output Kdenlive generates. Post that output here.
~\AppData\Roaming\kdenlive\transitions\previews exists, but it’s currently empty. I’ll check dbgview output in the morning.
You have to have Python installed otherwise the preview doesn’t build. In the meantime we are checking to have the previews pre-build and shipping directly with Kdenlive. So, no need for further testing. Thank you.
Was just home and about to take a look. Thanks for the update. I don’t have Python installed, so I guess that explains it. I’ll await your findings.
