+- Jellyfin Forum (https://forum.jellyfin.org)
+-- Forum: Support (https://forum.jellyfin.org/f-support)
+--- Forum: Troubleshooting (https://forum.jellyfin.org/f-troubleshooting)
+--- Thread: Cannot play 480p content on TV or mobile devices (/t-cannot-play-480p-content-on-tv-or-mobile-devices)
Pages:
1
2
RE: Cannot play 480p content on TV or mobile devices - Skellum - 2024-11-27
Pastebin added here: https://pastebin.com/FyCgf2UV
Don't judge me on the file, it's a request from my girl lol
I've got HD copies of these now so I may just replace them with that
RE: Cannot play 480p content on TV or mobile devices - TheDreadPirate - 2024-11-27
The Nvidia driver you have installed is too old.
Code:
[hevc_nvenc @ 000000e977e38ac0] Driver does not support the required nvenc API version. Required: 12.0 Found: 11.1
[hevc_nvenc @ 000000e977e38ac0] The minimum required Nvidia driver for nvenc is 522.25 or newerI checked Nvidia's website, you may be SOL. The newest driver they have "certified" for your OS (I selected Windows 8.1) is 475.
RE: Cannot play 480p content on TV or mobile devices - Skellum - 2024-11-27
I saw that, didn't realise where I could view the logs so thats really helpful, so if I upgrade the GPU to something more recent on this machine it will work right?
For now I can use VLC as a workaround on these devices, and I guess when viewing in my browser it is using my actual computers GPU rather than transcoding from the server? Is my understanding correct there?
RE: Cannot play 480p content on TV or mobile devices - TheDreadPirate - 2024-11-27
The problem isn't the GPU, which is perfectly fine. The problem is the OS. If you upgraded to Windows 10 or 11, or their server equivalent, you'd be able to get a sufficiently new driver. The 1070 and 1060 in my wife and kid's PCs still get updates on Windows 10.
RE: Cannot play 480p content on TV or mobile devices - Skellum - 2024-11-27
Ahh that's a shame, this system WILL NOT run Windows 10/11 or anything remotely resembling it (Tiny11 or any proxy builds).
I had Linux Mint running on it but switched to Server 2012 as trying to share disks via Linux was more difficult than it needs to be IMO.
I did find the CPU was maxed out initially until I enabled hardware acceleration NVENC so I presume this IS working for most streams?
Other than this small snag the server performs impeccably and barely uses any CPU even with multiple streams being accessed at once, I imagine updating the files to 1080p will probably fix the playback issues.
I can continue to use VLC as a workaround should the file not be available in full HD.
RE: Cannot play 480p content on TV or mobile devices - TheDreadPirate - 2024-11-27
The issue with the failed videos is that most devices don't have, AFAIK never had, hardware decodes for XVID. So they are transcoded to H264 or HEVC. Most devices/players won't attempt to software decode due to inconsistent performance.
Another work around is to disabled hardware acceleration. Setting it to "None" will use the CPU for transcoding.
RE: Cannot play 480p content on TV or mobile devices - Skellum - 2024-11-27
Appreciate the help Dread.
This system is very old, the FX9590 was AMDs first 'attempt' at an 5ghz octocore CPU, it did this by autoboosting at high voltage.
The problem is that if you attempt to run Windows 10 or later OS on this system it will freeze and/or blue screen with CPU errors, it just doesn't like it.
You can get some stability by disabling the boost and throttling the RAM in my tests but none of this is required for Windows 7 or equivalent OS's (or it would seem, Linux.)
I'm not sure what exactly breaks in Windows 10 onwards but this was the reason this computer has been gathering dust in the corner of the room for years until I decided to 'try' to do something with it.
When I get the time I may take down the server and try a dual boot system with either Server 2022 or Tiny 11 if I can get them to install via DVD (USB isos froze the machine)
Either way, not complaining as this seems to be a self-inflicted issue running outdated OS and using VLC is a valid and acceptable workaround for me. Doesn't appear to be affecting CPU