Return frame count or pixel count for each segment from segmenter
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 283
- Forks
- 72
- Avg merge
- 27m
- Merged PRs (30d)
- 1
Description
The broadcaster may want to better estimate how much a certain segment will cost to encode, in order to avoid the possibility of under-payment.
While the resolution and duration of a segment is generally known, the frame rate of the input is not. This prevents the broadcaster from computing an estimate via w \* h \* duration \* fps .
To overcome this, the segmenter could be modified to also incorporate the number of frames in a segment, or a count of pixels. This could go into a custom M3U8 segment header, but that requires changes to ffmpeg. There may be better approaches.
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 locating the segmenter and reviewing how it currently exposes segment metadata. Determine whether frame count or pixel count is the agreed measure, and whether a custom M3U8 header or another interface should carry it. Done means the chosen metadata is returned for each segment and covered by appropriate tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- audio-video-rtc
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100