[Issue]: Playback Quality setting bitrate to start from the file bitrate instead of 60 Mbps

[CarbonV]

Please describe your bug

Currently the playback quality displays 60 Mbps as the Max bitrate, it would be nice if it could display the actual file bitrate as the max bitrate with the options going down starting from the max bitrate.

Not 100% sure if this would be a feature or is an Issue but it currently creates a lot of confusion for my users if they are playing direct or not and at what bitrate they are currently playing.

Jellyfin Version

10.7.7

if other:

No response

Environment

- OS: Ubuntu
- Virtualization: /
- Clients: Browser and Android
- Browser: Brave
- Playback Method: Direct Play
- Hardware Acceleration: VAAPI
- Reverse Proxy: Synology
- Storage: Local

Jellyfin logs

No response

FFmpeg logs

No response

Please attach any browser or client logs here

No response

Please attach any screenshots here

No response

Code of Conduct

• [X] I agree to follow this project's Code of Conduct

[CarbonV]

Just as a little add to this, it would maybe be even nicer to see the current transcode or DirectPlay for audio and video displayed somewhere in the gear icon. The same way that the Playback Reporting plugin reports it.

Example:

[dmitrylyzo]

https://github.com/jellyfin/jellyfin-web/issues/3708#issuecomment-1156082697 This list is more like "Max acceptable bitrate" (at least, this is how it currently works).

In addition, this bitrate is also applied to the next items.

Just as a little add to this, it would maybe be even nicer to see the current transcode or DirectPlay for audio and video displayed somewhere in the gear icon

This information can be found in the Playback Info dialog (can be called from the gear button).

[CarbonV]

Completely missed the Playback Info, my bad! I think I understand the max acceptable bitrate, maybe just showing what bitrate is currently being used right now, for example next to auto would add some more intuitiveness.

e.i.: Auto (7Mbps) <- in this example.

Don't know how much work that would be.

[jellyfin-bot]

This issue has gone 120 days without comment. To avoid abandoned issues, it will be closed in 21 days if there are no new comments.

If you're the original submitter of this issue, please comment confirming if this issue still affects you in the latest release or master branch, or close the issue if it has been fixed. If you're another user also affected by this bug, please comment confirming so. Either action will remove the stale label.

This bot exists to prevent issues from becoming stale and forgotten. Jellyfin is always moving forward, and bugs are often fixed as side effects of other changes. We therefore ask that bug report authors remain vigilant about their issues to ensure they are closed if fixed, or re-confirmed - perhaps with fresh logs or reproduction examples - regularly. If you have any questions you can reach us on Matrix or Social Media.