HandBrake / HandBrake/HandBrake
'Range: Seconds' enhancement request
Open
Nobody has claimed this yet.
Enhancement
- Dominant language
- C
- Stars
- 24.4k
- Forks
- 1.7k
- Avg merge
- 5d 1h
- Merged PRs (30d)
- 8
Description
Description of the feature or enhancement you'd like to see in HandBrake:
In order to do exact trimming, would you expand PTS selection (i.e. 'Range: Seconds') from hh:mm:ss to hh:mm:ss.sss? Alternatively, trimming to exact frame number, N=0,1,2..., would be very welcome and could be used to bypass potential PTS errors.
What version of HandBrake are you currently running (e.g., 1.3.0)?
1.3.1 (2020010400)
What operating system and version are you running (e.g., Ubuntu 19.10, macOS 10.15 Catalina, Windows 10 1909)?
Windows 10-1803
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 locating the HandBrake interface entry for “Range: Seconds” and trace how its PTS selection and trimming values are handled. The work is done when the range accepts hh:mm:ss.sss or exact frame numbers and trimming remains accurate around potential PTS errors.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- desktop
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100