2025-10-24, 03:48 PM
Hi, thanks for finding my GH issue. It seems like nobody on the development team uses the HDHR, which is a real shame.
I have managed to patch jellyfin to use the discardcorrupt feature, but it did not help. Here is a log of what that looks like:
You can see ffmpeg does drop the corrupt packet, but I still get "Error submitting packet to decoder: Invalid data found when processing input" which brings the stream to a stuck black screen.
This has been really frustrating because I ended up paying for emby premiere just so I can use my HDHR... and emby is able to tackle these corrupt packet issues no problem. But I can't find the difference between JF and Emby to copy it over to JF.
I have managed to patch jellyfin to use the discardcorrupt feature, but it did not help. Here is a log of what that looks like:
Code:
frame= 2889 fps= 39 q=22.0 size=N/A time=00:00:44.73 bitrate=N/A speed=0.608x
frame= 2889 fps= 39 q=22.0 size=N/A time=00:00:44.73 bitrate=N/A speed=0.604x
frame= 2889 fps= 39 q=22.0 size=N/A time=00:00:44.73 bitrate=N/A speed= 0.6x
frame= 2889 fps= 39 q=22.0 size=N/A time=00:00:44.73 bitrate=N/A speed=0.596x
[mpegts @ 0x561c8cc13800] PES packet size mismatch
[mpegts @ 0x561c8cc13800] Packet corrupt (stream = 1, dts = 6520092009), dropping it.
[mpeg2video @ 0x561c8edc7a40] slice too small
[vist#0:0/mpeg2video @ 0x561c8dee6ac0] [dec:mpeg2video @ 0x561c8cd835c0] Error submitting packet to decoder: Invalid data found when processing input
[hls @ 0x561c8edc6fc0] Opening '/var/cache/jellyfin/transcodes/6ac185d824c6774fa01b64af06ba7e6215.ts' for writing
[hls @ 0x561c8edc6fc0] Opening '/var/cache/jellyfin/transcodes/6ac185d824c6774fa01b64af06ba7e62.m3u8.tmp' for writing
[hls @ 0x561c8edc6fc0] Opening '/var/cache/jellyfin/transcodes/6ac185d824c6774fa01b64af06ba7e6216.ts' for writing
[hls @ 0x561c8edc6fc0] Opening '/var/cache/jellyfin/transcodes/6ac185d824c6774fa01b64af06ba7e62.m3u8.tmp' for writing
[out#0/hls @ 0x561c8edb8400] video:40079KiB audio:1483KiB subtitle:0KiB other streams:0KiB global headers:0KiB muxing overhead: unknown
frame= 2913 fps= 39 q=-1.0 Lsize=N/A time=00:00:44.82 bitrate=N/A dup=2 drop=0 speed=0.595x
[libx264 @ 0x561c8ea9e480] frame I:17 Avg QP:20.76 size:121845
[libx264 @ 0x561c8ea9e480] frame P:2896 Avg QP:23.80 size: 13456
[libx264 @ 0x561c8ea9e480] mb I I16..4: 100.0% 0.0% 0.0%
[libx264 @ 0x561c8ea9e480] mb P I16..4: 3.7% 0.0% 0.0% P16..4: 32.6% 0.0% 0.0% 0.0% 0.0% skip:63.7%
[libx264 @ 0x561c8ea9e480] coded y,uvDC,uvAC intra: 30.7% 54.0% 21.8% inter: 14.9% 11.9% 1.9%
[libx264 @ 0x561c8ea9e480] i16 v,h,dc,p: 33% 33% 16% 18%
[libx264 @ 0x561c8ea9e480] i8c dc,h,v,p: 35% 33% 20% 12%
[libx264 @ 0x561c8ea9e480] kb/s:6755.85
[aac @ 0x561c8eed59c0] Qavg: 33523.980You can see ffmpeg does drop the corrupt packet, but I still get "Error submitting packet to decoder: Invalid data found when processing input" which brings the stream to a stuck black screen.
This has been really frustrating because I ended up paying for emby premiere just so I can use my HDHR... and emby is able to tackle these corrupt packet issues no problem. But I can't find the difference between JF and Emby to copy it over to JF.