Quality select does not display resolution but only bitrate #6638

New Issue

OVERLORD · 2026-02-07T03:55:23+03:00

OVERLORD commented

2026-02-07 03:55:23 +03:00

Originally created by @vaderkos on GitHub (Jan 7, 2025).

This issue respects the following points:

This is a bug, not a question or a configuration issue; Please visit our forum or chat rooms first to troubleshoot with volunteers, before creating a report. The links can be found here.
This issue is not already reported on GitHub (I've searched it).
I'm using an up to date version of Jellyfin Server stable, unstable or master; We generally do not support previous older versions. If possible, please update to the latest version before opening an issue.
I agree to follow Jellyfin's Code of Conduct.
This report addresses only a single issue; If you encounter multiple issues, kindly create separate reports for each one.

Description of the bug

I've used to see resolution in quality select. Is this a bug or intentional?

Reproduction steps

Sign in into Jellyfin
Play any movie
Click on quality select
No resolution information only bitrate

What is the current bug behavior?

No resolution information in quality select only bitrate

What is the expected correct behavior?

Resolution is displayed near bitrate in quality select.

Jellyfin Server version

10.10.0+

Specify commit id

No response

Specify unstable release number

No response

Specify version number

10.10.3

Specify the build version

10.10.3

Environment

- OS: Truenas Scale 
- Linux Kernel: 
- Virtualization:
- Clients: LG TV client, firefox, and chrome
- Browser:
- FFmpeg Version:
- Playback Method:
- Hardware Acceleration:
- GPU Model: 
- Plugins:
- Reverse Proxy:
- Base URL:
- Networking:
- Storage:

Jellyfin logs

FFmpeg logs

Client / Browser logs

No response

Relevant screenshots or videos

No response

Additional information

No response

Originally created by @vaderkos on GitHub (Jan 7, 2025). ### This issue respects the following points: - [x] This is a **bug**, not a question or a configuration issue; Please visit our forum or chat rooms first to troubleshoot with volunteers, before creating a report. The links can be found [here](https://jellyfin.org/contact/). - [x] This issue is **not** already reported on [GitHub](https://github.com/jellyfin/jellyfin/issues?q=is%3Aopen+is%3Aissue) _(I've searched it)_. - [x] I'm using an up to date version of Jellyfin Server stable, unstable or master; We generally do not support previous older versions. If possible, please update to the latest version before opening an issue. - [x] I agree to follow Jellyfin's [Code of Conduct](https://jellyfin.org/docs/general/community-standards.html#code-of-conduct). - [x] This report addresses only a single issue; If you encounter multiple issues, kindly create separate reports for each one. ### Description of the bug I've used to see resolution in quality select. Is this a bug or intentional? ![Image](https://github.com/user-attachments/assets/341f0d20-c9e8-4db9-87fa-aa3ddc86370a) ### Reproduction steps 1. Sign in into Jellyfin 2. Play any movie 3. Click on quality select 4. No resolution information only bitrate ### What is the current _bug_ behavior? No resolution information in quality select only bitrate ### What is the expected _correct_ behavior? Resolution is displayed near bitrate in quality select. ### Jellyfin Server version 10.10.0+ ### Specify commit id _No response_ ### Specify unstable release number _No response_ ### Specify version number 10.10.3 ### Specify the build version 10.10.3 ### Environment ```markdown - OS: Truenas Scale - Linux Kernel: - Virtualization: - Clients: LG TV client, firefox, and chrome - Browser: - FFmpeg Version: - Playback Method: - Hardware Acceleration: - GPU Model: - Plugins: - Reverse Proxy: - Base URL: - Networking: - Storage: ``` ### Jellyfin logs ```shell ? ``` ### FFmpeg logs ```shell ``` ### Client / Browser logs _No response_ ### Relevant screenshots or videos _No response_ ### Additional information _No response_

OVERLORD closed this issue

2026-02-07 03:55:24 +03:00

OVERLORD commented

2026-02-07 03:55:25 +03:00

@gnattu commented on GitHub (Jan 7, 2025):

It’s intentional because the previous resolution text was nonsensical, incorrect, and misleading. That option was a bitrate limitation from a long time ago, and the actual output resolution is determined by the server based on various factors, rather than being hardcoded to a specific bitrate.

@gnattu commented on GitHub (Jan 7, 2025): It’s intentional because the previous resolution text was nonsensical, incorrect, and misleading. That option was a bitrate limitation from a long time ago, and the actual output resolution is determined by the server based on various factors, rather than being hardcoded to a specific bitrate.

OVERLORD referenced this issue

2026-02-07 06:31:45 +03:00

[PR #6639] [MERGED] Add mp4 track title fallback #11062

OVERLORD referenced this issue

2026-02-07 06:31:53 +03:00

[PR #6646] [MERGED] Add test data and unit test for mp4 metadata probe #11070

Sign in to join this conversation.