Show helpful error message when "No capable devices found" #3596

Closed
opened 2025-12-21 22:26:50 +01:00 by backuprepo · 5 comments
Owner

Originally created by @Germs2004 on GitHub (Feb 9, 2022).

Please describe your bug

When transcoding is attempted and ffmpeg outputs the error "No capable devices found," that error gets written to a log file and the Jellyfin web client only shows a generic error to the user. That makes it difficult for the user to identify the cause of the problem unless they happen across that log file and understand it. Please change Jellyfin to detect that error output and display a more helpful error message.

Suggested new error message:

"This media cannot be played right now because the server's hardware acceleration device is not available. The server administrator likely needs to choose a different hardware acceleration device in the Jellyfin settings."

Jellyfin Version

10.7.7

if other:

No response

Environment

- OS: Windows 10
- Virtualization: none
- Clients: Browser
- Browser: Brave, Chrome, Edge
- FFmpeg Version: n4.3.2-Jellyfin
- Hardware Acceleration: nvenc
- Reverse Proxy: no

Jellyfin logs

No response

FFmpeg logs

Stream mapping:
  Stream #0:0 -> #0:0 (hevc (native) -> h264 (h264_nvenc))
  Stream #0:1 -> #0:1 (aac (native) -> aac (native))
Press [q] to stop, [?] for help
[h264_nvenc @ 000001f3783d8a00] No capable devices found
Error initializing output stream 0:0 -- Error while opening encoder for output stream #0:0 - maybe incorrect parameters such as bit_rate, rate, width or height
[aac @ 000001f3783be540] Qavg: 64087.523
[aac @ 000001f3783be540] 2 frames left in the queue on closing
Conversion failed!

Please attach any browser or client logs here

No response

Please attach any screenshots here

No response

Code of Conduct

  • I agree to follow this project's Code of Conduct
Originally created by @Germs2004 on GitHub (Feb 9, 2022). ### Please describe your bug When transcoding is attempted and ffmpeg outputs the error "No capable devices found," that error gets written to a log file and the Jellyfin web client only shows a generic error to the user. That makes it difficult for the user to identify the cause of the problem unless they happen across that log file and understand it. Please change Jellyfin to detect that error output and display a more helpful error message. Suggested new error message: "This media cannot be played right now because the server's hardware acceleration device is not available. The server administrator likely needs to choose a different hardware acceleration device in the Jellyfin settings." ### Jellyfin Version 10.7.7 ### if other: _No response_ ### Environment ```markdown - OS: Windows 10 - Virtualization: none - Clients: Browser - Browser: Brave, Chrome, Edge - FFmpeg Version: n4.3.2-Jellyfin - Hardware Acceleration: nvenc - Reverse Proxy: no ``` ### Jellyfin logs _No response_ ### FFmpeg logs ```shell Stream mapping: Stream #0:0 -> #0:0 (hevc (native) -> h264 (h264_nvenc)) Stream #0:1 -> #0:1 (aac (native) -> aac (native)) Press [q] to stop, [?] for help [h264_nvenc @ 000001f3783d8a00] No capable devices found Error initializing output stream 0:0 -- Error while opening encoder for output stream #0:0 - maybe incorrect parameters such as bit_rate, rate, width or height [aac @ 000001f3783be540] Qavg: 64087.523 [aac @ 000001f3783be540] 2 frames left in the queue on closing Conversion failed! ``` ### 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
backuprepo 2025-12-21 22:26:50 +01:00
  • closed this issue
  • added the
    feature
    label
Author
Owner

@sourpatched commented on GitHub (Feb 10, 2022):

Is it possible for Jellyfin to have a "health Check" when the transecode settings are saved. This would include searching the server for the devices and letting admin know if something is missing.

@sourpatched commented on GitHub (Feb 10, 2022): Is it possible for Jellyfin to have a "health Check" when the transecode settings are saved. This would include searching the server for the devices and letting admin know if something is missing.
Author
Owner

@Germs2004 commented on GitHub (Feb 10, 2022):

Is it possible for Jellyfin to have a "health Check" when the transecode settings are saved. This would include searching the server for the devices and letting admin know if something is missing.

That's a good idea too - that settings page would be easier if it could hide the options that aren't valid, or at least warn the admin when they click save if they have selected a device that isn't detected in that system.

@Germs2004 commented on GitHub (Feb 10, 2022): > Is it possible for Jellyfin to have a "health Check" when the transecode settings are saved. This would include searching the server for the devices and letting admin know if something is missing. That's a good idea too - that settings page would be easier if it could hide the options that aren't valid, or at least warn the admin when they click save if they have selected a device that isn't detected in that system.
Author
Owner

@sourpatched commented on GitHub (Feb 13, 2022):

And on the dashboard page within the server info have "hardware acceleration: Active (in green)"

@sourpatched commented on GitHub (Feb 13, 2022): And on the dashboard page within the server info have "hardware acceleration: Active (in green)"
Author
Owner

@nyanmisaka commented on GitHub (Jun 17, 2022):

[h264_nvenc @ 000001f3783d8a00] No capable devices found
It means your NVIDIA GPU doesn’t support NVENC.

@nyanmisaka commented on GitHub (Jun 17, 2022): `[h264_nvenc @ 000001f3783d8a00] No capable devices found` It means your NVIDIA GPU doesn’t support NVENC.
Author
Owner

@Germs2004 commented on GitHub (Jul 13, 2022):

It means your NVIDIA GPU doesn’t support NVENC.

Yes, I figured that out after spending some time troubleshooting. The point of this issue was to suggest showing that helpful information right in the web GUI where everyone will see it, instead of expecting users to hunt down a log file, locate that line amongst many, and understand it.

@Germs2004 commented on GitHub (Jul 13, 2022): > It means your NVIDIA GPU doesn’t support NVENC. Yes, I figured that out after spending some time troubleshooting. The point of this issue was to suggest showing that helpful information right in the web GUI where everyone will see it, instead of expecting users to hunt down a log file, locate that line amongst many, and understand it.
Sign in to join this conversation.
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#3596
No description provided.