-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
[Issue]: Transcoding immediatly stops after starting playback #5039
Comments
Second and third FFMpeg log, which were automatically created by Jellyfin during the same playback attempt:
|
Just going to hop onto this bug report since I am suffering the exact same issue: Just going to drop my logs here in case they help. This happened to me only after upgrading to Version: 10.8.4.
|
I had a similar transcoding error after upgrading to a 10.8.4 docker image. Everything works when I revert to 10.7.7. Here are my FFmpeg transcoding logs.
|
This comment has been minimized.
This comment has been minimized.
I'm still affected by this issue. Currently running version 10.8.8 |
having this issue on 10.8.8, appeared after doing a system upgrade, not touching docker or jellyfin |
oh yeah, really strange thing, this is only an issue on web jellyfin, accessing it through the android app works perfectly |
I'm having this exact same problem, using the Jellyfin docker image on Ubuntu 22.04. |
I also am having this issue on Ubuntu Server 22.04 LTS + Docker image (linuxserver) |
Same problem on Ubuntu 22.04.2 LTS + Docker(nyanmisaka/jellyfin) |
Same problem. Running with podman on rockyLinux. |
I have exactly the same error as the original poster for some video files. This occurs with and without hardware acceleration enabled. The jellyfin log shows a In my case I noticed that all video files I found with this error all had Also important to note is that this just happens when transcoding. When ffmpeg is just serving the video (to a native client for example) it works fine. EDIT: Without diving into the code or anything like that, this seems to me like it might be a frontend issue. The frontend sends a EDIT2: My setup is running Jellyfin in a Podman Container using the linuxserver.io image (version 10.8.10) on a debian 12 host. EDIT3 (sorry lol): I just confirmed that this seems to be a frontend issue with AAC 7.1 (possibly 7.1 in general, but I can't check that). I found a video where I have an |
any updates on this? Is the answer to downgrade? |
I figured out how to prevent the issue when For some reason the |
The workaround proposed by @dnlmlr fixed the problem on my end as well. It always worked via the Chromecast App (Android TV I guess?), but didn't when using a browser. I've since set it to I'd assume the |
I had the same issue and the workaround from @dnlmlr also worked for me. For the server I am using the Windows build 10.8.13 and the issues only happened in the web client of a Windows 10 machine. It happened with Chrome, Firefox, and Edge, so I don't think it was related to the browser. Auto and 7.1 failed whether the selected device was the Realtek S1220 A audio chipset (which supports 8 channels) with the newest drivers, or a pair of Logitech 733s, which also support 7.1 surround. Hopefully this can get a proper fix in the next build. |
I also have the same problem with 7.1 audio. |
Same problem, same fix. I'm not sure the error lies within Jellyfin, though… I'm running Firefox on Windows 11 with SteelSeries Sonar, which tells Windows that it supports 7.1 surround sound, and Firefox will confirm that it supports 8 audio channels if you ask it (e.g., via the AudioContext API). Indeed, if you play a WAV file with 7.1 channels, it works fine (see an example at the bottom of this page), but the MP4 example on the same page does not work for me in Firefox (or even VLC, but Audacity confirms that the raw audio in the file is fine). Given this is happening across multiple browsers, it feels like this is a Windows bug — the workaround would be a hard limit of 6 channels for Windows clients, which feels a bit icky. I'd prefer that over having to set a maximum for my user, though — if I ever get around to having a 7.1 setup, I'll almost certainly forget I've done this and waste a lot of time trying to figure out why it isn't working. 😕 |
Another case of this bug here. Jellyfin 10.8.13 via Docker. The workaround established earlier (click the person icon in the top right of the web interface, click Playback, set Maximum Allowed Audio Channels to 5.1) did solve the issue for the client in question. Interestingly, my machine is running Ubuntu 23.10 and Firefox, and I don't have this issue, even when Maximum Allowed Audio Channels is still set to Auto. (Y'all have no idea how happy I am right now that my Linux machine is the one without the bug for once :-D ) |
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. |
@dnlmlr solution pointed me in the right track, had the same on an Android tv, fixed it by going to the playback settings, there was an audio channel setting regarding |
Please describe your bug
Transcoding immediately stops after starting playback for some video files, after which error "This client isn't compatible with the media and the server isn't sending a compatible media format" is shown. It looks like 3 attempts are being made to transcode the file, as there are 3 separate transcoding logs. One of them states 'copy' while the other two indicate transcoding.
Possibly related to jellyfin/jellyfin#8233 even though in my case not even a second of video is being shown.
Jellyfin Version
Other
if other:
10.8.4
Environment
Jellyfin logs
FFmpeg logs
Please attach any browser or client logs here
No response
Please attach any screenshots here
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: