Project

General

Profile

Forums » General »

Over time, same service ids appearing on different muxs

Added by Paul Freeman over 7 years ago

Hi,
I have a Debian Jessie OS installtion running tvheadend 4.1-2415~ge5f5a42 with a USB Leadtek WinFast DTV Dongle Dual (Afatech AF9033 (DVB-T) and ITE Tech IT913X components).

The system is working well and both adapters are identified and all muxs (6) and sids (39) are found that I would expect. Idle Scan is enabled for both adapters. The two tuners are not linked.

I notice that over time the system ends up with a number of instances of the same sid but on different muxs. This is not the case at initial setup and doesn't seem to happen to all sids. The system has not rebooted during the time this occurs and as far as I know, tvheadend has not restarted either.

I have attached a screen shot from the web interface, "Configuration/DBV Inputs/Services" page showing amongst others, the three services with sid 561 on three different muxs and a sample of debug logs from /var/log/syslog at the time of the creation of these services with sid 561 (nit, sid and pat debugging options enabled).

All of the log entries I have included are at the times specified in the "over the air grabbers" cron entry in "Configurations/Channel EPG/EPG Grabber". So I assume they are related to the process initiated at these times. However, there are a few entries in the log which are at different times.

Looking at the debug entries, I notice some entries related to "TSID change detected". Does this give a clue as to what is going on?

If there is any additional information required to assist debugging this please let me know.

Thanks

Paul

tvheadend_multiple_muxs_same_sids.png (322 KB) tvheadend_multiple_muxs_same_sids.png
tvheadend debug log.txt (81.5 KB) tvheadend debug log.txt

Replies (4)

RE: Over time, same service ids appearing on different muxs - Added by Mark Clarkstone over 7 years ago

It looks like you're receiving more than one transmitter and that secondary transmitter is just a relay/mirror. It seems a bit strange that Tvheadend would even detect them, they must be provided in the NIT from your main transmitter. You can manually add muxes & disable network discovery to prevent this.

You really don't need idle scanning enabled, not unless your provider makes changes to the service every day.

It's also strange seeing UK programming broadcast in Aussie land. Didn't think it would be such a big thing over there xD. All we get over here from AU on the main channels is Neighbours and Home and Away, both of which seem to be sinking fast, at least rating wise.

RE: Over time, same service ids appearing on different muxs - Added by saen acro over 7 years ago

