mltframework / mltframework/shotcut
Video mode Automatic sometimes does not act as documented
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 15.2k
- Forks
- 1.5k
- Avg merge
- 11h 27m
- Merged PRs (30d)
- 5
Description
OS and Version (please complete the following information):
- Operating System: Debian Trixie
- Shotcut Version:
shotcut-linux-x86_64-26.8.1.txzfrom the project download page
Describe the bug
Video mode Automatic sometimes does not act as documented: In contrast to what it says, it sometimes sets a frame rate that is different from the first video added.
Steps To Reproduce
- Start Shotcut
- Open a New Project, say Project name
automatic_framerate - Select Video mode Automatic, which says "the resolution and frame rate are based on the first file you add to your project".
- Quit Shotcut.
- Restart Shotcut.
- Open the previously created project,
automatic_framerate. - The title says:
automatic_framerate.mlt... 25.00fps. - Add, as the first video, any video with 60fps.
- The project unexpectedly remains at 25.00fps.
Expected behavior
The expected behaviour is that Shotcut does what it said: The frame rate is determined from the first video added, which is 60fps. Analogously for the resolution.
Can you reproduce this? Thank you a lot for Shotcut!
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
Reproduce the issue through New Project, Video mode Automatic, reopening the saved project, and adding a first 60fps video. Trace the project initialization and first-video handling entry points, then verify that reopening no longer locks the project to 25.00fps and that resolution still follows the first video.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- audio-video-rtc, desktop
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100