jellyfin / jellyfin-plugin-dlna

GNU General Public License v3.0
15 stars 12 forks source link

Issue when reproducing transcoded content via DLNA #65

Closed jesusfj710 closed 2 weeks ago

jesusfj710 commented 2 months ago

Hello there,

I have some content on x265.

Because my tv does not support x256, I have the transcoding by hardware enabled. Looks like its working just fine (colors for HDR looks really odd but its ok for now).

This is the config I have in Jellyfin (docker 10.9.7) image

This is the message I can see on the DLNA session created with the TV: image

However, it does not work. It shows an error on the tv. The logs from jellyfin says something like this:

[2024-07-03 17:33:44.684 +02:00] [INF] Authentication request for "admin" has succeeded.
[2024-07-03 17:33:44.685 +02:00] [INF] Current/Max sessions for user "admin": 1/0
[2024-07-03 17:33:44.687 +02:00] [INF] Creating new access token for user e2e57aed-c38a-45a0-8b55-ddd9235b203b
[2024-07-03 17:33:44.769 +02:00] [INF] WS "192.168.1.241" request
[2024-07-03 17:34:14.953 +02:00] [INF] DLNA Session created for "[TV] Jesús tv" - "UE55RU7172UXXH"
[2024-07-03 17:34:26.883 +02:00] [INF] "/usr/lib/jellyfin-ffmpeg/ffmpeg" "-analyzeduration 200M -probesize 1G -ss 02:15:42.165  -i file:\"/mnt/media/movies/MOVIE_WOLOLO/WOLOLO (2019)  - Imax [WEBRip-2160p][HDR10][TrueHD Atmos 7.1][x265]-MgB.mkv\" -vn -map 0:1 -map -0:s -codec:v:0 copy -map_metadata -1 -map_chapters -1 -threads 0 -codec:a:0 ac3 -ac 6 -ab 640000 -y \"/var/cache/jellyfin/transcodes/3be97ad2e329a4a0fe4a02e2fb1bcdb2.ts\""
[2024-07-03 17:34:39.319 +02:00] [INF] Transcoding kill timer stopped for JobId "ee36dca7a9b3414e87fde5d15af51c15" PlaySessionId null. Killing transcoding
[2024-07-03 17:34:39.319 +02:00] [INF] Stopping ffmpeg process with q command for "/var/cache/jellyfin/transcodes/3be97ad2e329a4a0fe4a02e2fb1bcdb2.ts"
[2024-07-03 17:34:39.380 +02:00] [INF] FFmpeg exited with code 0
[2024-07-03 17:34:39.381 +02:00] [INF] Deleting partial stream file(s) "/var/cache/jellyfin/transcodes/3be97ad2e329a4a0fe4a02e2fb1bcdb2.ts"
[2024-07-03 17:34:39.859 +02:00] [INF] WS "192.168.1.123" closed
[2024-07-03 17:34:40.075 +02:00] [INF] WS "192.168.1.123" request

If I try to direct play on Safari on MacOs (which does not support x256 either) I can see how the transcoding does works and the video just reproduce it correctly.

image

In Chrome I get directPlay, which makes sense since there is support for x256.

image

To be honest, I don't know where to look, I would love some help to dig deeper in more logs or something. BTW, x254 files does work with DLAN in the same tv just fine.

jesusfj710 commented 2 months ago

I have tried with version 1.0.0 and the same

gabrielsoldani commented 2 months ago

I'm having exactly the same issue. ffmpeg parameter -codec:v:0 copy indicates it's not transcoding the video at all, it's simply copying the HEVC stream, so the TV fails to decode it.

In my case, it's a Samsung TV, so the built-in transcoding profile specifies the h264 video codec, ac3 audio codec and ts container. And you can see it's looks like it's applying that transcoding profile, as it is transcoding the audio to AC3, but it should also be transcoding the video to H264.

jesusfj710 commented 2 months ago

I'm having exactly the same issue. ffmpeg parameter -codec:v:0 copy indicates it's not transcoding the video at all, it's simply copying the HEVC stream, so the TV fails to decode it.

In my case, it's a Samsung TV, so the built-in transcoding profile specifies the h264 video codec, ac3 audio codec and ts container. And you can see it's looks like it's applying that transcoding profile, as it is transcoding the audio to AC3, but it should also be transcoding the video to H264.

Did you find any way to solve/workaround this?