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.
Results 1 to 8 of 8

Thread: "Ignore DVB-C namespace sub network" What does it mean/do?

  1. #1

    Title
    Member
    Join Date
    Jun 2015
    Posts
    50
    Thanks
    4
    Thanked 13 Times in 9 Posts

    "Ignore DVB-C namespace sub network" What does it mean/do?

    Need some assistance figuring out what this setting does.

    And that setting has a "tooltip" saying: "On valid ONIDs, ignore frequency sub network part".

  2. #2
    EnoSat's Avatar
    Title
    Member
    Join Date
    Mar 2013
    Location
    Slovakia
    Posts
    60
    Thanks
    10
    Thanked 10 Times in 9 Posts
    Ignore namespace ON - XXXXxxxx - transponders with the same TID-NID will be overwritten last in the search (e.g. FFFF0000)
    Ignore namespace OFF - XXXXxxxx - transponders with the same TID-NID will not be overwritten but added (e.g. FFFFABCD or FFFF0123)
    (where - XXXX - position and xxxx - frequency)
    Last edited by EnoSat; 17-09-23 at 20:00.

  3. The Following 2 Users Say Thank You to EnoSat For This Useful Post:

    abu baniaz (17-09-23),el bandido (18-09-23)

  4. #3
    abu baniaz's Avatar
    Title
    Moderator
    Join Date
    Sep 2010
    Location
    East London
    Posts
    23,468
    Thanks
    6,485
    Thanked 9,206 Times in 6,276 Posts
    Question would sound better being inverted. Include instead of ignore. Avoids a double negative when advising people what to do.

  5. #4
    EnoSat's Avatar
    Title
    Member
    Join Date
    Mar 2013
    Location
    Slovakia
    Posts
    60
    Thanks
    10
    Thanked 10 Times in 9 Posts
    A small example:
    On 570 MHz, MUX1 transmits with quality parameters (MER-40dB) and on 642 MHz, MUX1 transmits with worse parameters (MER-20dB).
    With Ignore ON, after scanning, MUX1 from 570 MHz will be overwritten by MUX1 from 642 MHz (only worse will remain).
    With Ignore OFF, after scanning, MUX1 will be twice (both better and worse).

  6. #5

    Title
    Senior Member
    Join Date
    Dec 2013
    Posts
    127
    Thanks
    234
    Thanked 37 Times in 32 Posts
    I have terrestrial ATSC channels, where some channels transmit the same ONID I had to modify the lamedb file before this option was available or I would get dead services with the error message "SID not found in PAT".

    The Ignore namespace option has been available for some 6 years. interesting to see it discussed now. Here is the commit description from 2017:

    scan: do not ingore namespace subnetwork

    By default the namespace contains only part of the hash that is possible to store
    because when we are having valid ONID we are ingoring the last 2 bytes (subnetwork).

    That is happening when isValidONIDTSID is true and that exists since the initial
    import of enigma2 in git.

    In the subnetwork we are storing the frequency and polarization for sat
    and frequency for other systems and that solves all the problematic cases where
    same ONID is appeared twice, without hardcoding exceptions in isValidONIDTSID.

    Although by not ingoring the subnetwork all the service references will change
    making at least picons unusable.

    The findPicon can be optimized to ingore the subnetwork and that will be fixed
    by another.

    Ideally the namespace should not ingore the subnetwork and isValidONIDTSID
    check can go away, once there are no issues preventing to do so.

  7. #6
    Huevos's Avatar
    Title
    Administrator
    Join Date
    Jun 2010
    Location
    38.5N, 0.5W
    Posts
    13,777
    Thanks
    2,028
    Thanked 5,046 Times in 3,322 Posts
    Quote Originally Posted by Kojo_ View Post
    Need some assistance figuring out what this setting does.

    And that setting has a "tooltip" saying: "On valid ONIDs, ignore frequency sub network part".
    The simple answer is leave it set to "no" unless you understand why you are enabling it. Enabling this when not needed will cause problems.

    It is only required when two receivable multiplexes have the same identifier, which should never happen for DTH multiplexes.
    Help keep OpenViX servers online.Please donate!

  8. #7
    EnoSat's Avatar
    Title
    Member
    Join Date
    Mar 2013
    Location
    Slovakia
    Posts
    60
    Thanks
    10
    Thanked 10 Times in 9 Posts
    However, it is very common with feeds. Many transponders on one position use the same SID/TID/NID
    ROVER AtomLight STC+ , Televes H30 FLEX
    Gibertini OP100LN /85E-53W/
    WaveFrontier T90 /39E-36E-31E-28E-26E-23E-19E-16E-13E-9E-7E-5E-2E-1W-4W-30W/
    Mutant HD51 , Edision MIO+ 4K , QVIART Lunix , Ustym 4K S2 OTT , Ineos ZX4 , Dreambox 900UHD/7020HD/800se , TBS-5925 , TBS-5530 , TBS-5220

  9. #8
    Huevos's Avatar
    Title
    Administrator
    Join Date
    Jun 2010
    Location
    38.5N, 0.5W
    Posts
    13,777
    Thanks
    2,028
    Thanked 5,046 Times in 3,322 Posts
    Quote Originally Posted by EnoSat View Post
    However, it is very common with feeds. Many transponders on one position use the same SID/TID/NID
    Code:
    if onid == 0 or onid == 1 and tsid < 2 or onid >= 0xff00:
    Those are the conditions for turning on namespace automatically. In theory feeds should fall within those ranges.
    Help keep OpenViX servers online.Please donate!

  10. The Following User Says Thank You to Huevos For This Useful Post:

    EnoSat (20-09-23)

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.