OMG......
w_scan2 also needs to run on the same machine that the satellite tuners are installed on so that is not an option for me either.
Why would you even suggest that tool given everything I told you, about THREE times?
You want to send me on another wild goose chase that is never going to work for me.
wscan_cpp and dvbv5-scan ar for LOCAL DVBAPI aka tuners attached on device._
We already established several messages earlier in this thread that
w_scan_cpp could potentially be run from one machine and target the tuners on another machine. And that it is ridiculously complicated to install it.
Regardingdvbv5-scan : I mentioned in an earlier message that it needs to run on the same machine where the tuners are. You didn't need to tell me that again.
I guess I'm sounding annoyed again but I am trying to give you some feedback saen acro about the quality of the help you are giving. You should re-read a thread before giving any advice in case that was covered already or not going to be any help.
At least I finally figured out how initial scan list files work in TVHeadend.
Amongst the many things I struggled with, including my own lack of intelligence, was that even though there are THREE Astra 28.2E scan files in /usr/share/dvb/dvb-s/ only TWO were showing up in the TVH Edit Network Tab > “Pre-defined muxes” drop down. The logic for this in TVH source code has a bug I guess. I had to rename the three files..
From:
Astra-28.2E
Astra-2F-28.2E
Astra-2G-28.2E
To:
Astra-28.2E-Astra-28.2E
Astra-28.2E-2F-Astra-28.2E
Astra-28.2E-2G-Astra-28.2E
Or else only two would appear in the drop down OR none at all or only one...
Also if a file is named: "Astra-28.2E" you get "Astr" in the drop down.
That was not helping my confusion!
I also took a while to realise that to properly test I needed to first delete all my existing Muxes in the "Muxes" tab and in the Edit Network Tab I Disabled Network discovery otherwise TVH would straight away start adding new Muxes that are not in those initial scan files then I couldn't tell if the muxes listed in the Muxes tab were from the files or discovered from the satellite tuner by TVH.
I also figured out that the path: /usr/share/tvheadend/data/dvb-scan didn't seem to exist on my TVHeadend server because the .../dvb-scan directory is a simlink to /usr/share/dvb
In case anyone ever reads this thread and might find it useful I'll just write some more of my findings...
As their name suggests... "Initial scan lists" are only used by TVHeadend once. Because it creates separate (?binary) files for each Mux/Transponder that are listed in the TVH Muxes tab in a directory called "muxes" in ~/.hts/tvheadend/input/dvb/networks/ for EACH Network you defined in TVH.
The most helpful advice I got in this thread was that up-to-date "initial scan lists" are available from here:
https://git.linuxtv.org/dtv-scan-tables.git/plain/dvb-s
You just put them in /usr/share/dvb/dvb-s (in the case of satellite TP lists) and restart TVHeadend.
You might need to rename them so they show up in the TVHeadend Edit "Network" screen. Although you probably won't have this problem if your initial scan list is all in ONE file.
A quick way to backup and restore a curated list of Muxes is to copy the contents of ~/.hts/tvheadend/input/dvb/networks/[code for your network]/muxes/
In practice it's better to copy the entire ~/.hts/tvheadend directory.
E.G
Make the backup
# sudo su
# systemctl stop tvheadend
# cd ~/.hts
# tar cvfp ../tvheadend.tar tvheadend
Restore a backup
# systemctl stop tvheadend
# sudo su
# cd ~/.hts
# mv tvheadend tvheadend-backup
-- make sure the .tar backup file is in ~/tvheadend.tar
# tar xvfp ~/tvheadend.tar
This thread could be marked as solved now. If anyone has any related questions I am happy to try and answer them!
Flex
