-
Describe The Bug I have enabled transcoding on Jellyfin. Running Jellyfin via Portainer on RPi4. Movie can't be even played after enabling transcoding, if I disable transcoding then movie is playing, however RPi4 cannot keep up with that bitrate. Trancoding issue happens with every movie. Steps To Reproduce
Expected Behavior Movie should transcode. Logs
Screenshots System (please complete the following information):
Additional Context |
Beta Was this translation helpful? Give feedback.
Replies: 51 comments 38 replies
-
I have the same issue with 10.7.5. Downgraded docker image to 10.7.1 and it works now. |
Beta Was this translation helpful? Give feedback.
-
Jumping on this one too. I had everything working on 10.6.4 and after upgrading to 10.7.1/5 i keep getting this error. Downgrading back to 10.6 seems to put everything back in place. I do not have transcoding enabled, however FWIW, this is the relevant log i get from jellyfin-mpv-shim
Edit: Maybe it is transcoding...
|
Beta Was this translation helpful? Give feedback.
This comment was marked as spam.
This comment was marked as spam.
-
Unless the ticket is going to be closed due to inactivity there is absolutely no reason to comment "bump". That provides no value whatsoever to resolving the issue. If you wish to be notified of any updates use the features built into GitHub to subscribe. |
Beta Was this translation helpful? Give feedback.
-
@sang-ook This doesn't look to actually be a Jellyfin error.
So looks like invalid hardware decoding/transcoding configuration. Try with software-only transcoding and see if it works. @TwistTheNeil Looks like yours is similar - I see VAAPI in there, but we'd need to see the ffmpeg logs themselves to know for sure.
Generally speaking that message means something has gone wrong with |
Beta Was this translation helpful? Give feedback.
-
I am seeing the same error msg which has nothing to do with transcoding. It happens when I try to play episodes from multiple series in shuttle in a Collection. |
Beta Was this translation helpful? Give feedback.
-
Same issue, jelly 10.7.6, windows as a service via a caddy proxy, works on other clients. No ffmpeg exit code error here. whats even weirder is the movie starts to play before dying. EDIT: turning off subtitles makes it work??? maybe related to jellyfin/jellyfin#3488 but it happens on both nvenc and x264
|
Beta Was this translation helpful? Give feedback.
-
I got the same issue with 10.7.7 (from focal PPA) on Linux in an LXC-Container, but i think I nailed it down: i forwarded the device-files of my nvidia p400 to the lxc-container, which is running on proxmox7, nvidia-smi runs on the host as well as on the container, so basic access to the gpu is possible, but jellyfin throws me the error noted in the title of this issue on playback attempts. It seems, that the cuda-cores did not get activated automatically. Also the However, if i run something, which activates the cuda cores, like Unfortunately this has to be done on every reboot for now in order to get nvenc to work. |
Beta Was this translation helpful? Give feedback.
-
Apparently this issue can also crop up if jellyfin doesn't have access permissions to the log dir. Yes, my server sometimes locks out jellyfin from its own logs...it's a long story. |
Beta Was this translation helpful? Give feedback.
-
I got this message on one album of FLAC files, and it worked fine on a copy converted to FLAC again through foobar2000, weird. |
Beta Was this translation helpful? Give feedback.
-
same issue here at ver. 10.7.7 |
Beta Was this translation helpful? Give feedback.
-
I get the same error on all my FLAC, MP3, etc., files when playing through any of the official clients (which afaik are all based on the web client), including the browser (tested both Firefox and Chromium). However, I only get the error when accessing my media over https with my domain (using a Caddy reverse proxy) and not when directly connecting via LAN address and port (i.e. When using 3rd party clients such as Finamp or Gelli or Mopidy, I can connect over https/domain and play the same file successfully from any network. Only the official jellyfin clients are effected. I run jellyfin from Docker, using the latest stable official image. My log files don't contain any errors, there is no transcoding going on either (there shouldn't need to be with FLAC anyways). Relevant logs that occur when the error is displayed are below. Let me know if full logs are necessary. Would anyone having similar issues mind testing if they go away when connecting over LAN IP? Note in the below, the song (Particle Arts) is stopped (not by me, this is when the error displays) after 0 ms, before the logs even report on the fact that I was listening to the song. There are no more logs after the below.
|
Beta Was this translation helpful? Give feedback.
-
I was getting the same error. In my case, the issue was because Jellyfin couldn't see the drives attached. The drive was plugged into the computer, but it got unmounted (maybe because of a power failure). Once I remounted it, I could play everything fine. I hope this could be useful for someone else that faces this issue in the future. Also, @thornbill, can we have the error message updated for the case when Jellyfin can't find the drives? The current message I got is not really helpful for this. |
Beta Was this translation helpful? Give feedback.
-
I'm having a similar issue to theAeon, web playback with transcoding doesn't work on certain files until you disable the integrated subtitles. If subs are disabled transcoding and web playback work just fine. Also, I've tried disabling Nvenc Hardware Acceleration and still had the same result. |
Beta Was this translation helpful? Give feedback.
-
Thanks for this, now I know I can at least disable subtitles to playback media. Issue is the same for me. When subtitles are disabled playback works fine. Otherwise it seems random. It even happens on H264 videos through web browser, which don't usually need to be transcoded. v10.7.7 in UnRaid docker (Linuxserver). |
Beta Was this translation helpful? Give feedback.
-
Adding my solution for Docker in unRAID using my 11600K's UHD 750 and linuxserver's container version 10.8.4:
Notes:
My resources: |
Beta Was this translation helpful? Give feedback.
-
For me the issue and the solution were the user-level permissions in Jellyfin, where even video conversion without transcoding was unchecked. I checked all the boxes in the user's media playback settings server side and voilà! I can play all H264 mp4s again! |
Beta Was this translation helpful? Give feedback.
-
Make sure to give jellyfin permission to the folders with this command, make sure to change the directory to your own.
|
Beta Was this translation helpful? Give feedback.
-
If you are running docker and see error message
you could try use the way by @DesertCookie to correct this |
Beta Was this translation helpful? Give feedback.
-
Jellyfin on Synology NAS story: |
Beta Was this translation helpful? Give feedback.
-
In my case, I had uBlock origin blocking large media content which explains why it gave the error for flac and not mp3. |
Beta Was this translation helpful? Give feedback.
-
Well, i increased the buffer, ensured that the sudo chmod -R +r /pathtomedia and remove the path to ffm... in settings saved, then set it back saved , restart jellyfin and it works , just takes a min to load up :) |
Beta Was this translation helpful? Give feedback.
-
Everything is perfect since the 10.8.10 update on my LG C1 . The old VC1 and mpeg2-FULLHD movies are successfully transcoded to HEVC. Thanks very much. ⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⣀⣀⣤⣀⢠⡤⠤⠖⠒⠒⠒⠲⣆⠀⠀⠀⠀⣾⠋⠉⠉⠛⢷⠀⣴⠖⠒⠤⣄⠀⣀⡀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀ |
Beta Was this translation helpful? Give feedback.
-
I just wanted to add a alternate solution if someone searches for the same error code. |
Beta Was this translation helpful? Give feedback.
-
I have this issue only when shuffling a Collections contents and I've had it on all previous iterations of Jellyfin (running 10.8.10). If I go into any individual show and shuffle it, all content works. If I try to shuffle between shows in a collection, this error immediately pops up and logs show nothing loading or starting for me to point to as an error. |
Beta Was this translation helpful? Give feedback.
-
This issue only occurs in my Android browser, 'Kiwi browser.' Other browsers and devices work fine. It's weird.And the log doesn't show anything significant: |
Beta Was this translation helpful? Give feedback.
-
Hi All. I came across this post while working on a new JF install, specifically trying to get HWA HDR->SDR tonemapping working. Turns out this error is also spit out when trying to use HDR TM and the host system doesn't support OpenCL/CUDA. (In this case I've installed JF as a docker container on a TrueNAS SCALE host) When software Transcoding is enabled, all is fine. When HWA Transcoding is enabled, all is fine. But when HWA Transcoding with HDR tonemapping is enabled && host does not have OpenCL, the error appears Video example of behaviour below: |
Beta Was this translation helpful? Give feedback.
-
I don't know if it's the same issue but I'm trying to play an ogg VORBIS audio file using the jellyfin Android app and I get the exact same error. The logs look like the client didn't even attempt to make the server transcode anything. I see a bunch of
I'm using podman and software transcoding. |
Beta Was this translation helpful? Give feedback.
-
I'm on Artix with Dinit Jellyfin logs
Dinit service
From logs:
But then I'm unable to set it settings, the box just not interactiable, see screenshot. SolvedAfter two weeks I found I edited it to add following lines:
After that it worked! |
Beta Was this translation helpful? Give feedback.
-
I recently had a user on my server bring this issue to me, which I hadn't seen before. Turned out to be due to merged episodes. I use the Merge Versions plugin, and due to some bugs it often ends up grouping multiple episodes together, rather than just 2 versions of the same episode (like a 1080p and 4k version). Once I split the items apart, the issue went away. |
Beta Was this translation helpful? Give feedback.
I have converted this to a discussion because at this point everyone commenting seems to be having different issues and the original author has not responded to feedback to their specific issue.
Typically this error message is displayed for one of the following reasons: