SOLVED: DirectPlay freezing after skipping WebOS

[LodocArt]

Hello everyone! 

This is my first time spinning a jellyfin instance. It's running on a NAS with an Intel Core i5-12500. My main problem is HDR playback on my LG G2 TV, using the native Jellyfin app.

I'm playing a Joker file with these infos :
https://pastebin.com/T01rKztH
(it has more audio and subtitle tracks, however these aren't selected).

If I play the movie, I can pause, resume, and it works great in Direct Play
https://pastebin.com/AQJkHAGt

After skipping in the movie, ffmpeg keeps creating log file, the player just freezes and the movie never resumes. Here is an extract of the log file :
https://pastebin.com/fewPBzuJ

Here is an example of a ffpmeg log :
https://pastebin.com/WhUreXKd

Direct Streaming works great in my browser, and transcoding works on my Android phone (even though the logs and ffmpeg keep repeating).

For further infos, I've tried enabling and disabling "Prefer fMP4-HLS media container".
Here is my docker compose file :
https://pastebin.com/TRS5Jn19

Here is my transcoding settings on Jellyfin :
   


I'm lost with all the possible points of failures. I've followed jellyfin official guide on Intel GPU hardware acceleration, I've been using official docker image, I can't understand what is happening...

Thank you very much by advance! 😊

[TheDreadPirate]

You enabled AV1 encoding, which your 12500 doesn't support. It only supports AV1 decoding.

[LodocArt]

You were right, this fixed the transcoding error! I however still have the problem of Direct Play switching to Transcoding when skipping forward or backward.
https://pastebin.com/J9dBemLF

And ffmpeg logs are clean and simple, enconding the file without any issues.
https://pastebin.com/A9bRtib0

Enabling and disabling Prefer fMP4-HLS media container didn't help. The only thing I find is on the WebOS client, a generic error : "There was an error starting direct playback". I can't find in the logs where is the error stated.

[TheDreadPirate]

I'm getting mixed messages from your log. The ffmpeg log you shared says it is hardware transcoding, but the jellyfin log says it was software transcoding.

Code:

-codec:v:0 libx265

Instead of this from the ffmpeg log.

Code:

-codec:v:0 hevc_qsv

And when you say "NAS", is this a NAS you built? Or a NAS appliance you bought that has a 12500 in it?

Can you share your docker compose file?

[LodocArt]

The NAS is indeed the one I've built with the 12500. For the log messages I think I've mixed up the log files, I've deleted them to generate fresh one, I've edited the previous pastebin so you will get the proper logs!

[TheDreadPirate]

Not sure why it isn't transcoding right away. Dolby Vision 7.6 is not playable by anything accept bluray players. Definitely strange.

[LodocArt]

The strangest thing is that I don't have the Dolby Vision popup on the television, just the regular HDR one. But the colours don't look strange so I thought it was just fallbacking to the regular HDR. Should I open a Github issue then?

[TheDreadPirate]

Submit a bug report on the jellyfin-webos git.

[LodocArt]

Hello again!

I've deleted my Dolby Vision movie because of what a pain it was, and enjoyed Direct Play on normal 1080p HEVC files. However, on my LG G2 WebOS tv, Direct Play stops and transcoding starts when skipping in the movie file. I was able watching an entire tv show episode in Direct Play without any issues, as long as I didn't move in the video file. What I can't understand is where is the TranscodeReason is on the log file, I cannot find it. The LG web browser triggers the transcoding when skipping but doesn't struggle as much when skipping in the video file. And with the Windows client on a computer with a RTX 3080 Ti, Direct Play works even when skipping.

Video file log
https://pastebin.com/uQrKu6ZD

Jellyfin log
https://pastebin.com/KecMYHGc

Ffmpeg log
https://pastebin.com/1mDJ9u1B

Is is just because LG has a shitty codec support and I've screwed with using a Chrome Cast or any other device?

[TheDreadPirate]

Disable "Prefer fMP4" on your TV. This is a known issue for WebOS clients.