Bug #2822
Mux scan fails sometimes
0%
Description
Currently testing latest builds of tvheadend on RPi2 with Milhouse test builds (OpenElec).
It seems at some point after build 3.9.2690 signal strength has decreased even though nothing has changed physically with aerial position or location (UK DVB-T), Muxes which previous scanned fine are now failing to find anything. I have included some screenshots of my settings and also the status panel which shows the current signal about -86 this was previously at ~(-50)
I understand the signal strength is pretty bad anyway at -50% but it was working fine with no issues until moving to a more recent build on tvheadend. Has something changed in the latest commits which could of affected this?
Files
History
Updated by Wesley Ellis over 9 years ago
Also on another point should the signal strength be showing as -50% or 50%?
Updated by B C over 9 years ago
Reception quality should only be influenced by firmware/drivers, depending on your stick these come from either a newer kernel or drivers/firmware updated in OpenElec. If nothing is found at all it could be a tvh problem for sure but as I understand it just some are not working. Can you compare if the failing muxes are still detected with the same parameters in tvh?
Updated by Jaroslav Kysela over 9 years ago
The negative percentual presentation is wrong. It should be positive.
Updated by Jaroslav Kysela over 9 years ago
Could you turn on the 'force old status' in the adapter settings ?
Updated by Wesley Ellis over 9 years ago
- File Screenshot from 2015-05-06 10_38_14.png Screenshot from 2015-05-06 10_38_14.png added
- File Screenshot from 2015-05-06 10_38_22.png Screenshot from 2015-05-06 10_38_22.png added
That seems to have made things better. Just one mux failing now. Status panel also seems correct.
FYI am using the Sony PlayTV Adapter.
Any reason why that mux could be failing, haven't changed anything in the settings for it and it was previously fine?
Updated by Wesley Ellis over 9 years ago
Left it for a 5 mins and now that mux is working but two others aren't, strange...
Updated by Wesley Ellis over 9 years ago
and after another 5 mins or so, its changed which muxes have failed again.
Updated by Rafal Kupiec over 9 years ago
Wesley Ellis wrote:
and after another 5 mins or so, its changed which muxes have failed again.
Same here, on both DVB-T and DVB-S.
Also sometimes it is impossible to switch channel... Kodi says buffering all the time.
Updated by Jaroslav Kysela over 9 years ago
I can do hardly something without logs. Like:
2015-05-12 08:58:41.000 [ TRACE]:mpegts: 482MHz in DVB-T - scan needs more time 2015-05-12 08:58:41.382 [ INFO]:mpegts: 482MHz in DVB-T scan complete 2015-05-12 08:58:41.382 [ DEBUG]:mpegts: 482MHz in DVB-T - 1000 (4096) pmt complete 2015-05-12 08:58:41.382 [ DEBUG]:mpegts: 482MHz in DVB-T - 0900 (2304) pmt complete 2015-05-12 08:58:41.382 [ DEBUG]:mpegts: 482MHz in DVB-T - 1250 (4688) pmt complete 2015-05-12 08:58:41.382 [ DEBUG]:mpegts: 482MHz in DVB-T - 1900 (6400) pmt complete 2015-05-12 08:58:41.382 [ DEBUG]:mpegts: 482MHz in DVB-T - 1A00 (6656) pmt complete 2015-05-12 08:58:41.382 [ DEBUG]:mpegts: 482MHz in DVB-T - 1700 (5888) pmt complete 2015-05-12 08:58:41.382 [ DEBUG]:mpegts: 482MHz in DVB-T - 0500 (1280) pmt complete 2015-05-12 08:58:41.382 [ DEBUG]:mpegts: 482MHz in DVB-T - 1400 (5120) pmt complete 2015-05-12 08:58:41.382 [ DEBUG]:mpegts: 482MHz in DVB-T - 0200 (512) pmt complete 2015-05-12 08:58:41.382 [ DEBUG]:mpegts: 482MHz in DVB-T - 1800 (6144) pmt complete 2015-05-12 08:58:41.382 [ DEBUG]:mpegts: 482MHz in DVB-T - 0011 (17) sdt complete 2015-05-12 08:58:41.382 [ DEBUG]:mpegts: 482MHz in DVB-T - 0001 (1) cat complete 2015-05-12 08:58:41.382 [ DEBUG]:mpegts: 482MHz in DVB-T - 0000 (0) pat complete
Updated by Jaroslav Kysela over 9 years ago
- Subject changed from Loss of signal stength since latest builds to Mux scan fails sometimes
Updated by Wesley Ellis over 9 years ago
Just done a manual scan on Build: 3.9.2825~gae281c9 and it looks as if the issue maybe resolved. No muxes have failed yet. I will monitor the issue further today.
2015-05-12 11:40:45.489 [ INFO]:mpegts: 682MHz in SD - tuning on DiBcom 7000PC : DVB-T #0 2015-05-12 11:40:45.489 [ INFO]:subscription: 001A: "scan" subscribing to mux "682MHz", weight: 6, adapter: "DiBcom 7000PC : DVB-T #0", network: "SD", service: "Raw PID Subscription" 2015-05-12 11:40:59.289 [ INFO]:mpegts: 682MHz in SD scan complete 2015-05-12 11:40:59.289 [ INFO]:subscription: 001A: "scan" unsubscribing 2015-05-12 11:40:59.291 [ INFO]:mpegts: 690MHz in SD - tuning on DiBcom 7000PC : DVB-T #0 2015-05-12 11:40:59.291 [ INFO]:subscription: 001C: "scan" subscribing to mux "690MHz", weight: 6, adapter: "DiBcom 7000PC : DVB-T #0", network: "SD", service: "Raw PID Subscription" 2015-05-12 11:41:12.869 [ INFO]:mpegts: 690MHz in SD scan complete 2015-05-12 11:41:12.870 [ INFO]:subscription: 001C: "scan" unsubscribing 2015-05-12 11:41:12.873 [ INFO]:mpegts: 714MHz in SD - tuning on DiBcom 7000PC : DVB-T #0 2015-05-12 11:41:12.873 [ INFO]:subscription: 001E: "scan" subscribing to mux "714MHz", weight: 6, adapter: "DiBcom 7000PC : DVB-T #0", network: "SD", service: "Raw PID Subscription" 2015-05-12 11:41:24.981 [ INFO]:mpegts: 714MHz in SD scan complete 2015-05-12 11:41:24.981 [ INFO]:subscription: 001E: "scan" unsubscribing 2015-05-12 11:41:24.983 [ INFO]:mpegts: 722MHz in SD - tuning on DiBcom 7000PC : DVB-T #0 2015-05-12 11:41:24.983 [ INFO]:subscription: 0020: "scan" subscribing to mux "722MHz", weight: 6, adapter: "DiBcom 7000PC : DVB-T #0", network: "SD", service: "Raw PID Subscription" 2015-05-12 11:41:37.716 [ INFO]:mpegts: 722MHz in SD scan complete 2015-05-12 11:41:37.717 [ INFO]:subscription: 0020: "scan" unsubscribing 2015-05-12 11:41:37.719 [ INFO]:mpegts: 754MHz in SD - tuning on DiBcom 7000PC : DVB-T #0 2015-05-12 11:41:37.719 [ INFO]:subscription: 0022: "scan" subscribing to mux "754MHz", weight: 6, adapter: "DiBcom 7000PC : DVB-T #0", network: "SD", service: "Raw PID Subscription" 2015-05-12 11:41:51.809 [ INFO]:mpegts: 754MHz in SD scan complete 2015-05-12 11:41:51.809 [ INFO]:subscription: 0022: "scan" unsubscribing
Updated by Wesley Ellis over 9 years ago
are here we are. I have idle scanning turned off at the moment. But I just scanned manually again and some are failing.
2015-05-12 11:46:48.332 [ INFO]:mpegts: 658MHz in SD - tuning on DiBcom 7000PC : DVB-T #1 2015-05-12 11:46:48.332 [ INFO]:subscription: 002C: "scan" subscribing to mux "658MHz", weight: 6, adapter: "DiBcom 7000PC : DVB-T #1", network: "SD", service: "Raw PID Subscription" 2015-05-12 11:46:48.333 [ INFO]:mpegts: 682MHz in SD - tuning on DiBcom 7000PC : DVB-T #0 2015-05-12 11:46:48.334 [ INFO]:subscription: 002D: "scan" subscribing to mux "682MHz", weight: 6, adapter: "DiBcom 7000PC : DVB-T #0", network: "SD", service: "Raw PID Subscription" 2015-05-12 11:46:49.636 [WARNING]:linuxdvb: DiBcom 7000PC : DVB-T #0 - poll TIMEOUT 2015-05-12 11:46:53.000 [ INFO]:mpegts: 682MHz in SD - scan no data, failed 2015-05-12 11:46:53.000 [ INFO]:subscription: 002D: "scan" unsubscribing 2015-05-12 11:46:53.003 [ INFO]:mpegts: 690MHz in SD - tuning on DiBcom 7000PC : DVB-T #0 2015-05-12 11:46:53.004 [ INFO]:subscription: 002F: "scan" subscribing to mux "690MHz", weight: 6, adapter: "DiBcom 7000PC : DVB-T #0", network: "SD", service: "Raw PID Subscription" 2015-05-12 11:46:54.307 [WARNING]:linuxdvb: DiBcom 7000PC : DVB-T #0 - poll TIMEOUT 2015-05-12 11:46:58.000 [ INFO]:mpegts: 690MHz in SD - scan no data, failed 2015-05-12 11:46:58.000 [ INFO]:subscription: 002F: "scan" unsubscribing 2015-05-12 11:46:58.003 [ INFO]:mpegts: 714MHz in SD - tuning on DiBcom 7000PC : DVB-T #0 2015-05-12 11:46:58.003 [ INFO]:subscription: 0031: "scan" subscribing to mux "714MHz", weight: 6, adapter: "DiBcom 7000PC : DVB-T #0", network: "SD", service: "Raw PID Subscription" 2015-05-12 11:47:01.539 [ INFO]:mpegts: 658MHz in SD scan complete 2015-05-12 11:47:01.539 [ INFO]:subscription: 002C: "scan" unsubscribing 2015-05-12 11:47:01.541 [ INFO]:mpegts: 722MHz in SD - tuning on DiBcom 7000PC : DVB-T #1 2015-05-12 11:47:01.541 [ INFO]:subscription: 0033: "scan" subscribing to mux "722MHz", weight: 6, adapter: "DiBcom 7000PC : DVB-T #1", network: "SD", service: "Raw PID Subscription" 2015-05-12 11:47:09.989 [ INFO]:mpegts: 714MHz in SD scan complete 2015-05-12 11:47:09.989 [ INFO]:subscription: 0031: "scan" unsubscribing 2015-05-12 11:47:09.992 [ INFO]:mpegts: 754MHz in SD - tuning on DiBcom 7000PC : DVB-T #0 2015-05-12 11:47:09.992 [ INFO]:subscription: 0035: "scan" subscribing to mux "754MHz", weight: 6, adapter: "DiBcom 7000PC : DVB-T #0", network: "SD", service: "Raw PID Subscription" 2015-05-12 11:47:12.532 [ INFO]:mpegts: 722MHz in SD scan complete 2015-05-12 11:47:12.533 [ INFO]:subscription: 0033: "scan" unsubscribing 2015-05-12 11:47:22.000 [ INFO]:mpegts: 754MHz in SD scan complete 2015-05-12 11:47:22.000 [ INFO]:subscription: 0035: "scan" unsubscribing
Updated by Wesley Ellis over 9 years ago
And scanned again, you can see that the previous muxes that failed now work. and others have failed.
2015-05-12 11:49:43.680 [ INFO]:mpegts: 658MHz in SD - tuning on DiBcom 7000PC : DVB-T #1 2015-05-12 11:49:43.680 [ INFO]:subscription: 0036: "scan" subscribing to mux "658MHz", weight: 6, adapter: "DiBcom 7000PC : DVB-T #1", network: "SD", service: "Raw PID Subscription" 2015-05-12 11:49:43.680 [ INFO]:mpegts: 682MHz in SD - tuning on DiBcom 7000PC : DVB-T #0 2015-05-12 11:49:43.680 [ INFO]:subscription: 0037: "scan" subscribing to mux "682MHz", weight: 6, adapter: "DiBcom 7000PC : DVB-T #0", network: "SD", service: "Raw PID Subscription" 2015-05-12 11:49:48.000 [ INFO]:mpegts: 682MHz in SD - scan complete 2015-05-12 11:49:48.000 [ INFO]:subscription: 0037: "scan" unsubscribing 2015-05-12 11:49:48.003 [ INFO]:mpegts: 690MHz in SD - tuning on DiBcom 7000PC : DVB-T #0 2015-05-12 11:49:48.003 [ INFO]:subscription: 0039: "scan" subscribing to mux "690MHz", weight: 6, adapter: "DiBcom 7000PC : DVB-T #0", network: "SD", service: "Raw PID Subscription" 2015-05-12 11:49:56.541 [ INFO]:mpegts: 658MHz in SD scan complete 2015-05-12 11:49:56.541 [ INFO]:subscription: 0036: "scan" unsubscribing 2015-05-12 11:49:56.543 [ INFO]:mpegts: 714MHz in SD - tuning on DiBcom 7000PC : DVB-T #1 2015-05-12 11:49:56.543 [ INFO]:subscription: 003B: "scan" subscribing to mux "714MHz", weight: 6, adapter: "DiBcom 7000PC : DVB-T #1", network: "SD", service: "Raw PID Subscription" 2015-05-12 11:49:57.801 [WARNING]:linuxdvb: DiBcom 7000PC : DVB-T #1 - poll TIMEOUT 2015-05-12 11:50:01.000 [ INFO]:mpegts: 714MHz in SD - scan no data, failed 2015-05-12 11:50:01.000 [ INFO]:subscription: 003B: "scan" unsubscribing 2015-05-12 11:50:01.004 [ INFO]:mpegts: 722MHz in SD - tuning on DiBcom 7000PC : DVB-T #1 2015-05-12 11:50:01.005 [ INFO]:subscription: 003D: "scan" subscribing to mux "722MHz", weight: 6, adapter: "DiBcom 7000PC : DVB-T #1", network: "SD", service: "Raw PID Subscription" 2015-05-12 11:50:02.816 [ INFO]:mpegts: 690MHz in SD scan complete 2015-05-12 11:50:02.816 [ INFO]:subscription: 0039: "scan" unsubscribing 2015-05-12 11:50:02.820 [ INFO]:mpegts: 754MHz in SD - tuning on DiBcom 7000PC : DVB-T #0 2015-05-12 11:50:02.820 [ INFO]:subscription: 003F: "scan" subscribing to mux "754MHz", weight: 6, adapter: "DiBcom 7000PC : DVB-T #0", network: "SD", service: "Raw PID Subscription" 2015-05-12 11:50:12.495 [ INFO]:mpegts: 722MHz in SD scan complete 2015-05-12 11:50:12.495 [ INFO]:subscription: 003D: "scan" unsubscribing 2015-05-12 11:50:16.958 [ INFO]:mpegts: 754MHz in SD scan complete 2015-05-12 11:50:16.958 [ INFO]:subscription: 003F: "scan" unsubscribing
Let me know if you need anymore info, I can build tvheadend and test new code if needed.
Updated by Wesley Ellis over 9 years ago
I just rescanned only the mux that failed, and it works again now.
2015-05-12 11:51:57.016 [ INFO]:mpegts: 714MHz in SD - tuning on DiBcom 7000PC : DVB-T #1 2015-05-12 11:51:57.016 [ INFO]:subscription: 0040: "scan" subscribing to mux "714MHz", weight: 6, adapter: "DiBcom 7000PC : DVB-T #1", network: "SD", service: "Raw PID Subscription" 2015-05-12 11:52:09.922 [ INFO]:mpegts: 714MHz in SD scan complete 2015-05-12 11:52:09.923 [ INFO]:subscription: 0040: "scan" unsubscribing
Updated by Jaroslav Kysela over 9 years ago
It looks like the driver fault. Could you upgrade to v3.9-2826-gcd8fe91, enable the "--trace mpegts" and retrigger this issue ?
Updated by Wesley Ellis over 9 years ago
This is how openelec starts tvheadend, so to enable tracing am I right in thinking this is correct? guessing it can't be done from frontend of tvheadend.
1. kill active pid for tvheadend
2. start with:
tvheadend -B -C -u root -g video -c /storage/.kodi/userdata/addon_data/service.multimedia.tvheadend --trace mpegts
Updated by Wesley Ellis over 9 years ago
Ok, took me a while to figure out I needed to compile tvheadend with trace enabled in Openelec
Logs are attached and shows the issue first scan some muxes fail, second scan some muxes succeed that had just failed and others fail now.
Let me know if you need more info.
Updated by Wesley Ellis over 9 years ago
I just manually scanned in only the failed muxes this time, I have ok status on all muxes now. Log attached.
Updated by Jaroslav Kysela over 9 years ago
No input data from the driver:
2015-05-13 08:17:21.017 [ INFO]:mpegts: 682MHz in SD - tuning on DiBcom 7000PC : DVB-T #0 2015-05-13 08:17:21.017 [ DEBUG]:mpegts: 682MHz in SD - started 2015-05-13 08:17:22.316 [WARNING]:linuxdvb: DiBcom 7000PC : DVB-T #0 - poll TIMEOUT 2015-05-13 08:17:26.001 [ INFO]:mpegts: 682MHz in SD - scan no data, failed 2015-05-13 08:17:26.001 [ INFO]:subscription: 000C: "scan" unsubscribing
You may try to activate some workarounds like 'Tune Repeats' (try value 1 or 2).
Updated by Jaroslav Kysela over 9 years ago
See that the other input received data correctly:
2015-05-13 08:17:21.599 [ TRACE]:mpegts: input DiBcom 7000PC : DVB-T #1 got 18800 bytes
Updated by Erik R over 9 years ago
Hi,
I can confirm the same problem.
TVHeadend fails to read anything from some MUXes but MythTV and Kaffeine works fine (our most important MUX )
I use a DiBcom 700PC device as well but I do not think it is the driver because I can repeat the problem using a Terratec T2 device as well. Both are connected to USB though.
In Kaffeine I can see that the signal strength is only 30%.
Updated by Erik R over 9 years ago
By the way, I have this problem on on stable version 3.4.27 as well as the most recent version that is tagged in GIT.
Updated by Jaroslav Kysela over 9 years ago
There is timeout (5 seconds) - if no data are received in this time windows, tvh takes the input as broken. Anyway, I cannot do anything without logs.
Updated by John Swanson about 9 years ago
- File tvheadend_forced_1success.log tvheadend_forced_1success.log added
- File tvheadend_forced_1success-set_oldstatus+tune_repeats_3+status_period_2000.log tvheadend_forced_1success-set_oldstatus+tune_repeats_3+status_period_2000.log added
- File tvheadend_forced_3success-tune_repeats_3.log tvheadend_forced_3success-tune_repeats_3.log added
- File tvheadend_forced_4success-set_oldstatus.log tvheadend_forced_4success-set_oldstatus.log added
- File tvheadend_forced_5success-set_oldstatus+tune_repeats_3.log tvheadend_forced_5success-set_oldstatus+tune_repeats_3.log added
- File tvheadend_forced_5success-set_oldstatus+tune_repeats_3+status_period_500.log tvheadend_forced_5success-set_oldstatus+tune_repeats_3+status_period_500.log added
- File tvheadend_vanilla.log tvheadend_vanilla.log added
Jaroslav Kysela wrote:
There is timeout (5 seconds) - if no data are received in this time windows, tvh takes the input as broken. Anyway, I cannot do anything without logs.
Hi there,
I can confirm the problem, too. I have tried 3.9.XXX, 4.0.3 and 4.0.5-17 from http://sources.openelec.tv/devel/.
All three showed these strange problems with the DiBcom7000PC. Further I cannot watch any Live TV... well once it works it judders and eventually stops playing...
I can remember, that I had no such severe problems with OpenELEC 5.0.8< on my RPi1.
Anyways, as you said Jaroslav you cannot work without logs, so here are some with mpegts traces:
(All stem from TVHeadend 4.0.5-17 builds; not mentioned settings are set to default; if you need further data, pls request)