[BUG] Jellyfin playback glitches on S02E06 (My Dress-Up Darling) - Downloaded via AniBridge

[Zzackllack]

Summary

• Symptom: scenes repeat/seek weirdly in Jellyfin; seeking is unstable.
• Context: local file from AniWorld/S.to release; Jellyfin transcodes via FFmpeg.

Evidence (from Jellyfin FFmpeg log)

• Packet corruption in the source stream: "Packet corrupt", "PES packet size mismatch".
• Timestamp regression: "Non-monotonic DTS" and "Queue input is backward in time".
• Decode failures in H.264/AAC: "Invalid data found when processing input", "Input buffer exhausted".
• Extra data stream present: timed_id3 (common in HLS/TS sources).

Not an AniBridge playback bug

• Jellyfin uses its own FFmpeg for playback/transcoding; AniBridge is not in that path.
• AniBridge only uses ffprobe for metadata lookup and yt-dlp/ffmpeg as a downloader; it does not transcode or modify media during playback.
• The errors above are classic indicators of corrupted or badly muxed input streams (especially HLS/TS sources).

Why it plays fine on VOE (Aniworld/S.to)

• Web players often tolerate/skip over small timestamp or packet errors.
• Online delivery may use a different set of segments or a cleaner mux than the downloaded file.
• Jellyfin transcoding is stricter and exposes timestamp regressions.

Reproduction

1. Play the affected local file in Jellyfin.
2. Observe repeated scenes / unstable seeking.
3. Check Jellyfin FFmpeg log for the errors listed above.

Fix / Workaround that helped

• Remux by keeping only video + audio streams (drop data streams):
  ffmpeg -i "input.mp4" -map 0:v -map 0:a -c copy "output.mp4"
• After remuxing, the file plays cleanly in Jellyfin.
• After remuxing, Jellyfin reports Direct Play instead of Remux.
• Optional if timestamps are broken: regenerate PTS while remuxing:
  ffmpeg -fflags +genpts -i "input.mp4" -map 0:v -map 0:a -c copy "output.mp4"

Notes about AniBridge downloader settings

• AniBridge uses yt-dlp with ffmpeg as downloader and hls_use_mpegts=True.
• HLS/TS inputs commonly carry timed_id3 data streams and can have timestamp quirks.
• This can explain the presence of a data stream but does not indicate a playback bug in AniBridge.

Proposed enhancement (optional)

• Consider a post-download remux option to drop non-A/V streams and normalize timestamps.
• This would be a mitigation feature for known-bad releases, not a fix for an AniBridge playback bug.

Conclusion

• Root cause is the media file stream integrity (corrupt packets and non-monotonic DTS).
• Not a codebase bug in AniBridge playback (AniBridge is not part of Jellyfin transcoding).
• Mitigation: remux to video+audio only, or re-download from a better release.