Tvheadend

Could you retest with v3.9-2467-g83d05d4 ?

Jaroslav Kysela wrote:

Could you retest with v3.9-2467-g83d05d4 ?

Thanks for helping,

It seems that I still need to add the fastscan mux and enable autodiscovery, scanning still takes around 15 minutes.
But, it seems that the oribital position shows 0.0 instead of 19.2E if I add that mux manually.

Also I still need to add that fastscan mux?

I'm not aware of the intended behavior but here is how it works on a linux stb:
1) Do your disecq setup, AA=19.2E, AB=23.5E, BB=28.2E (fastscan from tvvlaanden and canaldigitaal should point to services on 23.5E and 28.2E too)
2) Select HD or SD list and scan
3) After 30 second you'll have these and only these services: http://www.tv-vlaanderen.be/uploadedFiles/Prospect/Klantenservice/Downloads/Zenderlijst_TV_VLAANDEREN.pdf
Y

Are you sure that you need to enable auto-discovery when you add the initial mux with the fastscan tables manually ? My changes should force the mux addition for the fastscan tables.

The initial mux with fastscan table must be added manually or autodiscovered using the scan tables - the mux parameters are not in the fastscan configuration file (it seems like a duplicate information - scan tables).

My motivation to add the fastscan was for bouquets / local channel numbers. The mux discovery is something "extra", because auto-discovery is used more widely.

For keeping testing simple I only added 1 network (19.2E)

Procedure:
1) I added 1 network and disabled "network discovery"
2) I added the fastscan mux (12515H)
3) enabled fastscan (rescan), nothing happened
4) I opened the config file for that mux and changed "orbital": "0.0" tot "19.2E"
5) Restart tvh, now fastscan kicks in
6) Only services from 12515 are found
7) Enabled "network discovery"
8) Rescan fastscan, now all services from 19.2E are found (but tvh adds 130 muxes and starts to scan them)
9) The fastscan mux seems to be added twice now (through network discovery??), so services from 12515H are added twice as channel.
i.e. I have 2 channels named NPO1 and 2 channels named NPO2,.. etc

Btw, muxes on 28.2E in my running setup are also showing "0.0" as orbital, causing picons aren't found.

The picons issue should be resolved now - the orbital position can be set in the network settings. Also, in latest tvh the mux discovery should be fixed for fastscan.

I believe that this should work now:

1) add the network with the correct orbital position
2) add the fastscan mux
3) ... wait until muxes and services are scanned

Jaroslav Kysela wrote:

The picons issue should be resolved now - the orbital position can be set in the network settings. Also, in latest tvh the mux discovery should be fixed for fastscan.

The oribital list stays empty? it seems only working when using a predefined satellite.
Also, the orital from the network ins't copied to the newly created mux (mux shows still shows 0E while network shows 19.2E).

glenn ch wrote:

Jaroslav Kysela wrote:

The picons issue should be resolved now - the orbital position can be set in the network settings. Also, in latest tvh the mux discovery should be fixed for fastscan.

The oribital list stays empty? it seems only working when using a predefined satellite.

Updated. Thanks. I forgot to add the position list to git repo..

Also, the orital from the network ins't copied to the newly created mux (mux shows still shows 0E while network shows 19.2E).

This information is determined from the MPEG-TS feeds. The network settings has higher priority than mux settings.