-
-
Notifications
You must be signed in to change notification settings - Fork 519
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
'Auto' setting for max streaming bitrate not working as expected #2601
Comments
Yeah, Auto Bitrate is not working very well but 120MB/s does work correctly, you can find more info here: #1753 |
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. |
This issue hasn't been fixed, not even on the latest betas. |
This comment has been minimized.
This comment has been minimized.
Still waiting for a fix... |
Would it make sense to treat same-network connections differently, as in the web client? |
No, LAN detection is not reliable. Especially when the Jellyfin is containerized or a reverse proxy is used. At this moment we do not recommend using the "auto" bitrate and is is disabled by default. |
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. |
Just encountered this on Amazon fire stick 4K. |
This comment has been minimized.
This comment has been minimized.
This issue is fixed in #3372 for 0.17. |
Describe the bug
I had the
max streaming bitrate
setting in its default value ofauto
when I tried to play a 4K movie on my CCwGTV. When it played, I found it was being transcoded when it was capable of direct playing. In trying to figure out why this might have been, I switched theauto
setting to the maximum numerical value of120 Mbit/s
, and it didn't try to transcode anymore, and successfully direct played.My CCwGTV is connected via Gigabit Ethernet so none of my files should be getting transcoded because of a bandwidth limitation.
Since switching the
max streaming bitrate
to120 Mbit/s
resulted in the file direct playing, I have to assume something is wonky with theAuto
setting, or perhaps the detection of available bandwidth.Key log information:
PlayMethod=Transcode, TranscodeReason=ContainerBitrateExceedsLimit
Logs
With
Max streaming bitrate
set toAuto
:With
Max streaming bitrate
set to120 Mbit/s
:Application version
0.15.5
Where did you install the app from?
Google Play
Device information
CCwGTV
Android version
12
Jellyfin server version
10.8.9
The text was updated successfully, but these errors were encountered: