starred/jellyfin
1
0
Fork 0
mirror of https://github.com/jellyfin/jellyfin.git synced 2026-05-04 18:09:12 +03:00
Code Issues 822 Packages Projects Releases 10 Wiki Activity

video playback looping back several minutes after film has ended #6648

New Issue
Closed
opened 2026-02-07 03:56:02 +03:00 by OVERLORD · 8 comments
OVERLORD commented 2026-02-07 03:56:02 +03:00
Owner
Copy Link

Originally created by @Wurzelmann on GitHub (Jan 11, 2025).

This issue respects the following points:

  • This is a bug, not a question or a configuration issue; Please visit our forum or chat rooms first to troubleshoot with volunteers, before creating a report. The links can be found here.
  • This issue is not already reported on GitHub (I've searched it).
  • I'm using an up to date version of Jellyfin Server stable, unstable or master; We generally do not support previous older versions. If possible, please update to the latest version before opening an issue.
  • I agree to follow Jellyfin's Code of Conduct.
  • This report addresses only a single issue; If you encounter multiple issues, kindly create separate reports for each one.

Description of the bug

After a movie has ended (it never happens with series, only movies), the video loops back a few minutes and starts playback again from there, no idea why.

Reproduction steps

  1. watch movie until the very last second
  2. movie should end but jumps back a few minutes and continues playback from there
  3. rinse and repeat

What is the current bug behavior?

the movie playback does not stop at the end of the movie, it rewinds back a few minutes and continues from there.

What is the expected correct behavior?

Movie playback is at its end, movie stops, closes and is done.

Jellyfin Server version

10.10.0+

Specify commit id

No response

Specify unstable release number

No response

Specify version number

10.10.3

Specify the build version

10.10.3

Environment

- OS: Debian 12.8
- Linux Kernel: 6.1.0-28-amd64
- Virtualization: bare metal installation
- Clients: Browser (Firefox ESR)
- Browser: Firefox 128.6.0esr (64-bit)
- FFmpeg Version: ffmpeg: 5.1.6, jellyfin-ffmpeg6: 6.0.1
- Playback Method: DirectPlay
- Hardware Acceleration: none
- GPU Model: none
- Plugins: none
- Reverse Proxy: nginx
- Base URL: none
- Networking: Host
- Storage: local

Jellyfin logs

none applicable

FFmpeg logs

Client / Browser logs

No response

Relevant screenshots or videos

No response

Additional information

No response

Originally created by @Wurzelmann on GitHub (Jan 11, 2025). ### This issue respects the following points: - [x] This is a **bug**, not a question or a configuration issue; Please visit our forum or chat rooms first to troubleshoot with volunteers, before creating a report. The links can be found [here](https://jellyfin.org/contact/). - [x] This issue is **not** already reported on [GitHub](https://github.com/jellyfin/jellyfin/issues?q=is%3Aopen+is%3Aissue) _(I've searched it)_. - [x] I'm using an up to date version of Jellyfin Server stable, unstable or master; We generally do not support previous older versions. If possible, please update to the latest version before opening an issue. - [x] I agree to follow Jellyfin's [Code of Conduct](https://jellyfin.org/docs/general/community-standards.html#code-of-conduct). - [x] This report addresses only a single issue; If you encounter multiple issues, kindly create separate reports for each one. ### Description of the bug After a movie has ended (it never happens with series, only movies), the video loops back a few minutes and starts playback again from there, no idea why. ### Reproduction steps 1. watch movie until the very last second 2. movie should end but jumps back a few minutes and continues playback from there 3. rinse and repeat ### What is the current _bug_ behavior? the movie playback does not stop at the end of the movie, it rewinds back a few minutes and continues from there. ### What is the expected _correct_ behavior? Movie playback is at its end, movie stops, closes and is done. ### Jellyfin Server version 10.10.0+ ### Specify commit id _No response_ ### Specify unstable release number _No response_ ### Specify version number 10.10.3 ### Specify the build version 10.10.3 ### Environment ```markdown - OS: Debian 12.8 - Linux Kernel: 6.1.0-28-amd64 - Virtualization: bare metal installation - Clients: Browser (Firefox ESR) - Browser: Firefox 128.6.0esr (64-bit) - FFmpeg Version: ffmpeg: 5.1.6, jellyfin-ffmpeg6: 6.0.1 - Playback Method: DirectPlay - Hardware Acceleration: none - GPU Model: none - Plugins: none - Reverse Proxy: nginx - Base URL: none - Networking: Host - Storage: local ``` ### Jellyfin logs ```shell none applicable ``` ### FFmpeg logs ```shell ``` ### Client / Browser logs _No response_ ### Relevant screenshots or videos _No response_ ### Additional information _No response_
OVERLORD added the bug label 2026-02-07 03:56:02 +03:00
OVERLORD commented 2026-02-07 03:56:05 +03:00
Author
Owner
Copy Link

@Aydonger commented on GitHub (Jan 11, 2025):

Same happens at my Jellyfin Installation. But (currently) not with the "Main" Movies, but with Moviefiles in the "behind the scenes" or "extra" Folders.

@Aydonger commented on GitHub (Jan 11, 2025): Same happens at my Jellyfin Installation. But (currently) not with the "Main" Movies, but with Moviefiles in the "behind the scenes" or "extra" Folders.
OVERLORD commented 2026-02-07 03:56:07 +03:00
Author
Owner
Copy Link

@Wurzelmann commented on GitHub (Jan 11, 2025):

Funny, for me it is just the main movies, just tested a folder full of specials and they were okay...

@Wurzelmann commented on GitHub (Jan 11, 2025): Funny, for me it is just the main movies, just tested a folder full of specials and they were okay...
OVERLORD commented 2026-02-07 03:56:11 +03:00
Author
Owner
Copy Link

@Aydonger commented on GitHub (Jan 11, 2025):

At first I thought it might be due to the file format (MP4 or MKV). As the specials with the error are all in MP4 format, I didn't have a chance to verify this idea.

I suspected that I had encoded something incorrectly when creating the film files. But that doesn't seem to be the case...

@Aydonger commented on GitHub (Jan 11, 2025): At first I thought it might be due to the file format (MP4 or MKV). As the specials with the error are all in MP4 format, I didn't have a chance to verify this idea. I suspected that I had encoded something incorrectly when creating the film files. But that doesn't seem to be the case...
OVERLORD commented 2026-02-07 03:56:13 +03:00
Author
Owner
Copy Link

@Wurzelmann commented on GitHub (Jan 11, 2025):

I also did not find any hints what the problem might be, I have MP4s, MKVs all behaving in this way and is really annoying...

@Wurzelmann commented on GitHub (Jan 11, 2025): I also did not find any hints what the problem might be, I have MP4s, MKVs all behaving in this way and is really annoying...
OVERLORD commented 2026-02-07 03:56:14 +03:00
Author
Owner
Copy Link

@felix920506 commented on GitHub (Jan 11, 2025):

Are you sure it is direct playing? If it is direct playing then there is nothing we can really do about it unfortunately.

@felix920506 commented on GitHub (Jan 11, 2025): Are you sure it is direct playing? If it is direct playing then there is nothing we can really do about it unfortunately.
OVERLORD commented 2026-02-07 03:56:16 +03:00
Author
Owner
Copy Link

@Wurzelmann commented on GitHub (Jan 11, 2025):

Are you sure it is direct playing? If it is direct playing then there is nothing we can really do about it unfortunately.

Yes it is, I just checked with the last film it happened to:

Playback Info
Player
Html Video Player
Play method
Direct streaming
Protocol
https
Stream type
HLS
@Wurzelmann commented on GitHub (Jan 11, 2025): > Are you sure it is direct playing? If it is direct playing then there is nothing we can really do about it unfortunately. Yes it is, I just checked with the last film it happened to: ``` Playback Info Player Html Video Player Play method Direct streaming Protocol https Stream type HLS ```
OVERLORD commented 2026-02-07 03:56:17 +03:00
Author
Owner
Copy Link

@felix920506 commented on GitHub (Jan 11, 2025):

Yeah, closing as there is nothing we can really do about it. Your best course of action would be to simply not use Firefox for Jellyfin.

@felix920506 commented on GitHub (Jan 11, 2025): Yeah, closing as there is nothing we can really do about it. Your best course of action would be to simply not use Firefox for Jellyfin.
OVERLORD commented 2026-02-07 03:56:19 +03:00
Author
Owner
Copy Link

@Wurzelmann commented on GitHub (Jan 11, 2025):

Yeah, closing as there is nothing we can really do about it. Your best course of action would be to simply not use Firefox for Jellyfin.

Okay, fair enough and just for the record: I just tried to reproduce this with Chromium and it just worked, thanks for your time.

@Wurzelmann commented on GitHub (Jan 11, 2025): > Yeah, closing as there is nothing we can really do about it. Your best course of action would be to simply not use Firefox for Jellyfin. Okay, fair enough and just for the record: I just tried to reproduce this with Chromium and it just worked, thanks for your time.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
EFjellyfin.db
area:database
awaiting-feedback
backend
blocked
breaking change: web api
bug
build
ci
confirmed
discussion needed
dotnet future
downstream
duplicate
enhancement
feature
future
github-actions
good first issue
hdr
help wanted
invalid
investigation
librarydb
live-tv
lyrics
media playback
music
needs testing
nuget
performance
platform
pull-request
Mirrored from GitHub Pull Request
 question
regression
release critical
requires-web
roadmap
security
security
stale
support
syncplay
ui & ux
upstream
wontfix
No Label bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
OVERLORD
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/jellyfin#6648
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?