tiny-pilot / tiny-pilot/tinypilot
Revise language around bit rate for H.264 settings
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 3.5k
- Forks
- 291
- PR merge metrics
- No merged PRs in 30d
Description
I was speaking to a customer yesterday, and they mentioned that our usage of the term "Bit Rate" confused them:
Revisiting the language, it is confusing to a person who's not familiar with the term. They wouldn't have a good intuition about whether increasing or decreasing the bit rate would reduce latency/quality.
Should we replace it with a more intuitive term?
One thought I had was to replace it with "Quality" so that we're consistent between MJPEG and H.264. We'd have to come up with some formula for converting a quality percentage to a bitrate. And it wouldn't be a simple linear transformation because we'd probably say 5 Mbps is equivalent to 80%, but 6.25 Mbps wouldn't be 100%.
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.
Research direction
Start by locating the H.264 and MJPEG settings UI and reviewing how their current labels are presented. The issue does not name files or tests; done would require agreeing on clearer terminology and defining a conversion approach that preserves the intended quality and latency behavior.
Written by the indexing model from the issue text.
Assessment
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100