Live TV Freezing - but only one channel

[jad3675 26]

My setup:

Emby  4.7.11.0 on Ubuntu 20.04

HDHR5-4US Tuner

Viewing Client is Emby App on FireTV

 

I have the HDHR and TVE setup in Channels-DVR and I export all of the channels as m3u. Emby consumes it with this as a source:

http://192.168.1.25:8089/devices/ANY/channels.m3u?format=ts&filter=favorites

I do not have the HDHR setup in Emby as a standalone device.

This issue only appears to happen with a local channel (19.1 and its sub channels). It occurs both with the FireTV client and the web browser. It does not happen if I view the stream in VLC (http://192.168.1.25:8089/devices/ANY/channels/19.1/stream.mpg?format=ts&filter=favorites) or from the Channels-DVR web client. It usually takes around 15 minutes before it freezes in Emby.

I've attached the log, but here's where it gets wonky:

08:42:17.778 [segment @ 0xe3a740] Opening '/home/emby/transcoding-temp/38D6AA/38D6AA.m3u8.tmp' for writing
08:42:17.779 SegmentComplete=video:0 Index=292 Start=876.790700 End=879.359922 Duration=2.569222 offset_pts=0 start_pts=
876790700 Frames=157 filename=hls/38D6AA/38D6AA_292.ts
08:42:17.779 [segment @ 0xe3a740] Opening '/home/emby/transcoding-temp/38D6AA/38D6AA_293.ts.tmp' for writing
08:42:17.977 elapsed=00:14:36.18 frame=52700 fps= 60 q=-1.0 size=N/A time=00:14:34.56 bitrate=N/A throttle=off speed=0.9
98x
08:42:18.480 elapsed=00:14:36.68 frame=52735 fps= 60 q=-1.0 size=N/A time=06:46:56.33 bitrate=N/A throttle=off speed=27.
9x
08:42:18.480 [mpegts @ 0xe2b7c0] DTS 2525619718 < 4644697452 out of order
08:42:18.480 [segment @ 0xe3a740] Non-monotonous DTS in output stream 0:0; previous: 2198365146, current: 79287412; chan
ging to 2198365147. This may result in incorrect timestamps in the output file.

And it goes on from there.

 

The only thing I've noticed is that the signal quality on the tuner isn't quite 100% on the HDHR tuner status screen - it's hovering around 91%. Strength is 90% and Symbol Quality is 100%.

 

Turning debug on in VLC while watching the channel:

ts warning: discontinuity received 0x5 instead of 0x4 (pid=49)

ts debug: transport_error_indicator set (pid=49)

ts warning: discontinuity received 0x9 instead of 0x8 (pid=49)

main warning: picture is too late to be displayed (missing 51 ms)

ts debug: transport_error_indicator set (pid=53)

ts warning: discontinuity received 0x4 instead of 0x3 (pid=49)

main warning: picture is too late to be displayed (missing 50 ms)

 

It would appear it's a signal issue - just the Emby can't handle it as well as VLC or channels-dvr.

John

 

 

 

 

ffmpeg-directstream-6c039369-88e9-428a-a4bf-e12dfb7467cc_1.txt

Edited January 7, 2023 by jad3675

[Luke 42085]

@jad3675

Hi.  Can you try sideloading our standard android app on the same device and see how that compares?

https://emby.media/emby-for-android.html

Thanks.

 

[jad3675 26]

12 hours ago, Luke said:

@jad3675

Hi.  Can you try sideloading our standard android app on the same device and see how that compares?

https://emby.media/emby-for-android.html

Thanks.

 

Thanks Luke. Same issue with the sideloaded app.

 

John

[Luke 42085]

@jad3675 can you please attach the corresponding emby server log? Thanks.

[jad3675 26]

On 1/11/2023 at 5:22 PM, Luke said:

@jad3675 can you please attach the corresponding emby server log? Thanks.

I've attached the server log and the transcode log. I had it streaming in Chrome window.

ffmpeg-transcode-c3184a52-2b41-45e6-82cc-af5b43ae1675_1.txt issue_embyserver.txt