Problem with driver ;(
I see this before only new driver fix it ;(

RE: Over time, same service ids appearing on different muxs - Added by Joe User over 7 years ago

The extra muxes/services are probably appearing because "Network Discovery" is enabled for the network (Melbourne DVB-T) and the provider is sending the information for all the muxes - maybe some are for different regions??

What does "Scan Status" and "Scan Result" show for the extra muxes? Can you play any of the services from the different Frequencies?

If the services you have assigned to channels are the only ones which work (or are the ones with the best signal...) then go to Configuration-> DVB Inputs-> Networks-> and set "Network Discovery" to disabled. Then in Configuration-> DVB Inputs-> muxes, remove the extra muxes. With "Network Discovery" disabled, they should not show up again.

Feb 20 14:04:09 freenas-01 tvheadend[8628]: tbl-base: nit: network 321B (12827) [ABC Melbourne]
Feb 20 14:04:09 freenas-01 tvheadend[8628]: tbl-base: nit:  onid 1010 (4112) tsid 0231 (561) mux <none> (discovery)
Feb 20 14:04:09 freenas-01 tvheadend[8628]: tbl-base: nit:    DVB-T freq 226500000 bw 7MHz cons QAM/64 hier NONE code_rate 3/4:NONE guard 1/16 trans 8k plp_id -1
Feb 20 14:04:09 freenas-01 tvheadend[8628]: mpegts: mux 226.5MHz in Melbourne DVB-T old params DVB-T freq 226500000 bw 7MHz cons QAM/64 hier NONE code_rate 3/4:AUTO guard 1/16 trans 8k plp_id -1 (00000020)
Feb 20 14:04:09 freenas-01 tvheadend[8628]: mpegts: mux 226.5MHz in Melbourne DVB-T new params DVB-T freq 226500000 bw 7MHz cons QAM/64 hier NONE code_rate 3/4:NONE guard 1/16 trans 8k plp_id -1 (00000020)
Feb 20 14:04:09 freenas-01 tvheadend[8628]: tbl-base: nit:  onid 1010 (4112) tsid 0231 (561) mux 226.5MHz in Melbourne DVB-T
Feb 20 14:04:09 freenas-01 tvheadend[8628]: tbl-base: nit:    service 0230 (560) type 01 (1)
Feb 20 14:04:09 freenas-01 tvheadend[8628]: tbl-base: nit:    service 0231 (561) type 01 (1)
Feb 20 14:04:09 freenas-01 tvheadend[8628]: tbl-base: nit:    service 0232 (562) type 01 (1)
Feb 20 14:04:09 freenas-01 tvheadend[8628]: tbl-base: nit:    service 0233 (563) type 01 (1)
Feb 20 14:04:09 freenas-01 tvheadend[8628]: tbl-base: nit:    service 0234 (564) type 01 (1)
Feb 20 14:04:09 freenas-01 tvheadend[8628]: tbl-base: nit:    service 0235 (565) type 19 (25)
Feb 20 14:04:09 freenas-01 tvheadend[8628]: tbl-base: nit:    service 0236 (566) type 02 (2)
Feb 20 14:04:09 freenas-01 tvheadend[8628]: tbl-base: nit:    service 0237 (567) type 02 (2)
Feb 20 14:04:09 freenas-01 tvheadend[8628]: tbl-base: nit:    sid 560 lcn 24
Feb 20 14:04:09 freenas-01 tvheadend[8628]: tbl-base: nit:    sid 561 lcn 2
Feb 20 14:04:09 freenas-01 tvheadend[8628]: tbl-base: nit:    sid 562 lcn 22
Feb 20 14:04:09 freenas-01 tvheadend[8628]: tbl-base: nit:    sid 563 lcn 21
Feb 20 14:04:09 freenas-01 tvheadend[8628]: tbl-base: nit:    sid 564 lcn 23
Feb 20 14:04:09 freenas-01 tvheadend[8628]: tbl-base: nit:    sid 566 lcn 200
Feb 20 14:04:09 freenas-01 tvheadend[8628]: tbl-base: nit:    sid 567 lcn 201
Feb 20 14:04:09 freenas-01 tvheadend[8628]: tbl-base: nit:    sid 565 lcn 20
Feb 20 14:04:09 freenas-01 tvheadend[8628]: tbl-base: nit:  onid 1010 (4112) tsid 0231 (561) mux 184.5MHz in Melbourne DVB-T
Feb 20 14:04:09 freenas-01 tvheadend[8628]: tbl-base: nit:    service 0230 (560) type 01 (1)
Feb 20 14:04:09 freenas-01 tvheadend[8628]: tbl-base: nit:    service 0231 (561) type 01 (1)
Feb 20 14:04:09 freenas-01 tvheadend[8628]: tbl-base: nit:    service 0232 (562) type 01 (1)
Feb 20 14:04:09 freenas-01 tvheadend[8628]: tbl-base: nit:    service 0233 (563) type 01 (1)
Feb 20 14:04:09 freenas-01 tvheadend[8628]: tbl-base: nit:    service 0234 (564) type 01 (1)
Feb 20 14:04:09 freenas-01 tvheadend[8628]: tbl-base: nit:    service 0235 (565) type 19 (25)
Feb 20 14:04:09 freenas-01 tvheadend[8628]: tbl-base: nit:    service 0236 (566) type 02 (2)
Feb 20 14:04:09 freenas-01 tvheadend[8628]: tbl-base: nit:    service 0237 (567) type 02 (2)
Feb 20 14:04:09 freenas-01 tvheadend[8628]: tbl-base: nit:    sid 560 lcn 24
Feb 20 14:04:09 freenas-01 tvheadend[8628]: tbl-base: nit:    sid 561 lcn 2
Feb 20 14:04:09 freenas-01 tvheadend[8628]: tbl-base: nit:    sid 562 lcn 22
Feb 20 14:04:09 freenas-01 tvheadend[8628]: tbl-base: nit:    sid 563 lcn 21
Feb 20 14:04:09 freenas-01 tvheadend[8628]: tbl-base: nit:    sid 564 lcn 23
Feb 20 14:04:09 freenas-01 tvheadend[8628]: tbl-base: nit:    sid 566 lcn 200
Feb 20 14:04:09 freenas-01 tvheadend[8628]: tbl-base: nit:    sid 567 lcn 201
Feb 20 14:04:09 freenas-01 tvheadend[8628]: tbl-base: nit:    sid 565 lcn 20
Feb 20 14:04:09 freenas-01 tvheadend[8628]: tbl-base: nit:  onid 1010 (4112) tsid 0231 (561) mux 557.625MHz in Melbourne DVB-T
Feb 20 14:04:09 freenas-01 tvheadend[8628]: tbl-base: nit:    service 0230 (560) type 01 (1)
Feb 20 14:04:09 freenas-01 tvheadend[8628]: tbl-base: nit:    service 0231 (561) type 01 (1)
Feb 20 14:04:09 freenas-01 tvheadend[8628]: tbl-base: nit:    service 0232 (562) type 01 (1)
Feb 20 14:04:09 freenas-01 tvheadend[8628]: tbl-base: nit:    service 0233 (563) type 01 (1)
Feb 20 14:04:09 freenas-01 tvheadend[8628]: tbl-base: nit:    service 0234 (564) type 01 (1)
Feb 20 14:04:09 freenas-01 tvheadend[8628]: tbl-base: nit:    service 0235 (565) type 19 (25)
Feb 20 14:04:09 freenas-01 tvheadend[8628]: tbl-base: nit:    service 0236 (566) type 02 (2)
Feb 20 14:04:09 freenas-01 tvheadend[8628]: tbl-base: nit:    service 0237 (567) type 02 (2)
Feb 20 14:04:09 freenas-01 tvheadend[8628]: tbl-base: nit:    sid 560 lcn 24
Feb 20 14:04:09 freenas-01 tvheadend[8628]: tbl-base: nit:    sid 561 lcn 2
Feb 20 14:04:09 freenas-01 tvheadend[8628]: tbl-base: nit:    sid 562 lcn 22
Feb 20 14:04:09 freenas-01 tvheadend[8628]: tbl-base: nit:    sid 563 lcn 21
Feb 20 14:04:09 freenas-01 tvheadend[8628]: tbl-base: nit:    sid 564 lcn 23
Feb 20 14:04:09 freenas-01 tvheadend[8628]: tbl-base: nit:    sid 566 lcn 200
Feb 20 14:04:09 freenas-01 tvheadend[8628]: tbl-base: nit:    sid 567 lcn 201
Feb 20 14:04:09 freenas-01 tvheadend[8628]: tbl-base: nit:    sid 565 lcn 20

One note, often when providers are in the process of changing frequencies, they will send multiple mux/service information entries in the nit so people can find the new frequencies easily/automatically. Not sure if that is the case here, or they are just sending all the same info to all regions, which is easier than providing different feeds to different transmitters.

RE: Over time, same service ids appearing on different muxs - Added by Paul Freeman over 7 years ago

Mark, Saen and Joe,
Thank you kindly for your comments and suggestions. I have disabled Idle scan for each adapter in DVB Inputs/TV Adapters and disabled Network Discovery in the DVB Inputs/Networks section. Since doing this I have not had the problems occur again.

Thank you all again.

Regards

Paul

    (1-4/4)