Bug 495897 - Make kdenlive XML more friendly to automatic generation
Summary: Make kdenlive XML more friendly to automatic generation
Status: REPORTED
Alias: None
Product: kdenlive
Classification: Applications
Component: Video Effects & Transitions (other bugs)
Version First Reported In: unspecified
Platform: Other Other
: NOR wishlist
Target Milestone: ---
Assignee: Jean-Baptiste Mardelle
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-11-06 22:49 UTC by jez9999
Modified: 2024-11-08 19:23 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description jez9999 2024-11-06 22:49:10 UTC
I’d like to suggest that a goal of kdenlive be that its XML should be at least somewhat friendly to automatic generation by other programs. I’m currently writing a program to auto-generate .kdenlive project files in order to automate the creation of some YouTube videos, and whilst I have been able to do it by and large, there are some issues that make it rather tricky:

- The recent addition of “kdenlive:control_uuid” properties all over the place; I don’t know what to set them to and if I omit them the project loading works, but gives me a message that the project was modified upon opening, which isn’t ideal.
- The “kdenlive:file_hash” on a sequence; I don’t know how this hash is generated, and whilst I can omit it and it seems to silently generate one, I wonder whether it’s really necessary.
- The fact that many timings seem to be slightly off. If I add a 5 second clip to a timeline with a 60FPS profile, many of the “out” attributes are actually set to 00:00:04.983. Not sure whether this is intentional or some kind of rounding bug.

I’m sure some people here will say that auto-generation of a .kdenlive project file is “not supported” but I guess I’m asking for it to be supported. Is it that unreasonable?