Tvheadend not mapping DVB-T/C channels on ARM device (R-Pi 2)

JohnBoyz · December 26, 2018 at 10:47 PM

I set up an E2 type DVB-T bouquet and used the same file on several devices to try to determine why the channels were not mapping.

On an X86_64 device this is installed (8.95.001 9.0 kernel: Linux 4.19.8)

Code

 Build: 4.2.7-34 ~ LibreELEC Tvh-addon v9.0.117 (2018-12-22T10:23:30+0100)

and the channels map correctly.

On an R-Pi 2 device this is installed

Code

Build: 4.2.7-34 ~ LibreELEC Tvh-addon v9.0.117 (2018-12-22T04:21:22-0500)

and no channels are seen or mapped.

I also tried CoreElec on a Tanix Tx3 Amlogic device

Code

Build: 4.2.7-34 ~ CoreELEC Tvh-addon v9.0.117 (2018-12-04T16:11:11+0000)

and again no channels were seen or mapped.

All devices were using the latest releases I could locate - both LE & CE.

It would appear that there is either something amiss in the ARM build of tvheadend (LE & CE use a similar build?), else there might be a problem with the ARM version of tvheadend.

The format of the DVB-T file entries are like this

Code

#SERVICE 1:0:1:452:3E9:2174:EEEE0000:0:0:0

In all cases the DVB-S E2 type bouquet worked as expected.

All devices I tested were on the same LAN, and using the same HDHomeRun tuner.

I hope this can be looked at, thanks.

**CvH** · December 27, 2018 at 1:13 PM Official Post

could you share an log of generic and arm ?

just try to map the same stuff that works at generic but not at arm

JohnBoyz · December 27, 2018 at 6:49 PM

Quote from CvH

could you share an log of generic and arm ?

just try to map the same stuff that works at generic but not at arm

I have never had to get logs before so I am unsure what you need.

Here is the tvheadend output in the browser when I enable the DVB-T bouquet on the X86_64 device

Code

2018-12-27 18:41:13.225 http: 127.0.0.1: HTTP/1.1 HEAD /imagecache/129 -- 404
2018-12-27 18:41:19.247 bouquet: DVB-T Network/746MHz/RTÉ One: mapped service from   My DBV-T
2018-12-27 18:41:19.248 bouquet: DVB-T Network/690MHz/RTÉ2: mapped service from   My DBV-T
2018-12-27 18:41:19.248 bouquet: DVB-T Network/690MHz/Virgin Media 1: mapped service from   My DBV-T
2018-12-27 18:41:19.248 bouquet: DVB-T Network/690MHz/Virgin Media 2: mapped service from   My DBV-T
2018-12-27 18:41:19.248 bouquet: DVB-T Network/746MHz/Virgin Media 3: mapped service from   My DBV-T
2018-12-27 18:41:19.248 bouquet: DVB-T Network/690MHz/TG4: mapped service from   My DBV-T
2018-12-27 18:41:19.249 bouquet: DVB-T Network/746MHz/RTÉ Junior: mapped service from   My DBV-T
2018-12-27 18:41:19.249 bouquet: DVB-T Network/746MHz/RTÉ One +1: mapped service from   My DBV-T
2018-12-27 18:41:19.249 bouquet: DVB-T Network/690MHz/RTÉ News Now: mapped service from   My DBV-T
2018-12-27 18:41:19.249 bouquet: DVB-T Network/690MHz/Tithe an Oireachtais: mapped service from   My DBV-T
2018-12-27 18:41:19.249 bouquet: DVB-T Network/802MHz/SKY-BOX: mapped service from   My DBV-T
2018-12-27 18:41:19.249 bouquet: parsed Enigma2 bouquet   My DBV-T (11 services)
2018-12-27 18:41:20.279 http: 127.0.0.1: HTTP/1.1 HEAD /imagecache/128 -- 404

Display More

Is that what you wished to see?

The corresponding ARM output was this

Code

2018-12-22 14:47:59.403 bouquet: parsed Enigma2 bouquet My DVB-T (0 services)

If you require something more please be as specific as possible as I have never accessed logs previously, thanks.

**CvH** · December 28, 2018 at 6:48 PM Official Post

Quote from JohnBoyz

I have never had to get logs before so I am unsure what you need.

there is a service.log at here - just open and copy it to pastebin.com for example

JohnBoyz · December 28, 2018 at 7:32 PM

This is from the CE Tanix Tx3 mini device

https://pastebin.com/raw/cserqscr

I will add the R-Pi2 LE equivalent soon I hope ......

Here it is

https://pastebin.com/raw/4z971zhi

The DVB-S bouquet has not been loaded deliberately to keep the output short.

JohnBoyz · December 30, 2018 at 7:11 PM

This really has me puzzled.

I went looking at some tvheadend files to compare, taken from the different installs.

Concentrating on the bouquet files for comparison this is what I find ...

The ARM device with no DVB-T services seen has the following in its bouquet file:

Code

{
"enabled": true,
"maptoch": true,
"mapopt": [
],
"chtag": [
"bouquet_tag"
],
"chtag_ref": "",
"name": "My DVB-T",
"ext_url": "file:///storage/.kodi/userdata/Bouquets/My_DVB-T.tv",
"ssl_peer_verify": false,
"ext_url_period": 60,
"source": "exturl://e6a7f341de0e65301af3697442316b79",
"services": {
},
"services_seen": 0,
"comment": "file:///storage/.kodi/userdata/Bouquets/My_DVB-T.tv",
"lcn_off": 1
}

Display More

If I add a DVB-S entry to that file, it is seen and the file contents reflect it:

Code

{
"enabled": true,
"maptoch": true,
"mapopt": [
"mapradio"
],
"chtag": [
"bouquet_tag"
],
"chtag_ref": "5f1efc004861b1244d7612d8afe094ef",
"name": "My DVB-T",
"ext_url": "file:///storage/.kodi/userdata/Bouquets/My_DVB-T.tv",
"ssl_peer_verify": false,
"ext_url_period": 60,
"source": "exturl://e6a7f341de0e65301af3697442316b79",
"services": {
"3f99409cc5d8c63d026af9f8fcb5a8ef": {
"lcn": 1000000
}
},
"services_seen": 1,
"comment": "file:///storage/.kodi/userdata/Bouquets/My_DVB-T.tv",
"lcn_off": 1
}

Display More

This is what the corresponding file looks like from the X86_64 install where all 11 entries are 'seen'

Code

{
"enabled": true,
"maptoch": true,
"mapopt": [
],
"chtag": [
"bouquet_tag"
],
"chtag_ref": "3018d08c05e9d2298a4958e1a410e278",
"name": "  My DBV-T",
"ext_url": "file:///home/<user-name>/.kodi/userdata/Bouquets/My_DVB-T.tv",
"ssl_peer_verify": false,
"ext_url_period": 60,
"source": "exturl://68ca3455b141128214fbb001ee10097e",
"services": {
"252f889f764061a8712e1df40e287f0d": {
"lcn": 11000000
},
"5bc05b56f281da5a61f75f97c582842d": {
"lcn": 9000000
},
"04b26e95d0d833ba336e76a3c70fe202": {
"lcn": 4000000
},
"884836f329e613aebae1a427d7566315": {
"lcn": 6000000
},
"a0ee4ac1872c1205f98a4da57ffbef6e": {
"lcn": 2000000
},
"a3d5a828b8b7c244f2aa59f04ed37505": {
"lcn": 3000000
},
"0bf5b5d98e7af23449fe4420341d91df": {
"lcn": 10000000
},
"cdbf3d17eeaa8c87fa7b321f8829c040": {
"lcn": 1000000
},
"f5eedad73b61a249544df40b83952e96": {
"lcn": 5000000
},
"e8e4a912d9dcb06080efbeb8ded7d80f": {
"lcn": 7000000
},
"6a39ace3a19423530b10a9609359b430": {
"lcn": 8000000
}
},
"services_seen": 11,
"comment": "file:///home/<user-name>/.kodi/userdata/Bouquets/My_DVB-T.tv",
"lcn_off": 1
}

Display More

Maybe the above added information will generate some idea where this is going wrong ... I can always hope

JohnBoyz · January 1, 2019 at 11:54 AM

CvH

Is there anything I can do that might help locate the source of this problem?

Thanks.

JohnBoyz · January 8, 2019 at 12:42 PM

Has any progress been made on determining the cause of this issue? (From other reports it affects DVB-C as well as DVB-T automapping)

Even if it is known where the problem is generated (during build or in tvheadend code) that would be very useful in trying to progress a solution.

Thanks.

JohnBoyz · January 10, 2019 at 5:13 PM

Is it possible to get a tvheadend build with this patch included for testing?

Bug #5387: External Bouquet for DVB-C/T does not see any services - Tvheadend