Yes, snp.index.
Maybe you could rename/move all picons. Run the missing picon script. Cross reference with the existing index file and only keep what was created from the missing file.
Yes, snp.index.
Maybe you could rename/move all picons. Run the missing picon script. Cross reference with the existing index file and only keep what was created from the missing file.
Hi has anyone had any success getting iptv channels built
In my movies.tv file i have for example the two line below
The servicelist-enigma2-srp.txt picks up something like#SERVICE 1:0:1:2404:7F9:2:11A0000:0:0:0: which is film4
and
#SERVICE 4097:0:1:87BE:8E4:934B:0:0:0:0:server address/user/pass/20663:SkyPremiereFHD
Looking at the 1-build-servicelist.sh you have the line below1_0_1_2404_7F9_2_11A0000_0_0_0 | | 2404_7F9_2_11A0000=filmfour
4097_0_1_87BE_8E4_934B_0_0_0_0 | | 87BE_8E4_934B_0=--------
Do i need to modify the #SERVICE .*:0:.*:.*:.*:.*:.*:0:0:0 ????lamedb=$(<"$location/build-input/enigma2/lamedb")
channelcount=$(cat "$location/build-input/enigma2/"*bouquet.* | grep -o '#SERVICE .*:0:.*:.*:.*:.*:.*:0:0:0' | sort -u | wc -l)
It uses lamedb file, not bouquet file. The matching is done by reference, so make sure you are using valid references in your IPTV.
Most people use SNP so the SRP index is not always correct. You can edit your srp.index so it has service references you are using. But better to submit corrections to the repository.
I tried deleting the lamedb file and I'm sure it went on to read the bouquet file which I modified to just refer to the movies.tv file and as I found out it picked up the text that started #SERVICE 1:0:1:
What I think I'll try tomorrow is to modify 1-build-servicelist.sh to look for the text lines that start with 4097
I have made some changes to the SRP file. It would be great if people who use the SRPicons report issues frequently and as soon as potted. It is harder to do fixes after a long time.
Code:https://github.com/picons/picons/commit/70203f640c8cd7bc8f5d653e0ba40baf1c5870aa
Willo3092 (27-12-19)