+- Jellyfin Forum (https://forum.jellyfin.org)
+-- Forum: Support (https://forum.jellyfin.org/f-support)
+--- Forum: Troubleshooting (https://forum.jellyfin.org/f-troubleshooting)
+--- Thread: Live tv seems to be borked in 0.16.4 (/t-live-tv-seems-to-be-borked-in-0-16-4)
Live tv seems to be borked in 0.16.4 - Caseywalt39 - 2024-01-17
Hello!
I guess I have two separate issues on 0.16.4 that are not present on 0.15.12. Hopefully I can help out in anyway to assist in getting these issues resolved. I am using the latest 10.8.13 Jellyfin server an an ubuntu 22.04 VM.
- The live tv option for "disable transcoding" does not work. I tried this on an Onn 4k box and a tcl android tv. Checking the box does nothing. If exo player is selected the screen just shows black and there is sound. Previously this worked just fine. Also using VIMU player works just fine. Both these TV's have MPEG2 support and are local to the jellyfin server, so it shouldn't be transcoding live tv ever.
- Second issue. Might be related. Sometimes I can get a direct stream to play. If it does start after a few seconds it will show "too many errors. Giving up".
Where would I pull the logs from to show what is going on? Id be more than happy to assist with this.
RE: Live tv seems to be borked in 0.16.4 - tmsrxzar - 2024-01-17
(2024-01-17, 06:57 PM)Caseywalt39 Wrote:
- The live tv option for "disable transcoding" does not work. I tried this on an Onn 4k box and a tcl android tv. Checking the box does nothing. If exo player is selected the screen just shows black and there is sound. Previously this worked just fine. Also using VIMU player works just fine. Both these TV's have MPEG2 support and are local to the jellyfin server, so it shouldn't be transcoding live tv ever.
what is your bandwidth limit set to in the android app?
if auto; this is largely broken
(2024-01-17, 06:57 PM)Caseywalt39 Wrote:
- Second issue. Might be related. Sometimes I can get a direct stream to play. If it does start after a few seconds it will show "too many errors. Giving up".
this is consistent with media that contains subtitles, PGS/ASS especially
provide your jellyfin server log and it should at least show the Transcode Reason as to why the client requested the transcode
RE: Live tv seems to be borked in 0.16.4 - Caseywalt39 - 2024-01-17
I have noticed problems before with the bandwidth set to auto. So i have it set at 100mbps.
Ill get those logs over to you. I just recreated it and have them. I'm just new to the forum
. Still figuring it out.
RE: Live tv seems to be borked in 0.16.4 - tmsrxzar - 2024-01-17
any public paste site will do, ensure it is redacted where needed
https://sourceb.in
RE: Live tv seems to be borked in 0.16.4 - Caseywalt39 - 2024-01-17
See attached. I only included data from 2 hours ago till now to get under the 200KB size limit.
I started direct playing (via VIMU) at 15:15. I changed the player to exo player and tried again. This time it transcoded.
RE: Live tv seems to be borked in 0.16.4 - tmsrxzar - 2024-01-17
according to what your device requested from the server none of it was supported, not the container, the video or the audio
PlayMethod=Transcode, TranscodeReason=ContainerNotSupported, VideoCodecNotSupported, AudioCodecNotSupported
last i checked none of that is configurable in the android-tv app
from that, since it's not configurable, i only have a couple suggestions
1. revert to the last version that worked and file an issue on github; i know there is a pending PR that should enable configuring
2. verify nothing changed in the live streams
3. try with using libvlc as the player; the only downside i am aware of is no dolby vision but you won't get them from live tv any way
RE: Live tv seems to be borked in 0.16.4 - TheDreadPirate - 2024-01-17
Looks like some of your streams are CPU transcoding.
Code:
PlayMethod=Transcode, TranscodeReason=ContainerNotSupported, VideoCodecNotSupported, AudioCodecNotSupportedCode:
[2024-01-17 15:16:37.387 -05:00] [INF] "/usr/lib/jellyfin-ffmpeg/ffmpeg" "-analyzeduration 3000000 -user_agent \"Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/64.0.3282.85 Safari/537.36\" -fflags +igndts -f mpegts -autorotate 0 -i \"http://10.0.0.106:8096/LiveTv/LiveStreamFiles/91bd48e01a8e4c85868668c0eca9ca40/stream.ts\" -map_metadata -1 -map_chapters -1 -threads 16 -sn -codec:v:0 libx264 -preset ultrafast -crf 33 -maxrate 20000000 -bufsize 40000000 -x264opts:0 subme=0:me_range=4:rc_lookahead=10:me=dia:no_chroma_me:8x8dct=0:partitions=none -force_key_frames:0 \"expr:gte(t,n_forced*3)\" -sc_threshold:v:0 0 -vfThis part, specifically. "-codec:v:0 libx264". It looks like it is transcoding fine, but not clear how quickly.
Can you share the ffmpeg log associated with this?
RE: Live tv seems to be borked in 0.16.4 - Caseywalt39 - 2024-01-17
(2024-01-17, 08:41 PM)tmsrxzar Wrote: according to what your device requested from the server none of it was supported, not the container, the video or the audio
PlayMethod=Transcode, TranscodeReason=ContainerNotSupported, VideoCodecNotSupported, AudioCodecNotSupported
last i checked none of that is configurable in the android-tv app
from that, since it's not configurable, i only have a couple suggestions
1. revert to the last version that worked and file an issue on github; i know there is a pending PR that should enable configuring
2. verify nothing changed in the live streams
3. try with using libvlc as the player; the only downside i am aware of is no dolby vision but you won't get them from live tv any way
I was afraid of these answers. I'm just going to continue using vimu for now. VLC audio is very far off and I really don't feel like messing with the timing. It will never be right on HAHA. Really the only downside of vimu is that I have to exit playback to get to the guide. That's not a huge deal.
I did not see before that it thinks none of this is supported. MPEG2, AC3 are 100% supported by the TV and work on the previous versions. Also in vimu.
RE: Live tv seems to be borked in 0.16.4 - Caseywalt39 - 2024-01-17
(2024-01-17, 08:43 PM)TheDreadPirate Wrote: Looks like some of your streams are CPU transcoding.
Code:PlayMethod=Transcode, TranscodeReason=ContainerNotSupported, VideoCodecNotSupported, AudioCodecNotSupported
Code:[2024-01-17 15:16:37.387 -05:00] [INF] "/usr/lib/jellyfin-ffmpeg/ffmpeg" "-analyzeduration 3000000 -user_agent \"Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/64.0.3282.85 Safari/537.36\" -fflags +igndts -f mpegts -autorotate 0 -i \"http://10.0.0.106:8096/LiveTv/LiveStreamFiles/91bd48e01a8e4c85868668c0eca9ca40/stream.ts\" -map_metadata -1 -map_chapters -1 -threads 16 -sn -codec:v:0 libx264 -preset ultrafast -crf 33 -maxrate 20000000 -bufsize 40000000 -x264opts:0 subme=0:me_range=4:rc_lookahead=10:me=dia:no_chroma_me:8x8dct=0:partitions=none -force_key_frames:0 \"expr:gte(t,n_forced*3)\" -sc_threshold:v:0 0 -vf
This part, specifically. "-codec:v:0 libx264". It looks like it is transcoding fine, but not clear how quickly.
Can you share the ffmpeg log associated with this?
I can. I guess I should be more clear about this. It does play fine when it transcodes. My issue is that it should not be transcoding at all. I also have the transcoding quality set very low since this is a VM and no dedicated HW transcoding options.
So its very obvious when it starts transcoding. It looks terrible. But that's on purpose.