Bug #5670
open
why tv headend channels freez in channels change
Added by Faizan khan almost 6 years ago. Updated almost 6 years ago.
0%
Description
kindly tell me why stream my client 2 to 3 clients stream start another user come old stream stop or frezz why kindly tell me why i am use letet verserion HTS Tvheadend 4.3-1795~g771dfd6be~bionic. my resolve my issue. only 1 client or 1 connection strea in iptv service channel stream good no stop no issue after 2 to 3 clients come chanenls stop and freez old connection bandwitdh show 0.
Files
| tv headend 1.png (70.2 KB) tv headend 1.png | Faizan khan, 2019-07-02 15:55 | ||
| tv headend 2.png (63.7 KB) tv headend 2.png | Faizan khan, 2019-07-02 15:55 | ||
| tv headend 4.png (64.8 KB) tv headend 4.png | Faizan khan, 2019-07-02 15:55 | ||
| tv headend 3.png (63.3 KB) tv headend 3.png | Faizan khan, 2019-07-02 15:55 | ||
| tv headend 5.png (81.1 KB) tv headend 5.png | Faizan khan, 2019-07-02 15:59 |
Updated by Flole Systems almost 6 years ago
Provide trace logs and verify with a packet capture if the source is stopping sending data or if tvheadend is no longer forwarding.
Updated by saen acro almost 6 years ago
Do we have to guess what hardware you have, connections you made, scenario you realised.
Most of IPTV providers allow ONE connection from IP.
Updated by Faizan khan almost 6 years ago
saen acro wrote:
Do we have to guess what hardware you have, connections you made, scenario you realised.
Most of IPTV providers allow ONE connection from IP.
Dear sir i have 10 channels connection. i used simple iptv one bye one add stream now issue resolve.But some times out bandwidth 0 in put bandwitdh come i dont know why.kindly help me
My hardware server Machine Dell power edge 720 24 core cpu 24gb of ram.
Updated by Faizan khan almost 6 years ago
Faizan khan wrote:
saen acro wrote:
Do we have to guess what hardware you have, connections you made, scenario you realised.
Most of IPTV providers allow ONE connection from IP.
Dear sir i have 10 channels connection. i used simple iptv one bye one add stream now issue resolve.But some times out bandwidth 0 in put bandwitdh come i dont know why.kindly help me
My hardware server Machine Dell power edge 720 24 core cpu 24gb of ram.
kindly add option stream break then retry again link auto retry stream link and channel play auto after timeout issue
Updated by Faizan khan almost 6 years ago
Flole Systems wrote:
Provide trace logs and verify with a packet capture if the source is stopping sending data or if tvheadend is no longer forwarding.
2019-07-01 20:12:34.351 subscription: 008F: "HTTP" unsubscribing from "Hum tv World", hostname="172.16.70.193", username="admin", client="Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/75.0.3770.100 Safari/537.36"
2019-07-01 20:12:35.127 mpegts: Ptv Home in Ptv Home - tuning on IPTV #1
2019-07-01 20:12:35.127 subscription: 0090: "HTTP" subscribing on channel "Ptv Home", weight: 150, adapter: "IPTV #1", network: "Ptv Home", mux: "Ptv Home", provider: "FFmpeg", service: "Service01", profile="webtv-h264-aac-matroska", hostname="172.16.70.193", username="admin", client="Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/75.0.3770.100 Safari/537.36"
2019-07-01 20:12:39.700 transcode: 008C: 01:H264: > Copy
2019-07-01 20:12:39.700 transcode: 008C: 02:MPEG2AUDIO: > Using profile webtv-vorbis
2019-07-01 20:12:39.967 transcode: 008C: 02:VORBIS: [mp2 => vorbis]: Detected framedrop in audio (80276 != 80652)
2019-07-01 20:12:39.992 transcode: 008C: 02:VORBIS: [mp2 => vorbis]: Detected framedrop in audio (113664 != 113275)
2019-07-01 20:12:39.992 libav: AVCodecContext: Queue input is backward in time
2019-07-01 20:12:40.299 transcode: 008C: 02:VORBIS: [mp2 => vorbis]: Detected framedrop in audio (443397 != 443540)
2019-07-01 20:12:40.340 transcode: 008C: 02:VORBIS: [mp2 => vorbis]: Detected framedrop in audio (493059 != 492918)
2019-07-01 20:12:40.340 libav: AVCodecContext: Queue input is backward in time
2019-07-01 20:12:41.406 transcode: 008C: 02:VORBIS: [mp2 => vorbis]: Detected framedrop in audio (608461 != 608845)
2019-07-01 20:12:41.447 transcode: 008C: 02:VORBIS: [mp2 => vorbis]: Detected framedrop in audio (658363 != 657963)
2019-07-01 20:12:41.447 libav: AVCodecContext: Queue input is backward in time
2019-07-01 20:12:50.133 transcode: 008C: 02:VORBIS: [mp2 => vorbis]: Detected framedrop in audio (969222 != 969377)
2019-07-01 20:12:50.173 transcode: 008C: 02:VORBIS: [mp2 => vorbis]: Detected framedrop in audio (1018895 != 1018675)
2019-07-01 20:12:50.173 libav: AVCodecContext: Queue input is backward in time
2019-07-01 20:12:50.214 transcode: 008C: 02:VORBIS: [mp2 => vorbis]: Detected framedrop in audio (1068193 != 1068434)
2019-07-01 20:12:50.253 transcode: 008C: 02:VORBIS: [mp2 => vorbis]: Detected framedrop in audio (1117952 != 1117742)
2019-07-01 20:12:50.253 libav: AVCodecContext: Queue input is backward in time
2019-07-01 20:12:50.293 transcode: 008C: 02:VORBIS: [mp2 => vorbis]: Detected framedrop in audio (1167261 != 1167861)
2019-07-01 20:12:50.319 transcode: 008C: 02:VORBIS: [mp2 => vorbis]: Detected framedrop in audio (1200873 != 1200214)
2019-07-01 20:12:50.319 libav: AVCodecContext: Queue input is backward in time
2019-07-01 20:12:50.358 transcode: 008C: 02:VORBIS: [mp2 => vorbis]: Detected framedrop in audio (1249732 != 1249883)
2019-07-01 20:12:50.398 transcode: 008C: 02:VORBIS: [mp2 => vorbis]: Detected framedrop in audio (1299402 != 1299261)
2019-07-01 20:12:50.398 libav: AVCodecContext: Queue input is backward in time
2019-07-01 20:12:50.427 transcode: 008C: 02:VORBIS: [mp2 => vorbis]: Detected framedrop in audio (1332273 != 1332614)
2019-07-01 20:12:50.465 transcode: 008C: 02:VORBIS: [mp2 => vorbis]: Detected framedrop in audio (1382132 != 1381832)
2019-07-01 20:12:50.465 libav: AVCodecContext: Queue input is backward in time
2019-07-01 20:12:51.485 transcode: 008C: 02:VORBIS: [mp2 => vorbis]: Detected framedrop in audio (1513881 != 1514155)
2019-07-01 20:12:51.526 transcode: 008C: 02:VORBIS: [mp2 => vorbis]: Detected framedrop in audio (1563673 != 1563373)
2019-07-01 20:12:51.526 libav: AVCodecContext: Queue input is backward in time
2019-07-01 20:12:59.707 transcode: 008C: 02:VORBIS: [mp2 => vorbis]: Detected framedrop in audio (1612892 != 1613133)
2019-07-01 20:12:59.842 transcode: 008C: 02:VORBIS: [mp2 => vorbis]: Detected framedrop in audio (1662651 != 1662431)
2019-07-01 20:12:59.842 libav: AVCodecContext: Queue input is backward in time
2019-07-01 20:13:00.107 transcode: 008C: 02:VORBIS: [mp2 => vorbis]: Detected framedrop in audio (1789764 != 1789945)
2019-07-01 20:13:00.147 transcode: 008C: 02:VORBIS: [mp2 => vorbis]: Detected framedrop in audio (1839464 != 1839254)
2019-07-01 20:13:00.147 libav: AVCodecContext: Queue input is backward in time
2019-07-01 20:13:00.188 transcode: 008C: 02:VORBIS: [mp2 => vorbis]: Detected framedrop in audio (1888772 != 1889282)
2019-07-01 20:13:00.216 transcode: 008C: 02:VORBIS: [mp2 => vorbis]: Detected framedrop in audio (1922294 != 1921817)
2019-07-01 20:13:00.216 libav: AVCodecContext: Queue input is backward in time
2019-07-01 20:13:00.322 transcode: 008C: 02:VORBIS: [mp2 => vorbis]: Detected framedrop in audio (2053866 != 2054306)
2019-07-01 20:13:00.359 transcode: 008C: 02:VORBIS: [mp2 => vorbis]: Detected framedrop in audio (2103825 != 2103346)
2019-07-01 20:13:00.359 libav: AVCodecContext: Queue input is backward in time
2019-07-01 20:13:00.399 transcode: 008C: 02:VORBIS: [mp2 => vorbis]: Detected framedrop in audio (2152864 != 2153013)
2019-07-01 20:13:00.441 transcode: 008C: 02:VORBIS: [mp2 => vorbis]: Detected framedrop in audio (2202532 != 2202391)
2019-07-01 20:13:00.441 libav: AVCodecContext: Queue input is backward in time
2019-07-01 20:13:00.466 transcode: 008C: 02:VORBIS: [mp2 => vorbis]: Detected framedrop in audio (2235403 != 2235756)
2019-07-01 20:13:00.508 transcode: 008C: 02:VORBIS: [mp2 => vorbis]: Detected framedrop in audio (2285274 != 2284964)
2019-07-01 20:13:00.508 libav: AVCodecContext: Queue input is backward in time
2019-07-01 20:13:01.270 transcode: 008C: 02:VORBIS: [mp2 => vorbis]: Detected framedrop in audio (2417013 != 2417195)
2019-07-01 20:13:01.310 transcode: 008C: 02:VORBIS: [mp2 => vorbis]: Detected framedrop in audio (2466714 != 2466503)
2019-07-01 20:13:01.310 libav: AVCodecContext: Queue input is backward in time
2019-07-01 20:13:06.029 transcode: 008C: 02:VORBIS: [mp2 => vorbis]: Detected framedrop in audio (2692873 != 2693075)
2019-07-01 20:13:06.124 transcode: 008C: 02:VORBIS: [mp2 => vorbis]: Detected framedrop in audio (2742594 != 2742296)
2019-07-01 20:13:06.149 transcode: 008C: 02:VORBIS: [mp2 => vorbis]: Detected framedrop in audio (2775308 != 2775458)
2019-07-01 20:13:06.191 transcode: 008C: 02:VORBIS: [mp2 => vorbis]: Detected framedrop in audio (2824975 != 2824835)
2019-07-01 20:13:06.191 libav: AVCodecContext: Queue input is backward in time
2019-07-01 20:13:06.228 transcode: 008C: 02:VORBIS: [mp2 => vorbis]: Detected framedrop in audio (2874353 != 2874706)
2019-07-01 20:13:07.064 transcode: 008C: 02:VORBIS: [mp2 => vorbis]: Detected framedrop in audio (2924225 != 2923915)
2019-07-01 20:13:07.064 libav: AVCodecContext: Queue input is backward in time
2019-07-01 20:13:12.004 transcode: 008C: 02:VORBIS: [mp2 => vorbis]: Detected framedrop in audio (3138494 != 3138797)
2019-07-01 20:13:12.044 transcode: 008C: 02:VORBIS: [mp2 => vorbis]: Detected framedrop in audio (3188315 != 3188017)
2019-07-01 20:13:12.044 libav: AVCodecContext: Queue input is backward in time
2019-07-01 20:13:12.193 transcode: 008C: 02:VORBIS: [mp2 => vorbis]: Detected framedrop in audio (3320066 != 3320235)
2019-07-01 20:13:12.235 transcode: 008C: 02:VORBIS: [mp2 => vorbis]: Detected framedrop in audio (3369754 != 3369546)
2019-07-01 20:13:12.235 libav: AVCodecContext: Queue input is backward in time
Updated by Faizan khan almost 6 years ago
Flole Systems wrote:
Provide trace logs and verify with a packet capture if the source is stopping sending data or if tvheadend is no longer forwarding.
2019-07-02 08:28:04.734 parser: Jalwaa/Jalwaa/Service01: H264 @ #256: DTS and PCR diff is very big (797400)
2019-07-02 08:28:04.734 tsfix: transport stream H264, DTS discontinuity. DTS = 51303120, last = 50575920
2019-07-02 08:28:04.855 tsfix: transport stream AAC-LATM, DTS discontinuity. DTS = 51315840, last = 50588160
how to fix this issue?
Updated by Faizan khan almost 6 years ago
Flole Systems wrote:
Provide trace logs and verify with a packet capture if the source is stopping sending data or if tvheadend is no longer forwarding.
kindly check stream time out waiting for packet how to auto retry
2019-07-02 11:27:48.124 subscription: 0022: "HTTP" unsubscribing from "Astro Cricket", hostname="172.16.77.247", client="Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/75.0.3770.100 Safari/537.36"
2019-07-02 11:27:49.506 subscription: 0024: "HTTP" subscribing on channel "Astro Cricket", weight: 150, adapter: "IPTV #2", network: "Astro Cricket HD", mux: "Astro Cricket HD", provider: "FFmpeg", service: "Service01", profile="webtv-h264-aac-matroska", hostname="172.16.77.247", client="Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/75.0.3770.100 Safari/537.36"
2019-07-02 11:28:10.126 webui: Stop streaming /stream/channel/f42fbe9ad609c04d91c6f74c7574ba0e?profile=webtv-h264-aac-matroska, timeout waiting for packets
2019-07-02 11:28:10.126 subscription: 0024: "HTTP" unsubscribing from "Astro Cricket", hostname="172.16.77.247", client="Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/75.0.3770.100 Safari/537.36"
2019-07-02 11:28:42.986 subscription: 0005: "HTTP" unsubscribing from "Astro Cricket", hostname="172.16.61.106", client="Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/75.0.3770.100 Safari/537.36"
Updated by Faizan khan almost 6 years ago
Faizan khan wrote:
Flole Systems wrote:
Provide trace logs and verify with a packet capture if the source is stopping sending data or if tvheadend is no longer forwarding.
2019-07-02 08:28:04.734 parser: Jalwaa/Jalwaa/Service01: H264 @ #256: DTS and PCR diff is very big (797400)
2019-07-02 08:28:04.734 tsfix: transport stream H264, DTS discontinuity. DTS = 51303120, last = 50575920
2019-07-02 08:28:04.855 tsfix: transport stream AAC-LATM, DTS discontinuity. DTS = 51315840, last = 50588160how to fix this issue?
2019-07-02 14:11:43.309 webui: Stop streaming /stream/channel/f42fbe9ad609c04d91c6f74c7574ba0e?profile=webtv-h264-aac-matroska, timeout waiting for packets
2019-07-02 14:11:43.309 subscription: 0128: "HTTP" unsubscribing from "Astro Cricket", hostname="172.16.61.106", client="Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/75.0.3770.100 Safari/537.36"
how to fix this issue. 2019-07-02 14:11:43.309 webui: Stop streaming /stream/channel/f42fbe9ad609c04d91c6f74c7574ba0e?profile=webtv-h264-aac-matroska, timeout waiting for packets
Updated by Faizan khan almost 6 years ago
Faizan khan wrote:
Faizan khan wrote:
Flole Systems wrote:
Provide trace logs and verify with a packet capture if the source is stopping sending data or if tvheadend is no longer forwarding.
2019-07-02 08:28:04.734 parser: Jalwaa/Jalwaa/Service01: H264 @ #256: DTS and PCR diff is very big (797400)
2019-07-02 08:28:04.734 tsfix: transport stream H264, DTS discontinuity. DTS = 51303120, last = 50575920
2019-07-02 08:28:04.855 tsfix: transport stream AAC-LATM, DTS discontinuity. DTS = 51315840, last = 50588160how to fix this issue?
2019-07-02 14:11:43.309 webui: Stop streaming /stream/channel/f42fbe9ad609c04d91c6f74c7574ba0e?profile=webtv-h264-aac-matroska, timeout waiting for packets
2019-07-02 14:11:43.309 subscription: 0128: "HTTP" unsubscribing from "Astro Cricket", hostname="172.16.61.106", client="Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/75.0.3770.100 Safari/537.36"how to fix this issue. 2019-07-02 14:11:43.309 webui: Stop streaming /stream/channel/f42fbe9ad609c04d91c6f74c7574ba0e?profile=webtv-h264-aac-matroska, timeout waiting for packets
kindly check
2019-07-02 15:16:14.678 webui: Stop streaming /stream/channel/048c209650bfff4d5fcf80fd353bcf7c?profile=webtv-h264-vorbis-mp4, muxer reported errors
2019-07-02 15:16:14.684 subscription: 010E: "HTTP" unsubscribing from "ptv sports", hostname="172.16.76.1", client="Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/75.0.3770.100 Safari/537.36"
2019-07-02 15:16:14.715 subscription: 017D: "HTTP" subscribing on channel "ptv sports", weight: 125, adapter: "IPTV #3", network: "Ptv sports", mux: "ptv sports", provider: "FFmpeg", service: "Service01", profile="webtv-h264-vorbis-mp4", hostname="172.16.51.79", client="Mozilla/5.0 (Windows NT 6.1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/75.0.3770.100 Safari/537.36"
2019-07-02 15:16:16.296 subscription: 017B: "HTTP" unsubscribing from "ptv sports", hostname="172.16.51.79", client="Mozilla/5.0 (Windows NT 6.1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/75.0.3770.100 Safari/537.36"
2019-07-02 15:16:16.725 mkv: Live stream: Write failed -- Connection timed out
2019-07-02 15:16:16.725 mkv: Live stream: Write failed -- Connection timed out
2019-07-02 15:16:16.726 webui: Stop streaming /stream/channel/f42fbe9ad609c04d91c6f74c7574ba0e?profile=webtv-h264-aac-matroska, muxer reported errors
2019-07-02 15:16:16.726 webui: Stop streaming /stream/channel/f42fbe9ad609c04d91c6f74c7574ba0e?profile=webtv-h264-aac-matroska, muxer reported errors
Updated by saen acro almost 6 years ago
You have network issues of incoming streams, or streaming service send you incorrectly compressed streams.
Updated by Faizan khan almost 6 years ago
- File tv headend 1.png tv headend 1.png added
- File tv headend 2.png tv headend 2.png added
- File tv headend 3.png tv headend 3.png added
- File tv headend 4.png tv headend 4.png added
saen acro wrote:
You have network issues of incoming streams, or streaming service send you incorrectly compressed streams.
kindly send me stream settings i send you screen shots
Updated by Faizan khan almost 6 years ago
- File tv headend 5.png tv headend 5.png added
Faizan khan wrote:
saen acro wrote:
You have network issues of incoming streams, or streaming service send you incorrectly compressed streams.
kindly send me stream settings i send you screen shots
Updated by Flole Systems almost 6 years ago
Fix your network issues and especially verify using a capture if the source stopped sending data.
This issue can be closed as its not an issue with tvheadend.
Updated by Faizan khan almost 6 years ago
Flole Systems wrote:
Fix your network issues and especially verify using a capture if the source stopped sending data.
This issue can be closed as its not an issue with tvheadend.
Ok i understand kindly add option if connection or packet time out stream stop and auto retry. Beacuse stream packet timeout stream freez. Then i stop stream again start work fine. In vlc without tv headend auto retry stream in vlc
Updated by Flole Systems almost 6 years ago
There is already an option for that.
Updated by Faizan khan almost 6 years ago
Flole Systems wrote:
There is already an option for that.
Help me Kindly tell me where is the option and tell me the name of option.
Updated by Faizan khan almost 6 years ago
Faizan khan wrote:
Flole Systems wrote:
There is already an option for that.
Help me Kindly tell me where is the option and tell me the name of option.
kindly tell me where is the option in tvheadend and tell name plzzz
Updated by Faizan khan almost 6 years ago
Flole Systems wrote:
There is already an option for that.
Kindly tell me where is the option in tvheadend and tell me the name?