Seite 1 von 2 12 LetzteLetzte
Ergebnis 1 bis 10 von 12
  1. #1
    Senior Mitglied
    Registriert seit
    21.10.2018
    Beiträge
    113
    Thanks (gegeben)
    3
    Thanks (bekommen)
    0
    Total Downloaded
    0
    Total Downloaded
    0
    ReceiverDanke
    Box 1:
    Dreambox DM7080HD
     
     

    IPTV #SERVICE 4097 and #SERVICE 1 syntax

    Please could someone kindly explain the syntax and usage of the IPTV bouquet file handles for #SERVICE 4097 and #SERVICE 1 in the following terms:

    #SERVICE 4097:x:x:x:x:x:x:x:x:http.......

    #SERVICE 1:x:x:x:x:x:x:x:x:x:http.....

    Thank you

    •   Alt Advertising

       

  2. #2
    Avatar von Papi2000
    Registriert seit
    20.04.2013
    Beiträge
    25.110
    Thanks (gegeben)
    4728
    Thanks (bekommen)
    9183
    Total Downloaded
    596,61 MB
    Total Downloaded
    596,61 MB
    ReceiverDanke
    Box 1:
    GB Q4K-SC / UE4K-SC / UE4K-C
     
     
    Box 2:
    GigaBlue Q-SSC / Q+-SSC
     
     
    Box 3:
    DM900uhd-SS / Vu+Duo
     
     
    Box 4:
    ZGemma H7/H9 SF8008
     
     
    Box 5:
    diverse andere . . .
     
     
    You may look there for explanation and exmples:
    Was ist beim erstellen eines File zum Einpflegen in ein Bouquet zu beachten
    Grüßle
    Ralf
    ---------------------------------------------
    Gigablue Quad4K-mixed, UE4K, Trio4K, Quad_Plus-SSC, UE_Plus-SC, X2/X3-SC, UltraUE-SC, ...
    Astra 19.2E UniCable & KabelBW, oATV/teamBlue
    (u.a.: DM900uhd,Vu+Duo,ZGemma H9Twin & H7S), PC-DVB-S/C/T, Xtreamer, BDP5200, Philips 24PFS4022/12, 65OLED855/12,UE32C5700, RPi3+
    ---- Einen Receiver kann sich jeder kaufen - Eine stabile E²-Box muß man sich verdienen! ----



  3. #3
    Senior Mitglied
    Registriert seit
    21.10.2018
    Beiträge
    113
    Thanks (gegeben)
    3
    Thanks (bekommen)
    0
    Themenstarter
    Total Downloaded
    0
    Total Downloaded
    0
    ReceiverDanke
    Box 1:
    Dreambox DM7080HD
     
     
    Thank you Ralf. Whilst that explains the first 2 digits, it does not explain the rest. Is there an explanation somewhere?

  4. #4
    Senior Mitglied Avatar von s3n0
    Registriert seit
    02.01.2017
    Ort
    Slovakia
    Beiträge
    1.477
    Thanks (gegeben)
    91
    Thanks (bekommen)
    424
    Total Downloaded
    323,0 KB
    Total Downloaded
    323,0 KB
    ReceiverDanke
    Box 1:
    Vu+ Zero 4K
     
     
    Box 2:
    Vu+ Solo SE V2
     
     
    Box 3:
    Formuer F4-TURBO
     
     
    Hello.

    It's a little more complicated. Information about Enigma is unfortunately difficult to find on the Internet and is scattered everywhere possible and in small parts . Unfortunately, there is no complete manual for a system programmer. It's an open source code, so it looks as well. You have to study it yourself. Unfortunately.

    Here's a short section of my own notes. Maybe it will help!

    For more information, you need to search for hours or even days on the Internet again.

    Code:
    ++++++++++++++++++++++++++++++
    +++ SERVICE REFERENCE CODE +++
    ++++++++++++++++++++++++++++++
    
             1 2 3   4   5  6    7   8 9 10
    ---------------------------------------
    #SERVICE 1:0:1:445C:453:1:C00000:0:0:0:
    ---------------------------------------
        order → explanation
    ---------------------------------------
        first → service type (stream source) - to select the appropriate player for this service (1 = DVB-S/T/C/IP - DVB-Mediasink decoder; 4097 = Gstreamer multimedia player; 5001,5002,5003 = ServiceApp plugin and additional players such as ffmpeg + exteplayer3; 8192 = external HDMI input; 8193 = Youtube /8xxx services do not work in every Enigma!!!!/)
       second → special purpose, normally there is always 0 ... but when there is an information line (so-called "marker") in the channel list, then the second position is 64 and the third position is the consecutive number of the information line, for example 1:64:consecutive_number:0:0:0:0:0:0:0: (the remaining portion of ServRefCode is filled with zeros in this case)
        third → type of service (or type of service with its more detailed specification)
               - 1=TV ; 2=RADIO ... in case of TV it is possible to specify a specific stream format: 16h = MPEG (SD); 19h = MPEG / H264 (HD,FHD); 1Fh = H265 (UHD,4K); etc.
    
    - some examples:
         1:0:1:...     DVB-stream:0:TV
         1:0:2:...     DVB-stream:0:RADIO
      4097:0:1:...     internet-stream:0:TV
      4097:0:2:...     internet-stream:0:RADIO
    
       fourth → Service ID (445C => "SAT.1") - the identification code of a specific channel (service)
        fifth → Transponder ID (453) - transponder number on a particular satellite
        sixth → Network ID (1) - according to specifications and standards, this item can take on different meanings ... in the case of DVB-S it is used to identify the service provider
      seventh → Namespace (00 C0 00 00)
    
            == the Namespace is a little more complicated to explain... so we will cover this item a little more extensively
    
               - the meaning of the item differs slightly depending on the DVB-S / T / C technology used
               - consists of a total of 4 bytes (8 ASCII characters as a hexadecimal value) and is divided into:
               - left part (2 bytes / 4 ASCII characters of hexadecimal value)
               - right part (2 bytes / 4 ASCII characters of hexadecimal value)
            
            == Namespace for DVB-T and DVB-C:
               
               - 2 bytes on the left (given in hexadecimal - as 4 ASCII characters):
                  - "EE EE" in hexadecimal value = identification code for DVB-T technology
                  - "FF FF" in hexadecimal value = identification code for DVB-C technology
               - 2 bytes on the right side (given in hexadecimal - as 4 ASCII characters):
                  - depending on Enigma2 configuration:
                    a) transponder frequency
                    b) zero value (in hexadecimal "00 00") - this applies in most known Enigma2 distributions as an unused value in Enigma2 distributions
            
            == Namespace for DVB-S:
               
               - 2 bytes on the left (given in hexadecimal - as 4 ASCII characters):
                  - represent the position of a satellite in space ... examples and their "recalculation" - see below
               - 2 bytes on the right side (given in hexadecimal - as 4 ASCII characters):
                  - depending on Enigma2 configuration:
                    a) transponder frequency ... where the bit on the left side of the binary numeric value, in this case means polarization (0 = H / 1 = V),
                       i.e. the 16-bit length of the entire 2-byte value is not used, but only 15 bits (1 bit is used as a so-called "sign")
                    b) zero value (in hexadecimal "00 00") - this applies in most known Enigma2 distributions as an unused value in Enigma2 distributions
            
            == examples for DVB-S "namespace":
            
                    00 82 00 00 => 0082 hex = 130 dec => 130 / 10 => 13.0 °E
                    00 A0 00 00 => 00A0 hex = 160 dec => 160 / 10 => 16.0 °E
                    00 C0 00 00 => 00C0 hex = 192 dec => 192 / 10 => 19.2 °E
                    00 EB 00 00 => 00EB hex = 235 dec => 235 / 10 => 23.5 °E
    
                ....DECIMAL POINT:
                --- in contrast to the use of the so-called "floating point" or otherwise as a data type "float", only the subtraction of the final "tithes" is used - as a decimal part of the number (in the decimal system)
                --- this means that there is always one decimal place specified, in the resulting decimal value (after conversion from hexadecimal value to decimal value)
               
                ....DETERMINATION OF AZIMUTE FROM EAST & WEST (DVB-S):
                --  if the value of the first 2 bytes is less than 1800 dec (708 hex) [or if it is equal to 1800 dec], then this value represents the azimuth in degrees from the East ... and is denoted by the sign "°E" (as East)
                --  if the value of the first 2 bytes is greater than 1800 dec (708 hex), then we calculate the azimuth by subtracting this value from the maximum number 3600 dec (E10 hex) ... and thus obtain the azimuth value in degrees from the opposite side of the world ... so we get a degree from the West, denoted by the sign "°W" (as West)
                --  the range of values 0 to 3600 (decimal value) is basically the range 0.0° to 360.0° and if we want to distinguish the azimuth to the West, then we must subtract the value from 360.0° (total 3600 decimal value)
                --  calculation examples for West azimuth (°W):
                    0E 08 00 00 =>  E10 hex (3600 dec) - E08 hex (3592 dec)  =  8 hex =  8 dec   =>    8 / 10  =>  0.8 °W
                    0D CA 00 00 =>  E10 hex (3600 dec) - DCA hex (3530 dec)  = 46 hex = 70 dec   =>   70 / 10  =>  7.0 °W
                    0D C0 00 00 =>  E10 hex (3600 dec) - DC0 hex (3520 dec)  = 50 hex = 80 dec   =>   80 / 10  =>  8.0 °W
    
    Factual note on the hexadecimal number system:
          - the zeros to the left of the hexadecimal numeric value are irrelevant and can be completely ignored
          - zeros on the left are usually used only to specify the maximum possible hexadecimal value (so-called maximum "bit length" of the variable)
    
    eight to ten 
              → 3 zeros at the end of the service reference code are currently unused by Enigma, perhaps used earlier or later. even now, as far as I know, they are using for experimental purposes (for testing) only
              - the last value of the three digits (10th position in total) when using service type 4097, has the following usage in some Enigmas: 
                0 = stream-buffer is not used
                1 = stream-buffer in RAM memory
                3 = stream-buffer in the file on the internal disk
    ---------------------------------------
    
    
    ---------------------------------------
    Another example of a service reference code from a particular Skylink provider ... on a specific satellite "Astra 23.5E" ... for a concrete channel Markiza:
    
    #SERVICE 1:0:19:13B4:C95:3:EB0000:0:0:0:
    
    - if we neglect the first three data, the other data means ...
    - 13B4 hex / 5044 dec means ServiceID - the unique number of a particular TV channel on a transponder or on a satellite (on other transponders or satellites, the same Markiza can be assigned a totally different number)
    - C95 hex / 3221 dec means TransponderID
    - value 3 represents NetworkID (I do not know what does it mean)
    - and finally the value of EB0000 hex represents the position of the satellite in the universe (EB hex => 235 dec => 23.5 E position)
    --------------------
    Example for DVB-IP (IPTV, MPEG-TS):
    Code:
    #NAME IPTV (CZ/SK/PL/DE/HU)
    #SERVICE 1:0:19:13B4:C95:3:EB0000:0:0:0:http%3a//192.168.1.1%3a4444/udp/232.48.42.17%3a4000/:Markíza HD
    #DESCRIPTION Markíza HD
    #SERVICE 1:0:19:1329:CA2:3:EB0000:0:0:0:http%3a//192.168.1.1%3a4444/udp/232.48.42.121%3a4000/:Jednotka HD
    #DESCRIPTION Jednotka HD
    #SERVICE 1:0:19:132A:CA2:3:EB0000:0:0:0:http%3a//192.168.1.1%3a4444/udp/232.48.42.122%3a4000/:Dvojka HD
    #DESCRIPTION Dvojka HD
    Using a translation Udpxy - a proxy that translates UDP to TCP protocol, because eDVBDemux (reference service number 1) can not read UDP protocol. Of course, Gstreamer (service number 4097) can also read the UDP protocol, so I would not have to use Udpxy. Unfortunately, Gstreamer (4097) for my DVB-IPTV is unreliable - there are problems with dropping sound. That's why I use eDVBDemux (reference service number 1) to watching my DVB-IP.

    The service reference code is inserted to identify and find EPGs and picons based on this service reference code (if you use EPG data and picons in Enigma from DVB-S/C/T sources and not from external sources or from DVB-IPTV source).

    Using #DESCRIPTION is not necessary. Well, this is probably the regular format for online streams in userbuquets. That's why I use it at least. It works without a tag, of course. But then the stream name is the end of the row. If you enter the #DESCRIPTION tag at the same time, this description is used solely as the stream name.

    This #DESCRIPTION is also not used for satellite channels. According to the service reference code, the satellite channel name is found in the lamedb file of Enigma.

    P.S.: IP addresses are invented and serve as an example of use.
    Geändert von s3n0 (19.09.2023 um 15:05 Uhr) Grund: added information about "namespace" field

  5. Thanks EnoSat, Joerg1909, Mr.Servo, -, cheetah and 2 others bedankten sich
  6. #5
    Senior Mitglied
    Registriert seit
    21.10.2018
    Beiträge
    113
    Thanks (gegeben)
    3
    Thanks (bekommen)
    0
    Themenstarter
    Total Downloaded
    0
    Total Downloaded
    0
    ReceiverDanke
    Box 1:
    Dreambox DM7080HD
     
     
    Hi there, sorry to bring up an old topic but could someone kindly inform me how to configure an external proxy within this file ?

  7. #6
    Senior Mitglied Avatar von s3n0
    Registriert seit
    02.01.2017
    Ort
    Slovakia
    Beiträge
    1.477
    Thanks (gegeben)
    91
    Thanks (bekommen)
    424
    Total Downloaded
    323,0 KB
    Total Downloaded
    323,0 KB
    ReceiverDanke
    Box 1:
    Vu+ Zero 4K
     
     
    Box 2:
    Vu+ Solo SE V2
     
     
    Box 3:
    Formuer F4-TURBO
     
     
    Hi.

    Do you mean UDP proxy (udpxy service) ?

    Simply change the LAN IP address of the proxy server (in my example it is 192.168.1.1) and also change the port (as needed, in my example is it port 4444).

  8. #7
    Senior Mitglied
    Registriert seit
    21.10.2018
    Beiträge
    113
    Thanks (gegeben)
    3
    Thanks (bekommen)
    0
    Themenstarter
    Total Downloaded
    0
    Total Downloaded
    0
    ReceiverDanke
    Box 1:
    Dreambox DM7080HD
     
     
    Sorry for the delay in replying, not a UDP proxy but an external HTTPS proxy

  9. #8
    Mitglied
    Registriert seit
    31.12.2015
    Beiträge
    40
    Thanks (gegeben)
    31
    Thanks (bekommen)
    9
    Total Downloaded
    0
    Total Downloaded
    0
    ReceiverDanke
    There is Streamlink for E2 with which this should be possible, use google with "billy2011 streamlink streamlinksrv".

  10. #9
    Senior Mitglied
    Registriert seit
    21.10.2018
    Beiträge
    113
    Thanks (gegeben)
    3
    Thanks (bekommen)
    0
    Themenstarter
    Total Downloaded
    0
    Total Downloaded
    0
    ReceiverDanke
    Box 1:
    Dreambox DM7080HD
     
     
    Thank you for the advice @Checker99. Is there a way of including a https proxy in a similar way to the UDP proxy syntax such as
    Code:
    https://proxy:port/https/StreamURL/path
    Or, using the example above:

    Code:
    SERVICE 1:0:19:13B4:C95:3:EB0000:0:0:0:https%3a//PROXY%3a8080/https/232.48.42.17%3a4000/:Markíza HD
    #DESCRIPTION Markíza HD
    Geändert von Willow5 (01.08.2020 um 10:51 Uhr)

  11. #10
    Mitglied
    Registriert seit
    31.12.2015
    Beiträge
    40
    Thanks (gegeben)
    31
    Thanks (bekommen)
    9
    Total Downloaded
    0
    Total Downloaded
    0
    ReceiverDanke
    No, there are proxy options (Command-Line Interface — Streamlink 1.5.0 documentation) for this, but for the usage you have to develop the appropriate basic knowledge for streamlink/streamlinksrv.


Seite 1 von 2 12 LetzteLetzte

Stichworte

Lesezeichen

Berechtigungen

  • Neue Themen erstellen: Nein
  • Themen beantworten: Nein
  • Anhänge hochladen: Nein
  • Beiträge bearbeiten: Nein
  •  
Alle Zeitangaben in WEZ +1. Es ist jetzt 13:27 Uhr.
Powered by vBulletin® Version 4.2.5 (Deutsch)
Copyright ©2024 Adduco Digital e.K. und vBulletin Solutions, Inc. Alle Rechte vorbehalten.
Resources saved on this page: MySQL 5,56%
Parts of this site powered by vBulletin Mods & Addons from DragonByte Technologies Ltd. (Details)
vBulletin Skin By: PurevB.com