SUMMARY Issue when i was editing STEPS TO REPRODUCE 1. i drop the filter "grayworld" over video on the timeline 2. Kdenlive closed suddenly 3. i can´t open my save project file again, because Kdenlive closes when loading the project, it´s the same when appear the message to recover file :( OBSERVED RESULT new projects have not problem (no grayworld filter used) EXPECTED RESULT stressed :( SOFTWARE/OS VERSIONS Windows: 10 22h2 (compilation SO 19045.5011) Qt Version: 6.8.0 (compilado con 6.8.0) ADDITIONAL INFORMATION I lost my work
Created attachment 175929 [details] crash_grayworld Thank you for reporting. I can confirm the crash. Attached the crash report. This seems to be either an FFMPEG or an MLT bug.
Please try to reopen the project. Or use a backup: Project -> Open Backup File.
Created attachment 175934 [details] attachment-917621-0.html Gracias por la respuesta, actualicé a la última versión (24.08.3) y todo funcionó bien, pero ya no usaré ese filtro. Gracias por responder. Saludos El lun, 18 nov 2024 a las 14:40, emohr (<bugzilla_noreply@kde.org>) escribió: > https://bugs.kde.org/show_bug.cgi?id=496281 > > emohr <fritzibaby@gmx.net> changed: > > What |Removed |Added > > ---------------------------------------------------------------------------- > Severity|critical |crash > > --- Comment #2 from emohr <fritzibaby@gmx.net> --- > Please try to reopen the project. Or use a backup: Project -> Open Backup > File. > > -- > You are receiving this mail because: > You reported the bug.
I can't recreate this on Kdenlive: 25.12.1 MLT: 7.36.1 FFmpeg KDE Frameworks: 6.21.0 Qt: Using 6.10.1 and built against 6.10.1 Manjaro Linux (Wayland) Build ABI: x86_64-little_endian-lp64 Kernel: linux 6.6.119-1-MANJARO
Opened forum thread: https://discuss.kde.org/t/kdenlive-bugzilla-bug-issue-with-grayworld-filter-needing-more-testers-to-reproduce/43836
>> Hmm, I just finished the test script for this effect, and using the 25.12.0 Flatpak on Pop!_OS works just fine. No crash. > Then close the bug as WORKSFORME. It’s 2 years old and was traced to dependencies we’ve updated multiple times. It can always be reopened if there later is more info about some continuing issue. From the forum thread.