mltframework / mltframework/shotcut
Performance issue when moving clips in or among video tracks
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 15.2k
- Forks
- 1.5k
- Avg merge
- 11h 27m
- Merged PRs (30d)
- 5
Description
Shotcut - Windows 10 - presumably all versions
Steps to reproduce:
1.) Create a project with several video tracks and so many clips that moving one doesn't seem "instantaneous" - even on a very fast machine this is not more than a few hundred (the project from issue #1029 may serve as an example)
2.) Drag an arbitrary clip from the timeline within its track and WITHOUT ever leaving said track - this is your normal operation speed for reference
3.) Drag the same clip but to another track - operation takes around 100 times longer (much longer than select, Ctrl+C, position playhead, Ctrl+B, Del of the original clip would take), at least several seconds
4.) Surprisingly this also happens if you just briefly leave the orignal track while dragging, even when releasing the clip on its original track but at a different position - the operation takes a very long time
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the timeline drag steps in Shotcut, using a project with several tracks and many clips; issue #1029 is mentioned as a possible example. Compare moving within one track with briefly crossing into another, and consider the issue resolved when cross-track or cross-track-boundary moves no longer incur the reported large delay.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- desktop, performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100