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

Visual artifacts during BDMV direct play #6386

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

Originally created by @Syndace on GitHub (Oct 27, 2024).

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

I am experiencing visual artifacts when direct-playing BDMV. The artifacts appear consistently at the same timestamps across all clients (tried iOS, LG WebOS, browser, Linux, Android TV). It is not an issue with the source material, it plays flawlessly from file with VLC. A mkv remux of the source material plays without issues as well. Artifacts appear on multiple different BDMVs, not just one specific, and they seem to coincide with high visual complexity. For example, "slow" scenes showing nature do not have artifacts, while "fast" scenes with fire etc. have them frequently. The artifacts do not appear when I enforce transcoding e.g. by limiting the bit rate. I have tried disabling hardware acceleration and playing around with QSV vs. VAAPI settings to no change. Running version 10.10.0.0 on Debian stable, not dockerized.

Reproduction steps

Play any affected medium in BDMV folder format. Make sure direct play is used. I encounter the issue with various different 1080 SHD media.

What is the current bug behavior?

Artifacts appear while direct-playing media in BDMV folder format. Here is an example of the artifacts happening during the initial Warner Bros. logo animation:

image

What is the expected correct behavior?

No artifacts.

Jellyfin Server version

10.10.0+

Specify commit id

No response

Specify unstable release number

No response

Specify version number

No response

Specify the build version

10.10.0

Environment

- OS: Debian 12
- Linux Kernel: 6.1.0-26-amd64
- Virtualization: None
- Clients: Probably all of them (tried iOS, LG WebOS, browser, Linux, Android TV)
- Browser: firefox
- FFmpeg Version: 6.0.1-Jellyfin
- Playback Method: Direct
- Hardware Acceleration: tried QSV, VAAPI and disabled
- GPU Model: Intel 630 in i7-7700
- Plugins: DLNA
- Reverse Proxy: nginx
- Base URL: none
- Networking: uh?
- Storage: local

Jellyfin logs

jellyfin20241027.log

FFmpeg logs

FFmpeg.DirectStream-2024-10-27_15-17-06_a700537e8479e7bd641ca6ce15b3e8b1_f5391d1b.log

Client / Browser logs

No response

Relevant screenshots or videos

No response

Additional information

No response

Originally created by @Syndace on GitHub (Oct 27, 2024). ### 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 I am experiencing visual artifacts when direct-playing BDMV. The artifacts appear consistently at the same timestamps across all clients (tried iOS, LG WebOS, browser, Linux, Android TV). It is not an issue with the source material, it plays flawlessly from file with VLC. A mkv remux of the source material plays without issues as well. Artifacts appear on multiple different BDMVs, not just one specific, and they seem to coincide with high visual complexity. For example, "slow" scenes showing nature do not have artifacts, while "fast" scenes with fire etc. have them frequently. The artifacts do not appear when I enforce transcoding e.g. by limiting the bit rate. I have tried disabling hardware acceleration and playing around with QSV vs. VAAPI settings to no change. Running version 10.10.0.0 on Debian stable, not dockerized. ### Reproduction steps Play any affected medium in BDMV folder format. Make sure direct play is used. I encounter the issue with various different 1080 SHD media. ### What is the current _bug_ behavior? Artifacts appear while direct-playing media in BDMV folder format. Here is an example of the artifacts happening during the initial Warner Bros. logo animation: ![image](https://github.com/user-attachments/assets/a0db76d4-2768-448b-8afc-b8f181271a83) ### What is the expected _correct_ behavior? No artifacts. ### Jellyfin Server version 10.10.0+ ### Specify commit id _No response_ ### Specify unstable release number _No response_ ### Specify version number _No response_ ### Specify the build version 10.10.0 ### Environment ```markdown - OS: Debian 12 - Linux Kernel: 6.1.0-26-amd64 - Virtualization: None - Clients: Probably all of them (tried iOS, LG WebOS, browser, Linux, Android TV) - Browser: firefox - FFmpeg Version: 6.0.1-Jellyfin - Playback Method: Direct - Hardware Acceleration: tried QSV, VAAPI and disabled - GPU Model: Intel 630 in i7-7700 - Plugins: DLNA - Reverse Proxy: nginx - Base URL: none - Networking: uh? - Storage: local ``` ### Jellyfin logs [jellyfin20241027.log](https://github.com/user-attachments/files/17534298/jellyfin20241027.log) ### FFmpeg logs [FFmpeg.DirectStream-2024-10-27_15-17-06_a700537e8479e7bd641ca6ce15b3e8b1_f5391d1b.log](https://github.com/user-attachments/files/17534297/FFmpeg.DirectStream-2024-10-27_15-17-06_a700537e8479e7bd641ca6ce15b3e8b1_f5391d1b.log) ### Client / Browser logs _No response_ ### Relevant screenshots or videos _No response_ ### Additional information _No response_
OVERLORD added the bugstalemedia playback labels 2026-02-07 03:34:05 +03:00
OVERLORD commented 2026-02-07 03:34:08 +03:00
Author
Owner
Copy Link

@felix920506 commented on GitHub (Oct 27, 2024):

