starred/jellyfin

Fork 0

mirror of https://github.com/jellyfin/jellyfin.git synced 2026-01-23 23:20:51 +01:00

Setting too high of a bandwidth for ffmpeg trips up NVENC (and probably other hardware encoders) #803

New issue

Open

opened 2025-12-21 17:22:47 +01:00 by backuprepo · 6 comments

backuprepo commented

2025-12-21 17:22:47 +01:00

Owner

Originally created by @EraYaN on GitHub (Jul 22, 2019).

Describe the bug
Reference: https://www.reddit.com/r/jellyfin/comments/cgac40/jellyfin_wont_use_hardware_transcoding_on_some/eufpgp6 (and childs)

So when jellyfin sets a bandwidth too high for the encoder the encoder errors out.
So -b:v 329027765 is clearly to high for this hardware (GTX650)

To Reproduce

Run ffmpeg with a -b:v argument outside the acceptable ranges for the encoder.

Expected behavior
Jellyfin should cap these given a table of encoders and their max bitrates.

Logs
(See reddit post)

System (please complete the following information):

OS: Windows
Browser: All
Jellyfin Version: 10.3.6

Additional context
This will hold for quicksync/vaapi/omx and others too I presume. NVidia does not publish these limits it seems.

EDIT: My GTX1080Ti seems to top out at 144M for the bitrate. I sense reason in the original 140MBps number ;)

Originally created by @EraYaN on GitHub (Jul 22, 2019). **Describe the bug** Reference: https://www.reddit.com/r/jellyfin/comments/cgac40/jellyfin_wont_use_hardware_transcoding_on_some/eufpgp6 (and childs) So when jellyfin sets a bandwidth too high for the encoder the encoder errors out. So `-b:v 329027765` is clearly to high for this hardware (GTX650) **To Reproduce** 1. Run ffmpeg with a `-b:v` argument outside the acceptable ranges for the encoder. **Expected behavior** Jellyfin should cap these given a table of encoders and their max bitrates. **Logs** (See reddit post) **System (please complete the following information):** - OS: Windows - Browser: All - Jellyfin Version: 10.3.6 **Additional context** This will hold for quicksync/vaapi/omx and others too I presume. NVidia does not publish these limits it seems. EDIT: My GTX1080Ti seems to top out at 144M for the bitrate. I sense reason in the original 140MBps number ;)

backuprepo added the

labels 2025-12-21 17:22:47 +01:00

backuprepo commented

2025-12-21 17:22:50 +01:00

Author

Owner

@k1lln1n3 commented on GitHub (Jul 30, 2019):

Is this something we also see cumulatively? Like will multiple streams adding up to a high bitrate have the same behavior? I was going to submit a feature request for the ability to determine a limit of streams sent to hardware encoders. Wondering if it could be linked back to this as well.

@k1lln1n3 commented on GitHub (Jul 30, 2019): Is this something we also see cumulatively? Like will multiple streams adding up to a high bitrate have the same behavior? I was going to submit a feature request for the ability to determine a limit of streams sent to hardware encoders. Wondering if it could be linked back to this as well.

backuprepo commented

2025-12-21 17:22:52 +01:00

Author

Owner

@stale[bot] commented on GitHub (Oct 28, 2019):

Issues go stale after 90d of inactivity. Mark the issue as fresh by adding a comment or commit. Stale issues close after an additional 14d of inactivity. If this issue is safe to close now please do so. If you have any questions you can reach us on Matrix or Social Media.

@stale[bot] commented on GitHub (Oct 28, 2019): Issues go stale after 90d of inactivity. Mark the issue as fresh by adding a comment or commit. Stale issues close after an additional 14d of inactivity. If this issue is safe to close now please do so. If you have any questions you can reach us on [Matrix or Social Media](https://docs.jellyfin.org/general/getting-help.html).

backuprepo commented

2025-12-21 17:22:53 +01:00

Author

Owner

@EraYaN commented on GitHub (Oct 30, 2019):

bot go away

@EraYaN commented on GitHub (Oct 30, 2019): bot go away

backuprepo commented

2025-12-21 17:22:54 +01:00

Author

Owner

@sevenrats commented on GitHub (Oct 23, 2023):

@EraYaN @k1lln1n3 a test file that reproduces this error would make a huge difference in getting it resolved.

@sevenrats commented on GitHub (Oct 23, 2023): @EraYaN @k1lln1n3 a test file that reproduces this error would make a huge difference in getting it resolved.

backuprepo commented

2025-12-21 17:22:55 +01:00

Author

Owner

@EraYaN commented on GitHub (Oct 24, 2023):

Ooh this is file independent, it's just the maximum output bandwidth. You can set anything as the input frankly. I think modern NVENC caps out at like 1200Mbits or something? But older cards cap out much much lower (as described above) and it's depends on the chosen codec it seems. I'm not at my home PC to try it out but ffmpeg craps out immediately so getting the limits is not that hard if you have the hardware.

@EraYaN commented on GitHub (Oct 24, 2023): Ooh this is file independent, it's just the maximum output bandwidth. You can set anything as the input frankly. I think modern NVENC caps out at like 1200Mbits or something? But older cards cap out much much lower (as described above) and it's depends on the chosen codec it seems. I'm not at my home PC to try it out but ffmpeg craps out immediately so getting the limits is not that hard if you have the hardware.

backuprepo commented

2025-12-21 17:22:56 +01:00

Author

Owner

@k1lln1n3 commented on GitHub (Oct 24, 2023):

@EraYaN is correct. This was a collective amount of data thrown at the older 10 series cards. I believe I Was able to make it happen with 2 separate files I had at the time but I couldn't tell you what they were. I''m not even sure this is an issue anymore as that card is long gone.

@k1lln1n3 commented on GitHub (Oct 24, 2023): @EraYaN is correct. This was a collective amount of data thrown at the older 10 series cards. I believe I Was able to make it happen with 2 separate files I had at the time but I couldn't tell you what they were. I''m not even sure this is an issue anymore as that card is long gone.

backuprepo referenced this issue

2025-12-22 06:49:01 +01:00

[PR #803] [CLOSED] fail2ban jellyfin #8325

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: starred/jellyfin#803

No description provided.

Rows
Columns