SOLVED: 4K Not playing on Google Streamer

[yeahzoomzoom]

I'm having a hard time getting 4K videos to play on my new Google TV Streamer, and even a harder time finding basic instructions on how to configure the correct transcoding options (and even if I need transcoding.)
When I play the video, I get audio, but the screen stays black. My logfile isn't very informative. The only error I see is:

"[WRN] [156] Emby.Server.Implementations.HttpServer.WebSocketConnection: WS "192.168.0.163" error receiving data: "The remote party closed the WebSocket connection without completing the close handshake."

I know details are important, so here's what I'm working with:

Windows 11
Jellyfin server 10.10.4
NVIDIA 3060Ti


Video file:      video.mkv
Codec:          MPEG-H Part2/HEVC H.265
10 bit
Resolution:    3840x1608
Frame Rate:  23.97 FPS

Jellyfin settings tried:

Transcoding

Test 1
Hardware acceleration off 
Result: audio only, black video

Test 2
Hardware acceleration Nvidia NVENC
Enable hardware decoding for HEVC, HEVC 10bit


Enable enhanced NVDEC decoder

Enable hardware encoding

Allow encoding in HEVC format


In all instances, i got audio only, and no video. and the only error in the log was closed without handshake

All of my 1080p content is playing fine.

I'd greatly appreciate some additional troubleshooting assistance.

Please let me know if I need to provide more details on my hardware setup, my Jellyfin settings, or the video file itself.

Thanks!

[theguymadmax]

This is a known issue caused by a bug in ExoPlayer on devices using the MT8696 MediaTek chipset, which is found in Fire TV 4K Sticks and the latest Google streamer. It occurs when playing media that includes both Dolby Vision and HDR10+. Here are several threads related to this.

AndroidTV
https://github.com/jellyfin/jellyfin-and...ssues/2630 (old issue)
https://github.com/jellyfin/jellyfin-and...ssues/4021 (new issue)

Exoplayer/AndroidX Media
https://github.com/google/exoplayer/issues/11096 (old issue)
https://github.com/androidx/media/issues/1895 (new issue)

Workarounds:

1. Remove DV Metadata: Follow the steps in this forum thread to strip out the Dolby Vision metadata.
   
   Code:

   /usr/lib/jellyfin-ffmpeg/ffmpeg -y -hide_banner -stats -fflags +genpts+igndts -loglevel error -i "/path/to/dvhdr10+_video.mkv" -map 0 -bsf:v hevc_metadata=remove_dovi=1 -codec copy -max_muxing_queue_size 2048 -max_interleave_delta 0 -avoid_negative_ts disabled hdr10_video.mkv
2. Remove HDR10+ Metadata:
   
   Code:

   /usr/lib/jellyfin-ffmpeg/ffmpeg -y -hide_banner -stats -fflags +genpts+igndts -loglevel error -i "/path/to/dvhdr10+_video.mkv" -map 0 -bsf:v hevc_metadata=remove_hdr10plus=1 -codec copy -max_muxing_queue_size 2048 -max_interleave_delta 0 -avoid_negative_ts disabled dv_video.mkv
3. Force Transcoding on ATV: Reduce the bitrate or set audio to stereo to trigger transcoding on the client.
   
4. Use Kodi as an external player for the ATV client: Kodi allows you to choose the format compatible with your TV. You can disable Dolby Vision or HDR10+ as needed.
   
5. Use Kodi with Jellyfin Plugin: Kodi allows you to choose the format compatible with your TV. You can disable Dolby Vision or HDR10+ as needed.
   

[yeahzoomzoom]

This is a known issue caused by a bug in ExoPlayer on devices using the MT8696 MediaTek chipset, which is found in Fire TV 4K Sticks and the latest Google streamer. It occurs when playing media that includes both Dolby Vision and HDR10+. Here are several threads related to this.

AndroidTV
https://github.com/jellyfin/jellyfin-and...ssues/2630 (old issue)
https://github.com/jellyfin/jellyfin-and...ssues/4021 (new issue)

Exoplayer/AndroidX Media
https://github.com/google/exoplayer/issues/11096 (old issue)
https://github.com/androidx/media/issues/1895 (new issue)

Workarounds:

1. Remove DV Metadata: Follow the steps in this forum thread to strip out the Dolby Vision metadata.
   
   Code:

   /usr/lib/jellyfin-ffmpeg/ffmpeg -y -hide_banner -stats -fflags +genpts+igndts -loglevel error -i "/path/to/dvhdr10+_video.mkv" -map 0 -bsf:v hevc_metadata=remove_dovi=1 -codec copy -max_muxing_queue_size 2048 -max_interleave_delta 0 -avoid_negative_ts disabled hdr10_video.mkv
2. Remove HDR10+ Metadata:
   
   Code:

   /usr/lib/jellyfin-ffmpeg/ffmpeg -y -hide_banner -stats -fflags +genpts+igndts -loglevel error -i "/path/to/dvhdr10+_video.mkv" -map 0 -bsf:v hevc_metadata=remove_hdr10plus=1 -codec copy -max_muxing_queue_size 2048 -max_interleave_delta 0 -avoid_negative_ts disabled dv_video.mkv
3. Force Transcoding on ATV: Reduce the bitrate or set audio to stereo to trigger transcoding on the client.
   
4. Use Kodi as an external player for the ATV client: Kodi allows you to choose the format compatible with your TV. You can disable Dolby Vision or HDR10+ as needed.
   
5. Use Kodi with Jellyfin Plugin: Kodi allows you to choose the format compatible with your TV. You can disable Dolby Vision or HDR10+ as needed.
   

Thank you for this detailed response!

Since HDR seems to be a more widely accepted format, i went with the first option of removing the DV metadata. (There is one minor issue with the example provided in that the final file name needs to be enclosed in quotes, but i got it working")

In addition, since I will need to do this with all 4K content that comes in, I wanted to automate this process. So, i utilized ChatGPT to help me build a powershell script to do this. I've created a "watched" folder, and when the 4K file is finished copying into that folder, the ffmpeg command is automatically triggered on the source file and generates the new file with -HDR added to the file name as a suffix.

I've tested this entire workflow, and the videos are playing properly in Google Streamer.

Thanks again for all your help!

[Adrian]

You can user Google Cast also. You need to use Google Cast in the Jellyfin app to the TV and then start the Film. The Film is then playing with hdr10.