+- Jellyfin Forum (https://forum.jellyfin.org)
+-- Forum: Support (https://forum.jellyfin.org/f-support)
+--- Forum: Troubleshooting (https://forum.jellyfin.org/f-troubleshooting)
+--- Thread: SOLVED: Colourful Artifacts During Bright Flashes (/t-solved-colourful-artifacts-during-bright-flashes)
Colourful Artifacts During Bright Flashes - NorthernFox - 2024-09-12
I am currently running Jellyfin 10.8.12 (updated now to 10.9.11) off the windows installer.
When I am watching a movie that contains a bright flash (such as a camera flash), the screen becomes a jumble of colours for a few seconds (1-2) after the flash then returns to normal. This problem seems to go away if I transcode the movie, watch it on a different device, or play the original file in something like VLC. It only appears when I watch it at original quality on the web browser.
Example screenshot included below.
I've also included the part of the log relating to the movie playback
RE: Colourful Artifacts During Bright Flashes - Efficient_Good_5784 - 2024-09-12
Any reason why you haven't updated yet to the latest server release? I would try upgrading and seeing if the issue still persists.
RE: Colourful Artifacts During Bright Flashes - NorthernFox - 2024-09-12
(2024-09-12, 04:54 AM)Efficient_Good_5784 Wrote: Any reason why you haven't updated yet to the latest server release? I would try upgrading and seeing if the issue still persists.
Because I haven't been paying attention to when updates come out lol. I have updated to the latest and still have the same issue.
RE: Colourful Artifacts During Bright Flashes - Efficient_Good_5784 - 2024-09-12
Can you playback the video that give the error so that it gets logged in the ffmpeg logs?
Then can you share the ffmpeg logs (and server logs too) here using a site like pastebin?
RE: Colourful Artifacts During Bright Flashes - NorthernFox - 2024-09-12
(2024-09-12, 05:36 AM)Efficient_Good_5784 Wrote: Can you playback the video that give the error so that it gets logged in the ffmpeg logs?
Then can you share the ffmpeg logs (and server logs too) here using a site like pastebin?
Apologies for the delay
FFMPEG: https://pastebin.com/eL1idq1n
Server: https://pastebin.com/5GZCUEPe
RE: Colourful Artifacts During Bright Flashes - TheDreadPirate - 2024-09-13
Since only the audio is being transcoded, I'm inclined to say this is corruption in the video. Maybe not the video itself but maybe in the original container. You can try manually remuxing and trying again.
In a command prompt.
Code:
ffmpeg -fflags +genpts+igndts -i file:"E:\Movies\Harry Potter and the Deathly Hallows - Part 1 (2010)\Harry Potter and the Deathly Hallows - Part 1 (2010).mkv" -codec copy -max_muxing_queue_size 2048 -avoid_negative_ts make_zero -max_interleave_delta 0 "E:\Movies\Harry Potter and the Deathly Hallows - Part 1 (2010)\newVersion.mkv"RE: Colourful Artifacts During Bright Flashes - NorthernFox - 2024-09-13
I have remuxed as suggested, no change.
I do not believe the issue is with the files themselves since when I play then in other players like VLC they do not have the same artifacts.
RE: Colourful Artifacts During Bright Flashes - gnattu - 2024-09-13
(2024-09-13, 04:06 AM)NorthernFox Wrote: I have remuxed as suggested, no change.
I do not believe the issue is with the files themselves since when I play then in other players like VLC they do not have the same artifacts.
Browsers have less tolerance about file and that is normal that VLC or MPV can play a file but the browser cannot. And as you said, even direct playing cannot resolve this issue we can do very little unless force transcoding to make it compatible with browsers.
This "issue" is not about if the original file is "corrupted", it may be not, but it is encoded in a way that is not compatible with most browsers, and that is the problem
RE: Colourful Artifacts During Bright Flashes - NorthernFox - 2024-09-13
Interesting. It may be compatibility issues with the browser.
It seems the artefacts appear with Chromium-based browsers (I tested with Brave and Chrome) but not with others like Firefox.
I'll mark this as resolved and chalk it up to a browser issue.