Different bitrates when uploading 4K videos
- Dominant language
- TypeScript
- Stars
- 88
- Forks
- 37
- PR merge metrics
- No merged PRs in 30d
Description
**Describe the bug (required)** A clear and concise description of what the bug
is.
Not sure if this is a bug but:
When uploading assets with 4K there are different results with bitrate which allows some to playback at 4k and some get downgraded to 1440p.
Example:
AssetId: 9b1d171b-c259-4f3f-88d5-9919b02ab11f
Bitrate: 21814755
https://bitmovin.com/demos/stream-test?format=hls&manifest=https%3A%2F%2Flp-playback.com%2Fhls%2F9b1dlnebk6z44w4a%2Findex.m3u8
Shows QHD as the highest quality for playback
AssetId: a057efef-4f56-436c-982e-37f887502c44
Bitrate: 22547564
https://bitmovin.com/demos/stream-test?format=hls&manifest=https%3A%2F%2Flp-playback.com%2Fhls%2Fa057o7p38yczlce6%2Findex.m3u8
Shows 4K as the highest quality for playback
**Expected behavior (required)** A clear and concise description of what you
expected to happen.
Expect that 4K assets are able to be played back at 4K or it gets downgraded to 1440p consistently.
Contributor guide
Research direction
Start by comparing the HLS manifests and reported bitrates for asset IDs 9b1d171b-c259-4f3f-88d5-9919b02ab11f and a057efef-4f56-436c-982e-37f887502c44 using the linked playback examples. Trace the upload and processing path to determine why otherwise similar 4K assets expose different maximum qualities; done means 4K playback or consistent 1440p fallback.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- audio-video-rtc
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100