Kdenlive currently has timeline guides as well as clip markers. Markers belong to clips, but are only visible within this particular clip in the timeline. They are thus hard to spot in more complex projects. In contrast, timeline guides are clearly visible. However, they are fixed to a particular position in the timeline. As a project grows and clips gets inserted or deleted, scenes often move. Unfortunately, timeline guides never move to accommodate for scene edits, moves, et cetera. I would like to propose that timeline guides can be attached to a particular clip in the timeline. Typically, this would be the leading clip for a scene opening. This way, the a "clip'ed" guide would automatically move accordingly with the clip it is attached to as scenes move in the timeline. Such "smart" guides would be a great help in more complex projects with maybe five or ten "scenes". The guides would offer, well, guide and would always correctly indicate the beginning of a scene without having them to maintain manually in a project. Reproducible: Always
Just a doubt, would a workaround of changing the way Markers are displayed work? As in maybe a way to configure Markers to appear at the top of the timeline just like guides do. Just a thought... :)
Unfortunately, that would not help, as only timeline guides can be used to set the rendering section. In contrast, clip markers are producer-specific, but never timeline-specific. But I haven't yet a good idea how to attach timeline guides to a clip in order to move, UI wise. Anyway, this will need some code in the timeline managers for handling such "guides".
Rendering from guide to guide is possible in the meantime (21.04). In bigger projects it could be useful guides could be "attached" to a clip as an option and the guide could move with the "attached" clip.
Hi, and thank you for your patience. Could you please check whether your issue has been resolved with the latest version 24.12.0? A lot of things have changed since you asked for this feature. If that is the case, please set the status of the report to RESOLVED-FIXED. If the issue still exists, please set the status report to CONFIRMED and change the version number to 24.12.0 This report will automatically be set to RESOLVED after 30 days of inactivity.
🐛🧹 ⚠️ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME. For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging. Thank you for helping us make KDE software even better for everyone!
🐛🧹 This bug has been in NEEDSINFO status with no change for at least 30 days. Closing as RESOLVED WORKSFORME.