[fixed] Channellist update really up to date? (3 Viewers)

high

Administrator
  • Team MediaPortal
  • August 31, 2004
    5,123
    5,530
    48
    Isselburg/NRW
    Home Country
    Germany Germany
    ini-files are updated daily from fastsatfinder and stored locally just to save them some bandwidth.
     

    findftp

    MP Donator
  • Premium Supporter
  • September 20, 2011
    184
    35
    Nootdorp
    Home Country
    Netherlands Netherlands

    high

    Administrator
  • Team MediaPortal
  • August 31, 2004
    5,123
    5,530
    48
    Isselburg/NRW
    Home Country
    Germany Germany
    Are you sure that it is still updating? Because the files have different contents.
    I'm not familiar with this stuff on mp-side but we get a special zip with formatted inis which are different from the generic ones.
    So yes, it includes the latest provided data from fastsatfinder (15.12.)
     

    findftp

    MP Donator
  • Premium Supporter
  • September 20, 2011
    184
    35
    Nootdorp
    Home Country
    Netherlands Netherlands
    Are you sure that it is still updating? Because the files have different contents.
    I'm not familiar with this stuff on mp-side but we get a special zip with formatted inis which are different from the generic ones.
    So yes, it includes the latest provided data from fastsatfinder (15.12.)
    Please compare both files I linked to, in my post earlier.
    They both contain different information and are updated december 15th
    I think the zip script is broken at fastsatfinder, because the ini files differ.
    Also, it is strange that ini files contain information from december 15th since it is already 21st.
    Maybe they update only once a week or month?

    For example, http://satellites-xml.eu/ or http://www.satbeams.com/downloads update their ini files daily!
    I already asked fastsatinder if this is right or not. I will post back with the answer
     
    Last edited:

    findftp

    MP Donator
  • Premium Supporter
  • September 20, 2011
    184
    35
    Nootdorp
    Home Country
    Netherlands Netherlands
    I checked the zip file (http://www.fastsatfinder.com/bin/Transponders.zip) which contain the ini files.
    These files are the same as the files located at http://www.fastsatfinder.com/transponders_europe.html
    But these are different than the ones located at MePo server.
    Are you sure that the download and unzip of the files is done right?

    0233.ini @ fastsatfinder says:
    [UPDATE]
    0=Dec 15, 2012
    1=4729
    2=http://www.mixesoft.com

    [SATTYPE]
    1=0233
    2=Astra 1D,3B

    [DVB]
    0=86
    1=10876,V,22000,56
    2=10891,H,22000,56
    3=11461,V,6666,78
    4=11462,H,9600,56,S2;8PSK
    5=11470,V,6111,34
    6=11472,H,4936,34,S2;QPSK
    7=11477,V,3300,78
    8=11478,H,4936,34
    9=11484,V,4937,34,S2;8PSK
    10=11488,H,7200,56,S2;8PSK
    11=11490,V,3250,34
    12=11500,H,3600,34
    13=11506,V,14400,34,S2;8PSK
    14=11519,H,6666,78
    15=11524,V,14400,34,S2;8PSK
    16=11528,H,6666,78
    17=11626,H,14400,34,S2;8PSK
    18=11639,H,6111,34,S2;8PSK
    19=11647,H,10000,34,S2;8PSK
    20=11659,H,3333,78
    21=11660,V,4937,34,S2;8PSK
    22=11666,V,4434,78
    23=11672,H,3600,34,S2;8PSK
    24=11672,V,4937,34,S2;8PSK
    25=11677,H,3656,34,S2;8PSK
    26=11678,V,4937,34,S2;8PSK
    27=11681,H,3656,34,S2;8PSK
    28=11684,V,4937,34,S2;8PSK
    29=11691,V,3333,78
    30=11720,H,28200,56,S2;8PSK
    31=11739,V,27500,23,S2;8PSK
    32=11758,H,30000,34,S2;QPSK
    33=11778,V,27500,91,S2;QPSK
    34=11798,H,27500,34,S2;8PSK
    35=11817,V,27500,56,S2;8PSK
    36=11836,H,27500,56
    37=11856,V,27500,23,S2;8PSK
    38=11876,H,27500,56
    39=11895,V,27500,56
    40=11914,H,27500,34
    41=11934,V,27500,34,S2;8PSK
    42=11973,V,27500,56
    43=12032,H,27500,91,S2;QPSK
    44=12051,V,27500,34,S2;8PSK
    45=12070,H,27500,34
    46=12110,H,27500,34,S2;8PSK
    47=12129,V,27500,23,S2;8PSK
    48=12148,H,27500,56,S2;8PSK
    49=12168,V,27500,34
    50=12188,H,27500,56,S2;QPSK
    51=12207,V,27500,56,S2;8PSK
    52=12304,H,27500,56,S2;8PSK
    53=12344,H,27500,56,S2;8PSK
    54=12363,V,30000,34,S2;QPSK
    55=12382,H,30000,89,S2;8PSK
    56=12525,H,27500,56,S2;8PSK
    57=12525,V,27500,34
    58=12550,V,4937,34,S2;8PSK
    59=12556,V,4937,34,S2;8PSK
    60=12562,V,4937,34,S2;8PSK
    61=12568,V,4937,34,S2;8PSK
    62=12572,V,3300,78
    63=12576,V,3300,78
    64=12580,V,4937,34,S2;8PSK
    65=12593,V,10000,56,S2;8PSK
    66=12605,V,9874,34,S2;8PSK
    67=12617,V,9874,34,S2;8PSK
    68=12639,V,941,12
    69=12645,H,30000,89,S2;8PSK
    70=12660,V,477,12
    71=12662,V,555,34
    72=12668,V,2400,34,S2;8PSK
    73=12671,V,2400,34,S2;8PSK
    74=12674,V,2400,34,S2;8PSK
    75=12677,V,2320,34,S2;8PSK
    76=12683,V,2320,34,S2;8PSK
    77=12685,H,30000,89,S2;8PSK
    78=12687,V,6666,78
    79=12691,V,4800,34,S2;8PSK
    80=12695,V,2320,34,S2;8PSK
    81=12698,V,2320,34,S2;8PSK
    82=12711,V,4937,34,S2;8PSK
    83=12717,V,4937,34,S2;8PSK
    84=12723,V,4937,34,S2;8PSK
    85=12725,H,30000,89,S2;8PSK
    86=12729,V,4937,34,S2;8PSK

    0233.ini @ MePo says:
    [UPDATE]
    0=Dec 15, 2012
    1=1355602468
    2=http://www.fastsatfinder.com

    [SATTYPE]
    1=0233
    2=Astra 1D,3B (23.3°E)

    [DVB]
    0=27
    1=10876,V,22000,56,DVB-S
    2=10891,H,22000,56,DVB-S
    3=11461,V,6666,78,DVB-S
    4=11470,V,6111,34,DVB-S
    5=11477,V,3300,78,DVB-S
    6=11478,H,4936,34,DVB-S
    7=11490,V,3250,34,DVB-S
    8=11500,H,3600,34,DVB-S
    9=11519,H,6666,78,DVB-S
    10=11528,H,6666,78,DVB-S
    11=11659,H,3333,78,DVB-S
    12=11666,V,4434,78,DVB-S
    13=11691,V,3333,78,DVB-S
    14=11836,H,27500,56,DVB-S
    15=11876,H,27500,56,DVB-S
    16=11895,V,27500,56,DVB-S
    17=11914,H,27500,34,DVB-S
    18=11973,V,27500,56,DVB-S
    19=12070,H,27500,34,DVB-S
    20=12168,V,27500,34,DVB-S
    21=12525,V,27500,34,DVB-S
    22=12572,V,3300,78,DVB-S
    23=12576,V,3300,78,DVB-S
    24=12639,V,941,12,DVB-S
    25=12660,V,477,12,DVB-S
    26=12662,V,555,34,DVB-S
    27=12687,V,6666,78,DVB-S

    Both "updated" december 15th, but different information.
     

    high

    Administrator
  • Team MediaPortal
  • August 31, 2004
    5,123
    5,530
    48
    Isselburg/NRW
    Home Country
    Germany Germany
    Last edited:

    findftp

    MP Donator
  • Premium Supporter
  • September 20, 2011
    184
    35
    Nootdorp
    Home Country
    Netherlands Netherlands
    When I updated the satellites.xml file (which is added to mantis), I used the combinated files as a reference.
    I cannot check if they differ from the ones you actually extract from the zip file because I cannot find that zipfile anywhere on fastsatfinders website.
    Can you post that zipfile here? I would like to check if I forget something.
    I also suggest that other people test if the satellites.xml file works for them.

    I'm curious to the reason why there was ever chosen to use seperate files for DVB-S and DVB-S2. To reduce scanning time for "DVB-S only" people?
     

    findftp

    MP Donator
  • Premium Supporter
  • September 20, 2011
    184
    35
    Nootdorp
    Home Country
    Netherlands Netherlands
    yes, they are different. Default fastsatfinders.inis contains dvb-s and dvb-s2, we get them both seperated in 2 files
    check
    http://install.team-mediaportal.com/tvsetup/DVBS/0233.ini &
    http://install.team-mediaportal.com/tvsetup/DVBS/0233-S2.ini (or ad -S2 to any other ID)
    tvsetup creates one xml out of that informations but that really should be answered by anyone else, I'm just the server-guy ;)

    Thank you for the private message containing the zip file.
    I noticed something which could make life a lot easier and prevent future problems with expired satellite positions.
    The zipfile you send me also contains a satellite.xml file linking to all relevant ini files.
    It is almost the same as my manual made xml file which was added to mantis.
    I would like to sugggest to use this file as a reference for the tvserver "satellites.xml" file. The only thing which should be replaced is "http://fastsatfinder.com/bin/mp/" with "http://install.team-mediaportal.com/tvsetup/DVBS/" and then you're almost sure that you never have any outdated satellite positions anymore.

    To prevent future problems with moved or abandoned satellites, you should not only update the ini files, but also the satellite.xml by the tvserver!
    By doing this, you're *always* sure that latest fastsatfinder info is being used. Now, if fastsatfinder decides to point Astra 3B @ 23,5E to 0235.ini again, everyone would still use the 0233.ini file because they have the old satellites.xml file. I think that in current release it would implicate that when people update the satellites.xml through tv-server, they have to restart the tv-server configuration application to actually use it (because then the xml file is being read, I think)

    For now, I did the find and replace thing and attached the new satellites.xml file to this post.
    The previous one I did almost manually, don't ask how. In that file I also replaced a lot of other characters till I finally figured that I had to use UTF-8 encoding to prevent error messages by tv-server. :)
    Please use this xml file in mantis, it's better. (but other people should also test it)
     

    Attachments

    • satellites.xml
      16.2 KB
    Last edited:

    flokel

    Portal Developer
  • Premium Supporter
  • October 11, 2005
    1,601
    168
    Unterfranken
    Home Country
    Germany Germany
    Looking at the code I can confirm that only the single satellite files are updated and not satellites.xml itself.
    So for a 1.3.1/1.4.0 release we should rework this area to update satellites.xml as well.
    I've created a mantis entry for this.

    For 1.3.0 RC we should include the updated satelittes.xml + the updated .ini files
    so that the user does not necessarily has to start the update process.
     

    Sebastiii

    Development Group
  • Team MediaPortal
  • November 12, 2007
    16,583
    10,403
    France
    Home Country
    France France
    Looking at the code I can confirm that only the single satellite files are updated and not satellites.xml itself.
    So for a 1.3.1/1.4.0 release we should rework this area to update satellites.xml as well.
    I've created a mantis entry for this.

    For 1.3.0 RC we should include the updated satelittes.xml + the updated .ini files
    so that the user does not necessarily has to start the update process.

    I have created a branch : Created a branch for it :
    https://github.com/MediaPortal/MediaPortal-1/commits/EXP-4130-Rework_the_update_process_for_satellite_files

    Now setuptv always take latest satellite.xml and update to latest .ini converted to .xml from setuptv :p

    I have tested it locally seems to be working correctly :p
     
    Last edited:

    Users who are viewing this thread

    Top Bottom