emveepee - I’m a little confused. I get my scan tables via the TVH JSON API.
http://<TVH>:9981/api/dvb/scanfile/list?type=dvb-t
I’m not sure where TVH gets that data from.
Are you saying that in the process of building the LE TVH addon, that LE download and insert the updated scan tables into their build of the TVH server somehow?
On my LE Dev box, I can see the scan files in:
/storage/.kodi/addons/service.tvheadend42/dvb-scan/dvb-t/au-Sydney
/usr/share/dvbv5/dvb-t/au-Sydney
LEDev:~/.kodi/addons/service.tvheadend42/dvb-scan # ls -laF
total 108
drwxr-xr-x 7 root root 4096 Dec 17 07:40 ./
drwxr-xr-x 9 root root 4096 Dec 17 07:41 ../
drwxr-xr-x 2 root root 4096 Dec 17 07:40 atsc/
drwxr-xr-x 2 root root 4096 Dec 17 07:40 dvb-c/
drwxr-xr-x 2 root root 4096 Dec 17 07:40 dvb-s/
drwxr-xr-x 2 root root 36864 Dec 17 07:40 dvb-t/
drwxr-xr-x 2 root root 53248 Dec 17 07:41 isdb-t/
I assume that TVH parses the file name to extract the ISO 3166-1 alpha-2 value and then converts that to the country name for presentation via the API. Alternately, TVH may parse the content of the scan files because there are some location descriptions within the comments. I have not looked into it.
Looking at how the scan table ‘vals’ are composed via the TVH API:
DVB-T = Country:Region
}, {
"key": "dvb-t/auto/dvb-t_auto-With167kHzOffsets",
"val": "--Generic--: auto-With167kHzOffsets"
}, {
"key": "dvb-t/ax/dvb-t_ax-Smedsbole",
"val": "Aland Islands: ax-Smedsbole"
}, {
"key": "dvb-t/ad/dvb-t_ad-Andorra",
"val": "Andorra: ad-Andorra"
}, {
"key": "dvb-t/au/dvb-t_au-Adelaide",
"val": "Australia: au-Adelaide"
}, {
Display More
DVB-C = Country:Cable Provider
}, {
"key": "dvb-c/at/dvb-c_at-Vienna",
"val": "Austria: at-Vienna"
}, {
"key": "dvb-c/be/dvb-c_be-IN.DI-Integan",
"val": "Belgium: be-IN.DI-Integan"
}, {
"key": "dvb-c/br/dvb-c_br-Net-Digital",
"val": "Brazil: br-Net-Digital"
}, {
"key": "dvb-c/hr/dvb-c_hr-B.net",
"val": "Croatia: hr-B.net"
}, {
Display More
DVB-S = Longitude:Satellite name
}, {
"key": "dvb-s/geo/dvb-s_> 76.5E:Telstar10_C",
"val": "> 76.5E:Telstar10_C"
}, {
"key": "dvb-s/geo/dvb-s_> 75.0E:ABS1",
"val": "> 75.0E:ABS1"
}, {
"key": "dvb-s/geo/dvb-s_> 72.0E:Intel4",
"val": "> 72.0E:Intel4"
}, {
ATSC-T = Country:Region or Protocol
}, {
"key": "atsc-t/ca/atsc-t_ca-ON-Toronto",
"val": "Canada: ca-ON-Toronto"
}, {
"key": "atsc-t/us/atsc-t_us-ATSC-center-frequencies-8VSB",
"val": "United States: us-ATSC-center-frequencies-8VSB"
}, {
ATSC-C = Country:Protocol
Harmonic Related Carrier (HRC)
Incremental Related Carrier (IRC)
{
"entries": [{
"key": "atsc-c/us/atsc-c_us-Cable-EIA-542-HRC-center-frequencies-QAM256",
"val": "United States: us-Cable-EIA-542-HRC-center-frequencies-QAM256"
}, {
"key": "atsc-c/us/atsc-c_us-Cable-EIA-542-IRC-center_frequencies-QAM256",
"val": "United States: us-Cable-EIA-542-IRC-center_frequencies-QAM256"
}, {
"key": "atsc-c/us/atsc-c_us-Cable-HRC-center-frequencies-QAM256",
"val": "United States: us-Cable-HRC-center-frequencies-QAM256"
}, {
"key": "atsc-c/us/atsc-c_us-Cable-IRC-center-frequencies-QAM256",
"val": "United States: us-Cable-IRC-center-frequencies-QAM256"
}, {
"key": "atsc-c/us/atsc-c_us-Cable-Standard-center-frequencies-QAM256",
"val": "United States: us-Cable-Standard-center-frequencies-QAM256"
}
]
}
Display More
ISDB-T = Country:Region
}, {
"key": "isdb-t/ar/isdb-t_ar-Argentina",
"val": "Argentina: ar-Argentina"
}, {
"key": "isdb-t/br/isdb-t_br-Brazil",
"val": "Brazil: br-Brazil"
}, {
"key": "isdb-t/br/isdb-t_br-ac-Bujari",
"val": "Brazil: br-ac-Bujari"
}, {
I will make the Wizard split into the same categories provided by the TVH API and label the buttons/steps accordingly.
With respect to users 'getting stuck': Perhaps an extensive 'try every combination' approach would be required. Unfortunately, that could take hours to do a scan. Every mux has a frequency, then several possible bandwidths for that frequency, then several possible encoding parameter variations.
