Support SCORE for prioritization of specific variants within a playlist
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- typescript
- Domain
- audio-video-rtc, frontend
Research direction
Start by tracing HLS.js's variant-selection path and the existing SCORE arbitration described in the issue. Define how score tiers interact with playlist order, unplayable variants, and stall risk; done means preferred playable variants are selected consistently across the requested cases.
Written by the indexing model from the issue text.
Description
Is your feature request related to a problem? Please describe.
Currently, HLS.js only uses SCORE for arbitration when no factors other than playlist order remain in selection. This is incorrect.
Describe the solution you'd like
Always pick a variant from those with the highest SCORE, except those that are unplayable or would degrade playback (stall).
The best way to score variants is in tiers. Give multiple bitrate variants in an adaptation set (with the same codecs) the same score. The "better" or more efficient sets should be assigned the highest score. This will force the client to select the preferred adaptation set according to available resources. Unsupported variants or variants that cannot be played without stalling should not be chosen, regardless of SCORE.
Additional context
No response
- Dominant language
- TypeScript
- Stars
- 16.9k
- Forks
- 2.8k
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 27
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.
More from video-dev/hls.js
-
Bug metadata Need sample stream Needs Triage
Difficulty 3/5 1-2 days Newbie friendliness 74/100
-
Bug Need info Needs Triage
Difficulty 5/5 Over a week Newbie friendliness 38/100
-
Difficulty 3/5 1-2 days Newbie friendliness 76/100
-
cannot reproduce Need info Question
Difficulty 4/5 3-5 days Newbie friendliness 45/100
-
Bug Needs Triage
Difficulty 4/5 3-5 days Newbie friendliness 55/100
All issues in video-dev/hls.js
Similar issues
-
clawsweeper:fix-shape-clear clawsweeper:queueable-fix clawsweeper:source-repro impact:ux-friction issue-rating: 🦞 diamond lobster no-stale P3
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
community first-timers-only good first issue hacktoberfest help wanted low hanging fruit up-for-grabs
Difficulty 1/5 Under an hour Newbie friendliness 76/100
-
code-quality refactoring
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
github/gh-aw-firewall#8816 ·
-
integration:quickjs org:external priority:backlog topic:code-interpreter topic:middleware type:feature
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
langchain-ai/deepagents#6450 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
vercel/react-tweet#225 ·