Hello Guest, if you are reading this it means you have not registered yet. Please take a second, Click here to register, and in a few simple steps you will be able to enjoy our community and use our OpenViX support section.
Page 3 of 3 FirstFirst 123
Results 31 to 35 of 35

Thread: Building picons using Bash on Ubuntu on Windows

  1. #31
    abu baniaz's Avatar
    Title
    Moderator
    Join Date
    Sep 2010
    Location
    East London
    Posts
    23,541
    Thanks
    6,517
    Thanked 9,224 Times in 6,287 Posts
    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.

  2. #32
    markus625's Avatar
    Title
    ViX Beta Tester
    Join Date
    Dec 2011
    Posts
    1,104
    Thanks
    208
    Thanked 711 Times in 266 Posts
    Hi has anyone had any success getting iptv channels built

    In my movies.tv file i have for example the two line below
    #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
    The servicelist-enigma2-srp.txt picks up something like

    1_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=--------
    Looking at the 1-build-servicelist.sh you have the line below

    lamedb=$(<"$location/build-input/enigma2/lamedb")
    channelcount=$(cat "$location/build-input/enigma2/"*bouquet.* | grep -o '#SERVICE .*:0:.*:.*:.*:.*:.*:0:0:0' | sort -u | wc -l)
    Do i need to modify the #SERVICE .*:0:.*:.*:.*:.*:.*:0:0:0 ????

  3. #33
    abu baniaz's Avatar
    Title
    Moderator
    Join Date
    Sep 2010
    Location
    East London
    Posts
    23,541
    Thanks
    6,517
    Thanked 9,224 Times in 6,287 Posts
    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.

  4. #34
    markus625's Avatar
    Title
    ViX Beta Tester
    Join Date
    Dec 2011
    Posts
    1,104
    Thanks
    208
    Thanked 711 Times in 266 Posts
    Quote Originally Posted by abu baniaz View Post
    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

  5. #35
    abu baniaz's Avatar
    Title
    Moderator
    Join Date
    Sep 2010
    Location
    East London
    Posts
    23,541
    Thanks
    6,517
    Thanked 9,224 Times in 6,287 Posts
    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

  6. The Following User Says Thank You to abu baniaz For This Useful Post:

    Willo3092 (27-12-19)

Page 3 of 3 FirstFirst 123

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
This website uses cookies
We use cookies to store session information to facilitate remembering your login information, to allow you to save website preferences, to personalise content and ads, to provide social media features and to analyse our traffic. We also share information about your use of our site with our social media, advertising and analytics partners.