Closed jesusfj710 closed 2 weeks ago
I have tried with version 1.0.0 and the same
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.
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 andts
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?
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
)This is the message I can see on the DLNA session created with the TV:
However, it does not work. It shows an error on the tv. The logs from jellyfin says something like this:
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.
In Chrome I get directPlay, which makes sense since there is support for x256.
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.