You are still using ffmpeg 6.x
Can you try updating to the latest jellyfin-ffmpeg7 package?

Uninstall the jellyfin-ffmpeg6 package and install the jellyfin-ffmpeg7 package

@felix920506 commented on GitHub (Oct 27, 2024): You are still using ffmpeg 6.x Can you try updating to the latest jellyfin-ffmpeg7 package? Uninstall the jellyfin-ffmpeg6 package and install the jellyfin-ffmpeg7 package
OVERLORD commented 2026-02-07 03:34:10 +03:00
Author
Owner
Copy Link

@Syndace commented on GitHub (Oct 27, 2024):

No change; same artifacts at the same timestamps. New ffmpeg log:

FFmpeg.DirectStream-2024-10-27_16-56-55_a700537e8479e7bd641ca6ce15b3e8b1_fea4e178.log

@Syndace commented on GitHub (Oct 27, 2024): No change; same artifacts at the same timestamps. New ffmpeg log: [FFmpeg.DirectStream-2024-10-27_16-56-55_a700537e8479e7bd641ca6ce15b3e8b1_fea4e178.log](https://github.com/user-attachments/files/17534539/FFmpeg.DirectStream-2024-10-27_16-56-55_a700537e8479e7bd641ca6ce15b3e8b1_fea4e178.log)
OVERLORD commented 2026-02-07 03:34:13 +03:00
Author
Owner
Copy Link

@Syndace commented on GitHub (Oct 27, 2024):

New information: enabling the "Prefer fMP4-HLS Media Container" option fixes the artifacts when using Firefox. ffmpeg log:
FFmpeg.DirectStream-2024-10-27_17-24-11_a700537e8479e7bd641ca6ce15b3e8b1_b4f177bc.log

On the native Linux client, the fMP4 option does not seem to have an effect for direct-streaming BDMV.

@Syndace commented on GitHub (Oct 27, 2024): New information: enabling the "Prefer fMP4-HLS Media Container" option fixes the artifacts when using Firefox. ffmpeg log: [FFmpeg.DirectStream-2024-10-27_17-24-11_a700537e8479e7bd641ca6ce15b3e8b1_b4f177bc.log](https://github.com/user-attachments/files/17534740/FFmpeg.DirectStream-2024-10-27_17-24-11_a700537e8479e7bd641ca6ce15b3e8b1_b4f177bc.log) On the native Linux client, the fMP4 option does not seem to have an effect for direct-streaming BDMV.
OVERLORD commented 2026-02-07 03:34:17 +03:00
Author
Owner
Copy Link

@felix920506 commented on GitHub (Oct 28, 2024):

does enabling fmp4 option in Jellyfin media player generate any ffmpeg logs? If so please post them here

@felix920506 commented on GitHub (Oct 28, 2024): does enabling fmp4 option in Jellyfin media player generate any ffmpeg logs? If so please post them here
OVERLORD commented 2026-02-07 03:34:19 +03:00
Author
Owner
Copy Link

@Syndace commented on GitHub (Oct 28, 2024):

Jellyfin Media Player with fmp4 enabled: FFmpeg.DirectStream-2024-10-28_19-56-32_a700537e8479e7bd641ca6ce15b3e8b1_29b36b5e.log

@Syndace commented on GitHub (Oct 28, 2024): Jellyfin Media Player with fmp4 enabled: [FFmpeg.DirectStream-2024-10-28_19-56-32_a700537e8479e7bd641ca6ce15b3e8b1_29b36b5e.log](https://github.com/user-attachments/files/17547573/FFmpeg.DirectStream-2024-10-28_19-56-32_a700537e8479e7bd641ca6ce15b3e8b1_29b36b5e.log)
OVERLORD commented 2026-02-07 03:34:22 +03:00
Author
Owner
Copy Link

@gnattu commented on GitHub (Oct 28, 2024):

JMP will not use the web's profile and will alway use its own, which means it will always request mpegts and that can be confirmed from your log.

@gnattu commented on GitHub (Oct 28, 2024): JMP will not use the web's profile and will alway use its own, which means it will always request mpegts and that can be confirmed from your log.
OVERLORD commented 2026-02-07 03:34:23 +03:00
Author
Owner
Copy Link

@jellyfin-bot commented on GitHub (Feb 26, 2025):

This issue has gone 120 days without an update and will be closed within 21 days if there is no new activity. To prevent this issue from being closed, please confirm the issue has not already been fixed by providing updated examples or logs.

If you have any questions you can use one of several ways to contact us.

@jellyfin-bot commented on GitHub (Feb 26, 2025): This issue has gone 120 days without an update and will be closed within 21 days if there is no new activity. To prevent this issue from being closed, please confirm the issue has not already been fixed by providing updated examples or logs. If you have any questions you can use one of several ways to [contact us](https://jellyfin.org/contact).
OVERLORD commented 2026-02-07 03:34:24 +03:00
Author
Owner
Copy Link

@jellyfin-bot commented on GitHub (Mar 19, 2025):

This issue was closed due to inactivity.

@jellyfin-bot commented on GitHub (Mar 19, 2025): This issue was closed due to inactivity.
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 media playback stale
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#6386
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?