Bug 505348

Summary: proxy building stops and will not resume/re-proxy when switching project render settings upon prompt
Product: [Applications] kdenlive Reporter: kurolotusblossom
Component: Project Bin & ImportAssignee: Jean-Baptiste Mardelle <jb>
Status: REPORTED ---    
Severity: minor    
Priority: NOR    
Version First Reported In: 25.04.1   
Target Milestone: ---   
Platform: Microsoft Windows   
OS: Microsoft Windows   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:
Attachments: video of the issue

Description kurolotusblossom 2025-06-08 14:15:11 UTC
Created attachment 182101 [details]
video of the issue

***
If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org

If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports

Please remove this comment after reading and before submitting - thanks!
***

SUMMARY
building proxies for an imported file that is different dimesions/resolution/framerate than the default set in the KDENLIVE settings will halt if the project is swapped to the imported clip settings, and not resume rebuilding the new proxy.
overall not an major issue (i think). the problem can be averted by allowing the full proxy creation to finish and then switching to the new settings prompted by KDENLIVE

STEPS TO REPRODUCE
1. import clip with different settings
2. kdenlive begins building a proxy
3. swap to new settings during building of current proxy
4.proxy building is halted, and new settings are applied to project
5.kdenlive will not try to rebuild new proxies

OBSERVED RESULT
importing a 2k clip into kdenlive will prompt proxies to commence building.
changing the project settings upon prompt stops any proxy form being built automatically.

EXPECTED RESULT
auto-rebuild/recommence proxy at new settings

SOFTWARE/OS VERSIONS
Windows: 10 Pro | 19045.5854
intel i9-14900k

ADDITIONAL INFORMATION
VoD of the issue in question attached

again, this can be worked around by simply letting the proxy be built fully, and then swapping to the new project settings, at which new proxies will be built