HandBrake / HandBrake/HandBrake

Start & End timestamps does not accurately populate when you go back to "Edit" a video from the Queue

Open
#6,316 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

LinuxUI
Dominant language
C
Stars
24.4k
Forks
1.7k
Avg merge
5d 1h
Merged PRs (30d)
8

Description

Problem Description

If you choose Seconds and set a Start and End timestamp for your encodes, going back to edit a previous job doesn't populate the timestamps correctly.

To reproduce:

  1. Pick any video.
  2. Choose "Seconds" in the Range dropdown.
  3. Set a start timestamp of 00:00:30.00 & end timestamp of 00:00:45.00.
  4. Click Add to Queue
  5. Set new start timestamp of 00:01:15.00 & end timestamp of 00:01:55.00.
  6. Click Add to Queue (probably need to change video title slightly to avoid the dupe name popup)
  7. Click "Queue" to view your job queue.
  8. Select the first job and click "Edit".

BUG: Instead of populating 00:00:30.00 to 00:00:45.00 (as per step 3), Handbrake shows 00:00:30.00 to 00:01:55.00 instead.

Activity Log, Crash Log or any other details
## Does Not Apply ##
What Operating System are you running?

Ubuntu 24.04

What version of HandBrake are you running?

20240717070229-c6546d3d9-master

Where did you download HandBrake from?

github

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the issue through the Queue and Edit flow using the timestamp values in the report, then trace how the selected queued job repopulates its start and end timestamps. Done means editing the first queued job restores 00:00:30.00 to 00:00:45.00 rather than using the second job's end time.

Written by the indexing model from the issue text.

Assessment

Tech stack
c
Domain
desktop
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.