reggermont
commented
2 years ago Same issue on my side, on my Windows and my Linux. Occurred after upgrading my server from 10.7.7 to 10.8.3, for any encoding (H/x264 SDR, HEVC SDR, HEVC HDR, ...)
Open GiovanH opened 2 years ago
reggermont
commented
2 years ago Same issue on my side, on my Windows and my Linux. Occurred after upgrading my server from 10.7.7 to 10.8.3, for any encoding (H/x264 SDR, HEVC SDR, HEVC HDR, ...)
reggermont
commented
2 years ago Fixed after updating my server to 10.8.4 and/or restarting my server, dunno why :man_shrugging:
FYI, I run my server with the official Docker image, maybe the 10.8.3 image was broken
iwalton3
commented
2 years ago I believe there was some rather significant breakage in the 10.8.3 release. It should be safe to close this.
GiovanH
commented
2 years ago I am still experiencing this with the latest version of the official docker image, running server 10.9.0 @iwalton3 please do not close, this issue is not resolved.
GiovanH
commented
2 years ago This definitely seems to be an issue with the player and not the server, as the working and non-working machines are both connecting to the same server.
reggermont
commented
2 years ago This definitely seems to be an issue with the player and not the server, as the working and non-working machines are both connecting to the same server.
On my side I didn't changed the clients. The only thing I did was upgrading from 10.8.3 to 10.8.4
Can you downgrade your server to 10.8.4 to see if it persists?
GiovanH
commented
2 years ago Yes, same issue with jellyfin/jellyfin:10.8.4.
GiovanH
commented
2 years ago Note that the "retry with transcode" option does work as expected, but my hosting box isn't powerful enough to transcode at full speed.
tarokeitaro
commented
1 year ago help me
[2023-03-28 23:06:44.041 +07:00] [INF] [18] Jellyfin.Api.Helpers.MediaInfoHelper: User policy for "kurikuri". EnablePlaybackRemuxing: True EnableVideoPlaybackTranscoding: True EnableAudioPlaybackTranscoding: True
[2023-03-28 23:06:44.042 +07:00] [INF] [18] Jellyfin.Api.Helpers.MediaInfoHelper: StreamBuilder.BuildVideoItem( Profile="Jellyfin Media Player", Path="/mnt/hgfs/TD-JELLY/K-JELLY/ANIME-COMPLETED/DISK-04/Seitokai Yakuindomo/Season 01/Seitokai Yakuindomo S01E03.mp4", AudioStreamIndex=null, SubtitleStreamIndex=null ) => ( PlayMethod=DirectPlay, TranscodeReason=0 ) "media:/videos/56290404-d228-b6ff-d53b-e6241bab4e81/stream.mov?MediaSourceId=56290404d228b6ffd53be6241bab4e81&Static=true&VideoCodec=h264&AudioCodec=aac&AudioStreamIndex=1&api_key=<token>&Tag=c444ecc3803786a4062f61dc2b2d13de"
[2023-03-28 23:06:44.432 +07:00] [ERR] [27] Microsoft.AspNetCore.Server.Kestrel: Connection id ""0HMPFJHJREF8M"", Request id ""0HMPFJHJREF8M:00000002"": An unhandled exception was thrown by the application.
System.InvalidOperationException: Response Content-Length mismatch: too few bytes written (1128976 of 385903022).
[2023-03-28 23:06:46.801 +07:00] [ERR] [17] Microsoft.AspNetCore.Server.Kestrel: Connection id ""0HMPFJHJREF92"", Request id ""0HMPFJHJREF92:00000002"": An unhandled exception was thrown by the application.
System.InvalidOperationException: Response Content-Length mismatch: too few bytes written (0 of 384774046).
[2023-03-28 23:06:48.031 +07:00] [ERR] [17] Microsoft.AspNetCore.Server.Kestrel: Connection id ""0HMPFJHJREF94"", Request id ""0HMPFJHJREF94:00000002"": An unhandled exception was thrown by the application.
System.InvalidOperationException: Response Content-Length mismatch: too few bytes written (0 of 384774046).
[2023-03-28 23:06:48.862 +07:00] [WRN] [3] Jellyfin.Server.Middleware.ResponseTimeMiddleware: Slow HTTP Response from "http://stream.kuhaku.id:8000/Items/415a5ba34be62b3aac24857cf4f36265/Images/Backdrop/0?tag=9c611e87149e4aee0a67184e8f8ec99e&maxWidth=1920&quality=80" to "10.10.10.100" in 0:00:01.3467965 with Status Code 200
[2023-03-28 23:06:51.291 +07:00] [ERR] [42] Microsoft.AspNetCore.Server.Kestrel: Connection id ""0HMPFJHJREF9C"", Request id ""0HMPFJHJREF9C:00000002"": An unhandled exception was thrown by the application.
System.InvalidOperationException: Response Content-Length mismatch: too few bytes written (0 of 384774046).
[2023-03-28 23:06:57.232 +07:00] [INF] [9] Emby.Server.Implementations.ScheduledTasks.TaskManager: "IntervalTrigger" fired for task: "Webhook Item Added Notifier"
[2023-03-28 23:06:57.233 +07:00] [INF] [9] Emby.Server.Implementations.ScheduledTasks.TaskManager: Queuing task "ItemAddedScheduledTask"
[2023-03-28 23:06:57.233 +07:00] [INF] [15] Emby.Server.Implementations.ScheduledTasks.TaskManager: Executing "Webhook Item Added Notifier"
[2023-03-28 23:06:57.233 +07:00] [INF] [15] Emby.Server.Implementations.ScheduledTasks.TaskManager: "Webhook Item Added Notifier" Completed after 0 minute(s) and 0 seconds
[2023-03-28 23:06:57.233 +07:00] [INF] [15] Emby.Server.Implementations.ScheduledTasks.TaskManager: ExecuteQueuedTasks
[2023-03-28 23:06:58.527 +07:00] [ERR] [27] Microsoft.AspNetCore.Server.Kestrel: Connection id ""0HMPFJHJREFA6"", Request id ""0HMPFJHJREFA6:00000002"": An unhandled exception was thrown by the application.
System.InvalidOperationException: Response Content-Length mismatch: too few bytes written (0 of 384774046).
[2023-03-28 23:06:58.726 +07:00] [ERR] [33] Microsoft.AspNetCore.Server.Kestrel: Connection id ""0HMPFJHJREFA8"", Request id ""0HMPFJHJREFA8:00000002"": An unhandled exception was thrown by the application.
System.InvalidOperationException: Response Content-Length mismatch: too few bytes written (1128976 of 385903022).
[2023-03-28 23:07:00.018 +07:00] [ERR] [9] Microsoft.AspNetCore.Server.Kestrel: Connection id ""0HMPFJHJREFAC"", Request id ""0HMPFJHJREFAC:00000002"": An unhandled exception was thrown by the application.
System.InvalidOperationException: Response Content-Length mismatch: too few bytes written (0 of 384774046).
[2023-03-28 23:07:01.256 +07:00] [ERR] [9] Microsoft.AspNetCore.Server.Kestrel: Connection id ""0HMPFJHJREFAE"", Request id ""0HMPFJHJREFAE:00000002"": An unhandled exception was thrown by the application.
System.InvalidOperationException: Response Content-Length mismatch: too few bytes written (0 of 384774046).If you are using symlinks, note that they aren't supported by Jellyfin.
GiovanH
commented
1 year ago I am seeing this behavior again after it subsided for a while.
tarokeitaro
commented
1 year ago If you are using symlinks, note that they aren't supported by Jellyfin.
I don't use symlink, it's directly mounted to /mnt/hgfs/.
GiovanH
commented
1 year ago I can confirm that I am also not using symlinks.
tarokeitaro
commented
1 year ago btw, how to downgrade jellyfin on fedora, i didn't find jellyfin-10.8.9-2.fc37.x86_64 package. i just realized this problem happens when upgrading jellyfin to jellyfin-10.8.9-3.fc37.x86_64. i have another jellyfin server with the same content and it doesn't behave badly. i think this is the impact of jellyfin package update on fedora server 37.
GiovanH
commented
5 months ago I have not seen this happen for a while. Possibly addressed in an update?
reggermont
commented
5 months ago Personally never had this issue again after upgrading to 10.8.4 :shrug:
Describe the bug When I first try to play any video, it fails to play and suggests I retry with transcode. However, if I cancel out of that screen, do not retry with transcode, and simply try to play the video again, it often works.
I have another computer set up with identical settings that does not experience this problem.
To Reproduce This seems to be specific to one machine, as I have another computer set up that does not experience this problem. I don't know that it will be easily reproducible on other hardware.
Expected behavior If the server has a compatible codec available, it will play it the first time.
Screenshots First click:
After clicking cancel:
After clicking "Got it" and trying to play the exact video again in the same way, it will often work after enough tries.
Desktop (please complete the following information):
Relevant logs: