Live TV stops after 3 seconds

[JuJuJurassic 49]

So do I have the longest outstanding ticket/support request?

I haven't been able to play Live TV since April, I've upgraded the versions since then. It worked previously, but now doesn't. If anyone can give me some advise on where to look, and what log file. Any help at all, I would be very grateful.

Here's the original post 

 

 

Thanks 

[Luke 42077]

Hi, have you updated to Emby Server 4.8.10? Has that helped?

[JuJuJurassic 49]

Hi, yes it's running 4.8.10

Here's the ffmpeg and the latest embyserver.txt.(and hardware detection)

Thanks

Julian

ffmpeg-transcode-e6521797-5d0a-4177-ac3f-dedb5a63a363_1.txt embyserver (25).txt

hardware_detection-63865121973.txt

Edited October 21, 2024 by JuJuJurassic

[JuJuJurassic 49]

The TV Tuner details are;

HD Homerun
Tuner IP Address
http://xx.xx.xx.xx

Restrict to channels marked as favourite (not ticked)
If enabled, only channels that are marked as favourite on the tuner device will be imported.

Allow hardware transcoding (ticked) <tested both ticked and not ticked>
If enabled, allow the tuner to transcode streams on the fly. This may help reduce transcoding required by Emby Server.
Channels with DRM will not be imported.

[Carlo 4560]

When I look at your log, I'm seeing the transcoder getting corrupt packets from the tuner.
Is the HDHomeRun and your Emby Server both connected via Ethernet?

What HDHomeRun is this you have?
Cable or OTA?

While watching this channel, hat does your HDHomeRun show for:

Signal Strength (ss)
Signal Quality (snq)
Symbol Quality (seq)

(use brower interface, tech3 or hdhomerun_config)

 

[sa2000 674]

Interesting - that is the Emby Web client app on Chrome that decided to stop the playback. It read the first 3 segments from the server stream and then stopped the playback. At this time the ffmpeg transcoder was past the first 3 segments and was writing the 4th segment when its process was aborted because the web app requested to stop.

Does this happen on all TV channels and all emby client apps ? On local devices?

I am extracting the sequence of requests from Emby Web running on Chrome 129 

2024-10-21 18:46:18.949 Info Server: http/2 GET https://emby_remote_ip:8920/emby/videos/5363945/master.m3u8
2024-10-21 18:46:18.992 Info Server: http/2 GET https://emby_remote_ip:8920/emby/videos/5363945/live.m3u8?
2024-10-21 18:46:19.525 Info Server: http/2 GET https://emby_remote_ip:8920/emby/videos/5363945/hls/F6828E/F6828E_0.ts?

2024-10-21 18:46:19.979 Info SessionManager: Playback start reported by app Emby Web 4.8.10.0 on Google Chrome Windows playing BBC ONE Yorks. Started at 0 ms. PlaySessionId: a256bdfb16634fdd8d4eb7947d1b7787

2024-10-21 18:46:20.709 Info Server: http/2 POST https://emby_remote_ip:8920/emby/Sessions/Playing/Progress?

2024-10-21 18:46:22.960 Info Server: http/2 GET https://emby_remote_ip:8920/emby/videos/5363945/live.m3u8
2024-10-21 18:46:22.969 Info Server: http/2 GET https://emby_remote_ip:8920/emby/videos/5363945/hls/F6828E/F6828E_1.ts?
2024-10-21 18:46:25.962 Info Server: http/2 GET https://emby_remote_ip:8920/emby/videos/5363945/live.m3u8?
2024-10-21 18:46:25.970 Info Server: http/2 GET https://emby_remote_ip:8920/emby/videos/5363945/hls/F6828E/F6828E_2.ts?
2024-10-21 18:46:28.951 Info Server: http/2 GET https://emby_remote_ip:8920/emby/videos/5363945/live.m3u8?
2024-10-21 18:46:29.959 Info Server: http/2 POST https://emby_remote_ip:8920/emby/Sessions/Playing/Progress?

and then request from the web app to stop the stream - logged at 18:46:30.338

2024-10-21 18:46:30.338 Info Server: http/2 POST https://emby_remote_ip:8920/emby/Sessions/Playing/Stopped?X-Emby-Client=Emby Web&X-Emby-Device-Name=Google Chrome Windows&X-Emby-Device-Id=0ba41ef1-5a5e-41c3-83aa-0d8f847c7660&X-Emby-Client-Version=4.8.10.0&X-Emby-Token=x_secret1_x&X-Emby-Language=en-gb&reqformat=json. Source Ip: host1, UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/129.0.0.0 Safari/537.36

2024-10-21 18:46:30.344 Info SessionManager: Playback stopped reported by app Emby Web 4.8.10.0 on Google Chrome Windows playing BBC ONE Yorks. Stopped at 3790 ms. PlaySessionId: a256bdfb16634fdd8d4eb7947d1b7787

The ffmpeg transcoder was on the 4th segment at this time

18:46:28.792 [segment @ 0x28a4240] Opening '/var/lib/emby/transcoding-temp/F6828E/F6828E_4.ts.tmp' for writing

There are corrupt packets logged by the transcoder - these were logged after the Emby Web app asked for the stream to stop

18:46:30.346 [mpegts @ 0x27ac600] PES packet size mismatch
18:46:30.346 [mpegts @ 0x27ac600] Packet corrupt (stream = 1, dts = 1172912981).
18:46:30.346 http://127.0.0.1:8096/LiveTv/LiveStreamFiles/86dfdaf69c404a2b8326dcd466f2a98a/stream.ts: corrupt input packet in stream 1
    Last message repeated 1 times
[segment @ 0x28a4240] Opening '/var/lib/emby/transcoding-temp/F6828E/F6828E.m3u8.tmp' for writing
SegmentComplete=video:0 Index=4 Start=12.960000 End=15.600000 Duration=2.640000 offset_pts=0 start_pts=12960000 Frames=66 filename=hls/F6828E/F6828E_4.ts
elapsed=00:00:11.14 frame=  366 fps= 33 q=11.0 Lsize=N/A time=00:00:14.86 bitrate=N/A dup=2 drop=0 throttle=off speed=1.33x    
video:7708kB audio:351kB subtitle:0kB other streams:0kB global headers:0kB muxing overhead: unknown

Would be useful to see what happens with emby apps streaming Live TV and also for different channels - to see if all the client apps abort in the same way (from the logs)

 

Edited October 23, 2024 by sa2000

[JuJuJurassic 49]

Hi Carlo,

Thank you for helping me.

While playing HD home run via the app on my Win 10 laptop, the stats from the device are;

I've hidden the IP Address. It's a freeview, OTA tuner

Tuner 0 Status
Virtual Channel    4 Channel 4
Frequency    658.000 MHz
Program Number    8384
Modulation Lock    t8dvbt
Signal Strength    100%
Signal Quality    100%
Symbol Quality    100%
Streaming Rate    2.179 Mbps
Resource Lock    xx.xx.xx.xx

The HD home run and Emby server are connected over a wired ethernet connection.

Thanks

[JuJuJurassic 49]

Hi sa2000,

Ive tried it from other clients within the lan of the house. I had it wired when it was built, it seems it's just chrome that's got the problem. it works ok from firefox and the firesticks on the TV.

all channels are affected, but only with chrome.

 

[sa2000 674]

19 hours ago, JuJuJurassic said:

it seems it's just chrome that's got the problem. it works ok from firefox and the firesticks on the TV.. 

all channels are affected, but only with chrome.

Well that is progress - so you can now stream Live TV if you avoid using Google Chrome for it.

You could try Google Chrome on the local network and see if there any clues if you run it with the browser dev console enabled (F12) and browser network logging - to see if any clues as to why the Web Client app is stopping playback after reading 3 segments

I am going to attach the streams extra data from the ffmpeg log in case it is needed in any further investigation. The stream is an HLS mpeg2video stream

extradata_from_ffmpeg-transcode-e6521797-5d0a-4177-ac3f-dedb5a63a363_1.txt

Edited October 24, 2024 by sa2000

[JuJuJurassic 49]

Let's close the case. It's a chrome issue, not Emby. Thank you for your help 

[sa2000 674]

2 hours ago, JuJuJurassic said:

Let's close the case. It's a chrome issue, not Emby

I will discuss with the development team to understand more about this hls stream issue

[leetxjd 5]

It isn't an issue with ONLY chrome.  I use firefox and appletv get this same behavior.  I'm going to gather some log files...

[leetxjd 5]

Here are the ffmpeg logs.  I tried with hardware acceleration/transcoding and without it.  Same behavior - 4 seconds of video, it kicks out, then the "throbber" appears and 4 additional seconds of video plays.

 

 

 

ffmpeg-transcode-9fdd5b82-a471-441f-bf86-3a62e5549477_1.txt

ffmpeg-transcode-2b90df72-8b0e-40d8-8930-feec0f03dfb7_1.txt

[sa2000 674]

13 hours ago, leetxjd said:

Here are the ffmpeg logs.

can you please provide the corresponding emby server logs

[sa2000 674]

13 hours ago, leetxjd said:

I tried with hardware acceleration/transcoding and without it.  Same behavior -

Thanks for trying both

Were subtitles in use? Could you repeat the two tests without subtitles and get me logs for these tests as well - server + ffmpeg

Thanks

 

[sa2000 674]

14 hours ago, leetxjd said:

It isn't an issue with ONLY chrome

There may be different issues.

[Carlo 4560]

On 10/28/2024 at 3:03 PM, JuJuJurassic said:

Let's close the case. It's a chrome issue, not Emby. Thank you for your help 

I know this is old but wondering if you ever got Chrome to work?
Did you try Chrome on multiple computers or just one?
Did you try it in MS Edge? Edge and Chrome use the same core.
Have you checked to see if you have the latest firmware on your HDHR?

Did you ever try this in an Incognito/InPrivate window?  This is often helpful as it won't have all the plugins or other features loaded.

I noticed in your ffmpeg logs (ones I saw anyway) the resolution was 704x576 or SD.  Have you tried HD channels as well?

Did you ever check to see if you were running the latest version of Chrome?

It would be interesting to know how this works in Vivaldi as well, as that could shed some light on the possible source of the issue.
Edge, Chome, Vivaldi are all Chromium based browsers. 

Carlo

[Carlo 4560]

On 12/12/2024 at 4:23 PM, leetxjd said:

It isn't an issue with ONLY chrome.  I use firefox and appletv get this same behavior.  I'm going to gather some log files...

It could be related but probably not the same issue. 

@JuJuJurassicis using an HDHomeRun setup directly in Emby while it appears you're using Media Portal as the source.
What's your source setup in Media Portal?

Carlo

[Luke 42077]

@leetxjd?

[JuJuJurassic 49]

Hi Carlo,
Sorry for not getting back to you quicker.

 Quicker.

To be honest when I got it working perfectly with Firefox, I gave up with Chrome. I haven’t investigated it since.

however, I am using HDHomeRun

it works perfectly from the Home run apps, it’s just envy that had the problem with Chrome. Everything is updated to the Nuz version of course.

 Everything is updated to the Nuz version of course.

 

[sa2000 674]

I have the issue with chrome and edge - ok with Firefox but if I disable hardware transcoding chrome and edge work ok 

I am gathering diagnostics for this 

[sa2000 674]

13 hours ago, sa2000 said:

I have the issue with chrome and edge - ok with Firefox but if I disable hardware transcoding chrome and edge work ok 

I am gathering diagnostics for this 

In my case it appears to be limited to Nvidia GPU hardware transcoding and Edge and Chrome.  The issue does not arise for me when Intel QuickSync is used for hardware transcoding

There may be different causes for this