Bug 352409 - SUGGESTION: Add markers at video gaps
Summary: SUGGESTION: Add markers at video gaps
Status: CONFIRMED
Alias: None
Product: kdenlive
Classification: Applications
Component: User Interface (show other bugs)
Version: unspecified
Platform: Debian testing Linux
: NOR wishlist
Target Milestone: ---
Assignee: Jean-Baptiste Mardelle
URL:
Keywords: junior-jobs
Depends on:
Blocks:
 
Reported: 2015-09-07 23:09 UTC by Sarah Sharp
Modified: 2021-03-06 15:08 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:
snd.noise: Brainstorm+
snd.noise: low_hanging+
snd.noise: Usability+


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Sarah Sharp 2015-09-07 23:09:35 UTC
Once I have my video editing mostly done, with separate audio and video tracks, I have to go through the tedious process of carefully looking for any frame gaps between video clips. Kdenlive obviously has the information about clip start and length, it has enough information to detect whether clips in the visible video tracks have gaps between them.

What I would like is a menu option to have kdenlive set a guide at the start of every gap between video clips, so that I can eliminate them all, while still keeping the audio and video clips in sync.  Then I could jump to each guide and fix them.  That would save me 15 minutes scrolling through zoomed in at the frame level.

Reproducible: Always

Steps to Reproduce:
I'm running kdenlive 15.04.03, checked out from the git commit b72f6b16b1dbaf8989d7519b67ae6ef63047b50c
Comment 1 Jean-Baptiste Mardelle 2015-09-11 18:59:51 UTC
Thanks for your report, I like the idea. Maybe in the workflow, just before rendering we could have a button to "Check the project" that could do things like check for blank spaces in the project, check if transitions are correctly aligned with clips and any other automated tests that might be useful.
Comment 2 Wegwerf 2016-10-18 17:48:36 UTC
Updated the report title to better describe the bug.
Comment 3 Wegwerf 2016-10-18 17:52:00 UTC
Argh. The bug reporting system is again mixing comments into the wrong reports!