Bug 454464

Summary: Kdenlive 22.04.1 title bug and preview render error
Product: [Applications] kdenlive Reporter: Jeff <jeffhahnmedia>
Component: Video Effects & TransitionsAssignee: Vincent PINON <vpinon>
Status: RESOLVED FIXED    
Severity: normal CC: fritzibaby
Priority: NOR    
Version First Reported In: 22.04.1   
Target Milestone: ---   
Platform: Microsoft Windows   
OS: Microsoft Windows   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description Jeff 2022-05-27 06:55:09 UTC
SUMMARY

I opened a project file from the previous build of Kdenlive version 22.04.0 and opened it in 22.04.1. All title backgrounds that were transparent were black making my video track not viewable. This could not be fixed in the title editor. I had the effects Old film and Glitch0r applied to my text. When I removed the Old film effect the text background became transparent again. 

I kept receiving an error notification that my timeline render preview parameters could not be rendered.  The timeline was rendering and playback was fine regardless.

Rolling back to version 22.04.0 resolved all of the issues.

NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols.
See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***


STEPS TO REPRODUCE
1. Open Kdenlive 22.04.1 in Windows 10
2. Apply Glitch0r and Old Film to a title
3. 

OBSERVED RESULT

Stated in summary

EXPECTED RESULT

No Bug


SOFTWARE/OS VERSIONS
Windows: 10
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION

I love Kdenlive and hope this helps
Comment 1 Jeff 2022-05-29 02:21:08 UTC
I just installed the Daily Experimental build Kdenlive_Nightly_mingw64 #1140 - Windows -May 28, 2022 6:04:46 AM	
This resolved all of the issues I had with 22.04.1. You guys work fast!!! Text and render bugs resolved.
Comment 2 emohr 2022-07-20 11:43:08 UTC
Thank you for the feedback and contribution. Glad to hear it works. 

I close this bug. If it still appears in the latest version, please feel free to re-open it and update the affected version number.