livepeer / livepeer/task-runner
Handle input asset `start_time` on transcode and prepare
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 3
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
When processing an asset through broadcasters, we demux the segments and transcode them independently. We then create an HLS playlist with all the output segments or a file with no metadata coming from the original file.
This causes things like start_time to be ignored, which can make a video have off-sync audio issues. This is my hypothesis based on the little I know and investigated about these files and behavior.
This might also be fixed by #18 at least for the transcode task. We might still need to do something for HLS playlists though, like for example using the new clipping feature https://github.com/livepeer/go-livepeer/pull/2280 on the works!
Contributor guide
No contributing guide indexed for this repository
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 tracing how broadcasters handle transcode tasks and assemble HLS playlists, then compare the behavior described here with issue #18 and the referenced clipping pull request. Done means confirming how input asset start_time and other original timing metadata are handled so transcoded output and HLS playlists avoid the reported audio-sync problem.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- audio-video-rtc, backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100